gkoh
M5Core2 touch screen stops responding if idle
I've randomly noticed that if I left my M5Core2 idling on the home screen for 'some' time, the touch screen becomes unresponsive. It's only the touch screen, because the power button lock/unlock still works.
Some basic logging shows everything else in the background still runs, so it isn't frozen.
Even more interestingly, a soft reboot (ie. by updating the firmware) doesn't fix it. It would appear to need a proper power cycle to recover.
I've noticed this with at least v3.5.0, typically needing several hours of idle to stop. However, with #224, I think I can reproduce this much more quickly, 30-60 minutes.
This seems to be a defect in the underlying M5 libraries.
Interesting. This appears to occur only if the GPS unit is attached and enabled. If I just switch off GPS, I cannot reproduce. Still investigating.
I've been testing with the new 'Module GPS v2.1' for the Core series: https://shop.m5stack.com/products/gps-module-v2-1-with-antenna-atgm336h
The original Core2 battery doesn't physically fit so I attached the 13.2 battery I had from the Core Basic: https://shop.m5stack.com/products/battery-module-13-2-1500mah
So the end result is:
- M5 Core2
- GPS v2.1
- 1500mAh battery
with some code changes and flicking the right DIP switches, I have it working and does not appear to hang.
I will continue testing with other combinations, I cannot work out what is actually happening.
Digging through the M5Unified and M5GFX libraries tends to suggest the touch screen is being suspended, the actual display is still responding (eg. if I disconnect GPS the icon updates). I was able to hack in a 'wakeup' command and get the touch screen to respond without reboot, but it shouldn't be suspending at all 🤷
So the end result is:
- M5 Core2
- GPS v2.1
- 1500mAh battery
with some code changes and flicking the right DIP switches, I have it working and does not appear to hang.
This is untrue, it managed to hang over weekend testing, back to IDK 😐