Ok, so I found that a reset (Paper plugged in and power button is pressed) resets the touch screen. Might be great to have a similar full reset on reboot.
Anybody knows what the power blocks in UIFlow (extern and main power on off) and from which state one could use Power On? I'll see if any of those could be used as a reset workaround for the touch screen?
I also added a few debugging lines to confirm that the touch is actually not working and I don't crash the loop. Loop still loops, just touch shuts down/gets unresponsive.
@ajb2k3 said in M5Paper reboot-persistent touchscreen failure (under UIFlow):
The firmware is marked as ALPHA Test which means that its not fully working.
Make a list of all issues and file a bug report.
Where would I post that report? I thought this might be the place. (Edit: found it. Under Software :)
Just be aware that its Chinese new year and the firmware was rushed out beforehand.
I know. Happy to have it with the device at all.
@felmue said in M5Paper reboot-persistent touchscreen failure (under UIFlow):
- have you considered a simpler UIFlow app which only uses touch (and no ESPNow)?
No. That ESPNow part is the actual fun part. Could use another transfer protocol. Still, it should not go out of sync nor kill the touchscreen while doing so :) My actual problem is that a normal reboot does leave it disabled. That should not be the case.
If you suspect a hardware failure I'd suggest installing the factory test firmware and check if you loose touch with that as well.
Well, you would only know if the same triggers are triggered. And since a full reset or firmware update (with a full reset) revives it...