Quote:
Originally Posted by encol
Wow!
I tried geekmaster's suggestions with no luck (even if i'm not sure if i looked everywhere  ), but this works!: |
While monitoring /proc and /sys for status changes, I would also look in /var/log/messages (and other places as well). It did not occur to me to explicitly say to look in "other places as well" when I posted. Yes, there can be useful log messages, but as mentioned previously, such things can vary by firmware model, and especially by log level (i.e. ~debugOn), and the 'dmesg' log can even have a log level set where almost NOTHING gets posted there (useful when re-puposing the serial port, which also displays log messages).
I will try to be more explicit in the future, but the reason I mentioned /proc and /sys is that the "next page" 'keypress' or touchscreen event may be found there, and lab126 is fond of putting things you would think belong in userland into their device drivers (such as screensaver management in the eink display driver).
Not only can various log messages be prevented from being logged, but their format can change as well so even if logged, detecting them reliably could be tricky if you want your hack to continue to work across multiple devices and firmware versions, and not suffer "
bit-rot" over time.
I prefer the simplest solution whenever possible, but it must also be robust and reliable.