(01-23-2023, 08:51 PM)Westslope Wrote: I am using Manjaro with Phosh and have a problem where the GUI will appear to freeze, well not quite, more like the input is no longer responsive. The GUI then becomes as what I would describe as "jittery", the last touch screen input toggles/untoggles rapidly, if using the onscreen keypad, or if scrolling, it shifts by a pixel or so and jumps back and forth. If I press the side power button to shutoff the screen and try to turn it back on, the backlight turns on but the screen remains black. The only way I've found to bypass this is to plug in a USB-C to USB-A adapter and hook up an external keyboard. This allows me to CTRL+ALT+F2 to a terminal login prompt and use that to 'systemctl restart phosh' which restarts it and brings back the lockscreen.

I'm still trying to find the exact error messages that would be associated with the problem, but I'll see if I can find them.

(01-24-2023, 09:50 AM)Kevin Kofler Wrote: Actually, before I applied your udev rules that make the bug go away, I had found that, at least for me, touch input was not actually dead in "flipping frames bug" mode: holding the power button for 3 seconds, then tapping where "Restart" should normally appear, successfully triggered a reboot.

(01-24-2023, 08:07 AM)zetabeta Wrote:

(01-23-2023, 08:51 PM)Westslope Wrote: I am using Manjaro with Phosh and have a problem where the GUI will appear to freeze, well not quite, more like the input is no longer responsive. The GUI then becomes as what I would describe as "jittery", the last touch screen input toggles/untoggles rapidly, if using the onscreen keypad, or if scrolling, it shifts by a pixel or so and jumps back and forth. If I press the side power button to shutoff the screen and try to turn it back on, the backlight turns on but the screen remains black. The only way I've found to bypass this is to plug in a USB-C to USB-A adapter and hook up an external keyboard. This allows me to CTRL+ALT+F2 to a terminal login prompt and use that to 'systemctl restart phosh' which restarts it and brings back the lockscreen.

I'm still trying to find the exact error messages that would be associated with the problem, but I'll see if I can find them.

sounds like what i have been dealing for MONTHS! (i shall get a life...some day). btw, you didn't tell your hardware version? hint, https://wiki.pine64.org/wiki/PinePhone#Hardware_revisions .

check this https://forum.pine64.org/showthread.php?tid=17771 .

videos:
https://barrelmem.s3.eu-north-1.amazonaws.com/flippingframesbug/VID_20230101_003350-mobian-powersavingbug.mp4
https://barrelmem.s3.eu-north-1.amazonaws.com/VID_20220723_232537.mp4
https://barrelmem.s3.eu-north-1.amazonaws.com/VID_20220830_202728.mp4
https://barrelmem.s3.eu-north-1.amazonaws.com/VID_20220908_222922.mp4
https://barrelmem.s3.eu-north-1.amazonaws.com/VID_20220917_135843.mp4

bug report for pmos (hint, fastforward to the end):
https://gitlab.com/postmarketOS/pmaports/-/issues/805

this bug can be bypassed, however i still wonder why all pinephones do not affect in same manner. this bug is perfect daily driver killer, even though battery life is already quite a killer.

few things. some cases there are more frames than two. the bug does not crash whole system, only u.i.. ttyescape and ssh is possible to do something. however, some cases system crashes totally, so only hard reset is only option.

if postmarketos then "dmesg" reveals logs. this command only show if system is still running, not for previous boot. others could use "journalctl", hint: "journalctl -r".