I’ve been using Tasker to autoadjust brightness when screen turns on or when shaking the phone. This uses a custom calibration curve (ambient lux → screen brightness) that I defined based on my preference. Although this requires a bit of work, it works flawlessly for me.
But yes that is different from AoD which is likely controlled deeply by the Fairphone firmware and this Tasker autobrightness adjustment is not what is causing the change in brightness when AoD pops in.
Strangely for me on a fp6 4.1.1 the auto screen brightness seems better to me than on 4.0. It doesn’t hunt as much as it used to.
Update is available since monday morning
Hi @kolkrabe
Thanks for your reply as well; it’s important to me because you have a GS290 too. I’m not in a hurry to upgrade, I’ll go through everything thoroughly again first and then list my steps. I think I’ll share that here too. Regards.
Hi @dave would you mind sharing a link to the issue?
I’m interested in it for the LC3 codec within BT LE, which hopefully unlocks better sound quality for my headset
Provider Name: Fairphone
Device Name: Murena Fairphone 6
Device Code Name: FP6
Version of /e/OS that existed before: e/OS 4.0-a15-20260610633983-official-FP6
Device is not rooted
Update OTA went through without any problems.
Problems: App Lounge no download and no updates possible. It works through the Aurora Store.
Name des Anbieters: Fairphone
Gerätename: Murena Fairphone 6
Gerätecode Name: FP6
Version von /e/OS die vorher existierte: e/OS 4.0-a15-20260610633983-official-FP6
Gerät ist nicht gerootet
Update OTA problemlos durchgelaufen.
Probleme: App Lounge kein Download und keine Aktualisierungen möglch.
Über den Aurora Store funktioniert es.
* Vendor Name: Fairphone
* Device Name: Fairphone 6
* Device CodeName: FP6
* Version of /e/OS or Stock which existed previously: v4.0
* Device not rooted
Upgraded yesterday in 0:35 hrs, used 2% of battery.
Went flawlessly, so far no issues.
I upgraded my OnePlus 6 last week to 4.1.1. Up to now, everything works as expected.
My Samsung S8 was also updated to 4.1.1. Until now, all is good.
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Current Version of /e/OS: 4.1.1 Rooted: No
Update was OK, but the new password manager is appearing every time I interact with any password field and it’s very annoying, I didn’t find how to disable it.
This is configurable under Settings → Accounts → Preferred Service and Additional Services. Make sure Passwords is not preferred nor enabled as additional.
Provider Name: Fairphone
Device Name: Murena Fairphone 6
Device Code Name: FP6
Version of /e/OS that existed before: (i don’t remember, probably the latest before the update) e/OS 4.0-a15-20260610633983-official-FP6
Device is not rooted (FP6 bought with Murena pre-installed)
Overall, things are working.
My banking apps are working normally. Crédit Coopératif and Fortuneo.
Concerning your account manager authentication failures:
I had exactly the same issues after updating for i would say almost a week (applounge, latency)… I don’t know what happened: but since a couple of days they disappeared.
As reported here by @Fibo16, VoWIFI seems to be working on FP6 since v4.1.1 although IMS status remains labelled as not available. I could place/receive phone calls in airplane mode with just wifi on.
There are 3 related issues in Gitlab
FP6: ASHA implementation ,
Sound stops playing though LE hearing aids after first use - Fairphone 6 (#9436) · Issues · e / Backlog · GitLab ,
FP6: Bluetooth LE (Low Energy) connections do not play audio (#8942) · Issues · e / Backlog · GitLab .
Not only is sound not streaming to my hearing aids properly, but hands-free calls are now not possible in my car whereas this used to work fine.
No Updates via App Lounge possible, stuck at 0 percent
EDIT:
Disregard the esim issue, after another few reboots and some time waiting, the issue somehow solved itself.
//The esim functionality is not available.//
I notice this:
Why Android 16 couldn’t turn Wi-Fi and Bluetooth into one-click toggles like in other android 16 os version?
See here under an example:
Vendor Name: Samsung
Device name: Galaxy A52 (5G 6GB)
Device CodeName: a52sxq
Version of /e/OS or Stock which existed previously: The previous version
Is the device Rooted / Not rooted: Rooted (?)
Sometimes, the phone would only charge when turned off (or, conversely, only when turned on - that kept changing). After experimenting with the Battery Manager and Charge Control settings, I found that enabling Battery Manager and disabling Charge Control resolved the issue. Unfortunately, I don’t recall the original settings.
Same issue on Samsung s10 5g a13. Voice call extremely low.
I can’t update because I need seedvault as the only viable backup solution. Also the high amount of issues with this release makes me hesitate, although I realize this is due to the new features.
Pixel 5 redfin on v4.0
