OSS Tanbou

Android Frameworks Base

inspect and modify core Android framework APIs and system services within a full AOSP build

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
10,820
Primary language
Java
License
Not determined
Repository last updated
Nov 12, 2025
On this page

Overview

frameworks/base is a major AOSP source tree implementing Android framework APIs, System APIs, system services, resources, permissions, and other platform code. It is used for Android OS development rather than as an application dependency.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Trace Android APIs to their framework implementation

AOSP defines the Android framework as the Java classes, interfaces, and other precompiled code on which apps are built. This source tree lets platform developers inspect implementation behind public Android APIs and OEM-facing System APIs.

Sources: [2]

Investigate framework-to-system-service behavior

Framework APIs communicate with system services such as system_server components to access lower layers. frameworks/base contains a large portion of the platform-side API, service, resource, and permission implementation.

Sources: [2]

Best fit

Fits Android OS, OEM customization, and platform-level debugging

This is not an app dependency. It is relevant to AOSP builds, framework modifications, OEM work, and source-level investigation of Android platform behavior.

Sources: [2][4]

Before adoption

The GitHub mirror is archived and is not the current upstream workflow

The canonical GitHub repository is archived, but AOSP development continues. Official documentation directs developers to sync the android-latest-release manifest with Repo, so the mirror's archive state should not be interpreted as end-of-life for the Android framework.

Sources: [1][3][5]

Build frameworks/base as part of the full AOSP tree

The official workflow initializes platform/manifest at android-latest-release, runs repo sync, then uses build/envsetup.sh, lunch, and m. Cloning this repository alone does not reproduce a normal platform build.

Sources: [3][4]

AOSP builds require substantial Linux workstation resources

Current official requirements call for a 64-bit x86 Linux workstation, at least 400 GB of free disk space, and a minimum of 64 GB of RAM.

Sources: [3]

Repository-wide license metadata remains NOASSERTION

The root includes MODULE_LICENSE_APACHE2 and an Apache-2.0 NOTICE, but the large platform tree also contains third-party notices. The catalog preserves GitHub's NOASSERTION metadata and downstream redistribution should review licenses at the relevant file or module level.

Sources: [1][6]

Official sources

  1. [1]aosp-mirror/platform_frameworks_base(2026-10-03)
  2. [2]AOSP architecture overview(2026-10-03)
  3. [3]Try Android development(2026-10-03)
  4. [4]Build Android(2026-10-03)
  5. [5]AOSP FAQ — android-latest-release(2026-10-03)
  6. [6]frameworks/base NOTICE(2026-10-03)
Supplemental curator note

This is not an app library; it is a large source tree for Android OS framework implementation. The GitHub mirror is archived, so current development should sync the official AOSP android-latest-release manifest with Repo instead of treating this mirror as the source of truth.

Try it in 3 steps

  1. 1

    Prepare a Linux AOSP workstation and install Repo

    Current official guidance calls for 64-bit x86 Linux, at least 400 GB of free disk space, and 64 GB of RAM.

    sudo apt-get update && sudo apt-get install repo
  2. 2

    Sync android-latest-release

    Fetch the full AOSP tree; frameworks/base is one project inside this checkout.

    mkdir -p ~/aosp && cd ~/aosp && repo init --partial-clone -b android-latest-release -u https://android.googlesource.com/platform/manifest && repo sync -c -j8
  3. 3

    Choose a target and build AOSP

    Use the documented Cuttlefish target example and build the platform including frameworks/base.

    source build/envsetup.sh && lunch aosp_cf_x86_64_only_phone-aosp_current-userdebug && m
Check the official README

Growth

Growth trends · Last 30 days

10,820 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
0
Open PRs
8

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data
Stars
10,820
Forks
6,541
Watchers
1
Open issues
0
Owner type
Organization
Primary language
Java
License
Not determined
Repository last updated
Nov 12, 2025
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?