I don't compile stuff. But if the release works and the nightlies work but when you compiled it it didn't work, you did something wrong.
Seems like we are on the same way. I tried to compile the latest commit and test, from the commit of adding screeninit, it crashes always. Just compile any commit before screeninit, and it works.No compilation errors (with either r46 or r47).
It just gives me a crash dump when I try to execute it.
You are right, thnxSeems like we are on the same way. I tried to compile the latest commit and test, from the commit of adding screeninit, it crashes always. Just compile any commit before screeninit, and it works.
If it was a compilation error, he wouldn't be getting a crash dump, because the build process wouldn't generate the output binaries.If you're getting errors, it must be a compilation error.
It fixed after I updated A9LHt to B9S.Now, SysNAND/EmuNAND TWLN and TWLP are worked correctly.I'm sorry for confusing you.Yes, both are created by GM9, but the one on the SD card is only a backup (of a backup, I know ).
That should not be possible. Is there anything special with that console? What is the entrypoint? Do you have an EmuNAND? Can you confirm it still worked in 1.2.1?
--------------------- MERGED ---------------------------
Not yet. I'll add that in the next version, though.
The input command is in the newest release.@d0k3 are there commands in the scripting language that allow for users to input strings of characters (like, for example, so the user can decide what to rename something), or that allows the user to choose one option from a list? Sorry if the answer is in the HelloScript file, I looked through it and couldn't find it.
I may look into it later, for now it's not a priority. Maybe some other dev wants to look into it in the meantime.Would it be possible to have GodMode9 access the NAND chip on the Ak2i? To sum up the reason behind this question, I am just going to post my quote from my thread
I'm currently doing some heavy modifications, and it is actually possible that there is strange behaviour on a small number of systems. To be up to date, compile from the xfirm branch for now.@d0k3
Hello, I'm getting crash dumps on your nightlies (tried 8e8df94 then e4a0d62). No compilation errors.
Your official GodMode9-20170711-185700.c60237a (v1.2.7) release works though.
Any ideas?
Thanx
Thank you for posting that bug report! I already fixed it in the latest release (v1.2.8), and, yes, for A9LH, too.It fixed after I updated A9LHt to B9S.Now, SysNAND/EmuNAND TWLN and TWLP are worked correctly.I'm sorry for confusing you.
Thanx for the info.I'm currently doing some heavy modifications, and it is actually possible that there is strange behaviour on a small number of systems. To be up to date, compile from the xfirm branch for now.
I was wondering if there anyway to disable to button combination for launching FIRM files? This is the kind feature I actually could see myself using, but the button combination just seems like a bit much.For everyone who hasn't seen it yet, there's a new release of GodMode9 v1.3.0. This adds RTC clock support and FIRM chainloading.
I'll think about a way to make this more comfortable for trusted payloads, alright?I was wondering if there anyway to disable to button combination for launching FIRM files? This is the kind feature I actually could see myself using, but the button combination just seems like a bit much.
Sounds cool to me!I'll think about a way to make this more comfortable for trusted payloads, alright?
You could have found out by just using the arrow keys. Yup, your assumption is correct.How is the RTC setter formatted? Day/month/year?