Feedback for v1.20

/e/OS Smartphone Operating System Build Feedback
100

As a family mobile tel maintainer my feeback is:

1

Google
Pixel 5
redfin
e-1-19.1-T-stable
not rooted

upgrade to e-1.20-t-stable locked at “reboot preparation” at 50% during 40mn. So I cancel upgrade.
Need to investigate why…

2

Lenovo
Yoga Tab 3 Plus Wi-Fi
YTX703F
e-1-19.1-R-dev
rooted

upgrade to e-1.20-R-dev : no issue evrything OK.

3

Xiaomi
MI10T
Appolon
e-1-19-1-S-dev
rooted

upgrade to e-1-20-T-dev not available from “param/system upgrade” so I upgrade the device manually (fastboot flash recovery and adb sideload). Upgrade works finely, no issue.

101

I updated my Fairphone 3 to E/OS V1.20 I noticed that" Quickly open Camera" setting does not work as described. Press the power button twice. I have never tried this before so I do not know if it worked in other versions.

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online servicesphone

102

@CFA Have you checked under Settings / System / Gestures whether ‘Quickly open camera’ is set to on? I can’t remember whether it’s the default setting.

1 Like
103

Thanks Dave
Saved: :person_raising_hand:
I found the problem. The FP case is quite thick making it difficult for me press the power key twice as quickly as required to turn on the camera. Usual end up locking the screen.

104

1st Device

Vendor Name: Xiaomi
Device name: Redmi Note 8T (with NFC) 4/64GB
Device CodeName: willow (not ‘ginkgo’)

Version of /e/OS which existed previously: /e/OS-R v1.15
Version of /e/OS Recovery which existed previously: /e/OS-R v1.15
Version of Android Security Update which existed previously: Aug 5, 2023
Is the device is Not rooted

Version of /e/OS after the update: /e/OS-R v1.20
Version of /e/OS Recovery after the update: /e/OS-R v1.20
Version of the Android security update after /e/OS-R installation: Jan 5, 2024

:ballot_box_with_check: No warning messages during the updates and at the first start.
:ballot_box_with_check: WLAN / BT works fine

2nd Device

Vendor Name: Xiaomi
Device name: Redmi Note 8T (with NFC) 4/128GB
Device CodeName: willow (not ‘ginkgo’)

Version of Xiaomi firmware which existed previously: willow V12.5.6.0.RCXMIXM_11.0 global
Version of /e/OS Recovery which existed previously: Android recovery
Is the device is Not rooted

Version of /e/OS after the update: /e/OS-R v1.20
Version of /e/OS Recovery after the update: /e/OS-R v1.20
Version of the Android security update after /e/OS-R installation: Jan 5, 2024

:x: No warning messages during the updates and at the first start, b u t WLAN / BT do not works

1st Trial installation:

  • Official Lineage-18.1-20240218-microG-ginkgo + LOS-Recovery
  • No warning messages during the updates and at the first start,

b u t

:x: WLAN / BT do not works

2nd trial installation:

  • PitchBlack Recovery Project: PBRP-ginkgo-4.0-20231217-1134-OFFICIAL
  • crDroidAndroid-14.0-20240209-ginkgo-v10.2
  • MinMicroG Minimal
  • Version of the Android security update after crDroid installation: Feb 5, 2024

:white_check_mark: No warning messages during the updates and at the first start.
:white_check_mark: WLAN/BT works fine

105

Perhaps try the steps here: Issues with the Updater and a solution

106
  • Vendor name: Oneplus
  • Device name: Oneplus 3T
  • Device codename: oneplus3
  • Previous version of /e/OS: 1.19.1-r
  • Rooted: no

Upgrade process, ok.
But it seems that the battery is draining very quickly.
I need to charge the phone after just over half a day, as opposed to 1.5 days before.
Thanks

107
  • Vendor name: Oneplus
  • Device name: Oneplus 9
  • Device codename: lemonade
  • Previous version of /e/OS: 1.19.1-t
  • Rooted: no

Upgrade process, ok.
No problems detected so far.
Thanks

1 Like
108 
Vendor Name: Xiaomi
Device name: Mi8
Device CodeName: Dipper
Version of /e/OS or Stock which existed previously: 1.19.1-t
Is the device Rooted / Not rooted: Not rooted

Everything is working fine. The only thing missing is the translation of the new pdf reader.

110 
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Current Version of /e/OS: 1.19.1-t (stable)
Rooted: No

Why my phone (FP5) says there is no OTA update available even if the new ROM is available on the repo?
https://images.ecloud.global/stable/FP5/

111

Hi, everyone, I wonder if I will see discovery update for 1.20-s or I need manually upgrade to 1.20-t. If I look on guide for discovery install I see there link name /e/OS build : S dev but when I open it I see only T zip file for 1.20 and older S versions.

I wonder if the S version will show up later or I need to do manual upgrade to 1.20-t?

Also a note that the link name should probably change to T dev version now?

