Not charging until 100% is good, it harms your battery. A bit lower is best
Vendor Name: Fairphone
Device Name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: 2.8-t-official-FP3
Not rooted
No issues so far. Thanks to the team!
Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName : FP5
Version of /e/OS or Stock which existed previously : 2.8
Is the device Rooted / Not rooted : No.
Overall the update process went fine, and the phone is working decently. However, there is 2 notable issues since the update :
- Iâm affected by the already reported problem when using a murena account with 2FA, where the account manager seems to interfere with SMTP/IMAP password configuration for the Mail app. I saw the issue thread and know this should be fixed soon, but this desserve to be reported due to the next issue.
- Since 2.9, my battery lifespan went from 3 days to <1 day today, without changing overall usage. I wonder whether this has something to do with the constant notification of the first issue ? Despite it appears as a single persistant notification, KDE Connect actually see it as several batches of 10+ notifications all along the day, that might indicate some kind of infinite loop in the background.
Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName : FP5
Version of /e/OS or Stock which existed previously : 2.8
Is the device Rooted / Not rooted : No.
As reported before, the Murena account manager throws an authentication error. I connect to my own Nextcloud instance (for Notes, mainly), in my case no Murena email account or 2FA is involved.
Hello,
Phone: Fairphone FP3+
Network: Orange
Country: France
I was previously on 2.8-t official and I updated to 2.9-t official.
All is working fine for me.
- Vendor name: OnePlus
- Device name: Nord
- Device CodeName: avicii
- Version of previous /e/OS: 2.4.1-s-official
- Not rooted
Installation of 2.9-s-official went smooth!
Everything works well so far except a probably minor issue with the browser:
If âSafe Browsingâ is enabled in the data privacy settings of the browser then it is always waiting for about 5 seconds (also observed 15 seconds) before a web page opens. If âSafe Browsingâ is disabled then no lags are observed. In /e/OS/ 2.4.1-s there were no problems with that (but I donât remember if the âSafe Browsingâ feature was available and/or enabled there).
I found a related posting where the same issue was discussed in january.
Is there a solution available or should I create a ticket in the bug-tracker?
Two weeks ago, I received a notification about the update to 2.9 for my Fairphone 4. I was travelling, so I didnât install it immediately. And now itâs gone. When I check for updates, it says that my current 2.8-a14 is the latest available version for my phone. Has the 2.9 update been retracted?
No, itâs available on the update server. Did you already refresh the updater (icon top right in the updater)?
Thanks a lot to e/OS team.
- Vendor Name: Samsung
- Device name: Galaxy S7 Edge
- Device CodeName: hero2lte
- Version of /e/OS or Stock which existed previously: e-2.8-s
- Is the device Rooted / Not rooted: Not rooted
Everything works well except battery is draining fast (almost doubled) compared to e-2.8-s.
Not able to figure out anything from Settings > Battery Usage or from Battery Guru.
Maybe something in the system draining battery.
Network: 4G
Location: Off
NFC: Off
Auto rotate: Off
Launcher: Bliss or NeoLauncher. Same issue
Pre-installed unused Apps: Disabled if possible
Seeing exactly same battery drain issue in another Samsung Galaxy S8 (dreamlte) which got a clean e-2.9-s install.
1 Like
Yes, twice, yesterday and this morning. Trying again⌠same result.
How often did you touch it? It sometimes takes atleast 4 times 
1 Like
Thatâs it! Three times in a row, and I see the 2.9 update. I wouldnât have expected magic spells in e/OS/, but now I know better. Thanks!
1 Like
It is not magic spell, it is just how the server behaves to prevent that everyone doesnât get the update at the same time because performance or unexpected bugs.
Back when I was using Windows you could also force a Service Pack by manually look for updates
1 Like
Then at the very least the UI is broken. If I ask is thereâs a new update and the answer is âno, no updateâ, then that should be true. For what you describe, the answer should be âcouldnât check, please try againâ.
This staggered release method should have ended a few days ago according to the first post. When I had a look at the server in a browser on my PC, the updates (official and community) were always there when I refreshed multiple times.
But in the end ⌠whatever works 
2 Likes
No, because itâs not the check that fails. The check simply gets shown thereâs no update, or thereâs an update, and that in a randomised fashion to achieve the effect @mihi described.
If everybody just tried again and got the update immediately, it wouldnât be much of a staggered release.
The question remains why it would still behave this way today.
1 Like
I donât mind if I get the initial notification at some random point. I do care about being shown correct and comprehensible information. Iâll happily let the developers figure out how to achieve this goal in a way that fits their needs, but showing wrong information is not a good way.
1 Like
They did.
During a staggered release the information shown is not wrong technically.
If the staggered release indeed already ended, you have a case, because then the updater shouldnât behave in the way it did for you.
1 Like
Per previous post, I am still unable to update my phone to new version, including a recent attempt today. Any help or thoughts or guidance available?
Do you have âlocal updateâ in the hamburger menu (3 dots top right corner)?
You could try that. You need to download the file.
adb sideload from recovery would also be possible.
Since it is not working as intended make sure you have a backup (which is good to have in any case) to be safe