The current build has issues with the browser, and the App Lounge is finicky, but Aurora and Firefox work just fine, and everything else appears to be stable so far.
One of my clients at work had a cyberattack this week, so I’ve been a bit preoccupied =). I haven’t had much time to do more testing, but I am looking forward to it. I stand on my earlier statement that I can work around the browser and App Lounge issues, but I was sincerely curious if there was an upcoming build in the pipeline, which would resolve either of those issues, so I know whether to pursue the cutover accordingly, or wait another few weeks.
I flashed it last night. The browser is fixed, and the issue which was causing the Duck Duck Go browser to crash-on-load as well, is also fixed.
The App Lounge is still subject to the anonymous issue affecting everyone, but it loads, and I was able to successfully install an OSS app with it as well.
So, I plan to do a bit more testing with a SIM card and Magisk/Root it, and if everything is solid, I’m looking forward to finally being able to use my NP2 =).
Thank you again, so so much, for all of your time and effort.
So, @ronnz98 , I’m running into a bit of a pickle, and I’m hoping you can weigh in…
I can’t seem to upgrade the App Lounge to version 2.10; I get this error when I do an adb install: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package foundation.e.apps signatures do not match newer version; ignoring!] . I tried doing an on-device install and got a variant of this error, and App Lounge doesn’t auto-update, either.
Is this something that requires a rebuild with the new store, or is there some CLI voodoo that can force the install?