# Android Open Source Project ## Identification The Android Open Source Project is the open-source base of Android. This notebook places it inside a device-sovereignty stack involving open repositories, ADB, SELinux, LineageOS, custom ROMs, Linux phones, automated testing, FOSS browsers, and launcher replacement. ## Notebook evidence - [[Scanned_20260730-1659#PDF page 25 — Storage Access Framework and open mobile infrastructure map|PDF page 25: Storage Access Framework and open mobile infrastructure map]] — The page sketches an unusually coherent **sovereign-mobile stack**. Android’s Storage Access Framework mediates user-approved document access; Android documentation requires third-party apps to use it for portable storage. F-Droid/APKPure/APKMirror supply software, AOSP supplies the base operating system, Ubuntu Touch/PinePhone/Librem 5 represent alternative mobile platforms and hardware, Firebase supplies backend services, and Tor/OpenVPN/FreedomBox supply privacy and self-hosting. - [[Scanned_20260730-1659#PDF page 26 — ADB over TCP, LineageOS, SELinux, and ownCloud|PDF page 26: ADB over TCP, LineageOS, SELinux, and ownCloud]] — ADB can place its daemon in TCP mode on port 5555, although modern Android strongly prefers authenticated wireless-debugging workflows and warns that network exposure must be controlled. LineageOS is the community successor to CyanogenMod; SELinux remains the mandatory-access-control substrate. `android.owncloud.com` points toward self-hosted file synchronization. The page was integrating **debug transport, alternate firmware, policy enforcement, and private cloud** into one mobile-control architecture. - [[Scanned_20260730-1659#PDF page 27 — Android package names, Dr. Ketan ROM, and Tasker security tools|PDF page 27: Android package names, Dr. Ketan ROM, and Tasker security tools]] — The three package names identify Android personalization/System UI and the Secure Settings plug-in used by automation tools such as Tasker. `N986B` corresponds to the international Samsung Galaxy Note20 Ultra family, and Dr. Ketan is associated with custom Samsung ROM work. Samsara, Dr.Web, and Car Home Ultra broaden the page into fleet/telemetry, antivirus, and automotive interfaces. The source supports a customization/security test environment, not a claim that all packages coexisted on one device. - [[Scanned_20260730-1659#PDF page 28 — Pebble, Appium, XDA, Settings+, and realme UI|PDF page 28: Pebble, Appium, XDA, Settings+, and realme UI]] — Pebble automation, Appium’s desktop server GUI, XDA, Settings+, and realme UI place this page in **cross-device interface testing**. Appium is an automation framework for mobile application testing; XDA is a developer community around Android modification. The parenthetical “Batman/cricket” cannot safely be mapped to Rushikesh Kamewar or a package without more evidence. - [[Scanned_20260730-1659#PDF page 29 — Browser interception and FOSS download tools|PDF page 29: Browser interception and FOSS download tools]] — The page lists applications for intercepting share intents, downloading, and browsing through open-source or lightweight clients, then records One UI as the operating context. This is a user-level complement to the lower-level ADB/SELinux pages: instead of modifying the platform, it maps how content enters and leaves applications. - [[Scanned_20260730-1659#PDF page 30 — Ingenium unlock-word sequence and Dr. Ketan reference|PDF page 30: Ingenium unlock-word sequence and Dr. Ketan reference]] — The numbered words are structured like passphrases, activation words, game clues, or command vocabulary—many mean opening, freedom, or power. Because the sequence includes repeated `Alohomora` and a package-like identifier, the strongest interpretation is an **unlock/activation codebook** associated with an app or ROM workflow. It is not treated as a credential because the page does not label the words as a password, but the sequence remains security-sensitive contextually and is not generalized beyond the source. - [[Scanned_20260730-1659#PDF page 31 — Android launcher sizes, Gboard, and graphics-driver preferences|PDF page 31: Android launcher sizes, Gboard, and graphics-driver preferences]] — Launcher names and rough sizes are being compared as interface substrates, while Gboard and graphics-driver preference extend the comparison from home screen to input and rendering. The `Dev No!` notation may indicate a warning not to change a developer option. The page captures a practical concern with **how much of the visible Android experience can be replaced without destabilizing graphics**. - [[Scanned_20260730-1659#PDF page 32 — Android launcher survey headed APUS|PDF page 32: Android launcher survey headed APUS]] — This is a broader launcher taxonomy: feature-dense dashboards, Pixel emulations, tablet launchers, accessibility-oriented large interfaces, and minimalist designs. APUS is singled out at the top, anticipating the APUS corporate notes on pages 68–69. The page supports a sustained inquiry into the launcher as a **governance layer over Android**—controlling search, recommendations, app discovery, telemetry, and visual identity rather than merely icons. - [[Scanned_20260730-1659#PDF page 43 — CyanogenMod/AOSP chain to OWASP Goat training systems|PDF page 43: CyanogenMod/AOSP chain to OWASP Goat training systems]] — CyanogenMod was an aftermarket Android distribution whose community lineage continued as LineageOS; AOSP is Android’s open-source platform base. OWASP’s iGoat and WebGoat are intentionally insecure training applications, while CloudGoat provides vulnerable cloud scenarios. The chain shows a deliberate lab concept: root a device, install a controllable OS, then use vulnerable targets to study exploitation and defense. ## Relationships and overlays The source places this record in an evidence cluster with [[Action Launcher|Action Launcher]] · [[AIO Launcher|AIO Launcher]] · [[Alohomora|Alohomora]] · [[Android Debug Bridge|Android Debug Bridge]] · [[Android Graphics Driver Preferences|Android Graphics Driver Preferences]] · [[Android Launcher|Android Launcher]] · [[Android Package Name|Android Package Name]] · [[Android Rooting|Android Rooting]] · [[APKMirror|APKMirror]] · [[APKPure|APKPure]] · [[Appium|Appium]] · [[APUS Launcher|APUS Launcher]] · [[BlackBerry Launcher|BlackBerry Launcher]] · [[BLU Products|BLU Products]] · [[Browser Interception|Browser Interception]] · [[Car Home Ultra|Car Home Ultra]] · [[Custom Pixel Launcher|Custom Pixel Launcher]] · [[CyanogenMod|CyanogenMod]]. The occurrence contributes to the notebook's larger model of [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Continuity Architecture|continuity architecture]]. ## Evidentiary status and open leads Determine whether this was a deployable architecture or a survey; identify the intended self-hosted alternative to Firebase. ## Source - [[Scanned_20260730-1659|Scanned_20260730-1659]] ## Scanned_20260730-1946 overlay PDF pages 2 and 6 record `AOSP`, with page 2 expanding it incorrectly as “Android Operating System Project.” The faithful quotation remains unchanged; the canonical expansion is **Android Open Source Project**. In this notebook AOSP is not isolated: it sits within a portability stack spanning OpenGL ES, Metal, Wayland/XWayland, desktop libraries, device filesystems, and later Android reverse-engineering tools. The pages document research and dependency mapping. They do not establish that a custom AOSP build was compiled, installed, or deployed on a particular device.