for testing I use a refrigerator magnet on the back of the device, far from the touchscreen.
and I was able to narrow the mystery down some:
- after input event, miniclock calls fbink to update the clock on the screen
- something fbink does wakes nickel
- somehow somewhere that triggers a touch event
- after input event, miniclock calls fbink to update the clock on the screen
...and back to top, the cycle never ends.
If I replace fbink with a wrapper that logs the call, but doesn't actually call fbink, the cycle breaks.
If I re-add the fbink call to the wrapper, the cycle resumes.
So... mysterious side effects. How fbink wakes nickel and how that translates into stray touch events that in turn wake miniclock, to call fbink in turn... that's still not clear to me.
And I'm back to the same issue I have with the screensaver addon of mine... I have no way to reliably detect that the device is currently supposed to be in standby mode. If I could detect it I'd just stop calling fbink during standby.
