Speaker
Description
While there are only a small number of devboards in AOSP, a number of vendors and community members have created external projects to enable their devices against AOSP.
Some examples:
- The GloDroid project: https://github.com/glodroid/glodroid_manifest
- android-rpi: https://github.com/android-rpi
- PocoF1 AOSP: https://github.com/pundiramit/device-xiaomi-beryllium/blob/master/README.md
- OnePlus AOSP: https://github.com/calebccff/android_device_generic_sdm845
After seeing some of the excellent work being done in the GloDroid project and realizing there is a fair amount of duplicated effort in keeping a device current with AOSP, I thought there might be a better opportunity for devboard vendors and community members who are focusing on AOSP to collaborate.
I'll cover my thoughts on what sort of collaboration might be useful, along with some of the potential pitfalls, and see what interest or ideas folks have on how we might work together and share more experience and knowledge as a community.
I hope have discussion on the topic from GloDroid maintainers, LineageOS developers, as well as other Linaro and Google developers and hopefully more.
| I agree to abide by the anti-harassment policy | I agree |
|---|
