rephone® 6/128 GB
SoC: MediaTek Helio G85 - k69v1_64_k419
Stock Android 12 (A12) Kernel: 4.19.191
No custom recovery
working ~ e-2.7-t-UNOFFICIAL-gsi_arm64_20250111 by @Colors
Successful repair of the WiFi/Internet/Network problem with:
adb shell settings put global restricted_networking_mode 0
Hi! I just made a new build. A few minor aesthetic changes and added a few vendor hardware overlays. I don’t know if it helps…
On my tablet everything is functional, as usual, so I do not know if it is an improvement.
Well, we live in a less ideal world…
Lenovo Smart Tab M10 HD TB-X306F
SoC: Mediatek MT6762 Helio P22T
Stock Android 11 (A11) Kernel: 4.19.127
No custom recovery
working ~ e-2.7-t-20250112-UNOFFICIAL-gsi_arm64_vN by @Colors
Successful repair of the WiFi/Internet/Network problem with:
adb shell settings put global restricted_networking_mode 0
There is no search bar at the top of the settings
App Lounge v2.12.2 foundation.e.apps finds the app you are looking for, offers to install it, but does not install with the message CANCEL
At first glance, I can’t see any difference to the previous version. However, it is great that the GSI is running.
Sidenote: On Samsung Galaxy S5 (klte) and Galaxy S8 / S8+ eAppLounge malfunction is also present.
Thank you, Xxpsilon!
@Colors, thank you very much for sharing 
Now you have a wide field of degooglization…
I have a few more versions in the plan until I set a general direction. Unfortunately I won’t have much time. Keep the latest version as a reference and against the GSi version of Null. Put aside which devices still can not be installed with eOS but where Lineage works. I sincerely hope Null and you and Ronnz are the shock team or the Three Musketeers.
For me, a /e/OS-T GSI is more valuable than a /e/OS-U GSI. However, when one day /e/OS GSI T+U is running and published on Generic System Image (GSI) list I predict that it will be very popular.
It will be! There is a lack of information about eOS or the fact that it has a bad name or a misunderstanding of what it is. Everything will change… But what I see as a bottleneck is AppLounge and its strategy. Maybe I don’t understand at all what is wanted or what it is, but I certainly wouldn’t link it to Google or an anonymous account at all. There are a lot of apk stores like AppGallery or Rustore as a standalone model. I see this problem as number one, and the second problem is the development of a GSi version that will quickly spread eOS. And number three as a priority is compatibility with older devices, in special the most popular ones, that will ensure a wide user base. These are, from my perspective, priorities and number four, partnering with various corporate or financial institutions for compatibility with specific applications. I know, there are legal implications of all kinds, but the reality is that all the other actors, except the big ones, are in a tight jacket, and the rules of the game are not in their favor. This is personal opinion. I’m under no illusions, I’m just doing what I consider principled as a position. We are not going to change the world, but with every download someone thanks you because there is an alternative. Ants are small, but they make everyone else flee when they invade.
I’m under no illusions when I say popular. GSI’s are used by a significantly smaller number of users than custom ROMs. And custom ROMs are used by a vanishingly small number of users compared to the entire Android market. In terms of size, both user groups are just like an ant in the Android universe. But ants have existed for over 100 million years and will always be there. So well-functioning GSI’s will also have their place among the Android operating systems.
I would also like to see a more flexible /e/OS, such as CalxyOS, iodéOS or VollaOS. All but a few system apps can be uninstalled or deactivated there - including microG services. It is certainly possible to build GSI’s based on e-Code, without implementing e-AppLounge, e-Drive, e-Mail et cetera pp. A CUSTOM instead of UNOFFICIAL GSI ( compare /e/OS Build Types ) together with signed dev keys would be one way.
Murena does not want a /e/OS GSI, this is proven by the fact that they intentionally messed with the SystemUI in order to cause breakage in GSIs after Colors and I released GSIs.
I think this is bad behavior to treat a project based on open source as proprietary and it makes me not want to execute any of their code on my devices, because if they’re willing to lock it down in this way (even though I still bypassed their breakage LOL) they’re going to do it to an even greater degree in the future, and I do not want to contribute to their rise if this is the case.
Anyway, I’ve wiped Murena’s code from my devices completely and have zero interest in playing a game of reverse engineering with the developers of this ROM, if I wanted to perpetually do that I would work on HyperOS or another proprietary solution but I don’t support projects that don’t play by open-source rules; and with these actions Murena has demonstrated that it belongs to this exclusive club.
My future forecase for Murena’s /e/OS is like this, in one of their files they have this code commented:
<!-- Component name for the activity that will be presenting the Recents UI, which will receive
special permissions for API related to fetching and presenting recent tasks. The default
configuration uses Launcehr3QuickStep as default launcher and points to the corresponding
recents component. When using a different default launcher, change this appropriately or
use the default systemui implementation: com.android.systemui/.recents.RecentsActivity -->
<string name="config_recentsComponentName" translatable="false">foundation.e.blisslauncher/com.android.quickstep.RecentsActivity</string>
In the future they will lock their ROMs features behind walls so that it will not run as the true system on ported devices. lol.
Better to leave it be
Strong stuff. Although I can install GSI, I don’t understand anything about its coding.
At least since the 41st week of 2023, it has been announced that a GSI is planned. Over the months it became “Team is working on /e/OS T GSI”. It is clear that this project is not a priority. I understand that /e/ Murena as a commercial company needs to make money to stay in existence and therefore focuses its available resources on more worthwhile projects.
There are a number of bright minds on this planet. One of them lives in the south of France and is building a first-class A/B device GSI with years of experience. Others will follow…
the config_recentsComponentName config xml string comment was introduced 6 years ago by google folk - looks to me like benign search&replace launcher3 activity to blisslauncher as in “works for me” ? it wasn’t on the systemui activity default since years