Hi all,
been very happy with e OS on my Samsung Galaxy Note 9; well, up until this latest release V26…
Now nothing on screen except background colour, and icons such as wifi etc on very top bar.
Nothing else showing at all; just a VERY quick pop up that’s too fast to read…think it’s an error message.
HELP; how can I fix this when nothing seems accessible?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Try to go to → settings → apps → blisslauncher → storage → clean storage
Hi piero, thanks…trying that. Nope, sadly no better 
So try to reflash latest /e/,
if not better, flash previous /e/
Hi again, sorry, I’m a REAL noob. Is it easy enough to explain how to go about doing either of your suggestions? TIA 
Thanks for your help; will read and try. Cheers
there are multiple ways to keep your data untouched :
Do not wipe or format, no factory-reset (dirty-upgrade)
OR
OR
OR
Installing adb and fastboot on a Linux PC
Installing adb and fastboot on Windows PC
download the latest /e/OS-T build for your device
(put it into the platform-tools folder)
.
.
Select Apply Update, then Apply from ADB
The screen should now change and the output at the bottom ask you to send the package from your computer.
Open a terminal from the /platform-tools folder, and
issue command to sideload the latest /e/OS-T installation zip.
adb sideload e-2.5-t-20241109446827-community-crownlte.zip
or
adb sideload e-2.6.3-t-20241219455848-community-crownlte.zip
the phone screen will be mostly blank with just the output at the bottom showing progress.
(Do not pay attention to the wipe related things on this photo that came from the full install from stock instructions !)
On the computer the sideloading shows progress as a percentage figure that will stop at 47%. The phone will still be installing though (even though it might feel like nothing is happening sometimes!) and you can expect to see the following screens (excepting the wipe related things)
Then press the arrow at the top of the screen to return to Home Screen
Tap Reboot system now to boot into eOS.
.
.
Go direct to point (8) or (9) of the guide
[HOWTO] an Unified Install Guide Project for /e/
Hi, sorry, had to step away…Xmas stuff Thanks for trying to help. I find this stuff quite challenging; and usually need someone else to do…but I will try to go back over it again and give it another try. Cheers
So far works without problems
OTA upgrade to 2.6.3 U was without issues.
All my usual apps works as expected.
Prior issues thats been solved ( it was user error):
Camera preview doesnt display image when DNG capture is activated. When I chose WebP and Raw it works fine.
Slow App Lounge: Some IP ranges from my VPN provider was blocked on the internet. I set up split tunneling and connecting to App Lounge without VPN. App Lounge works fine and is pretty fast.
Only for info:
Samsung S8 codename is dreamlte not starlte
Samsung S9 codename is starlte
Vendor Name: Samsung
Device name: Galaxy S8 -G950F
Device CodeName: dreamlte
Version of /e/OS which existed previously: e-2.2-r-20240715417776-stable-dreamlte
/e/Recovery which existed previously: e-2.2-r-20240715417776-stable-dreamlte
My device is Not rooted
My experience:
The /e/OS Updater finds the “stable” /e/OS-S 2.6.3 (A12) upgrade, but …
It’s downloaded and prompted for installation, but no installation takes place. After restarting, version /e/OS-R 2.2 is still running.
A manual upgrade via e-Recovery R-2.2 did not work either, because the e-System does not boot into the e-Recovery, but back into the normal /e/OS-R.
So I first had to install the new e-Recovery e-s-2.6.3 and then use it to install the new upgrade ROM /e/OS-S 2.6.3 (A12).
Merry Christmas all 
The upgrade went fast and smooth, everything runs well on Android 14 
Thank you so much for your hard work, enjoy some well deserved days off, and happy holidays 
@Manoj … By the looks of it, this OTA upgrade here is not in testing anymore:
References …
Thanks for pointing that out. Have updated in the weekly report.
Do not delete. Do not factory reset.
I had the same issue.
As an intermediate solution you can install Fossify Launcher.
Just try to follow the image instructions
Good luck
Only 99% convinced it’s due to this 2.6.3-U upgrade, but … for the first time ever, I can use my (1st generation and discontinued) Fairphone TWS earbuds for a telephone call on my Fairphone 3+ 
Everything is mostly OK, but the camera (foundation.e.camera) randomly crash while taking pictures.
Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Previous Version of /e/OS: 2.5-t
Version of /e/OS: 2.6.3-t
Device: Not rooted
Updated smoothly.
However there were a few glitches after the installation reboot. Firslty the SIM card wasn’t picked up. Corrected with a reboot of the phone.
Then there was a crazy battery drain attributed to Android OS in the battery usage stats. A further reboot corrected that glitch.
The fingerprint reader seems to be working better with this update. Unless my finger tips are just cleaner than before. 
I would like to add that the messaging around devices moving from Android 13 to Android 14 with this update was somewhat confusing. I struggled to make sense of what I was being told in the various statements. It’s understandable with everything going on and the different native languages in the milieu.
I think a bit of brevity was needed for the information presented. For example saying only devices FP4 etc will upgrade to Android 14 over OTA. All other OTA updates will remain Android 13. The following devices (per list) are upgradable to Android 14 via side loading the Community version.
As always, a hearty thank you the everyone. I continue to be very happy with the performance my de-googled phone.
Mile buiochas and Happy Christmas.
I upgraded the system last Sunday.
The method I used is the one mentioned on the lineage wiki and I had no problems. The phone booted normally, and at least for now the apps I use are working. I got app lounge working again. So far, no problems.
