# Android Android is Google's mobile operating-system ecosystem; it matters here as a device platform spanning controllers, alternative application distribution, and enterprise zero-touch enrollment. ## Historical and Technical Context The page appears to begin with a personal reminder and then pivots into controller interoperability. [[8BitDo|8BitDo]] built its reputation around retro-styled Bluetooth and USB controllers, adapters, and mod kits. Its official compatibility documentation repeatedly names Switch, Windows, macOS, Android, and Raspberry Pi, while product-specific exclusions often include Wii, Wii U, PlayStation, and Xbox; that distinction explains why the notebook lists both supported and questionable targets rather than merely copying a marketing page. [S01][S28] The likely task was to determine whether one controller family could become a **universal input layer** spanning consoles, computers, single-board computers, phones, and television boxes. ## Role in Scanned_20260730-1802 The primary identifying evidence appears on PDF page 2. A lined page in broad black marker. The upper quarter contains a small family-related note and a descending doodle at upper right. A horizontal gap separates it from a long compatibility list. Dashes function as bullets. “8BitDo” is emphasized with a leading dot and parenthetical gloss; the domain sits to the right. The layout reads as an expanding device-compatibility matrix rather than prose. Within that page, Android helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 2: "- Android mobile devices" **Evidentiary status:** Visible evidence: a mixed platform list under 8BitDo. Verified fact: compatibility varies by controller model and operating mode. Strong inference: the author was comparing controller reuse across heterogeneous hardware, perhaps for emulation, retro-gaming, or a unified media environment. The canonical name **Android** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers. ## Relationships On PDF page 2, Android appears in the same evidentiary cluster as [[8BitDo|8BitDo]], [[Bluetooth|Bluetooth]], [[Nintendo Wii|Nintendo Wii]], [[Nintendo Wii U|Nintendo Wii U]], [[Nintendo Switch|Nintendo Switch]], [[Joy-Con|Joy-Con]], [[Microsoft Windows|Microsoft Windows]], [[Raspberry Pi|Raspberry Pi]], [[macOS|macOS]], [[PlayStation|PlayStation]]. These links record page-level proximity and the reconstruction's systems map; they do not by themselves prove corporate ownership or a direct technical dependency. ## Cross-Notebook Significance The “[PERSON REDACTED]” fragment may connect to page 44, which records “[PERSON REDACTED] Real Number.” Here “Real” describes the number and is not a surname. The platform-spanning impulse anticipates pages 39-40, where “universal object interaction” and programmable interaction are treated as ontology problems rather than isolated device questions. ## Scanned_20260730-1706 Overlay **Source overlay:** [[Scanned_20260730-1706|Scanned_20260730-1706]] (specific PDF page references follow). `Scanned_20260730-1706.pdf`, PDF pages 5 and 31 add operational Android evidence. Page 5 records manual [[Access Point Name|APN]]/MMS provisioning for Mint Mobile, while page 31 preserves a sparse “Linux Android” UI fragment. This complements `Scanned_20260730-1802.pdf`, where Android appears in controller compatibility, enterprise zero-touch enrollment, and alternate app distribution: the first notebook emphasizes platform authority, while this one emphasizes restoring packet-data reachability. ## Missed Signals and Open Leads Resolve the upper-right doodle and the exact reading of “3M.” Identify which 8BitDo model was under consideration. Determine whether “Retro Freak” refers to Cyber Gadget’s multi-console emulation system or another product. ## Sources - [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF page 2. - `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`. - **[S01]** 8BitDo, “SN30 Pro FAQ”. https://api.8bitdo.com/faq/sn30-pro.html - **[S28]** 8BitDo, “M30 Bluetooth Controller FAQ”. https://api.8bitdo.com/faq/m30-bluetooth-controller.html ## Scanned_20260730-1314 overlay [[Scanned_20260730-1314#Scanned_20260730-1314.pdf — PDF page 3|Pages 3–6, 12–14, 17, and 37–41]]: Android serves as the notebook’s central substrate: handset identity and FRP lead into custom ROMs, packages, privileged system components, storage policy, and the graphics stack. **Relationship overlay:** [[LG K31]] · [[Factory Reset Protection]] · [[OmniROM]] · [[Android System UI]] · [[Gralloc]]. ## Scanned_20260730-1806 overlay [[Scanned_20260730-1806#Page 16 — `Scanned_20260730-1806.pdf`, PDF page 16|Pages 16–27]] move Android from a platform label to a layered forensic object. The notebook preserves a Moto G Stylus Android 10/API 29 build fingerprint, ART/APEX paths, kernel identity, FileProvider URI, APK dependencies, manifest components, package-state flags, shared UIDs, `android.uid.system`, `coreApp`, carrier libraries, repositories, and developer domains. **Relationship overlay:** [[Moto G Stylus (2021)]] · [[Android Build Fingerprint]] · [[Android Package State Legend]] · [[Mobile Application Forensics]] · [[Package Provenance]] · [[Software Bill of Materials]].