AOSP (Android 17)

for Raspberry Pi 4

Here’s my build of AOSP (Android 17) for Raspberry Pi 4 Model B, Pi 400, and Compute Module 4. It’s for advanced users only. Pi 4 model with at least 2GB of RAM is required to run this build.

Important! Raspberry Pi hardware specific implementation in this build is based on source code released on my Raspberry Vanilla project but this build offers various additional features and enhancements. This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build! You can contact me by email to discuss creating customized Android builds for commercial purposes.

screenshot

Do not mirror my builds! Please post a link to this page instead.

AOSP17-20261030-KonstaKANG-rpi4.zip
sha256:9c02408206053b8bcbf7591a02d8d28d09becf17cfa522f52a945c5f87deb709

Note! It’s not possible to OTA update from builds older than 20251124. Clean installation is required!

AOSP17-20261030-KonstaKANG-rpi4-ota.zip (recovery flashable OTA package)
sha256:768c5dc60c74dac7ff5f30d56d8017f47f6a46d5d7dd4ea5e4cd2d9b02bed295

Working:

  • Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headphones, etc)
  • Audio DAC (using GPIO DACs e.g. Hifiberry DAC+)
  • Bluetooth (and bluetooth tethering)
  • Camera (using official Pi camera modules & UVC USB webcams)
  • GPIO
  • GPS (using external USB modules e.g. U-Blox 7)
  • Ethernet
  • Hardware accelerated graphics (V3D, OpenGL & Vulkan)
  • Hardware video decoding (H.265 decoding)
  • HDMI display (and HDMI-CEC)
  • I2C
  • IR remotes (using external GPIO IR modules e.g. TSOP4838)
  • RTC (using external GPIO I2C modules e.g. DS3231)
  • Sensors (using external GPIO I2C modules e.g. MPU6050, LSM6DS3, LSM303DLHC, BME280/BMP280, and APDS9930 accelerometer, gyroscope, magnetometer, temperature, pressure, humidity, ambient light, and proximity)
  • Serial console (using external GPIO serial console adapters e.g. PL2303)
  • SPI
  • Touchscreen/multi-touch (official 7” touchscreen, USB touchscreens, Waveshare SPI touchscreens)
  • USB (mouse, keyboard, storage, etc)
  • USB-C (ADB, MTP, PTP, USB tethering)
  • Wifi (and wifi tethering)

Issues:

  • H.264 hardware video decoding & encoding is not supported
  • Various issues with CSI camera modules
  • SELinux is in permissive mode
  • Encrypting userdata is not supported
  • and more…

Sources:


How to install:

  1. Follow the official Raspberry Pi instructions for writing the image to the SD card.

How to update:

You can also update to newer builds using recovery flashable OTA packages.

Note! It’s not possible to OTA update from builds older than 20251124. Clean installation is required!

  1. Download AOSP17-xxxxxxxx-KonstaKANG-rpi4-ota.zip and save it to your device’s internal storage or use an external USB drive
  2. Boot to recovery mode (see FAQ)
  3. Install AOSP17-xxxxxxxx-KonstaKANG-rpi4-ota.zip from your selected storage
  4. (Flash GApps/Magisk/Widevine/other add-ons you had previously installed)
  5. Boot out of recovery (see FAQ)

Changes that are backed up and restored flashing OTAs:

  • Device specific settings changed using Settings -> System -> Raspberry Pi settings
  • Manual changes to /boot/resolution.txt and /boot/rc_keymap.txt
  • USB boot configuration in /boot/config.txt
  • User specific options in /boot/config_user.txt

Changes that are not backed up and restored flashing OTAs:

  • Manual changes to /boot/config.txt (and any other manual changes to /boot partition)
  • GApps
  • Magisk
  • Widevine

FAQ:

Q: How to find several Raspberry Pi specific settings options?
A: Settings -> System -> Raspberry Pi settings

Most options in this menu require you to reboot your device for the setting to take effect.

Q: How to enable developer options?
A: Settings -> About tablet -> Click ‘Build number’ several times.

Q: How to enable root access?
A: You can have root access via ADB after adb root, SSH (see FAQ below), or serial console. It is also possible to install Magisk following instructions later in the FAQ.

Q: My display is not working. I can only see the rainbow screen but no Android boot animation. What should I do?
A: This build only supports HDMI displays that report supported resolutions using EDID. 1920x1080 resolution is used by default with this build. You can change value in /boot/resolution.txt to use a different resolution that your display supports. Removing /boot/resolution.txt will use the preferred resolution of your display.

Q: How to use DSI touchscreen displays?
A: You can enable required configurations using a settings option found in Settings -> System -> Raspberry Pi settings -> DSI display. You need to disconnect any HDMI display when using the DSI display.

Q: How to use desktop mode on primary display?
A: Enable Settings -> System -> Raspberry Pi settings -> Desktop mode and reboot the device.

Q: Raspberry Pi doesn’t have a power button. How to power off/reboot device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.

Q: How to create a DIY hardware power button?
A: You can send power button events by connecting GPIO21 to ground.

fritzing

You can enable the feature by using a settings option found in Settings -> System -> Raspberry Pi settings -> Power button.

You can also use the DIY power button to boot the device to recovery mode. Press and hold the button while powering on the device until you see the recovery mode screen.

Q: How to enable audio through HDMI?
A: 3.5mm jack is used for audio by default. You can select the audio device you want to use by using a settings option found in Settings -> System -> Raspberry Pi settings -> Audio device.

