[LIST] Devices which will be getting upgraded to /e/OS T - Part I

Poco F3 is currently in transition to LineageOS 20 (Android 13) so chances are it will eventually be released for /e/OS T as well.

PLEASE remember to not blindly follow the official documentation and not update to eOS T after the foundation released a dev build if you have a POCO F3.

The S version required quite a lot of manual preparation to properly upgrade from R to S, all of which were not included in the official eOS documentation for months. I wrote the guide for properly upgrading to S here and it took quite some time to get it incorporated into the official documentation. I will be writing a guide for eOS T as well, since it will likely require the same amount of manual prep work. If you don’t want to lose your data and are not very experienced I recommend to be patient and wait until either I or someone else wrote a guide.

1 Like


I’m an Alioth owner on 1.8.1R (02/2023) and saw your active contribution here.
My version didn’t get any OTA update since february, thus am I wondering if I should update to S.

Can you confirm to me that it is now okay to completely follow the official documentation for this ? Or is it still better to follow your post on the topic I linked ?

Thank you in advance for you answer, have a good day.

They have incorporated some of my steps and have a link to my forum post. However I still recommend to just follow my guide from top to bottom if you want to make sure that everything works out. If you don’t like TWRP you can use their steps for the eOS Recovery though. Good luck!

1 Like

Do user of /e/OS S need to flash /e/OS T manually or will it be delivered via OTA?

If therr is the need to flash it manually, is there a possibility to retain apps, settings, messages, and other personal data?

Almost only Murena sold devices get upgrade OTA’s, all others need to do it manually

1 Like

Only stock firmware upgrade must (for now) be installed manualy.
All /e/OS updates and upgrades can simply be achieved by the recovery manager when upgrading the stock firmware is not necessary.

Please make sure this important LineageOS bit makes it into /e/OS T for FP3 …


… else a number of Apps will refuse to work with the fingerprint reader because of Google tightening the requirements and deeming the FP3 sensor’s security “weak” from Android 13 on, see also for reference …



Hello team,

Great work !
Do you plan to release /e/OS A13 for Samsung S10 (SM-G973F/DS - beyond1lte) ?

I can see that Lineage 20.0 / A13 is available on LOS repo : https://download.lineageos.org/devices/beyond1lte/builds


There is an unofficial /e/OS T build for Sony Xperia XZ1 Compact (lilac) - see this post


Just did it, your guide was peerless and really simple. Thanks a lot !

I see there is no new version available of /e/OS S since may ; do you know if the previous maintainer left ? Or are they working on /e/OS T ?

Since you seem quite knowledgeable, I’m currently wondering if compiling the image using the official guide would do the trick, I’m quite familiar with docker, so it shouldn’t be too hard. But I’m wondering if there is any perticular modification to do, which would be specific to this device, and that I would not be aware of. Seems risky, doesn’t it ?

Thanks in advance for you answer.

Where might one locate the Android T builds? I’'m on Redfin and the S builds have been incredibly problematic for me. So, I’m more than willing to load a newer DEV build and see what happens.

Not released yet. You can follow announcements about the progress here … https://community.e.foundation/tag/development-updates. Currently:

Many thanks! Sure appreciate the answer. I’ve marked the announcement post.

Better mark the category. Next week there will be a new topic for the new week and the old week’s post will not be updated :wink: .

I think you found your answer further down this thread. For what it’s worth, I’m currently not using eOS on any device because the home screen regularly reset itself and messed up my icon order. Also since eOS uses parts of Trebuchet (LineageOS UI) for app switching but didn’t change the package name, it’s impossible to install Trebuchet on an eOS device. But I should complain to eOS about that. Not to you. :wink:

You can use any launcher you want. Not using an OS because of the default launcher seems quite narrow. :smirk:

But there are threads about that odd behavior. I never use Bliss anyway.


Reading comprehension, kind sir. I said: You can not use the Trebuchet launcher because parts of it are used to provide app switching for Bliss.

You can verify this yourself: Just go to apps, enable system apps and search for “trebuchet”. You will realize that it is present on your device even though you don’t use that launcher. Since eOS team did not rename that package, you can’t install the actual Trebuchet launcher on an eOS device due to the name conflict.

Since Bliss launcher got reworked for eOS T this might have changed, I don’t know. But before that the above described situation is the case.

Hi everyone.

Do we have any update on this list?
Its 28 of august, almost 2 months after the initial date of this post.
From my eyes, the list remains the same.

Any updates?