GitPedia

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.

From GloDroid·Updated June 14, 2026·View on GitHub·

**NOTE:** If you are looking for Glodroid 1.0, please navigate to the [master branch](https://github.com/GloDroid/glodroid_manifest/tree/master) The project is first published in 2019. Key topics include: android, aosp, manifest, orange-pi, pinephone.

Latest release: v2.0GloDroid 2.0
April 27, 2023View Changelog →

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

GloDroid 2.0

Ports

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

PinePhone

PinePhone-Pro

Raspberry PI 4

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.

Contributors

Showing top 1 contributor by commit count.

View all contributors on GitHub →

This article is auto-generated from GloDroid/glodroid_manifest via the GitHub API.Last fetched: 6/21/2026