thanks for the link, even if it is quite old it is working and the file is downlodable.
Yeah, as you pointed, the launcher is an old version, recalling me the old pixel launcher.
But it is doing its job and it has also nice features.
If someone is looking for a working alternative to bliss, able to run even on e os t and lower version, i recommend to give it a chance.
Vendor: Fairphone
Device: Fairphone 3+
Device codename: FP3+
Previous version: 1.21
Device is not rooted
The update went smoothly, and I can’t see any major problems. The only thing I’ve noticed is that the wallpaper thumbnails in the settings don’t seem to match the actual (new) wallpapers in many cases. Could this be a cache-related issue or something similar?
When I press “Apply update” (in Paramètres > Mises à jour du système) every phase seems to be fine : download, preparation, finalisation of the package installation…
But 10-15 min later, when I press “Restart”, at the reboot, after the Google logo, I have this screen “FastBoot Mode”, and I can select few options : Start, PowerOff, BarCode, Rescue Mode, Recovery Mode, Restart bootloader. And when I choose start, my phone boots and… I’m still on version 1.21
Tried it five or six times now.
Playing android becoming hard, freetime runs damn fast, lol.
Almost forgetting about lawnchair.
But, searching, found they uploaded on git their last nightly, v14.
A 34mb launcher, wow, but will also try it.
Only then will make my decision.
don’ t waste your time anymore trying to apply ota.
Ota could fail, it happens.
I recommend you to manual update your device via adb sideload the zip package.
In my case, i don’ t have e recovery, i use twrp.
My updater app wasn’ t displaying the v2 update as available even if it was already there.
Once hardly downloaded it, it took a long time this time, i manually, as always, flashed it.
A new version is good, and I will applaud /e/OS for still building for FP2, but when it comes to security you gain next to nothing in terms of life span anymore this way, FP2 will be stuck on this level because Android 11 (R) doesn’t get security updates anymore and FP2 can’t be upgraded to Android 12 (S) or further for technical reasons.
So, if 2.0 for the FP2 did not receive any security updates and apparently also no (functional) updates of apps (like QR code scanning in the Camera app mentioned in the 2.0 release notes for Android R), what has actually changed with respect to 1.21?
Ingolf
PS: I do not intend to criticize the maintainers of the port. On the contrary – I am very grateful that they kept my FP2 alive for such a long time.
Vendor Name Motorola
Device name G7
Device CodeName River
Version of /e/OS or Stock which existed previously 1.21-t-20240325389105-dev
Is the device Rooted / Not rooted Rooted
Attempted to update via OTA but I keep getting a black screen on reboot. Attempted 3 times.
I then adb sideloaded the V2.0 build for Motorola River and got a black screen. I then pressed the power button and v1.21.-t-20240325389105 was still installed.
Unexpected, but perhaps purely co-incidental observation:
All of a sudden my FP3+ now handles my – previously problematic – SanDisk USB drive (it has both a USB-C and a USB-A plug) much more easily and without issues. Recognizes the drive much more reliably and without complaints.
Yeah, careful though with that version, because if you have repo on f-droid, it gets updated to old version (downgraded) accidently unless you ignore update for it.