I’ve tried that now both with the internal storage and the SD (first at the top level of the file tree, then in the Downloads folder – with both IS and SD), but no difference. Now given that this is the installation file that is now already installed, it might not qualify as “compatible” anymore? Might try again with the next smaller update.
- Vendor Name: Samsung
- Device name: S10e
- Code name: beyond0lte
- Version of /e/OS which existed previously: 1.18-s
- Not rooted
No issues so far. Thanks for good work to the team!
1 Like
- vendor name : xiaomi
- device name : MI10T
- device code name : apollon
- Previous version of /e/OS : 1.18S
- Rooted
No issue so far. Everything OK 
Happy new year to the team and congrats for the good work.
- vendor name : Oneplus
- device name : 8T
- device code name : kebab
- Previous version of /e/OS : 1.18T
- Rooted
Impossible to upgrade. When download is finished, package verification starts and immediatly an installation error is issued.
I try that : Issues with the Updater and a solution without any success.
I’m on a Samsung Galaxy S7, herolte. We haven’t had an update since v.1.17. Just wondering, is this the end of the line for us?
The herolte will get an OTA OS upgrade from Q(Android 10) to R (Android 11) as mentioned here. Will share dates when it will be released.
3 Likes
Awesome, thanks Manoj!
FP2, not rooted, Open Launcher 1.18. → 1.19.1-r
All fine 
Tested: MullvadVPN, Signal, Firefox, FreeOTP+, KeePassDX, Aurora, f-droid, easybank app
Especially the bug in the Emailclient (see feedback 1.18) is solved 
- Cheers!
1 Like
Widget calendar in dark mode is unusable. Above is Agenda Todo opensource widget, below e/OS default calendar.
Vendor name : lenovo
Device name : yoga tab 3 plus wifi
Device code name : YXT703F
Previous version : e-1.18-r-20231209360969-dev-YTX703F.zip
No issue, everything OK so far.
Good job e-os team
But for my kekab daily device it’s not the same story, I try a manual update with adb sideload!
It was not a good idea…
I just download the e-os-T-1.19.1 release, verify the MD5 hash code, and flash the new release with adb sideload.
After rebooting from recovery to system, I am still in 1.18 version but it seems some apps have been updated. For example, Magic Earth is released to 7.1.23.49. More than that, apps which use location data don’t works in fake location mode.
In conclusion a bunch of discrepancies, I’m afraid of reinstalling the whole stuff (fresh install).
Today, my recomandation to kebab owners, is to wait for a fix before switching to 1.19.1 release.
Vendor name : Pixel
Device name : 6a
Device code name : bluejay
Previous version : e-1.18-T-dev
Everything worked smooth. Even after 24h no hickups observed.
Thanks.
Vendor name: Motorola
Device name: Moto One Action
Device code name: troika
Previous version: e-1.18-t
Not rooted
No issues since yesterday. Used apps are mainly Firefox, K9 Mail, Organic Maps, Signal, Öffi, Calendar/DAVx5, KeePassDX.
Thanks to the dev team.
Hi,
Vendor Name : Fairphone
Device name : FP3
Device CodeName : IMG-e-1.17-s-20231111351092-dev-FP3.zip
Migration : e-1.19.1-t-20240113373116-dev-FP3.zip
Is the device Rooted / Not rooted : I don't know, it's stupid anyway. And I haven't found a reliable article to verify it. Given what I do on it, it must be rooted.
Thank you for all the sharing, it’s been very helpful.
I wanted to follow an old article to sideload the FP3, but the page no longer exists (here (not function of course)). It’s a good thing I wrote it all down in my documentation. There’s nothing in the docs and it took me at least 45 minutes to find the page with the info on FP3.
I had exactly the same problem as @urs_lesse (here) on the signature part of the .zip file. It’s due to a lack of knowledge on my part.
Apart from that, I only have one problem and the update was installed in less than 10 minutes.
The problem was that VLC was no longer reading my SD card. I uninstalled the application and reinstalled it. Since then, VLC has been reading my SD card just fine, with no problems.
And I’ve enlarged the display font by one notch. It was written slightly smaller
Here’s what I did:
-
First, add adb and fastboot. Follow the instructions here.
-
Find the right file here, thanks you @AnotherElk . It’s in JSON format, my file is on line 28.
-
Then activate the developer tools, plug the phone into USB: activate USB debugging (authorised by the PC) & unlock the OEM (see the start of the procedure here). At the end of the procedure, disable everything by doing the reverse.
-
Make sure you back up all your applications, photos, videos, OTP, etc.
-
Run the adb commands from the downloaded folder (I’m running Linux, Debian 12):
-
./adb reboot sideload (the phone reboots and goes into sideload mode)
-
./adb sideload
/mnt/X/Save\ FP3\ 17012024/e-1.19.1-t-20240113373116-dev-FP3.zip -
The phone reboots. Unplug everything and check that it works.
-
Keep the procedure in documentation if you wish, but above all share it here :).
The question I ask myself. Now that I’ve changed the way I upgrade, will I receive updates normally or should I always use sideload for updates and upgrades?
Thank you
Have a nice evening
4 Likes
You should receive updates normally.
Upgrades to future new Android versions would depend on what’s being made available then format-wise.
1 Like
- Vendor Name: Fairphone
- Device name: FP4
- Code name: FP4
- Version of /e/OS which existed previously: 1.18-s Stable
- Not rooted
Seems everything’s fine! Thank you to the dev team!
1 Like
- Vendor Name: Fairphone
- Device name: FP4
- Code name: FP4
- Version of /e/OS which existed previously: 1.18-s Stable
- Not rooted
Everything seems to work, thanks!
Happy about the tracker list in Advanced Privacy: still no facebook trackers found, that sounds weird.
Happy too about Browser and Webview update, I still get ads on youtube for example even though I added a lot of filter lists.
EDIT Enabling “anti-circumventions and snippets” in Adblock Plus Settings seem to solve this. Lots of not translated English in this section…
I also see a FP4 stable build for T! I know we are supposed to wait for 1.20 to get it OTA, so I am surprised to see a 1.19.1 build there…
2 Likes
Vendor Name: Fairphone
Device name: FP4
Code name: FP4
Version of /e/OS which existed previously: 1.18-s Stable
Not rooted
Hello.
Update over OTA V1.19.1-s-20240109372023-stable-FP4 from 09.01.2024
I have one issues:
- The calendar app crashes during the “search” and then has to be restarted. Like in V1.18-s
- After the OTA update to V1.19.1-s-20240109372023-stable-FP4 check the updater again and from time to time i can see a new version update to V1.19.1-s-20240110372023-stable-FP4 from 10.01.2024.
Should I install the newer one from 10.01.2024?
Thank you very much e/os team for the great work.
BR
Mark
2 Likes
- Vendor Name: Fairphone
- Device name: FP3+
- Code name: FP3
- Version of /e/OS which existed previously: 1.18-s Stable
- Not rooted
Works fine, except the release note from the updater that send to an error 404 webpage instead of the corresponding release’s note.
1 Like
@Manoj: https://gitlab.e.foundation/e/os/releases/-/releases currently says “This /e/OS v1.19.1 version includes the Android security patches available until December 2024.”
I don’t think so 
.
I shared the comment with the team to correct.
1 Like