PINE64
resolution stuck at 360x720 - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: General Discussion on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=127)
+--- Thread: resolution stuck at 360x720 (/showthread.php?tid=16558)



resolution stuck at 360x720 - tomgtc - 04-26-2022

My Pinephone (convergence) has horizontal pinstripe lines throughout the screen. I suspect it has to do with the resolution being set at 360x720. I can't find an xrandr mode that will let it be set at 720x1440.

I'm running Manjaro Phosh.

In case this has anything to do with the problem, I do not have a ~/.monitors.xml or ~/.config/monitors.xml file. If it's supposed to be there, it's gone.

Thanks.


RE: resolution stuck at 360x720 - fxc - 04-26-2022

Did you reflash a new OS and does the issue occur there too? It primarily sounds like an software issue with your installation.


RE: resolution stuck at 360x720 - tomgtc - 04-30-2022

I did that, yes, in fact I re-flashed it in multiple distros, all with the same result. Even the factory image had the same output. They all have it on their boot screen images, too; that is, the very first thing that shows on the screen after boot-up has the lines in it.

The odd thing, though, is what happened when I loaded up jumpdrive to reflash the emmc. It was pristine, clear, and unmarked by any of the horizontal lines I saw in every other distro. That might be diagnostic.

Also potentially diagnostic (though it could also be coincidence) is that the problem began right when, for an experiment, I tried loading Gnome Location services into Manjaro Plasma. The screen went crazy at exactly that moment. I don't know how that could have done any damage that would persist through all these software and distro changes, but if you know of some possible persistent effect, I'd be interested to hear it.

I've wondered about updating the mainboard firmware, but from what I've seen, that's got more to do with USB than anything else. I'll do it if someone says it's safe to try, but I need that reassurance first.

This is a new touch screen, by the way. This happened less than 24 hours after I replaced an older one. (That one had lost touch response in the lower 1/3 of the screen.) The replacement screen looked great and worked great when we installed it, but it didn't last long.


RE: resolution stuck at 360x720 - fxc - 04-30-2022

(04-30-2022, 06:55 AM)tomgtc Wrote: I did that, yes, in fact I re-flashed it in multiple distros, all with the same result. Even the factory image had the same output. They all have it on their boot screen images, too; that is, the very first thing that shows on the screen after boot-up has the lines in it.

The odd thing, though, is what happened when I loaded up jumpdrive to reflash the emmc. It was pristine, clear, and unmarked by any of the horizontal lines I saw in every other distro. That might be diagnostic.

Also potentially diagnostic (though it could also be coincidence) is that the problem began right when, for an experiment, I tried loading Gnome Location services into Manjaro Plasma. The screen went crazy at exactly that moment. I don't know how that could have done any damage that would persist through all these software and distro changes, but if you know of some possible persistent effect, I'd be interested to hear it.

I've wondered about updating the mainboard firmware, but from what I've seen, that's got more to do with USB than anything else. I'll do it if someone says it's safe to try, but I need that reassurance first.

This is a new touch screen, by the way. This happened less than 24 hours after I replaced an older one. (That one had lost touch response in the lower 1/3 of the screen.) The replacement screen looked great and worked great when we installed it, but it didn't last long.

Best if you upload an image of those lines, it is possible it is indeed an hardware issue, especially as it persists throughout different installations. There is no mainboard firmware, so that is indeed not a cause.