search

GloDroid / glodroid_manifest

Android port that aims to bring both user- and developer-friendly experience in using AOSP with a set of single-board computers (SBC), phones and other devices.
471 stars 67 forks source link

Build using /e/OS manifest! - Feature Request #173

Closed erikd256 closed 2 years ago

erikd256 commented 2 years ago

Would you like to try out this?

https://gitlab.e.foundation/pinephone/

It is /e/OS, which is waaaay better than AOSP. Maybe you could provide also an /e/OS image on top of the AOSP image still being offered as option?

rsglobal commented 2 years ago

Hi,

AOSP is the mainline while lineage/e. are forks. Our mission is to create foss vendor images. Mission of e. Is to somehow customize system/product images.

In the end we want to be gsi compatible, therefore lineage/e/other custom forks can mix their system/product images with glodroid vendor image/platform images.

Also looks like /e/ does blame Google for spying, while we are trying to collaborate with Google (upstreaming to AOSP is an important part of our activities) Therefore combine both e and glodroid here isn't a good idea for our progress.