10-25-2022, 11:57 AM
My recently-purchased Pine A64-LTS runs Armbian swimmingly. I also need to run Android on it— a seemingly trivial task, but one that has brought me to my wits end.
Here's what I've tried:
All images were burned the same Samsung 32GB microSD card using a ThinkPad built-in microSD slot, running Arch Linux with the following command:
Note that this exact combination was able to successfully boot Armbian prior.
Clearly, something is going horribly wrong with my board, being unable to boot Android despite so many failed attempts to make it so. My next attempts will be to boot the 8GB variant of the official Android 6 image, as well as the official Android 5 image, but I don't expect them to yield fruit. Though this is clearly a dated board with little support at this point, I'm posting here in the unlikely event that someone here will have some ideas.
Here's what I've tried:
- The official Android 6.0 image (in its 32GB variant). The first time I extracted and burned this image, I saw a blue light appear on the board, noticed that the CPU was running hot to the touch, and nothing else. I extracted and burned the image two more times and saw nothing at all happen.
- The Android 7.1 community image. This image allows the board to turn on— however, it loops forever at the Android splash screen (in which it plays a fun animation before, in a normal scenario, shifting to the word "Android".) I attempted to burn it a second time with the same result.
- The Android 6.0 community image. This image successfully boots, but something is clearly horribly wrong. It runs at ~10FPS with significant lag in all menus, and I can't get any sort of internet connection— neither Ethernet nor a USB Ethernet adapter yield a link, and wifi and Bluetooth refuse to turn on. The Ethernet jack on the board blinks an orange light rapidly forever. Thus, this image is unusable. I attempted to burn it a second time with the same result.
All images were burned the same Samsung 32GB microSD card using a ThinkPad built-in microSD slot, running Arch Linux with the following command:
Code:
sudo dd if=./IMAGE of=/dev/mmcblk0 bs=1MiB status=progress conv=fsync
Note that this exact combination was able to successfully boot Armbian prior.
Clearly, something is going horribly wrong with my board, being unable to boot Android despite so many failed attempts to make it so. My next attempts will be to boot the 8GB variant of the official Android 6 image, as well as the official Android 5 image, but I don't expect them to yield fruit. Though this is clearly a dated board with little support at this point, I'm posting here in the unlikely event that someone here will have some ideas.