Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
taiHENkaku B8 Release Notes

大変革 Beta 8

"When is the actual release?!? Why is this still beta?" Good question. Here's a secret: I have been constantly pushing small updates every couple of days without changing the beta number. Think of these release notes as status reports rather then, well, release notes. The idea of beta.henkaku.xyz is that since molecule has very limited resources, we cannot test all the different configurations, homebrews, and use cases. However, when I push an update to the beta site, I know that if something breaks I would get notified through Twitter, reddit, IRC, etc (although the perferred way of reporting bugs has always been the issue tracker). So if you don't notice any problems, that's good! It means I was able to fix any major issues before you woke up. These problems are usually very surface level (a misconfiguration/typo on my part) and the underlying code has a lot less bugs than HENkaku R6. So do I recommend everyone use beta.henkaku.xyz? Yes. I usually fix problems reported within the hour (seriously, how much am I getting paid for this?) and you get all the extra features I've added in the last couple of months. All that is to say that this might be the penultimate progress report. After all, the Settings string doesn't have room for two digit beta numbers :)

Please make sure you are using the latest toolchain from (https://vitasdk.org). We made a lot of changes so using an older toolchain to add taiHEN hooks will result in crashes! Also make sure to update your taiHEN development libraries to the latest version.

New Features

  • molecularShell updated to display if you are currently in "unsafe" mode or not. Shows all devices in unsafe mode again.
  • Some taiHEN API updates for developers
  • Compability for a future VitaShell update

Issues

Please report any issues you find to the issue tracker. Please incluse a screenshot/picture of the problem and any error codes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment