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?
After a week of using it, I can confidently say that this is the best release of /e/OS for this phone, everā¦
the auto-brightness function FINALLY works wellā¦had this issue on my OnePlus 8T for the longest; auto-bright would randomly max out at night, just the worst, so I dealt with it manually. /e/OS 2.6 has finally gotten auto-bright working properly, huzzah!
In 2.5, Nova Launcher would randomly crash, so I had to work around it by going to settings from the window-shade and force stopping the app. I wasnāt really in a place to report it, since it was a third party applicationā¦but this hasnāt happened since the 2.6 upgrade!
Seriously thrilled with this release!! Thank you, @ronnz98 !!!
Thank you very much for your input, itās great, Iām looking forward to try it on my Nothing Phone 2, but I have a question, is the Glyph working properly? I guess it is necessary to install the āNothing Launcherā for it.
Thank you very much, once again, for your contribution.
I can tell you that the glyph gives charging and volume status, and it does its flashy thing when calls come in. The music visualizer works as well as it does on NothingOS (i.e. ānot at all synced to music, but a light show takes placeā).
I havenāt seen it work for incoming text notifications, but I havenāt tried configuring it for the task, either. Also, while I have custom ringtones that have custom glyph patterns, I havenāt attempted to use them. Similarly, the Glyph Composer doesnāt work at all. Iād love to try Simone, but the App Lounge is still in a āworks-when-it-wants-toā state, and while Aurora Store generally fills the void just fine, in this particular case, it doesnāt seem to think the app is compatible. I donāt have Uber or the other third party apps which integrate.
Soā¦whether that constitutes āworking properlyā or not, depends on what functionality youāre looking for, exactly.
I love waking up on a Monday and seeing a new Ronnie build! Not sure if Iāll be installing it this week, but looking forward to it! Thank you, as always!
Thanks for these builds !
is the updates OTA are available once this build installed, or should we have to reinstall the system after each new release ?
Iāve had pretty good success dirty flashing them; aside from the 1.9>2.x install, everything has just-worked. Iāve also had good success using the system updater and picking the download.
Ronnz does the Lordās work in making the NP2 super easy to use /e/OS on.
Iām not sure to understand : after the main /e/OS-U installation ROM, can you keep update your phone regulary without reinstall everything ?
I have for now a Fairphone3 with /e/ and the updates are done on the air (OTA) nearly every 2 month, and itās work like a charm, with all my stuff on my phone.
I planned to buy a NP2 and Iām a little bit anoyed to be googlesized, but Iām too lazy to reinstall all my stuff after manual upgrade of /e/ if it doesnāt did it smoothly.
Yes; please forgive the technical jargon. A āclean flashā is when a user backs up their data, erases everything on the phone, and installs a ROM with a factory reset. A ādirty flashā is when a ROM is installed without erasing everything on the phone first. In my personal experience, Iāve been able to install new versions of /e/OS over the old ones without an issue.
Phones with ācommunityā builds, that are maintained by /e/OS directly, tend to get OTA updates that just-install. My OnePlus 8T is such a phone, and OTA updates show up when theyāre ready. Since the NP2 has an āunofficialā installer, handled by Ronnie directly, updates need to be installed manually.
In my experience, this works just fine directly on the phone. Simply download the ROM from a browser, then go to Settings > System Updates > 3-dot Menu > Local Updates, and go to the downloaded ZIP file in the Downloads folder. From there, itāll do the in-place update without erasing anything or using a computer / recovery / CLI tools.
The NP2 probably has the best Googled ROM of any phone Iāve used - everything I need, nothing I donāt, and its additions are genuine improvements to the system. Iād recommend it to anyone who is entrenched in the Google ecosystem, but if that were really fine with me, I wouldnāt be on the /e/OS community =).
The number of builds Ronnie maintains directly is probably in excess of the number of builds the /e/ Foundation supports directly. While it makes it possible for you and me to enjoy both /e/OS and our swanky glyphs, the drawback is a few extra steps in performing the updates when new builds are released. Iām fine with this, personally, because updating involves a new round of rooting with Magisk, but I can understand the absence of the OTA updates being a tradeoff, especially coming from an officially supported build.