Well, I know I very breifly touched on this before, but I had a couple ideas since then.
The built-in Finance App is basically useless. HOWEVER, it cannot be deleted. Off the top of my head, I dont remember how much space it takes up, but we might be able to make use of it?
Using a DoorsCSE routine, would it be possible to somehow overwrite the Finance app with DoorsCSE and hook it to be run as if it was the built-in app?
That would prevent Doors from being wiped out on RAM reset, and even full RAM/ARCHIVE reset.
From there, IF thats even possible, could a routine be made to prevent certain variables from being deleted? Maybe flag them as non-existent, or already deleted (so long as garbage collect doesnt clobber it)?
Im an Android programmer, so the hardware/memory/assembler side of calculators is a little over my head. Thats why Im asking here.
And of course, if someone wants to go back to plain firmware, then can always flash back an OEM copy of the system software, and everything will be overwritten. Back to stock.
The built-in Finance App is basically useless. HOWEVER, it cannot be deleted. Off the top of my head, I dont remember how much space it takes up, but we might be able to make use of it?
Using a DoorsCSE routine, would it be possible to somehow overwrite the Finance app with DoorsCSE and hook it to be run as if it was the built-in app?
That would prevent Doors from being wiped out on RAM reset, and even full RAM/ARCHIVE reset.
From there, IF thats even possible, could a routine be made to prevent certain variables from being deleted? Maybe flag them as non-existent, or already deleted (so long as garbage collect doesnt clobber it)?
Im an Android programmer, so the hardware/memory/assembler side of calculators is a little over my head. Thats why Im asking here.
And of course, if someone wants to go back to plain firmware, then can always flash back an OEM copy of the system software, and everything will be overwritten. Back to stock.