Google is working on a new developer option in Android that will swap out your device's Linux kernel with one that uses a 16K page size. Compiling the kernel to use 16K pages could provide a significant performance improvement but also break many apps. A page is a fixed-length contiguous block of virtual memory. Android currently uses a 4K page size, while iOS and macOS use a 16K page size. Some workloads benefit significantly by using a larger page size, like kernel compilation, as shown below: But although ARM64 Linux binaries are compatible with 4K, 16K, and 64K pages by default, many native apps and Android OS components that assume a 4K page size might just break. (These comments by the lead Asahi Linux developer go into a lot more detail about the potential challenges: github.com/k3s-io/k3s/issues… reddit.com/r/AsahiLinux/comm…) This is why Google is incrementally experimenting with 16K page size support in Android. They've been working on compiling the kernel with a 16K page size and fixing various issues since last October, but late last week, a Googler submitted a series of patches to AOSP (that have not yet been merged) that add a "developer option for booting with 16K pages." 16k_dev_ui: android-review.googlesource.… If/when these patches are merged, a new "enable 16K pages" toggle will be added under Settings > System > Developer Options. When you toggle this option, Android will warn you that "some applications may not be compatible with this mode." Android will then call update_engine - the system OTA service - to swap the kernel to a 16K compatible one. I have no idea if/when this developer option will land, nor whether Google will actually go through with changing to a 16K page size compatible kernel. If they do, it won't be a while and the transition will be slow given how much might break.