Feedback for v2.9

/e/OS Smartphone Operating System Build Feedback
123

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!

124

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.
125

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.

126

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.

127
  • 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?

/e/OS browser running very slowly on Fariphone 4
128

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?

129

No, it’s available on the update server. Did you already refresh the updater (icon top right in the updater)?

130

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
131

Yes, twice, yesterday and this morning. Trying again… same result.

132

How often did you touch it? It sometimes takes atleast 4 times :see_no_evil::see_no_evil:

1 Like
133

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
134

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
135

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”.

136

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 :+1:

2 Likes
137

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
138

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
139

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
140

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?

141

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

142

I have been reading this thread for a week or so and am a bit nervous about applying this update due to the number of comments about deterioration of battery life. If there is a known problem, could I be notified when it has been fixed. The battery life is really good with 2.8 and I would like to keep it that way. Or if the battery life issue is specific to a particular type of usage, it may not affect me anyway, so that would be useful to know as well.