Hi there,
I’m currently using e/os 3.0.4-t-community on a Pixel 4a sunfish. The current last OTA update was on july.
How can i switch smoothly to the 3.0.4-a14 or a-15 version ?
Is this method still ok ?
Thanks,
yes, “Apply update” will prompt you to adb sideload the zip.
As to smoothly - probably, but always have solid backups.
My Google Pixel 4a is running /e/OS 3.0.4 A13. I would like to upgrade to A15 and /e/OS 3.1.1. Is it absolutely necessary to update via command line? Isn’t an update directly from the smartphone planned (I’m willing to wait)?
Sorry for my question. I just realized that I could put the update on my smartphone and use the update module to install it locally.
1 Like
Thanks you very much, I will try this !
Yes, backups are always needed !
Correct that also works. It is still looked as a not proper update same as adb sideload, as far as I know but it worked for me flawlessly with 4a and 5 also. As mentioned before, have a backup for the exception
1 Like
I’m currently running GrapheneOS on a sunfish but it is now EOL so I’m thinking about installing /e/os instead. Does /e/os work properly on a sunfish?
I ask because in the Smartphone Selector compatibility list it is marked as Community rather than Official. But then when I click on the Community install doc link I see “Known issue(s) 0”.
So, the device has Safetynet: Yes, Rootbeer: Yes and 0 Known issues. Does that mean it works?!! (Auxilliary question: if yes, it does work, why then isn’t it marked as Official?)
Obviously I’m new to all of this! Any guidance gratefully accepted.
Thanks
Hello @johnericsutton, Welcome to the /e/ users forum.
“Official” builds are for models that are or were solded by the Murena Corporation. it is an ambigus naming.
“Community” builds are for all devices officially supported by the /e/ foundation (from “official” LineageOS list). it is an ambigus naming.
“Unofficial” builds are for devices not officially supported by /e/ but by users from the community (ha, ha,)
generaly builded from sources coming from unofficial LineageOS builds published on XDAforums
1 Like
Thanks for that @piero. So the distinction between Official and Community is largely irrelevant from a user’s perspective. And the Yes/Yes/0 for Safetynet/Rootbeer/KnownIssues for a particular device is the more important information, I surmise…
Still, it would be nice to hear from a real world sunfish user that it fully works! I’m loathe to trash my existing OS for something that works, except for x, y and z… I can cope with some deficiencies/challenges in my (Ubuntu) laptop experience but I find smartphones quite difficult and irksome things to live with even when they work properly!
not at all,
- “Official” builds update release is some days delayed so changes are tested by the “community” build users
- “Official” builds users benefits to OTA upgrade to major android version (here release could be some months delayed)
- “Official” builds can have their bootloader relocked
so, the forum’s search feature is you friend…
I used sunfish until I switched to redfin (Pixel 5) about 1.5 years ago. Everything worked. I have it still lying around as a test device for the test channel of /e/OS. There is also @obacht if I remember correctly who has a sunfish.
I can not recall that anything didn’t work (other than banking apps which need ‘official’ build or locked bootloader).
Let me know if you want to know something particular.
me neither, only that I do not do banking via phone anyways and I cannot say whether my use case is similar to others … so it´d be easier to answer more specific questions on specific apps.
I’d say so, yes!
1 Like