First of all thanks @Null for taking the time to create a GSI
Once you have checked the code may be you can do a merge request for it into our Gitlab. We can have the team members also check it out and integrate both into the same build. That way it is a win win for all.
@Manoj Thanks!!
The GSI I made is not perfect, on some devices it does not boot because /e/OS really has a lot going on for itself, it is not as straightforward as pure Lineage!
I will fork the relevant files in your gitlab and push the changes needed to make the GSI boot on most devices though.
I like /e/OS and like the concept of it; I think it is beautifully designed so it’s a real honor to even have my work considered
2 Likes
The GSI as you mentioned in one of your posts is is not a replacement for the ROM. I do not expect even our GSI to be perfect. It is just to give the user a feel of the device and the OS. I was checking with our developers and they are still not removed all the chinks in the build. Let see how it goes. For now users have your GSI to test and check out. Our problem would be to give dedicated developers for this project as this was not taken as a top priority task.
2 Likes
As a rule, a GSI is not a real replacement for a custom ROM, but if no custom ROM is available and it runs reasonably well, then for me it is 1,001x better than a stock ROM.
I have a dozen smartphones and tablets with GSI from @AndyYan, @Ponces and @iodeOS - and all elementary functions work flawlessly. The @iodeOS A/B GSI even works with OTA updates if the device meets all the requirements.
Here is a dump of the changes I made:
Before anything, the following additions to manifests are needed
<project name="AndyCGYan/android_packages_apps_QcRilAm" path="packages/apps/QcRilAm" remote="github" revision="master" />
<project name="TrebleDroid/vendor_hardware_overlay" path="vendor/hardware_overlay" remote="github" revision="pie" />
<remove-project name="LineageOS/android_packages_apps_Camera2" />
<remote name="gitlab" fetch="https://gitlab.com/" />
<project name="TrebleDroid/vendor_interfaces" path="vendor/interfaces" remote="github" revision="android-14.0" />
<project name="platform/prebuilts/vndk/v28" path="prebuilts/vndk/v28" remote="aosp" clone-depth="1" revision="204f1bad00aaf480ba33233f7b8c2ddaa03155dd" />
<project name="phhusson/vendor_vndk-tests" path="vendor/vndk-tests" remote="github" revision="master" />
4: Overlay for SystemUI elements
placed in vendor/hardware_overlay
5: Removed references to the following in hardware/lineage/compat/Android.bp:
prebuilt_libprotobuf-cpp-full-vendorcompat
prebuilt_libprotobuf-cpp-lite-vendorcompat
VNDK28 uses the prebuilt .so files.
6: In the vendor/hardware_overlay folder, delete Navbar and Trebleapp, they will cause breakage, Android has a default overlay manager that will handle it there is no need for Trebleapp
With this, your GSI should build and boot.
1 Like
Maybe you should add this post under the GSI category as this is a weekly report and will be closed. There it could be helpful for other trying to build and test GSI’s
@Null maybe add this too to the bringup thread?
(you could fork andys unified repo and do numbered file-based patches (the framework_base sensor change) - easier diffing/collab/upstreaming)