v3.6-a16
https://sourceforge.net/projects/e-os/files/GSI/16/v3.6-a16-20260318-microG-gsi.img.xz/download
v3.6-a16
https://sourceforge.net/projects/e-os/files/GSI/16/v3.6-a16-20260318-microG-gsi.img.xz/download
@Colors with enthusiasm I found your GSI builds. Thanks a lot for them, thats really great! Althoug I got a professional IT background, I’m really a noob when it comes to Android and only just learned what this GSI thing is about. I own an Android MP3 player (Mechen X56) which is running A13. Treble Info consideres it to be GSI compliant. So I gave your build a try and… failed. Now I have two questions:
I noticed you removed all builds but the 3.6-A16 one from sourceforge. What does it tell us? I’m fine with only the most recent Android, but it seems you updated the A15 build to /e/ OS 3.7 before you removed the file, while A16 is still on 3.6. I hope you don’t have any plans to abandon this project?
Treble Info tells me I would need an arm64-ab.img.xz file. In fact while trying to flash the image, I got an error message which implied I should have listened to that. Luckily the flashing just failed and the device came back up with it’s default install. You provide just one GSI file, without the ab suffix. Did I miss something? Is there no need for the different flavours any more, or do you just feel busy enough with that one version?
All my GSI builds are arm64-ab.
It is not guaranteed that you can upgrade from a13 to a16. You can try another version of a13 or immediately the next generation, a14, to see the result. Of course, it may not work anything other than the original Android or lose the device permanently, becoming non-functional. But knowledge always carries a risk.
https://sourceforge.net/projects/e-os/files/GSI/14/v3.7-a14-20260428-microG-gsi.img.xz/download
a15 and a16 will be updated.
Update to v3.7-a16
https://sourceforge.net/projects/e-os/files/GSI/16/v3.7-a16-20260512-microG-gsi.img.xz/download
Your a14 build working smoothly. But a16 have firewall no internet issue.
doze-off said fuck-bpf/packages/modules/Connectivity/0007-Support-non-working-BPF-maps-on-old-BPF-less-kernel.patch at sixteen-qpr2 · techyminati/fuck-bpf · GitHub this patch may fix this problem.
I`m on 4.14.x karnel. Please fix it.
How do I install your GSI build on a device running a normal Android? Can I just use adb install v3xxx.img.xz from the command line? Do I need to replace the original recovery with a TWRP recovery before I can use your GSI?
I appreciate any help.
I don’t use this phone anymore, but because of the new version with A16 I tested it. The telephony has not been tested with sim, but I’m pretty sure it will work without VoLTE. Some phone functions I see for the first time on A16 gsi! The only delay I see is in the animations of the stock launcher,but overall performance is GREAT ! If someone with a similar phone wants, I can do more extensive tests. Xperia 10 III
Update to v4.0-a16
https://sourceforge.net/projects/e-os/files/GSI/16/v4.0-a16-20260612-microG-gsi.img.xz/download
I followed this guide to install your GSI (v3.7-a16):
https://iamkaif.me/Guide-for-flashing-GSI-to-any-device/
without any problems. Thank you for putting in all the work to make this GSI available.
The only problem I have noticed so far is that I cannot use Android Auto. The phone sends me a notification that it is connected but I never see the setup screen. I noticed that all the notification settings for the Android Auto app are active but greyed out. That is not the case on my other /e/OS devices running community builds and on which Android Auto is working as expected.
Is there anything I can do to get Android Auto working with your GSI?
Currently I do not use Android Auto, I do not know what it could be. There are people on the forum who also have difficulty using this app. Some have been successful, so it’s worth asking.
4.0 update fixes UI animation sluggishness.