Raspberry Pi Forums

Hello.

I'm trying to use the Android on my Rasp 3B+.
I'm using the Lineage 15.1 image to this. I have a problem when I try to write the image to the sd card.
After the writing process finished, it is created some partitions on the SD and the Android does not start when I insert the card in the Rasp.

I'm using the SD card formatter to format the sd card (sandisk 16 GB);
I tried to write the image with the win32 disk imager and the balenaEtcher. I have similar results with both softwares.
I tried to use the KonstaKANG version 20180706 and after the version 20180307. The same results for the both versions.

Between each attempt, I remove all the partitions from the sd; I create a new partition (entire); and format the sd again.

The rasp is ok because I have other sd card running rapbien ok.

Thanks,

Hisse!

Looks like the same issue I have. Will try to get some more details to recover it.

Since this concerns LineageOS 15.1 why are you not posting in the correct thread (viewtopic.php?f=73&t=220613&sid=0ff1eed ... 2f4b4c6546) instead of opening a new one? Similar question has actually already been discussed there so you would have found your answer already.

If nothing obvious goes wrong with writing the sdcard, there really no reason to assume something did. You need to use a display that support 720p resolution, though.

Konsta wrote: ↑

Fri Mar 15, 2019 8:35 am

Since this concerns LineageOS 15.1 why are you not posting in the correct thread (viewtopic.php?f=73&t=220613&sid=0ff1eed ... 2f4b4c6546) instead of opening a new one? Similar question has actually already been discussed there so you would have found your answer already.

If nothing obvious goes wrong with writing the sdcard, there really no reason to assume something did. You need to use a display that support 720p resolution, though.

Regarding the issue support (use a display that support 720p resolution), thank you. The android is working as expected after use a new monitor. Great!

Sorry about open a new post. I could not relate the issue to the OS. I related (wrongly) the issue to the image write.