Feedback for v2.1

/e/OS Smartphone Operating System Build Feedback
21 
    Vendor Name Motorola
    Device name moto g32
    Device CodeName devon
    Version of /e/OS or Stock which existed previously e-2.0-t-20240507399779-dev-devon
    Is the device Rooted / Not rooted rooted

Update went well and no issues found. Thank you!

22 
Vendor Name: Fairphone
Device name: Fairphone 5
Code name: beyond0lte
Version of /e/OS which existed previously: 2.0-t-20240506399547-stable-FP5

not rooted

update does not show up in the updater

1 Like
23

It could be, as Manoj write:

1 Like
24

Fairphone 5 is not beyond0lte :wink:

stable is released a couple days after dev. Patience or hit the refresh button more than 3 times and get lucky

1 Like
25

Please see Different Build Types ~ Official ~ stable

This build undergoes additional and longer testing cycles

2 Likes
26

Vendor Name: Xiaomi
Device name: Redmi Note 8T (with NFC)
Device CodeName: willow
Version of /e/OS which existed previously: e-1.20-r-20240221382014-dev-ginkgo
Device is Not rooted

Since no OTA update to version e-2.1-r-20240606407290-dev-ginkgo has been offered on the system so far, I have successfully carried out a manual update via PC and adb sideloadand, - also ended up in fastboot mode after the reboot.

After I installed recovery-e-2.1-r-20240606407290-dev-ginkgo and booted into e-Recovery, I am shown:

The system has been destroyed
Press powser button to shutdown

Next I installed PitchBlack Recovery Project and with it /e/OS-R v2.1, but again the system only booted into fastboot mode.

I had no choice but to completely reinstall Global Firmware Android 11

Now that /e/OS-R will no longer be officially supported in the foreseeable future (as of today, the latest Andrid security update is February 5, 2024), I successfully switched to crdroid 10.5 (Android 14) with MinMicroG.

See also

27
  • Vendor Name: Samsung
  • Device name: S10
  • Code name: beyond1lte
  • Version of /e/OS which existed previously: 2.0-t
  • Not rooted

No issues so far. Thanks for good work to the team!

28

Vendor Name: Google
Device name: Pixel 6a
Code name: Bluejay
Version of /e/OS which existed previously: 2.0-T-dev

Update went smoothly. In usage I detected a little regression with regard to animations (opening/closing apps): https://gitlab.e.foundation/e/backlog/-/issues/8040

29

Vendor Name: Oneplus
Device name: 8T
Code name: kebab
Version of /e/OS which existed previously: 2.0-T-dev

Update ok, no issue.
Good job.

30 
Vendor Name: Asus
Device name: Zenfone 8
Device CodeName: sake
Version of /e/OS or Stock which existed previously: 2.0-t-dev
Is the device Rooted: no

All good - update went smooth - no issues so far.
Thanks Team!

31

G7 power “ocean” had an issue with updater when upgrading to /e/ v2.1. After being notified by the updater something went wrong during the update process. When i tapped “apply update” , updater appeared to initiate and download the files well. After that it tried to “finish installation” but kept crashing. The weird part is that the updater subtitle said updating even after the crash(es).

Anyway, I grew tired of the automatic OTA route and went to recovery. To my surprise it appears that /e/ shown me that it updated to v2.1 in the header. When i rebooted, the OS made my phone bootloop a bit then stabilized after a manual restart.

Just a note for future releases on the “ocean” channel.

32

Is this really out there now for FP4 ?
I don’t see here any feedbacks for Fairphone 4 and I tried since 3 days to get the update offer (so pressed the button almost 100 times [In the past you could increase your chance with that]) and I don’t get it…

1 Like
33

Apparently it is … dev and stable.

grafik
grafik2144×1743 271 KB

(I looked up dev, too.)

2 Likes
34

Yes.
But OTA via updater ?

1 Like
35

The screenshot shows the query response of the usual OTA update server including the new version. Does the Fairphone 4 use a different server? Possible, but I wouldn’t know.

2 Likes
36

OK, thanks.
I just wondering because tomorrow is already the last stage day

37

Vendor Name: Samsung
Device name: Galaxy S9+
Code name: star2lte
Version of /e/OS which existed previously: 1.21 R dev

Did a succesful manual update/upgrade from 1.21 R to 2.1 S

38 
Vendor Name: Google
Device name: Pixel 4a
Device CodeName: sunfish
Version of /e/OS or Stock which existed previously: 2.0-t (dev)
Rooted: No

All good, no issues detected after couple of days of usage.

1 Like
39

Working fine just like 2.0 on POCO X3 NFC / NO ROOT, haven’t found issue yet.
Thanks for providing the update.

40

In case your updater is the culprit, clearing its storage should help … Issues with the Updater and a solution

Also make sure no firewall or Antivirus Apps on your phone or on your network block it.

1 Like