The Pixel 4 sunfish a16 build has been rolled back. As the team detected it was not booting post installation.
FP6 official has not been rolled out as yet. Should be later today.
Any other builds failing after v4.3 update.
Did the update to 4.3 yesterday evening, but used the community build.
https://images.ecloud.global/community/FP6/IMG-e-4.3-a16-20260919677978-community-FP6.zip
Used the installer documentation, which was very clear.
The installation worked, with 2 minor flaws, which were that i could not install the e-sim that my provider (odido) sent me. The link should get me to the right spot where i should copy and paste the code, but it only copied the code and got me nowhere. (so i cannot call right now) I’m going to the shop in a few hours to get a physical sim.
The other issue is that i have no security on the phone. The finger button on the right side is not working when i touch it. (it did not ask for a finger scan also) I really have to press is. Then i also cannot install a code or anything else to secure it for unlocking.
Could it be that when i try to install the official build tonight when i’m home again, that the security thing should work again?
Vendor: Fairphone
Device name: Fairphone 6
Checked with the build team:
Yes, it’s expected fairphone vendor is still on A14 even on A16. We match what FairphoneOS ships on their end. With a GRF (Google Requirements Freeze) and GKI (Generic Kernel Image), it’s normal for the android 14 branch to be used.
Once we get the updated GRFs we add that to our build, post the testing and development.
What’s the best way to monitor when it will be rolled out for the installer? Excited to get started. Thanks!
How could You provide update for Fairphone 4 knowing that voice in the apps sounds like from Alvin and the Squirrels movie? This is a joke. People reported it in alpha, in beta, You did not patch it and released the update anyway. Not Everyone has time to read through the forum daily.
If You dont patch it ASAP, I switch to Iode OS, Graphene OS, Sailfish from Jolla, Volla OS from Volla, AphyOS from Punkt or any other custom ROM in the world first day my Fairphone warranty expires (I dont have time to backup data and do switch now Im going to buy new device anyway cause I dont like Fairphone being too big and heavy). One month is much too much of a time to wait for it. I give You two weeks to regain my trust.
“The patch was missed in A16, it will be fixed in /e/OS 4.4”
- V. 4.3 should not even come to FP4 without that fixed. Voice calling is too important function for the smartphones to have it like that.
- Even if released, there should be warning in Settings → Updates on the phone itself, not only on GitHub or Community Forum
- Even if released and without warning, patch should be made ASAP as v. 4.3.1, not 4.4. Many much less important things were patched in x.y.1 patches in the history of /e/ OS (on many smartphones, not only FP4).
Well done, but just not to intimidate or confuse others reading along … The install instructions contain a link to the download page with the IMG install files (/e/OS official FP6 download), they don’t reference OTA update files or OTA download pages.
So, just following the instructions should be straightforward.
if the audio problem on fp4 is solved with official (others?):
is it possible to go from community to official without loosing data? if yes: how? afterwards on could lock the bootloader, too, right?
I agree. The issue was opened long before the final release.
For Pixel 4 sunfish users stuck on the Google Splash screen after the v4.3 update
-
Reboot your phone into fastboot mode:
- Power off the phone, then hold Power + Volume Down until the bootloader screen appears, or
- If ADB is reachable: adb reboot bootloader
-
Connect via USB and confirm the device is detected:
fastboot devices -
Switch back to the previous, working slot:
fastboot --set-active=a -
Reboot:
fastboot reboot
Your phone should boot normally back into your previous working /e/OS install.
- Do not accept the OTA update again until this is fixed upstream. We will let you know on this forum when it is fixed upstream.
More info / install guide: Info about Google - Pixel 4a - sunfish | /e/OS documentation
I totally agree too.
Fairphone 4
4.3-a16-20260917677552-official-FP4
Previous 4.2 A14
Phone does not ring when receiving a call. It used to ring in my hearing aids, but now it just vibrates (the ring tone sounds for a fraction of a second after a while but not in the hearing aids). I used to be able to hear calls in Signal or WhatsApp in the hearing aids - both ringing and conversation, but now no sound.
Update went smooth, no major problems discovered so far.
Minor problems (this list may get additional entries if I find more):
ntfy is unable to connect to push.murena.com because of channelpush.murena.com/eOS-OnePlus6-4_3-de. When I delete it, a connection can be established. cc @Manoj- The problem is only temporary, see message Feedback for v4.3 - #102 by Tentos.
Same here. In the settings screen is says “e/os v4.3 - update available”, but when I go to the update screen it says “no updates found”.
What an ultimatum! ![]()
Ha ha… they work like IT in some banks! ![]()
Downloading now. thanks for making it available. Will share feedback.
Volla Tablet
Mimir
Murena
E-os 4.2 a14 official
Update to 4.3 fails. After downloading and update an Installation error shows up. I retried and cleared updater cache, but same error.
Edit: After a restart, deleting updater cache again and removing charger, the update installed smoothly.