Feedback for v1.20

Tested after update:

  • Vendor Name: Murena
  • Device name: Fairphone 4
  • Device CodeName: FP4
  • Previous Version of /e/OS: 1.19.1-s (stable)
  • Rooted: False

All good once I changed @e.email account to @murena.io ( this resolved my cloud sync issues at murena cloud) :+1:

Vendor Name: Xiaomi
Device name: Mi A1
Device CodeName: tissot
Version of /e/OS which existed previously: e-1.5-R
The device is Not rooted

Manual upgrade to /e/OS-T V1.20

First function test successful:
:white_check_mark: Works fine: 4G LTE, WLAN, BT, GPS (GPS, GLONASS, BDS), e-Cameras
:heavy_heart_exclamation: Very pleasing additional functions: Infrared port, FM radio (UKW)

1 Like

@Xxpsilon, Any special action in compare to documented except wipe/ format? Did you wipe cache, data? Asking because I dont know why my upgrade failed.I have two profiles on this phone and wonder if that could prevent booting. Thx

My Mi A1 is not a daily driver. It was upgraded from /e/OS-R (A11) to /e/OS-T (A13). Therefore I did a clean install (irretrievable deletion of all data) to have a perfect installation for future updates.

Vendor Name: Xiaomi Redmi
Device name: Note 6 Pro
Device CodeName: twolip
Version of /e/OS which existed previously: e-1.16-r-20231021343335-dev-twolip
The device is Not rooted

OTA-Update to /e/OS-R V1.20

First function test successful:
:white_check_mark: Works fine: 4G LTE, WLAN (Wi-Fi 802.11 a/b/g/n/a) , BT 5.0, GPS, e-Cameras
:heavy_heart_exclamation: Very pleasing additional functions: Infrared port, FM radio (UKW)

Vendor Name: Gigaset
Device name: GS290
Device CodeName: GS290
Version of /e/OS or Stock which existed previously: 1.19.1-s-20240109372023-stable-GS290
Is the device Rooted/ Not rooted: Not rooted

Updated smoothly via OTA.

There was an increased level of battery consumption. However after a few days the rate of battery depletion reduced but is still ever so slightly more than it was using v1.19.

Overall very happy with the performance of the phone using the /e/OS versions released after December 2023. The phone had become so slow and frustating to use, I was on the verge of binning it and using an old Samsung phone running LineageOS.

Vendor Name: Murena Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Previous Version of /e/OS: 1.19.1-s (stable)
Rooted: False

Won’t update past 81% updater now keeps crashing.

Well, my Samsung A5 is also draining my battery. I have 3000 mAh of capacity, but I like to think the battery is old. Still, the app Accu Battery tells me my battery health is 80%. I am really not a heavy user, in contrary: I use the phone far less than most people do.

I still don’t have 1.20 available. I have a Samsung Galaxy S10+ (currently running 1.19).

Is it the case that the “slotted” release time/date hasn’t reached me yet, or the 1.20 update is not available for the S10+? Does anybody know?

1 Like

Looking at the ROMs published for Galaxy S10+ https://images.ecloud.global/dev/beyond2lte/ we see that the final Android 12 (S) was e-1.19.1-s and that your next build now will be e-1.20-t, Android 13 (T) so a manual Upgrade will be required (no OTA Upgrades on dev builds).

Android (T) upgrades should need no Format data and no “Return to stock ROM” just adb sideload as this [Guide]. Always take a back up of essentials first.

Fairphone 5 /FP5
1.20-t-20240220382010-stable-FP5
Regularly bought via Murena. Not rooted

“Smooth display” feature (90Hz) makes bliss launcher crash regularly once a day at random. It looks like the phone is rebooting, but uptime is the same.

Today it crashed and displayed the bootloader the first time.

With 60Hz setting no crash, or with 90Hz and KISS launcher no crash.

1 Like

My KISS crashes. What’s the german name of this feature so I can try out other settings?

Heißt auch auf dt. Smooth Display (unter den display Einstellungen). Wenn du ein FP5 oder ein Gerät mit 90Hz Display hast. Featurevgibtsvauch noch nicht lange und hatte schon einige bugs.

Same for my S10 Beyond1lte

@Blank_Space @centaurus Update from 1.19.1-s to 1.20-t on beyond2lte
that helped me. :wink:

How can I file a bug report related to v1.20 in GitLab? I have not find how I can create an account - when I tried I was not allowed to create one with my e-mail address. Or where/how can I request a bug report to be created?

Support topic: Getting an error message in new ID creation on /e/OS Gitlab?

1 Like

Yes, it does not like my e-mail. Ref this snapshot. How do they (or myself) know which is my regular e-mail? In the form, it states something like they recommend a business e-mail, but I use (of course) one of my personal e-mails. https://gitlab.e.foundation
gitlab

@hehemrin, my response is a link! Please just follow the recommended path to ask for help.

2 Likes