Q: How to use IR remote?
A: You can enable the feature by using a settings option found in Settings -> System -> Raspberry Pi settings -> Infrared remote.

You can place a keymap for your remote as /boot/rc_keymap.txt to be automatically loaded on boot. See available keymaps for reference. You can use ir-keytable -p all -t in rooted shell to figure out the keycodes for the remote you’re using.

Q: How to use RTC?
A: You can enable the feature by using a settings option found in Settings -> System -> Raspberry Pi settings -> Real time clock.

System time is automatically read and set from the RTC on boot once you’ve enabled the feature. You need to write the system time you want to use to the RTC in rooted shell:

hwclock -w -f /dev/rtc0

Q: How to use SSH?
A: You can start/stop the built-in SSH server by using a settings option found in Settings -> System -> Raspberry Pi settings -> SSH.

Android doesn’t have user accounts with passwords so key based authentication is used with SSH instead. Necessary keys are generated on the first boot and you need to pull the private key to your computer (or alternatively you can push your own previously generated keys to the device). See Settings -> About tablet -> IP address for your device’s IP address (192.168.0.100 is assumed here). Enable Settings -> System -> Raspberry Pi settings -> ADB.

adb connect 192.168.0.100
adb root
adb pull /data/ssh/ssh_host_ed25519_key my_private_key
chmod 600 my_private_key
ssh -i my_private_key root@192.168.0.100

It’s recommended to disable adb after this.

Q: How to boot from USB device?
A:

  1. Install EEPROM that supports booting from USB
  2. Write image to your USB/NVME storage device as above
  3. Mount the USB/NVME device on your computer and modify /boot/config.txt under ‘Boot device’ section (e.g. for USB boot):
    #dtoverlay=android-sdcard
    dtoverlay=android-usb
    #dtoverlay=android-nvme
    
  4. Connect the USB/NVME device to your Raspberry Pi, remove any sdcard, and boot

Q: How to boot to recovery mode?
A: AOSP doesn’t have reboot to recovery option in power menu. You can boot to recovery mode by selecting option in Settings -> System -> Raspberry Pi settings -> Reboot to recovery.

Q: How to boot out of recovery mode?
A: You can boot out of recovery by simply selecting ‘Reboot system’ option in recovery mode.

Q: My device keeps booting into recovery mode. What should I do?
A: If you have GPIO21 connected to ground (or if you have something drawing power from it) your device will always boot to recovery mode (see FAQ section about DIY power button). If you have a hardware failure on GPIO21 you can edit /boot/config.txt to remove the GPIO21 related logic (see ‘Ramdisk’ and ‘Graphics acceleration’ sections).

Q: Settings -> Storage shows total system size of 15.5 GB. There’s unallocated space on my sdcard. What should I do?
A: This is a 15.5 GB image, remaining space on your sdcard will remain unallocated.

  1. Download KonstaKANG-rpi-resize.zip (sha256:f495955633afe38ae36fee5e550602aec490a3703c3d7f455342800ac394bef4) and save it to your device’s internal storage or use an external USB drive
  2. Boot to recovery mode (see FAQ)
  3. Install KonstaKANG-rpi-resize.zip from your selected storage
  4. Boot out of recovery (see FAQ)

Q: How to install Widevine L3?
A:

  1. Download KonstaKANG-rpi-widevine-17.zip (sha256:fdd225c8704f35876d5f32dd6457b152ca56738cbbfc3373c00978e7a1914b66) and save it to your device’s internal storage or use an external USB drive
  2. Boot to recovery mode (see FAQ)
  3. Install KonstaKANG-rpi-widevine-17.zip from your selected storage
  4. Boot out of recovery (see FAQ)

Q: How to install Magisk?
A:

  1. Download KonstaKANG-rpi-magisk-v31.1.zip (sha256:c0a2c55ea224cce20c56a7dca44da41683c9734c4617a0cb0bfeea232be90180) and save it to your device’s internal storage or use an external USB drive
  2. Download Magisk-v31.1.apk
  3. Boot to recovery mode (see FAQ)
  4. Install KonstaKANG-rpi-magisk-v31.1.zip from your selected storage
  5. Boot out of recovery (see FAQ)
  6. Install Magisk-v31.1.apk using Android’s built-in file manager/adb install/etc.
  7. Ignore suggestions to reinstall Magisk within the app and/or warning about the installation method

Q: How to install Google apps?
A:

  1. Download GApps-17.0-arm64-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
  2. Boot to recovery mode (see FAQ)
  3. Install GApps-17.0-arm64-xxxxxxxx.zip from your selected storage
  4. Factory reset -> Format data partition / factory reset!
  5. Boot out of recovery (see FAQ)
  6. Settings -> Google -> Sign in
  7. Register Google Services Framework Android ID with the same Google account you’ve signed in
  8. Wait for a while and reboot the device until you’ve signed into your Google account successfully

30.10. changelog:

  • initial release (android-17.0.0_r1)
  • implement new recovery mode
  • add support for wifi direct
  • Mesa 26.2.6
  • FFMpeg 9.0.2
  • libcamera v0.7.2, libpisp v1.5.0
  • alsa-lib v1.2.16.1, alsa-utils v1.2.16
  • Linux 6.18.38 kernel
  • Android security patch level: 5 June 2026

Previous builds:


Tags: rpi4 AOSP