Vendor Name: Samsung
Device Name: Galaxy S8
Code Name: dreamlte
Version of /e/OS which existed previously: e-2.7-s-20250109460371-official-dreamlte
Device Not rooted
everything is fine, running perfectly. 
many thanks to the creator team great work 
My fairphone 5 is now on 2.8, working perfectly, thanks all.
My pixel tablet is also working great on 2.8, although I still can’t get the fingetprint sensor to work. Perhaps a problem with my device specifically.
Vendor Name:Fairphone
Device name: Fairphone 4
Device Code Name: FP4
/e/OS version 2.7-t-official Stable
The device is not rooted
So far all is perfect! 
I think you can speed up your next update by using the “caffeine” mode in the quick settings menu. Helped a lot for me…
FP4 Security patch is 2024-12-01 ？
Should be January 2025 according to Releases · e / os / 🚀 Releases · GitLab, but the install pages (Install /e/OS on a Fairphone FP4 - “FP4” in this case) sometimes show some lag while adopting the new info after a release.
If this is what you mean. Or are you reporting from your updated device?
Teracube 2e
Murena
e_emerald-user 12 SQ3A.220705.004 eng.root.20250219.235526
Phone : pixel 7a lynx
Unrooted
Previous: 2.7-u
The update worked flawlessly, the phone works as intended.
You mean the ‘prioritize update’ slider in the settings ?
Vendor Name : Fairphone
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 2.7-u-20250109460370-official
Is the device Rooted / Not rooted : Not rooted
Update in ± 10 minutes, that was very quick
So far, no issues. Good job!
Vendor Name: Google
Device Name: Pixel 5
Device CodeName: Redfin
Version of /e/OS which existed previously: 2.7 T Official
Is the device Rooted / Not Root
Updated without a hitch.
Only one thing: after each E/OS update I have to delete the data from the “France Identité” application and reimport my ID card for it to work properly again.
thank you for this update!
@Manoj Quick question concerning the updates and their availability in the update pipeline:
If an update appears on the website, does it mean the the update should be available in the updater as well. Or could it be that there are notable delays?
Ex: I have a Pixel 7 (Panther) in front of me. The v2.8 update (official) is available on the website, but not (yet) in the updater. Is that correct?
There could be a delay in it showing up on the updater. It may not be exactly in sync. May show up first on the website and then on the device.
If you check in your own phone after the update to 2.8 you’ll see january 1, 2025.
Cheers
Hi there,
just updated to /e/OS 2.8-a14-2025021 and all incoming calls are displayed “Unknown caller”.
Tried a lot of settings and tips (suggested on community forums), nothing works.
My carrier is Telekom in Slovenia.
Please help.
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Blisslauncher crashes when I do a search.
Rotating an image crashes the application (FX ?).
Vendor Name : Fairphone
Device name : Fairphone 4
Device CodeName : FP4
Version of /e/OS or Stock which existed previously : 2.7-u-20250109460370-official-FP4
Is the device Rooted / Not rooted : Not rooted
Upgrade joyful, no issues to report. Thank you e/OS Team
No … Check out the quick settings menu which is available by sliding down from top of screen, else see here:
Great find! It looks like manually cycling through Fastboot and then back into Recovery helped the OTA update process continue smoothly.
This is a useful workaround for others who might face the same issue! 
Thanks for sharing your accidental fix—it might save someone else a lot of time. 