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