~/talk

Develop the Android Context Hub Runtime Environment (CHRE) Nanoapps in WebAssembly

links:none on file
slides:none on file

Project compiles unmodified CHRE nanoapps to WebAssembly using Wasm Micro Runtime (WAMR), preserving CHRE lifecycle and enabling interop with native nanoapps via a one-to-one wrapper per nanoapp that copies events into linear memory and maps nested C structs using static_assert checks. Runtime supports interpreter/JIT/AOT modes, runs on MCUs with a few hundred KB RAM, adds roughly ~300 KB memory increase and delivers about 2–11% runtime overhead in prototypes, proving a practical migration path while highlighting the cost of wrappers versus a native Wasm-native CHRE design.

AI-written summary · about

  1. 0:00CHRE and Nanoapps intro
  2. 1:46What is CHRE
  3. 3:10Why CHRE exists
  4. 4:55Nanoapp ecosystem challenges
  5. 5:59WebAssembly for Nanoapps
  6. 7:01CHRE on WebAssembly goals
  7. 8:25Why WAMR
  8. 10:12How Nanoapps work
  9. 12:00Moving Nanoapps to WASM
  10. 14:09Data structure solutions
  11. 16:47Event handling in WASM
  12. 19:03CHRE on WASM architecture
  13. 20:12Live WASM Nanoapp demos
  14. 21:16Memory and performance impact
  15. 21:58Project learnings and future
  16. 24:10Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.