Q&A: Android engineers Dave Burke and Iliyan Malchev on “Generic Kernel Image” for Android, hidden developer options like “Gabeldorsche” in Android 11, and more
Ron Amadeo / Ars Technica : Tweets: @mishaalrahman and @somospostpc Tweets: Mishaal Rahman / @mishaalrahman : Relevant quote from Iliyan Malchev (@imalchev) from @RonAmadeo's interview for @arstechnica: “Going into the next Android release, we're aiming to have devices actually shipping with these Generic Kernel Images.” https://arstechnica.com/... https://twitter.com/... Alex B / @somospostpc : Android team talks about finishing Android 11 after an abrupt switch to remote working, how they developed the Covid tracking stuff with Apple, Project Mainline (the new fast update mechanism) and more. Super interesting https://arstechnica.com/... https://twitter.com/...
Context & Ripple Effects
This interview is the third chapter in Google's long campaign to decouple Android's software stack from the hardware it runs on. Project Treble first split OEM implementations from the OS in 2017, and last year's Q&A on Project Mainline extended that logic to letting Google push updates to individual OS modules. Now kernel lead Iliyan Malchev says the team is aiming for devices actually shipping with Generic Kernel Images in the next Android release — pulling even the Linux kernel under a common, updatable umbrella.
The interview also lands just after Android 11 crossed the finish line: the team released it following an abrupt switch to remote working, building on the messaging-and-bubbles groundwork of Android 11 Beta 1. Hidden flags like the 'Gabeldorsche' developer option give a rare look at Bluetooth work still in flight, and Burke confirms the exposure-tracking API was built jointly with Apple.
First-order effects
- OEMs and silicon vendors face a concrete deadline: Malchev says devices should ship with Generic Kernel Images in the next Android release, ending per-device kernel forks as the default.
- The Android 11 team has already shipped the release despite the mid-cycle pivot to remote work, so the update pipeline Pixel users saw at Beta 1 proceeds without a pandemic-induced slip being acknowledged.
Second-order effects
- With the kernel unified the way Treble and Mainline unified higher layers, security patches can flow from Google straight to more devices without waiting on each SoC vendor or OEM to rebuild custom kernels, squeezing out one of the main justifications for slow Android update rollouts.
- Apple gains a template from the joint COVID-19 exposure-tracking work for cross-platform cooperation that neither company would attempt through normal OS channels, since both had to ship it outside their usual release cadences.
Third-order effects
- If GKI ships as planned, Google will have detached the kernel, the OS framework, and individual modules from hardware vendors in sequence — concentrating long-term update authority at Google and reducing OEM differentiation to what sits above the common base.
- A common kernel image makes Android's fragmentation problem progressively an application-layer question, which is where governance fights over who controls platform APIs tend to migrate next.
The trend: Android is being rebuilt layer by layer — Treble, then Mainline, now the kernel itself — so that Google, not device makers, controls how far down the stack updates reach.