Remember the last blog where I said I hate setting ETAs? There's a reason.
ISSUE #1
--------------------------------------------------------
We tried AROMA and found that our touchscreen is incompatible. With no volume buttons, there's no way to use AROMA without rewriting many parts of it. We searched for another solution, and found it in shell code.
Since then, we have tried multiple different methods of creating an installer. It's been a struggle, but we've got a hold on it somewhat. A big issue is that TWRP does not return syntax error code. Is there a way to find it? I dunno, but I'm not wasting the time trying to find it right this second.
We've got a list of options that we can try,
1. New script that takes over update-binary could work, but needs fixing up to be more in line with proper shell syntax again (ShellCheck fucked some stuff) [currently on my local machine]
2. Old updater-script which appears to have syntax errors [currently on nfc branch]
3. The current update-binary shell script, the one that extracts to /data, also has syntax errors [currently on nfc-newbinary]
To end users, that probably looks like a lot of gobbledy-gook, but all you need to know is, our code is fucked and we have multiple ways of approaching it. Option 2 is ideal because it will allow for more compressed images, saving space.
----------------------------------------------------------
ISSUE #2
----------------------------------------------------------
In order for Option #2 to work, we need a .new.dat file. In order to get that, we need a "sparse image". In order to get THAT, we need to provide the build process with a file that tells it which directories get which permissions. Perfect, we can extract it from official builds.
Except... when we give it to the image making program, it throws an error telling us it's missing one specific permission. But AOSP says that permission isn't needed, it's inherited through another permission.
We don't know why this program asks for this permission. We might just write the permission a second time and see if that fixes it.
------------------------------------------------------------
And that's just what we have right now. After that, we have to make sure the system boots correctly. Then we have to implement a method to enable NFC, preferably through the launcher and system settings. We'll have beta testers check everything over.
Once that's all done... we'll finally be at our first milestone, and we can release to end users.
------------------------------------------------------------------------------------------------
Come check out our website and join our Discord.
Comments
Post a Comment