Feedback for v2.8

/e/OS Smartphone Operating System Build Feedback
84

Great find! It looks like manually cycling through Fastboot and then back into Recovery helped the OTA update process continue smoothly.

Summary of the Fix (if OTA update fails and reboots into Recovery):

  1. In Recovery Mode, go to Advanced.
  2. Select Enter Fastboot.
  3. Then return by selecting Enter Recovery.
  4. The update should now proceed normally, updating both Recovery and /e/OS 2.8-u.

This is a useful workaround for others who might face the same issue! :rocket: Thanks for sharing your accidental fix—it might save someone else a lot of time. :blush:

1 Like
85

CMF Phone 1 A015 by Nothing

OTA-Update
FROM: e-2.7-u-20250109460370-official-tetris
TO: e-2.8-a14-20250219469961-official-tetris
Not rooted
BlissLauncher 3.1.2
App Lounge 2.13.2 > works

/e/OS download is faster than per WLAN / Wi-Fi via (noname) LAN RJ45 USB-C adapter.

86

Smoothly updated, nearly everything is fine besides, as in the previous /e/OS version, “Notes”: Opening the app for the first time, it loops on its start screen, no matter if you choose online (cloud) or offline mode. This behaviour is already listed in GitLabs’ e/Backlog (Impossible to use/startup Notes app (#8542) · Issues · e / Backlog · GitLab).

87

Are you using VoLTE?

88

I tried both, with and without VoLTE. No effect.
Communicated with my carrier (Telekom Slovenija), they switched off VoLTE. No effect.
It must be something with the /e/OS (using 2.8, newest update on FP4)!

1 Like
89

Vendor Name Fairphone
Device name Fairphone 4
Device CodeName FP4
Version of /e/OS which existed previously: 2.7-u-20250109460370-official-FP4
The device is Not rooted

All seems to work for me, also the problem with QR code scanning I’ve reported here is solved:

90

You checked the APN?

91

Yes this worked for me as well. Had the same issue (ending up in recovery while updating), was still on 2.6, skipped 2.7 for this reason (too lazy), going to fastboot and then back to recovery makes it install after you accept the signature failed. Curious if this will happen again with 2.9

Vendor Name : Samsung
Device name: GalaxyS10
Device CodeName: beyond1lte
Version of /e/OS or Stock which existed previously : /e/OS/ 2.6-U
Is the device Rooted / Not rooted : Not rooted
92

Hi all

Vendor Name Fairphone
Device name Fairphone 4
Device CodeName FP4
Version of /e/OS which existed previously: 2.7-u-20250109460370-official-FP4
The device is Not rooted
Thanks for the update but I still can’t search an app in Bliss, Bliss crashes, really annoying.

A screen capture here :

94

Yes very lucky and very useful solution I hope.

With 2.7, I also posted a solution but that was with fastboot flash recovery and adb flash image, did work but more work and not everybody knows how to work with adb/fastboot

95

Vendor Name: OnePlus
Device name: 5T
Device CodeName: dumpling
Version of /e/OS or Stock which existed previously: v2.8
Is the device Rooted / Not rooted: Not Rooted

The Gallery app is not preserving the timestamps correctly, instead in some images it is using the Modified Date instead of the Date Taken.

This is really bad needing to have the Gallery app display the correct timestamps, this is a serious issue I hope will be corrected soon.

I made a bug report on e’s Gitlab;

96 
Vendor Name: Google 
Device name: Pixel 5
Device CodeName: redfin
Version of /e/OS or Stock which existed previously: fresh install
Is the device Rooted / Not rooted: not rooted

The camera app doesnt work, sometimes its start but sometimes its crashes.

97

Hello,
Teracube 2e emerald
2.8-s-20250219470167-official-emerald
Update Successful
previous version 2.7 -official emerald
Running Android 12
Abdroid Security Patch January 2025

Device working well - responsive and fast
Many thanks to the e- team for delivering a quality OS! Needed now more than ever
USA

98

I also have fp4 - everything works. Try to clear cache of bliss maybe?

99

Hi Kipry, i cleared the cache and even all the bliss stored data but it didn’t helped

Thanks

101

no issues so far - thanks

102 
Vendor Name : Murena Store
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 2.7
Not rooted

Depuis la 2.6 j’ai un probleme rĂ©curent avec les donnĂ©es mobiles. Le tĂ©lĂ©phone perds la connexion soudainement, et parfois pendant plusieurs minutes ou heures. Si je dĂ©sactive et rĂ©active manuellement les donnĂ©es mobiles, le tĂ©lĂ©phone les reprends presque immĂ©diatement.
Si je traverse un trou d’onde, je perds la connexion mais lĂ  c’est normal. Sauf que le tĂ©lĂ©phone peut perdre la connexion n’importe ou n’importe quand. Y compris lĂ  oĂč la connexion est efficace habituellement.
Du coup, je ne sais pas si c’est un problùme de software ou directement du hardware 

Ce qui me pose soucis, c’est que ce problĂšme Ă©tait systĂ©matique en 2.6 et depuis la 2.8 il revient moins souvent.
Je le vois avec ces icĂŽnes :
image

Il affiche bien la 5G mais avec le point d’exclamation. Donc il le voit ? Ou est-ce qu’il ne le voit plus ?

Sur un note positive, la mise Ă  jour s’est dĂ©roulĂ©e rapidement et l’os fonctionne toujours aussi bien.

Since 2.6 I have a recurring problem with mobile data. The phone loses connection suddenly, and sometimes for several minutes or hours. If I manually turn off and on mobile data, the phone resumes it almost immediately.
If I go through a wavehole, I lose the connection but that’s normal. Except that the phone can lose connection anywhere at any time. Including where the connection is usually efficient.
So, I don’t know if it’s a software problem or directly with the hardware

What worries me is that this problem was systematic in 2.6 and since 2.8 it comes back less often.
I see it with these icons:
image

It does display 5G but with the exclamation mark. So he sees it? Or does he no longer see it?

On a positive note, the update went quickly and the bone is still working well.

103

On Releases · e / os / 🚀 Releases · GitLab shows for Samsung devices:
“Signature mismatch preventing sideload/OTA updates is now fixed”
My tablet is S6 Lite, gta4xlwifi, I encountered the same problem with OTA upgrade, once downloaded, it reboots into recovery mode and shows an error; choosing reboot the tablet, it still be on /e/ 2.7. So I started from scratch, i.e. re-install the tablet as it was under Samsung Firmware to install /e/OS for the first time:

  • Download both /e/OS and recovery version 2.8.
  • Proceed to Download mode to Flash recovery file.
  • Proceed to Recovery mode, then choose enable ADB;
  • Flash /e/OS;
  • Reboot the tablet.
    And now, everything would be back in order, entering in recovery mode, it shows well the current version is 2.8.
    I think that you can try/proceed without problems and hope that can help you and others in Community.

Kind regards.

104

Vendor Name : Fairphone
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 2.7-u-20250109460370-official
The device is not rooted

No issues so far.

Thanks /e/-Team :+1::+1::+1:

105
  • Vendor Name : Samsung
  • Device name : Galaxy Tab S6 Lite
  • Device CodeName : gta4xlwifi
  • Version of /e/OS or Stock which existed previously : 2.7U
  • Device not rooted
    OTA upgrade unsuccessful, probably due to “Signature mismatch preventing sideload/OTA updates” from the previous /e/ 2.7, then I had to start from scratch, i.e. re-install the tablet by flashing recovery file, 
, and so on.
    Everything is working well. Thanks to the TEAM.