Android's CHRE and Open Source Frameworks
summary
Runtime that hosts nanoapps and arbitrates sensor access so small apps request streams and the system picks a single hardware rate rather than duplicating drivers, demonstrated with a concrete arbitration example of 100 hz vs 200 hz. Sensor subsystem provides virtual sensors (drop, step, hinge angle), a host message API with default buffer 4000 bytes, and Pigweed RPC/HDLC for testing. Some pieces are implemented and working; dynamic loading and hotplug remain in progress.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:56Building a fitness tracker
- 2:40The components..
- 3:43Top level view
- 5:09Context Hub Runtime Environment
- 8:55Nanoapp flow
- 10:21Loading nanoapps
- 12:57Communicating off chip
- 13:53What is pigweed
- 16:06Nanoapps additional resources
- 18:01Physical sensors
- 19:54Writing custom virtual sensors
- 21:03What sensors to expect?
- 22:07Using the sensor subsystem
- 23:50Other Frameworks
related talks
29mDevelop the Android Context Hub Runtime Environment (CHRE) Nanoapps in WebAssembly
37mAndroid Industrial: Real-time data visualization
43mUsing Android as OS for a single purpose system
40mAndroid high performance baby
01h 08mAndroid Plateform Anatomy
48mFramework Fireside Chat
15mCan mainline Linux run on Android without vendor hooks
35mIntegrating Sensors into Android Hardware