(05-17-2016, 09:42 AM)Ghost Wrote: (05-17-2016, 09:16 AM)Luke Wrote: That said, since the resolution is non-standard I will make an educated guess that there is some internal scaler of some sort which may not play nice with the pine64
I think you're right. The large analogue clock described in the first post in this thread seems like it is the clock from the Android desktop, but vastly scaled up (actual size of clock is supposed to be quite small).
Yea, perhaps because the native resolution is 1080 vertical it outputs 1080p?
Okay, I've tried the TV64 image aaaaaand.... Same issue :/ distorted greyscale screen, I can make out a menu bar an the word favourites but that's about it. Any other thoughts?
(05-21-2016, 07:05 AM)Cestrefeld Wrote: Okay, I've tried the TV64 image aaaaaand.... Same issue :/ distorted greyscale screen, I can make out a menu bar an the word favourites but that's about it. Any other thoughts?
Its a problem with an unsupported resolution, so I am afraid there is very little that you can do at the moment (especially using android). Could you try linux and report back ? - I just want to know if the same thing happens if you boot into debian or ubuntu (how the internal scaler reacts).
(05-24-2016, 01:43 PM)Luke Wrote: (05-21-2016, 07:05 AM)Cestrefeld Wrote: Okay, I've tried the TV64 image aaaaaand.... Same issue :/ distorted greyscale screen, I can make out a menu bar an the word favourites but that's about it. Any other thoughts?
Its a problem with an unsupported resolution, so I am afraid there is very little that you can do at the moment (especially using android). Could you try linux and report back ? - I just want to know if the same thing happens if you boot into debian or ubuntu (how the internal scaler reacts).
Okay, I've given the Ubuntu image a try and its still Out Of Range although slightly different. its still greyscale but the image is now smaller and has a doubled up ghost image floating partially to the right of the original. :/
I'll try some of the others when I get a minute.
Remix is tested, still no good :/
(05-26-2016, 10:15 AM)Cestrefeld Wrote: Remix is tested, still no good :/
I think that you should PM someone with considerable knowledge in these matters: longsleep, Lennyraposo, rahlquist, tkaiser are some of the names that come to mind.
You can also pop by the IRC and see if anyone can help you troubleshoot the issue live. Plenty of clever people on including some of the aforementioned.
Sorry I couldn't be of more help 
(05-25-2016, 01:54 PM)Cestrefeld Wrote: (05-24-2016, 01:43 PM)Luke Wrote: (05-21-2016, 07:05 AM)Cestrefeld Wrote: Okay, I've tried the TV64 image aaaaaand.... Same issue :/ distorted greyscale screen, I can make out a menu bar an the word favourites but that's about it. Any other thoughts?
Its a problem with an unsupported resolution, so I am afraid there is very little that you can do at the moment (especially using android). Could you try linux and report back ? - I just want to know if the same thing happens if you boot into debian or ubuntu (how the internal scaler reacts).
Okay, I've given the Ubuntu image a try and its still Out Of Range although slightly different. its still greyscale but the image is now smaller and has a doubled up ghost image floating partially to the right of the original. :/
I'll try some of the others when I get a minute.
Hey,
I had a similar issue, where my TV wouldn't get any signal from the board. With Luke's help, we managed to get mine working (under Ubuntu) by forcing the resolution, so maybe it will solve your issue too.
I had to update my kernel and u-boot (there are scripts which do this in /usr/local/sbin -- just run them with sudo), then reboot, and then I had to add the following line to /boot/uEnv.txt:
Code: extraargs=console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1280x720p50 rootwait rootfstype=ext4
This will force 720p (you can change the resolution to get 1080p, but I didn't spot any difference, so not sure). After saving the changes you do need to reboot.
I also had to unplug my HDMI cable and re-plug it in after rebooting.
Hope this helps!
|
