<![CDATA[PINE64 - Android on PINE A64-LTS / SOPINE]]> https://forum.pine64.org/ Fri, 10 Apr 2026 12:28:30 +0000 MyBB <![CDATA[Legaxy LCD images]]> https://forum.pine64.org/showthread.php?tid=20128 Thu, 18 Dec 2025 12:47:00 +0000 TaleyaJ]]> https://forum.pine64.org/showthread.php?tid=20128
I'm hitting dead end after dead end trying to find a working legacy / LCD image for the LTS that doesn't 404.  Does anyone have a source?

these will be used in a closed environment to control smart home, so not fussed about OS age. They'll be barred from the internet, so no concerns there.]]>
I'm hitting dead end after dead end trying to find a working legacy / LCD image for the LTS that doesn't 404.  Does anyone have a source?

these will be used in a closed environment to control smart home, so not fussed about OS age. They'll be barred from the internet, so no concerns there.]]> <![CDATA[is there a new version of pine installer for windows 10, can please share a link]]> https://forum.pine64.org/showthread.php?tid=17581 Wed, 09 Nov 2022 11:35:10 +0000 Little_Johnny]]> https://forum.pine64.org/showthread.php?tid=17581 its a new pine board, new lcd screen,
i have tried Android 7 and 6, using 2 different 64gb and 2 different 32gb micro sd cards, and a 64gb emmc, i get a blank screen or the pine splash screen, but none load the os, i have tried both ayufan images and the official images, i have tried using the newer version and an older version of etcher and win32 disk imager, i have also tried the pine installer but it errors out when i go to flash the image, all my cards get corrupted too, i have tried about 30 times with different cards and readers, im not sure what the problem is,

is there a new version of pine installer for windows 10, can someone please share a working link or links to working android images]]> its a new pine board, new lcd screen,
i have tried Android 7 and 6, using 2 different 64gb and 2 different 32gb micro sd cards, and a 64gb emmc, i get a blank screen or the pine splash screen, but none load the os, i have tried both ayufan images and the official images, i have tried using the newer version and an older version of etcher and win32 disk imager, i have also tried the pine installer but it errors out when i go to flash the image, all my cards get corrupted too, i have tried about 30 times with different cards and readers, im not sure what the problem is,

is there a new version of pine installer for windows 10, can someone please share a working link or links to working android images]]> <![CDATA[Struggling to get Android running]]> https://forum.pine64.org/showthread.php?tid=17514 Tue, 25 Oct 2022 17:57:45 +0000 qwe]]> https://forum.pine64.org/showthread.php?tid=17514
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.]]>
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.]]> <![CDATA[EMMC with Android on Sopine]]> https://forum.pine64.org/showthread.php?tid=9941 Mon, 25 May 2020 07:47:50 +0000 koekoeboy]]> https://forum.pine64.org/showthread.php?tid=9941 ]]> ]]> <![CDATA[usb gps module]]> https://forum.pine64.org/showthread.php?tid=7346 Wed, 03 Apr 2019 21:49:47 +0000 phantom89]]> https://forum.pine64.org/showthread.php?tid=7346 i'm trying to use an gps usb module with it, but i haven't success.
Is there a method to have "high precision" in geolocation and exploit the module?
Thanks!

ps: i'm using the 6.0.1 version.]]> i'm trying to use an gps usb module with it, but i haven't success.
Is there a method to have "high precision" in geolocation and exploit the module?
Thanks!

ps: i'm using the 6.0.1 version.]]> <![CDATA[LCD not functioning with A64-LTS/SOPINE]]> https://forum.pine64.org/showthread.php?tid=5854 Wed, 14 Mar 2018 22:46:55 +0000 icullumber]]> https://forum.pine64.org/showthread.php?tid=5854
Using Android 5.1.1 I am able to flash an image to a SD card and run it with HDMI output.  The LCD stays blank.  The backlight doesn't even come on.

Using Android 6.0.1, which states that it supports dual display, I am able to run the board just fine with HDMI output.  However, as soon as I plug in the LCD the system won't boot.  The power light comes on for a couple of seconds and then it goes off.  This can be repeated by asserting the power button.  After asserting the power button, the power light comes on for a couple seconds and then shuts off.  It would seem to me that something is forcing the SOPINE to power down when it tries to power the LCD and I'm not convinced that it is hardware related.

My initial thought would be that the LCD is bad.  This theory seems to be disproved when Android 7.1 is loaded on the SD card.

