Feedback for v4.3

/e/OS Smartphone Operating System Build Feedback
1

Release information

Please share feedback on the v4.3 build for your device, and let us know how it works with the apps you use.

What is a staggered release?

All /e/OS releases are staggered. During the release window, a small set of devices is published each day.

This is because we support 250+ devices. Releasing every build at once would overload the servers with thousands (or millions) of simultaneous downloads.

Official builds are usually published toward the end of the release process. The full process typically takes 7–10 days.

Feedback poll

We will also run a poll so you can rate this build.

  • I have updated to v4.3 on my device and it is working well
  • I updated to v4.3 but I am having issues (please share details in this thread)
  • I am not able to update to v4.3 (please share details in this thread)
0 voters

To report issues with the build or with apps, open an issue on GitLab. Ideally, discuss the problem here first and check whether other users of the same device on this build are seeing the same thing.

When sharing feedback or issues, please include:

  • Vendor name
  • Device name
  • Device codename
  • Previous version of /e/OS or stock ROM
  • Whether the device is rooted or not

Use this table for vendor and codename details.
Use this guide to include more complete version information.

:warning: Do not share test-build information on the forum or in this thread

This thread is only for official and community /e/OS builds.

To understand the difference between build types, see this guide.

Please do not post information or links to /e/OS test builds here. Those builds are untested, still in development, and can in some cases soft-brick a device. Sharing them also confuses users who do not see those builds in the updater.

Not everyone on this forum is experienced with custom ROMs. Trying a test build can seriously damage a device.

If you want to help with testing and already know how to recover from common custom-ROM issues, you are welcome to join the testing team. Testers can share comments on the dedicated testing Telegram channel.

6 Likes
Week 39. Development and Testing Updates
The call icon keeps getting crossed out
Week 39. Development and Testing Updates
Pixel 4a Update to v4.3 stuck at google logo
2

Pixel 4a
sunfish
before: 4.2-a16-20260814662908-community-sunfish
still: 4.2-a16-20260814662908-community-sunfish
not rooted

update not possible:

  • Accepting restart/new start whilst (after?) OTA-update in system updater leads to eternity in G-screen without progress (waited up to 30 min)
  • long pressing combo of power button and volume controls eventually brings up a menu (red fonts) that allows “Power off” and after a few attempts it will eventually restart into previous version (4.2)
  • managed to do/ tried that twice, now will stay on 4.2 for the time being…
1 Like
3

I would like to update my fairphone 6+, but I’m getting the error message (below) on the web installer. In troubleshooting it looks like I have to wait for 4.3 to meet the security patch level already on the phone.

Your phone’s Android Security Patch Level is newer than what this /e/OS build supports. Due to anti-rollback protection, installing it now could leave your device stuck in bootloader mode, unable to start. Please wait for the next monthly /e/OS release, which ships with an updated security patch, before trying again.

Device security patch (20260805) is newer than this build supports (20260801)
4

Hi,

that is like this as long as i know e/os. They never adjusted their built date to the Fairphone ones.

  • You need to wait for the next E/OS release
  • Make sure, that you do NOT install the next security update from FairPhone, or you will be in the same situation again.

@Manoj

Is there a good reason that the e/os build dates are always some days before the the FairPhone built dates? Why can’t e/os just wait these 5 days and synchronize the built dates with FairPhone?

5

The response from the team :

It currently makes sense for security patches & rollback:

  • FPOS release happens around the time of /e/ OS release.
    • Both will have same Android Security Patch Level & same rollback.
  • For Vendor Security Updates:
    • We are able to integrate into the latest beta, as soon as FPOS releases
    • Undergo testing & release with approx delay of a month.
2 Likes
6

Would it be possible to sideload 4.3 to the FP6+ (outside of the webtool) since the 4.3 patch level is higher?

I received this message when trying to convert a couple of days ago and 4.3 has been released since, but I don’t think the webtool is pulling the 4.3 image.

7

maybe that?

2 Likes
8

Same issue with the Pixel 4a (sunfish) here. In my case I couldn’t get it to boot back into 4.2 at first. No matter how often I tried the “Power off” selection, it didn’t revert to the 4.2 slot. I then tried “Rescue Mode” and “Recovery Mode” from the same “Hold Power-Off + Volume Down Menu” and then it stopped to hang in the G-screen and instead showed the “dead Android” screen.

After some fiddling and querying the LLM the following got me back into 4.2:

  1. Hold Power-Off + Volume-Down until it reboots and shows the fastboot menu
  2. Quickly use the Volume-Up key to stop it from continue booting (no idea why)
  3. Connect to PC and run fastboot erase misc(do on your own risk)
  4. Run fastboot rebootand wait for the boot into 4.2
1 Like
9

If you want to New install /e/OS I suggest to carefully read and follow Install /e/OS on a Fairphone - The Fairphone (Gen. 6/Gen. 6+) - "FP6" | /e/OS documentation

  • At this time in the release cycle there are multiple questions like “when will I get the new release”. Please watch the forum for the multiple answers that will follow all week and over next weekend. :slight_smile:

The situation today is expressed as:

For your own up to date answer for fp6 official at any time, one can just tap the install download link:

and check if updated to e-4.3 yet.

2 Likes
Week 39. Development and Testing Updates
10

I also had that dead android screen…

Good you succeeded and provide a more systematic approach for return to previous version than I did.

Can’t recall what I did exactly but it worked with only device buttons (and the power cord being connected or not seemed to make a difference…)

11

Merged from here: Pixel 4a Update to v4.3 stuck at google logo

I encounter problems, with recent update to e/os v4.3. I restarted the device after completion of installation and the phone now stucks at the google logo.

Has this been encountered by other users, too? What should I do to get it back working without data loss?

12

See the above posts on most likely the same issue with pixel 4a

13

As for Pixel 4a, there is no need to delete anything! I tried this with success:

  1. Reboot with Power-Off + Volume - Down
  2. Check with fastboot devices
  3. Get current partition with fastboot getvar current-slot => will reveal a or b
  4. Switch current-partition with fastboot --set-active=a or b
  5. Reboot with fastboot reboot

You are now back with v4.2

Good luck!

2 Likes
14

  • Vendor name: Oneplus

  • Device name: 13R

  • Device codename: giulia

  • Previous version of /e/OS: 4.2 a16

  • Whether the device is rooted or not: not rooted

Everything working fine. Rainmaps on ilmatieteen laitos (Finnish meteorological institute) app are finally working! Great job, thank you!

15

Th

This was one of the first things I tried, but it didn’t work for me. It might have been due to a bad USB connection, though. The fastboot commands were very flaky for me. Even after trying different ports and cables the CLI sometimes just didn’t do anything after issuing the command.

16

You should make sure that your device is in fastboot mode. It’s indicated with red letters in the lower left part of the screen. Running fastboot devices should return some device being found. Otherwise, it’s pointless to use fastboot.

17

Of course. I know that. That’s not the issue.

1 Like
18
  • Samsung
  • S10e
  • beyond0lte
  • Version previously: 4.2-a16-community
  • Not rooted

Update went smooth and fast. No issues so far.
Thanks to the team maintaining this device.

19

  • Vendor name: Fairphone

  • Device name FP4

  • Previous version 4.2 OTA Official to 4.3 A16

  • Device not rooted

Apart from VoIP apps being broken (thread below), no other significant issues noted.

Voice Calls over Signal/WhatsApp Sound Like Mickey Mouse

20

There is no official 4.3 build released yet.