AIC: Hosting Multiple Interactive Physical Clients on Single Computing Platform for IOT
summary
AIC runs multiple containerized Android instances on one Linux kernel using namespaces and cgroups, assigns dedicated devices (HDMI, USB cameras, touch) or shared devices via a display composer merging backend, and implements a per-instance binder device to avoid massive kernel changes. A proof-of-concept cloud gaming setup captures touch, routes input to specific Android instances, sends rendered frames to a GPU encoder and streams video; performance is near-native and maintenance effort is reduced, security isolation improvements remain planned.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:59NEW USE CASES FOR ANDROID
- 5:12EASIEST SOLUTION: MULTIPLE DEVICES
- 6:22SOLUTION: ENHANCE ANDROID FRAMEWORK
- 8:11OUR SOLUTION
- 9:56ARCHITECTURE
- 14:28IMPLEMENTATION
- 14:38CONTAINER
- 16:19KERNEL
- 18:22I/O DEVICE VIRTUALIZATION
- 19:44DEDICATED I/O DEVICES: PASS-THROUGH
- 20:27SHARED 1/0 DEVICES: SHARING GRAPHIC AND DISPLAY
- 23:34AOSP:LOW MEMORY KILLER
- 25:09USE CASE: CLOUD GAMING
- 27:20SUMMARY
related talks
40mLightweight and Easy to Integration Into Embedded System Using Linux Container.
44mACRN: A Big Little Hypervisor for IoT Development
40mCase Study for Resource Control in Embedded Linux Container Integration
17mTowards Intelligent Automobile Cockpit via A New Container Architecture
34mIntegrated Physical Computing on the Web
40mCloud-Native Automotive Edge: AGL for Software-Defined Vehicles
37mAndroid Industrial: Real-time data visualization
28mXen in OSS based In--Vehicle Infotainment Systems