MobileRead Forums - View Single Post

frostschutz · 07-18-2019, 09:15 AM

OK, now I can reproduce the issue with my H2O.

Put the device into standby, all is fine. Use a refrigerator magnet to wiggle the sensor a bit: even though the device is supposed to be sleeping, and sleepcover support is turned off, the magnet sensor wakes the device and MiniClock updates.

Worse, the device does not go back to sleep when removing the magnet, instead for some mysterious reason it keeps receiving touchscreen events in an endless loop(*). It does not stop at all. So the clock keeps updating and updating while sleeping and yes, eventually that will drain the battery, for the screen updates for one, and due to the device itself only pretending to be in low power (standby) state when it's really not.

At this point I'm not sure what to do about it. I'm also not sure if this is just a bug in Kobo firmware itself or the modification that's keeping the device awake, etc. In any case, it's weird and even if I took the effort of ignoreing the magnet key event, that does still not fix the issue.

(*)This may be misbehavior of how I'm reading the touchscreen... not entirely sure what's going on there, yet.

07-18-2019, 09:15 AM	#195
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	OK, now I can reproduce the issue with my H2O. Put the device into standby, all is fine. Use a refrigerator magnet to wiggle the sensor a bit: even though the device is supposed to be sleeping, and sleepcover support is turned off, the magnet sensor wakes the device and MiniClock updates. Worse, the device does not go back to sleep when removing the magnet, instead for some mysterious reason it keeps receiving touchscreen events in an endless loop(). It does not stop at all. So the clock keeps updating and updating while sleeping and yes, eventually that will drain the battery, for the screen updates for one, and due to the device itself only pretending to be in low power (standby) state when it's really not. At this point I'm not sure what to do about it. I'm also not sure if this is just a bug in Kobo firmware itself or the modification that's keeping the device awake, etc. In any case, it's weird and even if I took the effort of ignoreing the magnet key event, that does still not fix the issue. ()This may be misbehavior of how I'm reading the touchscreen... not entirely sure what's going on there, yet. Last edited by frostschutz; 07-18-2019 at 09:26 AM.