112 
Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously : 1.19-t
Is the device Rooted / Not rooted : Not rooted

Update was ok (still very slow compared to other devices) but there are still a bunch of things that did not work on this phone or are even missing compared to stock

1 Like
113

OK for my Pixel5 (purchased in /e/-shop) not rooted. It was upgraded with 1.20-t stable release (updated from 1.19.1 to 1.20 (1.20-t-20240220382010-stable-redfin) - e_redfin-user 13 TQ3A.230901.001 eng.root.20240220.200127 dev-keys).
To be noted : upgrade to e-1.20-t-stable locked at “reboot preparation” at 50% during 40mn (same as here) for a total time about 1h30.
Also, 2 reboot were needed before internet access can work correctly (wifi or data). Some applications could access it while others (Firefox) could not.

As for previous releases, all functions seems to be OK except the #citymapper app which is generally freezed (no map and/or functions) when I opened it (same pbm as with previous releases from 1.15). uninstalled !

The camera pbm (described here or there ) is still here : when I take a picture with lens1 the final picture is blurry when I’m not in “auto” mode.
It never append when I received my phone from Murena.

114

OK for my Murena2 (purchased in KickStarter /e/-shop) not rooted. It was updated from 1.19.1 to 1.20

All functions/apps seems OK except the I still have the camera pbm (described here) : when I take a picture with lens1 the final picture is blurry when I’m not in “auto” mode.

Thanks all for the work !

115 
Samsung
Galaxy S9+ 
star2ltee
1.19T (dev)
Device unlocked

Catastrophic discharge while not doing (almost) anything. See below for behavior before and after the update:

Screenshot_20240304-091852_Settings
Screenshot_20240304-091852_Settings1440×2960 215 KB

116

Thanks for the advice.

I did get the upgrade done.

117

Vendor Name: Sony
Device name: Xperia 10
Device CodeName: kirin
Version of /e/OS which existed previously: e-1.10-s-20230413279105-dev-kirin
Version of /e/ Recovery which existed previously: recovery-e-1.10-s-20230413279105-dev-kirin
Device is Not rooted

Version of /e/OS after the upgrade: e-1.20-t-20240222382228-dev-kirin.zip
Version of /e/ recovery after the Upgrade: recovery-e-1.20-t-20240222382228-dev-kirin.img

To be on the safe side, I did a clean install via e-Recovery v1.20 and everything went smoothly. Thank you e-Dev Team.

119

Vendor Name: Nothing
Device name: Nothing Phone (1)
Device CodeName: Spacewar
Version of /e/OS which existed previously: e-1.20-t-20240301-UNOFFICIAL-Spacewar.zip by @ronnz98
Version of /e/ Recovery which existed previously: recovery.img e-1.20-t-20240301-UNOFFICIAL-Spacewar by @ronnz98
Device is Not rooted

Version of /e/OS after fresh clean install: e-1.20-t-20240223382228-dev-Spacewar.zip
Version of /e/ recovery after fresh clean install: recovery-e-1.20-t-20240223382228-dev-Spacewar.img

My fresh clean install followed this /e/OS documentation to the letter. For this I needed the file vendor_boot.img. This file is not yet officially available for download. Therefore I extracted the file payload.bin contained in the e-zip file. The file payload.bin contains the following files:

boot (101 MB), dtbo (25 MB), odm (696 kB), product (500 MB), system (1.7 GB), system_ext (368 MB), vbmeta (8.2 kB), vbmeta_system (4.1 kB), vendor (495 MB), vendor_boot (101 MB), vendor_dlkm (13 MB)

:new: Safe download of this vendor_boot.img here

To be on the safe side, I performed a clean installation via OFFICIAL e-Recovery v1.20 and everything went smoothly - without the incidents described here

Glyph Interface works right away including light functions, as well as Fingerprint (under display, optical), and wireless charging.

Thank you e-Dev Team :+1:

NP1 ‘Sparewar’ Documentation Suggestions

Flashing additional partitions & Temporarily Booting a custom recovery using

  1. Next we manually reboot into bootloader or download mode

  2. You can also boot into fastboot mode via a key combination:

  • With the device powered off
  • hold Volume Down + Power

Instead of switching off the smartphone each time and then booting it back into download-/fastboot- and recovery-mode - the VOL and POWER device buttons can simply be used during operation (without switching off the NP1) to execute the respective function (see attached image). This method is also foolproof.

Photo

spacewar_Recovery-mode_restart-bootloader
spacewar_Recovery-mode_restart-bootloader956×446 116 KB

120
  • Vendor Name: Fairphone
  • Device name: Fairphone 4
  • Device CodeName: FP4
  • Previous Version of /e/OS: 1.19.1-s (stable)
  • Rooted: hidden with Magisk

all works fine

121

Hello,
Samsung galaxy herolte. Running 1.17 before
Not rooted
Mail, phone, SMS, agenda, photo & galery working.
Still the echo in call problem though

2 Likes