07-26-2016, 07:16 AM
(07-15-2016, 02:26 PM)ColourDen Wrote:(07-14-2016, 11:15 AM)ColourDen Wrote:(07-14-2016, 10:00 AM)DonFL Wrote: Loading a linux image and seeing if you can ssh into the board (suggestion 5, above) would tell you a lot, especially considering display issues are a common start-up issue that users battle. That would definitely be the next step I'd take.
Yeah that's definitely my next attempt. I've got my Pine64 and a Raspberry Pi 3 to mess with over the next few days. Hopefully good news by the weekend
Update: It's working! Appreciate the suggestions everyone. My fix was the display issue, I did a reset on the board to allow it to boot and it magically fixed the HDMI output. Next mission, the touchscreen setup.
Hi everyone,
I am having similar issues as stated above... has this been resolved for the touchscreen/LCD?
I have managed to successfully burn and boot into an android DD image and a Remix OS image using an HDMI out. However, I have not managed to pass the boot screen on the LCD using an android DD LCD panel image. The image does show on the screen but I never pass the boot screen.
I have tried two cards (16Gb and 32Gb) in the hopes a different image or a different card would fix the issue. This was not the case. I burned the Android .img using Mac OS X El Captain with the following dd command:
Code:
sudo dd bs=1m if=path_of_your_image.img of=/dev/rdiskn
Where "path" is replaced by the image path and "n" by the unmounted disk number. Again, this worked for the Remix OS and Android image no problem. The issue occurred when I tried loading and booting into the touchscreen image.
Info: I have a Pine64+ 2Gb model with only the LCD, wifi/bluetooth dongle and the power connected to the board.
Any help would really help. Not sure what else I could try? Thanks!
______
Ps: Remix OS on the 2GB model is very very slow... Android through HDMI is rock solid.