https://github.com/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.
https://github.com/glodroid/glodroid_manifest

android aosp manifest orange-pi pinephone pinephone-pro raspberry-pi raspberrypi rpi4 sunxi

Last synced: about 21 hours ago
JSON representation

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.

• Host: GitHub
• URL: https://github.com/glodroid/glodroid_manifest
• Owner: GloDroid
• Created: 2019-11-14T13:25:57.000Z (about 5 years ago)
• Default Branch: v2.0
• Last Pushed: 2023-12-17T13:15:08.000Z (about 1 year ago)
• Last Synced: 2024-12-22T02:08:45.090Z (about 21 hours ago)
• Topics: android, aosp, manifest, orange-pi, pinephone, pinephone-pro, raspberry-pi, raspberrypi, rpi4, sunxi
• Homepage:
• Size: 188 KB
• Stars: 476
• Watchers: 33
• Forks: 66
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml

Awesome Lists containing this project

README

        
**NOTE:** If you are looking for Glodroid 1.0, please navigate to the

[master branch](https://github.com/GloDroid/glodroid_manifest/tree/master)

# GloDroid 2.0

## Ports

At this moment we ported the following devices to GloDroid 2.0:

[PinePhone](https://github.com/GloDroidCommunity/pine64-pinephone)

[PinePhone-Pro](https://github.com/GloDroidCommunity/pine64-pinephonepro)

[Raspberry PI 4](https://github.com/GloDroidCommunity/raspberry-pi)

We are currently working on porting the remaining devices / adding new ones.

## Introduction

GloDroid is an 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.

Version 2.0 brings a mono-repository approach, which gives the following benefits

compared to the classic manifest-based approach:

1. No need to maintain forks. All necessary delta is stored in the form of patches.

   Benefits: Such patches are a lot easier to maintain. No need to merge/rebase

   fork repositories. Patches are much easier to review by external auditors to

   ensure high project trustworthiness.

2. Atomic changes.

   Benefits: Classic approach may require synchronization of multiple changes in

   different repositories. Gerrit has a "Topic: " field for this purpose, but

   GitHub/GitLab doesn't support such flow. The mono-repository approach makes it possible.

   CI is much easier to integrate.

3. Decouple devices or devices group from each other.

   As time has shown, maintaining all devices under the same manifest is impractical.

   It significantly increases the release cycle since all devices must be validated before

   publishing. Also, some devices may require custom patches on top of AOSP or vendor

   components, while others don't.

   It also allows different people to maintain different devices independently,

   benefiting from using a common code, without waiting for each other.