2. What and Why
1
What is the
problem? Why do
we care to solve
it?
Userspace
2
What is the
solution?
What is the
timeframe?
Kernel
3
Tackling kernel
fragmentation
Results
4
Some stats and
early results
I Agenda
7. Faster Device Launches on Latest Google SoC OEM users
Easier Device Upgrades Google
Better Quality Google SoC OEM users
BEtter Security (esp. Kernel) Google SoC OEM users
I Who Wants What
13. ● Short product cycles
● No Single Android OS to update
○ Large AOSP Delta
○ SoC Support not universal
● Certification: Carrier, Regulatory, CTS
● QA
● Support (Call Center), OTA Infrastructure, etc...
"HALs"
ExtAOSP
I Difficult means Expensive
17. kernel driverdriverdriver driverdriver
libc
other libraries
activity
Media
Server
System
Server
Camera
Server
Audio
Server
Surface
Flinger
OMX
...
...
camera
HAL
audio
HAL gralloc
hwc
sensor
HAL etc
ART
API java.* android.*
GL
HAL
Binder
I Android Architecture Pre-O
18. kernel driverdriverdriver driverdriver
libc
other libraries
activity
Media
Server
System
Server
Camera
Server
Audio
Server
Surface
Flinger
OMX
...
...camera
HAL
audio
HAL
gralloc
hwc
sensor
HAL etc
ART
API java.* android.*
GL
HAL
Binder
Binder
I Android Architecture Post-O
19. I The Vendor Test Suite
CTS
VTS
Android
Framework
VINTF
Implementation
General
System
Image
VINTF
Implementation
CTS on AOSP
<Before Oreo> <Android Oreo>
HAL Kernel Library
21. Q3 ACP ALL HANDS
Multiple implementations of same functionality
Drive convergence between AOSP and Framework Variants
Forum involving major contributors to AOSP
Feature review, approval, (re)engineering
Non-US regulatory requirements
Extensions to Bluetooth, Telephony, Dialer, SysUI, Home Screen
I Upstreaming
23. Must pass Vendor Test Suite (VTS; tests for HALs) for approval
All OEM devices launched with O must implement Treble HALs
Must pass CTS on AOSP
Q3 ACP ALL HANDS
This includes older SoCs that will be used by OEMs to launch O-based
devices
I Compatibility Requirements
25. ● Release uptake is 6 months to a year
○ Mostly just flagships
● Solving the problem forwards
● Customer pull is strong
● Attention Span outside and within
● Addressing fragmentation is a MUST
I The One-Release Fix
27. Existing LTS is not Enough
Device Kernel
Stable Long Term Support
Android Common
SoC Kernel
Device
Release
Device
Update
Clone Merge Cherry-Pick
Device
Update
Device
Update
Device
Update
28. Announcing 6-year LTS
Device Kernel
Stable Long Term Support
Android Common
SoC Kernel
Device
Release
Device
Update
Clone Merge Cherry-Pick
Device
Update
Device
Update
Device
Update
34. Clone Merge Cherry-Pick
Linux 4.9.y
Android Common 4.9
msm-4.9
(Common SoC
Kernel)
MSMXXXX based
device 1
MSMXXXX based
device 2
MSMXXXX based
device 3
Linux 4.9.y xLTS
backports
exynos-4.9
(Common SoC
Kernel)
mediatek-4.9
(Common SoC
Kernel)
I Kernel Unification
35. I There's More To Do
● Continued work with SoC Vendors
● Continued work on Kernel Unification
● Expanding test coverage
● Bringing the ecosystem together with Linaro