Are you running experimental driver?
Your problem is similar to the one Slow Catalyst did encounter : https://forum.freeplaytech.com/showthread.php?tid=4931 in your case, the problem could be DISPLAY_CONSIDERED_INACTIVE_PERCENTAGE, it is hardcoded to 5% in https://github.com/juj/fbcp-ili9341/blob...r/config.h
Conbined to SAVE_BATTERY_BY_PREDICTING_FRAME_ARRIVAL_TIMES, it could be the problem.
I am not English and I have some troubles understanding : 'My gut says there's some kind of input polling event that runs wild' :S
When you will have access to WiFi, you can try these commands :
'sudo jstest /dev/input/js0' , this only monitor joystick event.
'sudo evtest /dev/input/event0' , this one monitor all events, SYN included.
The GPIO driver has been update 20 days ago, this new version does handle analog input a different way to solve possible troubles with evdev input based emulator but I don't think your problem is related to this.
Your problem is similar to the one Slow Catalyst did encounter : https://forum.freeplaytech.com/showthread.php?tid=4931 in your case, the problem could be DISPLAY_CONSIDERED_INACTIVE_PERCENTAGE, it is hardcoded to 5% in https://github.com/juj/fbcp-ili9341/blob...r/config.h
Conbined to SAVE_BATTERY_BY_PREDICTING_FRAME_ARRIVAL_TIMES, it could be the problem.
I am not English and I have some troubles understanding : 'My gut says there's some kind of input polling event that runs wild' :S
When you will have access to WiFi, you can try these commands :
'sudo jstest /dev/input/js0' , this only monitor joystick event.
'sudo evtest /dev/input/event0' , this one monitor all events, SYN included.
The GPIO driver has been update 20 days ago, this new version does handle analog input a different way to solve possible troubles with evdev input based emulator but I don't think your problem is related to this.