Using the Android 7.1 image for A64-LTS/SOPINE everything, again, works just fine with the HDMI output.  The LCD screen, however, has its backlight turned on during initial bootup and there are a couple of flickers of the screen, but as soon as Android starts the LCD screen is turned off.  I have tried manipulating the uEnv.txt file, but to no avail.

Does anyone else here have experience with a similar setup that you were able to get working?  If so, what image did you use?

I'm not yet convinced that there is something wrong with the LCD, but I am open to the possibility that there is.  The issue that baffles me the most is why it just shuts off when using Android 6.0.1.

If anyone has any insights into why it is behaving in any of the ways listed above I would greatly appreciate hearing them.  Thanks.

Ivon]]>
Using Android 5.1.1 I am able to flash an image to a SD card and run it with HDMI output.  The LCD stays blank.  The backlight doesn't even come on.

Using Android 6.0.1, which states that it supports dual display, I am able to run the board just fine with HDMI output.  However, as soon as I plug in the LCD the system won't boot.  The power light comes on for a couple of seconds and then it goes off.  This can be repeated by asserting the power button.  After asserting the power button, the power light comes on for a couple seconds and then shuts off.  It would seem to me that something is forcing the SOPINE to power down when it tries to power the LCD and I'm not convinced that it is hardware related.

My initial thought would be that the LCD is bad.  This theory seems to be disproved when Android 7.1 is loaded on the SD card.

Using the Android 7.1 image for A64-LTS/SOPINE everything, again, works just fine with the HDMI output.  The LCD screen, however, has its backlight turned on during initial bootup and there are a couple of flickers of the screen, but as soon as Android starts the LCD screen is turned off.  I have tried manipulating the uEnv.txt file, but to no avail.

Does anyone else here have experience with a similar setup that you were able to get working?  If so, what image did you use?

I'm not yet convinced that there is something wrong with the LCD, but I am open to the possibility that there is.  The issue that baffles me the most is why it just shuts off when using Android 6.0.1.

If anyone has any insights into why it is behaving in any of the ways listed above I would greatly appreciate hearing them.  Thanks.

Ivon]]> <![CDATA[Pine A64 _LTS]]> https://forum.pine64.org/showthread.php?tid=5574 Fri, 12 Jan 2018 16:15:45 +0000 moorayilnaveen]]> https://forum.pine64.org/showthread.php?tid=5574 <![CDATA[Compile kernel /Android and can't detect SDHC from Kernel]]> https://forum.pine64.org/showthread.php?tid=5524 Wed, 03 Jan 2018 06:55:32 +0000 spbrain]]> https://forum.pine64.org/showthread.php?tid=5524
I found how to compile compile pine64 android 5.1.1 from https://gitlab.com/pine64-android/manifest/wikis/home.

I modified some parameters (LPDDR3 define from uboot) and I made sun50iw1p1_android_Baomi-db1000_uart0.img and write to sdcard using Phoenix program(Start Up Option).

Then finally confirmed the boot screen.

But Strangely, system.img was not mounted.

console output is

  30.041548] fs_mgr: __mount(source=/dev/block/by-name/system,target=/system,type=ext4)=-1
[   30.050642] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/system at /system options: (null) error: No such file or directory
[   49.727478] fs_mgr: check_fs(): mount(/dev/block/by-name/cache,/cache,ext4)=-1
[   49.735547] fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p10[   49.743178] fs_mgr: Not running /system/bin/e2fsck on /dev/block/by-name/cache (executable not in system


And Kernel Parameters
[    0.000000] Kernel command line: enforcing=1 earlyprintk=sunxi-uart,0x01c28000 initcall_debug=0 console=ttyS0,115200 loglevel=8 root=/dev/mmcblk0p7 init=/init partitions=bootloader@mmcblk0p2:env@mmcblk0p5:boot@mmcblk0p6Confusedystem@mmcblk0p7:misc@mmcblk0p8:recovery@mmcblk0p9:cache@mmcblk0p10:metadata@mmcblk0p11:private@mmcblk0p12:alog@mmcblk0p13:UDISK@mmcblk0p1 cma=384M androidboot.selinux=permissive androidboot.serialno=74005034440c080b038e androidboot.hardware=sun50iw1p1

And I found problem log from kernel message.
As Image from offical site "http://files.pine64.org/os/SOPINE/android/android-ver5.1.1-20160630-sopine-8GB.img.gz", 
Linux Kernel found "mmcblk0".
Log is 
==========================================
9.929729] mmc0: new high speed SDHC card at address 59b4
9.930831] mmcblk0: mmc0:59b4 USD00 29.5 GiB
==========================================
But compiled linux kernel can not found SDHC card.

