16k page size support
summary
Android moves to 16 KB base pages and hits two concrete barriers: a USB host controller rejects transfers larger than 4 KB (workaround requires roughly 20 lines split into eight patches and may affect 1–20 million devices), and existing 4 KB ELF binaries fail to load because program headers and segment alignments break permissions. Attempts include setting all segments R+X (rejected for security), ELF binary rewriting (using objdump, recursive disassembly; binary rewriting fails due to code+data and dynamic relocations), and running 4 KB apps under KVM/PKVM (loses 16 KB performance).
AI-written summary · about
chapters (7)
- 0:00Introduction and problem overview
- 2:10Maintainer concerns and hardware quirks
- 5:26Compatibility issues with 4K binaries
- 9:04Potential solutions and community input
- 13:30Technical challenges in binary analysis
- 15:39Alternative approaches and security trade-offs
- 17:12Closing remarks and next steps
related talks
38mEmbracing 16 KB Page Sizes in Android
21mPrepare your app for the 16 KB page migration
26mBootloops & Coffee: The Daily Grind of an AOSP Developer
08mKeep your app from failing in a 64-bit only world
40m640K ought to be enough for anyone
36mAndroid memory and games
44mVirtualization for the Masses: Exposing KVM on Android
32mMoving with the Android ecosystem towards a 64-bit r-Evolution