Hi everyone,
So with v1.20 the Pixel 7a (lynx) is now supported, thanks a lot to the team !
However, I had some difficulties to achieve the installation, since the e-recovery image provided doesn’t work (and Lineage recovery does but won’t install /e/OS), and the additionnal partition files are missing…
I would have suggested improvements in documentation but the topic doesn’t exists yet in the wiki section (@Manoj ?)
So if someone wants to install 1.20 on a Pixel 7a (lynx) device, I managed to do it by downloading the /e/OS 1.20 zip file provided in the installation instructions, then use the payload-dumper-go tool (see here) to extract from the the zip file all the .img files needed to flash the various partitions AND the recovery.
Using those files in the same way as described in the install proc finally worked !
Now, the phones seems to work great, even tho I haven’t used it for long at the moment.
Thanks again !
And one final question, I see that it is possible to relock the bootloader for Pixel 7 and Pixel 7 Pro, but I can’t manage to find a solution to do it on the Pixel 7a. Does someone know if it could be possible ?
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Previous Version of /e/OS: 1.19.1-s
Rooted: False
Working fine apart from now having a persistent ‘cloud storage full’ notification meaning i cant sync things despite only using 656.8 MB of 1GB storage.
I have the same ecloud problem. Yesterday the ecloud was supposedly empty, today it says it is too full and I get warning notifications. I only have 500MB used though. Surely a more general issue. @Manoj do you have any information about it by chance?
Hi dexic, i suggest having a look at the akku usage page in settings to check if an app uses unusual amounts of battery.
For my FP4 I noticed that advanced privacy consumes some more than before v1.20 but its still tolerable to me.
HTH
Only glich I noticed is gps sometimes can’t find exact location on magic maps, organic maps and google maps also. I believe this phone’s gps module not so convinient even in stock software. Other than this:
I updated the latest software with February Security Update then did clean /e OS install. Everything is working fine, I don’t even encounter lineageos problems mentioned on xda. Works perfectly, no fast battery drain, no heatup. I get 1.5-2 days battery. Speed is fine.
Referring to the ROM download page of this device https://images.ecloud.global/dev/lisa/ e-1.20-t is published but it will be a manual upgrade to Android 13 (T).
• Vendor Name : Motorola
• Device name : moto g32
• Device CodeName : Devon
• Version of /e/OS or Stock which existed previously : Stock
• Is the device Rooted / Not rooted : Not
As a first time user of /e/OS I had some trouble with the the install. After successfully unlocking and installing the recovery-image I could not flash the main part of the software with the ADB command line options. My solution, to put the zip file on a SD card and boot in the recovery → Apply update → Choose from disk. This did the trick for me.
To avoid confusion, it is advantageous to always specify the code name Xiaomi Mi 11 Lite 5G “renoir” of the device used.
Updates and upgrades are often confused with each other. The differences are:
An “update” is an update of the existing version /e/OS-R. An “upgrade” is an update to a higher operating system version: /e/OS-T.
The /e/OS updater app does not support “upgrades” from one version of /e/OS to another, and will block installation to any update for a different version.
Technically it does, but such “OTA upgrades” will have to be meticulously prepared with a lot of development and testing effort for an individual device for an individual upgrade step.
This has been done in the past, and efforts are ongoing. Anybody interested can follow proceedings in the weekly development and testing updates … https://community.e.foundation/tag/development-updates … section currently named “OS OTA Related information”.
But … the default is indeed manual upgrading when an upgrade of the underlying Android version is needed.
Yes, this info is included in the “OS OTA Related information” currently. And it isn’t any different on stable when an OTA upgrade is not prepared for the individual device for the individual upgrade step at hand.
Doesn’t take away from the fact that the updater App can do this in general.
Edit: The feature was introduced in week 6, 2022 with an OTA upgrade for Samsung S9/S9+ … Week 06, 2022 : Development and Testing Updates
OTA upgrades mean a comfortable user experience for e-users and usually a loss-free (personal data, apps) transition to the next /e/OS generation. The sooner it is available for all devices, the better.
By the way @AnotherElk my messages did not refer to Xiaomi 11 Lite 5G NE / 11 Lite NE 5G / Mi 11 LE “lisa” nor Samsung S9/S9+ but to @moeppie’s request Xiaomi Mi 11 Lite 5G “renoir”