I tried 8GB SDHC Card but it same.
What do I modify bootloader config or kernel ??
How do I fix this problem?

SD Card Init Log is below from kernel and no detect SDHC card 
=======================================
[    8.730445] sunxi-mmc 1c0f000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.20 2015-7-13 16:28) Compiled in Jan  3 2018 at 09:36:58
[    8.743342] sunxi-mmc 1c0f000.sdmmc: regulator prop vmmc,str none
[    8.750009] sunxi-mmc 1c0f000.sdmmc: regulator prop vqmmc,str none
[    8.756760] sunxi-mmc 1c0f000.sdmmc: regulator prop vdmmc,str vcc-sdc
[    8.763920] sunxi-mmc 1c0f000.sdmmc: No vmmc regulator found
[    8.770110] sunxi-mmc 1c0f000.sdmmc: No vqmmc regulator found
[    8.776929] sunxi-mmc 1c0f000.sdmmc: Got CD GPIO #166.
[    8.782910] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B
[    8.793861] sunxi-mmc 1c0f000.sdmmc: no vqmmc,Check if there is regulator
[    8.816982] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    8.846524] sunxi-mmc 1c0f000.sdmmc: base:0xffffff80000ba000 irq:92
[    8.853803] sunxi-mmc 1c10000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.20 2015-7-13 16:28) Compiled in Jan  3 2018 at 09:36:58
[    8.866672] sunxi-mmc 1c10000.sdmmc: Can't get vmmc regulator string
[    8.873611] sunxi-mmc 1c10000.sdmmc: Can't get vqmmc regulator string
[    8.880656] sunxi-mmc 1c10000.sdmmc: Can't get vdmmc regulator string
[    8.887695] get() with no identifier
[    8.891594] get() with no identifier
[    8.895491] get() with no identifier]]>
I found how to compile compile pine64 android 5.1.1 from https://gitlab.com/pine64-android/manifest/wikis/home.

I modified some parameters (LPDDR3 define from uboot) and I made sun50iw1p1_android_Baomi-db1000_uart0.img and write to sdcard using Phoenix program(Start Up Option).

Then finally confirmed the boot screen.

But Strangely, system.img was not mounted.

console output is

  30.041548] fs_mgr: __mount(source=/dev/block/by-name/system,target=/system,type=ext4)=-1
[   30.050642] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/system at /system options: (null) error: No such file or directory
[   49.727478] fs_mgr: check_fs(): mount(/dev/block/by-name/cache,/cache,ext4)=-1
[   49.735547] fs_mgr: begin to format ext4 buffer : /dev/block/mmcblk0p10[   49.743178] fs_mgr: Not running /system/bin/e2fsck on /dev/block/by-name/cache (executable not in system


And Kernel Parameters
[    0.000000] Kernel command line: enforcing=1 earlyprintk=sunxi-uart,0x01c28000 initcall_debug=0 console=ttyS0,115200 loglevel=8 root=/dev/mmcblk0p7 init=/init partitions=bootloader@mmcblk0p2:env@mmcblk0p5:boot@mmcblk0p6Confusedystem@mmcblk0p7:misc@mmcblk0p8:recovery@mmcblk0p9:cache@mmcblk0p10:metadata@mmcblk0p11:private@mmcblk0p12:alog@mmcblk0p13:UDISK@mmcblk0p1 cma=384M androidboot.selinux=permissive androidboot.serialno=74005034440c080b038e androidboot.hardware=sun50iw1p1

And I found problem log from kernel message.
As Image from offical site "http://files.pine64.org/os/SOPINE/android/android-ver5.1.1-20160630-sopine-8GB.img.gz", 
Linux Kernel found "mmcblk0".
Log is 
==========================================
9.929729] mmc0: new high speed SDHC card at address 59b4
9.930831] mmcblk0: mmc0:59b4 USD00 29.5 GiB
==========================================
But compiled linux kernel can not found SDHC card.

I tried 8GB SDHC Card but it same.
What do I modify bootloader config or kernel ??
How do I fix this problem?

