Hello,
updated today on 2.1 – has no Wifi (if I swith Wifi on,it swithes immediately off again; had this problem also with MOTO G5 e/os 1.21 in the past), so don’t update on this version, wait for next update.
Update after 24h:
I hoped 13/T would be the solution for my big battery life problem but I am endless disappointed.
Nothing better, still worse. With V2.0 little bit more worse.
Vendor must not be named
Device name: Pixel 4a
Device CodeName: sunfish
Version of /e/OS or Stock which existed previously: Android 13 / T (stock rom)
Rooted?: NO
Same for me:
FP4, previous OS v. 2.0 A12 stable, not rooted.
Until on A12 I used as camera app also FP4 stock camera but witout be able to use 48MP. Now that stock app doesn’t work anymore but I tried with the eOS camera app: same behaviohr as MMaTT88.
To be honest, I am not sure about the rest. It was on 2.0 before. I am just doing the standard thing. Since the update today, after unlocking, I shortly see the background screen and then a black screen. I can’t do much. Notifications are received, I see App Lounge updating some apps, but I don’t know what to do.
Update: After two restarts and a bit of random button pressing, it seems to have resolved itself
after the Update to 2.1-t (Android 13) my Fossil Smartwachtes App no longer works. All cached data was deleted and I cannot reconnect my two watches. Bluetooth connects, but the setup cannot finish. There is always a “network connection error”, although every other app works.
I tried switching off Advanced Privacy thinking that it maybe blocked the connection to the Fossil servers, but that did not solve it.
Samsung
Galaxy S7
SM-G930F
Version 2.0 R Stable-herolte
Not rooted
Hello,
The update to version 2.1 went without issue. It has been running without issue for four days now.
I hope my phone holds out, materially speaking, as long as e/os can be updated!
Thanks to the whole team.
Claudiousse
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: v.2.0 stable
Is the device Rooted / Not rooted: Not rooted
Despite patchnotes regarding solved issue with crashing Bliss launcher forcing to see boot logo animation, this issue is still present and occurs when display is set to 90hz.
Within the first day I got two crashes, one using Bliss Launcher and the other using Discreet launcher. Switching to 60hz seems to not cause crashes.
Vendor Name: Fairphone
Device: Fairphone 4
Device: FP4
Version of /e/OS or Stock which existed previously: v2.0 stable
Is the device Rooted / Not rooted: Not rooted
Have found the same issue as another user in his thread: Fairphone 4 some (USB-C?) chargers do not work
one side of the USB-C Charger does not fast-charge while the other side does. It does sometimes switch as well. May have been present in v.2 but was not (for me) present in 1.19.1
Vendor Name: Xiaomi
Device name: Mi 10T Pro
Device CodeName: Apollon
Version of /e/OS or Stock which existed previously: 2.0
Is the device: Not rooted
The update itself went smoothly. But beginning with /e/OS 2.0 I realize a heavy battery drain of “App Lounge” when apps are updated. The download percentage indicator goes up to 100% for the first updatable app and then stays like this for around 15 to 30 minutes. No “installing” indicator vor anything else comes up. Sometimes after around 30 minutes App Lounge sends the notification that n apps have been updated, sometimes a phone reboot is needed. During this time the phone gets warm and the battery drains rapidly about 20-30% within minutes (pls. See Screenshot).
I’ve already cleared the cache and storage of App Lounge with no difference.
Besides this /e/OS doesn’t handle self installed trusted CAs correct for 3rd party apps. Apps like Homeassistant or Firefox browser don’t trust theses self installed CAs while the internal browser does. I’ve checked with LineageOS and LineageOS with microG where these CAs are trusted in 3rd party apps. So it doesn’t seem to be the apps itself nor the CA certificates.
Since version upgrade from 2.0 (Android 12 S) to 2.1 (Android 13 T) crashes and reboots happen. Sometimes complete eOS restarts but without displaying the initial fairphone screen. Signal app crashes when opening a received message. Maybe eOS crashes when receiving a whatsapp message (not sure if this is the reason).
I had a lot of issues with the camera after upgrading to 2.1-t. No picture saved or corrupted image. Clearing the camera app. data and cache solved the issue.
No trouble whatsoever save the, now classical, Citymapper app that for a couple of years has been starting but freezing itself (only itself) seconds after its welcome screen… I remember it working on /e/ but that was long, long ago really…
Apps optimization after update was very long (but I have lots)
Vendor Name : Fairphone
Device name : Fairphone 4
Device Code Name : FP4
Version of /e/OS : 2.1-t - stable
Previous version of /e/OS: 2.0-s - stable
Is the device Rooted / Not rooted : rooted
problem with Wifi: when clicking to connect on a specific wifi the phone restarts
click on “Networks needs to be verified” and it restarts
I’ll go back to 2.0
Update: Finally, it’s specific to a certain Wifi network… not sure why. now working with another Wifi network.
Hello -
Great update from 2.0 to 2.1 and R to S with a Samsung S9 (starlte). Huge thanks to /e/ team.
It went smooth and nothing to complain so far except minor android changes… BUT I suspect a noticeable battery drain compared to 2.0/R. Now clearly “OS Android” is the top battery user.
To be monitored…
Vendor Name : Samsung
Device name : S9
Device CodeName : starlte
Version of /e/OS : 2.1-s - stable
Previous version of /e/OS: 2.0-r - stable
Not rooted
To be clear:
after 6h from last full load, with a normal usage, the phone is at 54% battery with:
“OS Android” 19% of use (an android robot black icon)
“Android System” 4% of use (a blue and grey gear icon)
That was absolutely not the case with 2.0 and R … I remember seeing “Android System” but not “OS Android” at all, or it was really low in the consumption list…