Using Android as OS for a single purpose system
summary
Built a telepresence endpoint using AOSP as the OS: development uses Android Studio and virtual devices, JNI for C/C++ HDMI and driver hooks, and a custom proxy resolver to emulate PAC behavior. The team ships and supports the product but later replaces Android with an in‑house Linux stack because of missing APIs (HDMI, Ethernet, temperature sensors), MAC/privacy changes, brittle Bionic pthread/real‑time limits, and vendor binary drivers tied to Android releases. headless Android approaches and libhybris are explored as workarounds.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:26Outline
- 1:15History
- 7:05The Android Open Source Project (AOSP)
- 10:44Android/Linux differences
- 13:36Bionic vs glibc
- 15:40Hardware independence
- 16:48Vendor support
- 18:12Tooling
- 19:46Android APIs
- 21:17Community
- 22:24API behaviour
- 24:29Platform
- 26:09HTTP Proxy
- 28:47Hardware information
- 31:03Java Native Interface (JNI)
- 34:28AOSP Upgrade
- 36:57Android toolchain
- 39:32Summary
- 40:47Maybe?
- 42:23Resources
- 42:46Questions?
related talks
12mAndroid AOSP TV, making Android TV Boxes and Smart TVs better
13mPorting Android Automotive on Xen
37mOpen source and Android Automotive OS
48mAn Introduction to Android Automotive OS
46mWhy Projects Succeed: Lessons Learned from the Android OS
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...
17mDeploying Android AOSP at Scale
38mHow to Enable Android (AOSP) on Your Developer Board