SD Card Init Log is below from kernel and no detect SDHC card 
=======================================
[    8.730445] sunxi-mmc 1c0f000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.20 2015-7-13 16:28) Compiled in Jan  3 2018 at 09:36:58
[    8.743342] sunxi-mmc 1c0f000.sdmmc: regulator prop vmmc,str none
[    8.750009] sunxi-mmc 1c0f000.sdmmc: regulator prop vqmmc,str none
[    8.756760] sunxi-mmc 1c0f000.sdmmc: regulator prop vdmmc,str vcc-sdc
[    8.763920] sunxi-mmc 1c0f000.sdmmc: No vmmc regulator found
[    8.770110] sunxi-mmc 1c0f000.sdmmc: No vqmmc regulator found
[    8.776929] sunxi-mmc 1c0f000.sdmmc: Got CD GPIO #166.
[    8.782910] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B
[    8.793861] sunxi-mmc 1c0f000.sdmmc: no vqmmc,Check if there is regulator
[    8.816982] sunxi-mmc 1c0f000.sdmmc: sdc set ios: clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[    8.846524] sunxi-mmc 1c0f000.sdmmc: base:0xffffff80000ba000 irq:92
[    8.853803] sunxi-mmc 1c10000.sdmmc: SD/MMC/SDIO Host Controller Driver(v0.20 2015-7-13 16:28) Compiled in Jan  3 2018 at 09:36:58
[    8.866672] sunxi-mmc 1c10000.sdmmc: Can't get vmmc regulator string
[    8.873611] sunxi-mmc 1c10000.sdmmc: Can't get vqmmc regulator string
[    8.880656] sunxi-mmc 1c10000.sdmmc: Can't get vdmmc regulator string
[    8.887695] get() with no identifier
[    8.891594] get() with no identifier
[    8.895491] get() with no identifier]]> <![CDATA[How to get & compile Android 5.1 for Pine A64-LTS]]> https://forum.pine64.org/showthread.php?tid=5509 Thu, 28 Dec 2017 07:03:29 +0000 spbrain]]> https://forum.pine64.org/showthread.php?tid=5509
I tested android 6.0 but hdmi output display still 1 min delayed. 
And I think it seem to be not stable.

So I tested android 5.1 and it works that I wanted.

Then I want to get android 5.1 PINE64-LTS source, but i could not find infomation about source of android 5.1(PINE64-LTS, SOPINE)

How to get & compile Android 5.1 for PINE64-LTS ?
(I want 1.1 stable version same as download image site "http://wiki.pine64.org/index.php/SOPINE_Software_Release#Android_5.1.1_.5B20160630.5D")

I visited "https://github.com/ayufan-pine64/android-5.1" but DEPRECATED]]>
I tested android 6.0 but hdmi output display still 1 min delayed. 
And I think it seem to be not stable.

So I tested android 5.1 and it works that I wanted.

Then I want to get android 5.1 PINE64-LTS source, but i could not find infomation about source of android 5.1(PINE64-LTS, SOPINE)

How to get & compile Android 5.1 for PINE64-LTS ?
(I want 1.1 stable version same as download image site "http://wiki.pine64.org/index.php/SOPINE_Software_Release#Android_5.1.1_.5B20160630.5D")

I visited "https://github.com/ayufan-pine64/android-5.1" but DEPRECATED]]> <![CDATA[Android 6.0.1 (PINE A64-LTS / SOPINE)]]> https://forum.pine64.org/showthread.php?tid=5192 Fri, 29 Sep 2017 06:51:30 +0000 pineadmin]]> https://forum.pine64.org/showthread.php?tid=5192 Android 6.0.1 (PINE A64-LTS / SOPINE) 20170726]]> Android 6.0.1 (PINE A64-LTS / SOPINE) 20170726]]> <![CDATA[Android 7.1 (SOPINE)]]> https://forum.pine64.org/showthread.php?tid=5148 Tue, 19 Sep 2017 07:19:59 +0000 pineadmin]]> https://forum.pine64.org/showthread.php?tid=5148 Android 7.1 (SOPINE) v0.3.10-r66]]> Android 7.1 (SOPINE) v0.3.10-r66]]> <![CDATA[When will Remix OS be available for sopine?]]> https://forum.pine64.org/showthread.php?tid=4480 Wed, 26 Apr 2017 08:25:17 +0000 Will.]]> https://forum.pine64.org/showthread.php?tid=4480