Same on my FP6, mainly in my default browser Firefox, but also in Vivaldi and, I think, in some other apps too.
Yes, its a FP6 problem. For me too.
I think i have the same (FP6), feels like the phone just hangs. When i lock and unlock the phone it’s gone.
Since i haven’t had an Android phone for a decade i thought this was just an Android thing and that i was pushing the phones memory or cpu to much. ![]()
Just read my last post:
You can download 4.3.1 for FP4 manually: See my post above.
Thanks. It worked for me
I had a xiaomi phone before with eos for years and there was no such problem.
Hi @Manoj,
I’ll try asking you directly since I think some “insider info” with a reasonable amount of certainty will be useful here instead of “guessing”.
- Also referring to the documentation you pointed out here Week 40, Development and Testing Updates - #60 by Manoj; what is, at this moment, the rollout percentage for 4.3 A16 for the FP6 (a release which was paused and then resumed by the /e/OS Team)?
- Is it possible/advisable on a FP6 with official OTA 4.1.1 A16 to skip directly to 4.3 A16 via the updater on the phone (in case the updater will offer such an option) or are there fixed-paths/dependencies which will need that the phone goes from 4.1.1 A16 then followed by 4.2 A16 and then finally getting 4.3 A16?
The updater on the Fairphones which I use is always set with the “See all available updates” option enabled and I always use the updater with OTA updates aiming at not losing my data on the phone.
I update the phone not on a regular basis and in the past (for the FP4, not yet for the FP6) it has occurred to me that the updater on the phone was offering me more than one version of /e/OS (though I am quite sure they were anyways all within the same corresponding Android base version) and I was able to directly update to the latest release while skipping the ones in between (some years ago I also posted in this Forum about “skipping some OTA releases available on the updater on the phone in favour of the most recent one” and I was told “it’s OK to do that”).
As it can be read from my chain of posts and the corresponding replies in this thread, I am currently on 4.1.1 A16 and, as of this morning, on the updater on the FP6 I still can only see 4.2 A16 available and not version 4.3 A16.
If the updater on the phone is “telling me” something like “I am not offering 4.3 to you because for technical reasons from your current 4.1.1 you first need to have 4.2 and only after having updated to 4.2 you will have the offer for 4.3” then I’d rather follow what the updater is telling me rather than doing other things.
So my two questions above.
Thanks
Vendor name: Fairphone
Device name: FP5
Device codename: FP5
Previous Version: 4.2 official on A15
Device not rooted.
OS works fine, but:
- I noted an issue with charging - maybe it’s a coincidence, but since the update I noted problems with some chargers which worked fine before - they are reported as slow charging. Maybe it’s an OS issue, maybe it’s a USB port problem that occurs just after update, no idea.
- I have problem with UPS parcel racking application - I cannot log in - I have a message from app “we have technical issues, try again later”. The same app on Googled device works fine
The testing is done from v4.1.1 A16 to v4.2 A 16 and then to v4.3. You should follow that route without skipping builds in between. It may work but since it is not tested it is not advisable to skip the builds in between.
Hi Manoj,
Thanks for getting back to me.
Now I am in this “lucky” situation that the updater is offering me only version 4.2 A16 and so I’d rather get 4.2 A16 or remain with 4.1.1 A16; meaning the updater is not offering me both 4.2 A16 and 4.3 A16.
As it can be read here Regarding /e/OS updates in the past the updater has been offering more than one version and I was told “it’s OK to skip to the latest” (my very short summary of that thread).
So now I have a bit of a conflict in my head between “it’s OK to skip to the latest” and your “do not skip builds in between” (my summary of your reply).
What should I do in case the updater offers more than one release?
But again: right now I am in a “lucky” situation because it seems that the updater might be telling me something like (copy/pasting my own text) “I am not offering 4.3 to you because for technical reasons from your current 4.1.1 you first need to have 4.2 and only after having updated to 4.2 you will have the offer for 4.3”.
Though I might try clearing the data of the Updates system app to see if I will still get offered only 4.2 A16 or 4.2 A16 and 4.3 A16 (I already tried clearing the cache of that app: From 3.7.3 A15 to 4.3 A16 on FP6)
Version 4.3 is not visible on my Fairphone 6 in the OTA updater.
The last version visible for me was the 4.2-A16 from August, which was installed successfully.
Is something wrong, or is this behavior intentional and temporary?
Vendor name: Google
Device name: Pixel 8
Device codename: shiba
Previous Version: 4.2 official on A15
Device rooted
Everything works perfectly (except for the usual issue with QR code reading in the EasyBank app for Belgium present from v4.0). Thank you!!!
-
Vendor name: Murena
-
Device name: Fairphone Gen 6
-
Previous version of /e/OS or stock ROM: 4.2-a16
-
Whether the device is rooted or not: Not rooted
The OS is working great! I’ve just noticed a new pin icon that runs pretty often saying “Account Manager” in notifications.
Vendor Name: Motorola
Device: moto g84 5G
Device CodeName: bangkk
Previous OS: /e/OS: 4.3-a15-community
Not rooted
Did a dirty upgrade
- from /e/OS: 4.3-a15-community
- to /e/OS: 4.3-a16-community
following this HowTo
Doing it with the recommended method using the “system updater” didn’t work, but the classic approach with adb succeeded finally and I’m happy ![]()
No issues observed so far.
(because of the build date)
I’m not sure if the build date was the reason, but it makes sense:
I updated from 4.2-a15 to 4.3-a15 some days before (OTA). Yesterday I did the the dirty upgrade. Now I had a look on the available images:
- 4.3-a15 is built on 2026-09-22
- 4.3-a16 is built on 2026-09-19 (4 days earlier!)
As written in the HowTo thread I also have got a warning message concerning a downgrade when flashing the upgrade via adb. An earlier build date could be the reason for this, too.
Gigaset
GS290
Previous version 4.2
Not rooted
4.3-a15-20260917677554-official-GS290
OTA installation went fine and fast. Everything seems to work well. Esp. happy, that older phone is still supported. Thank you!
Hi Manoj, are there any news on 4.3 for Pixel 4a?
Ah that’s what I missed, I saw a bunch of code about different builds, but because it is all in red I didn’t notice it was a hyperlink to the file.
Here:
Vendor: Fairphone
Device: Fairphone 4
Codename: FP4
Now:
4.3.1-a16-20260929682353-official-FP4
Previous version:
4.3-a16-20260917677552-official-FP4
Device not rooted
Device locked
Obviously, the Mickey Mouse is gone. Cheers for that.