Quote:
Originally Posted by ichnilatis
I gave two examples above. The functions that depend on the time have no effect untill I turn the page or close the file.
|
The functions that depend on time are constrained to a given timeframe on Pocketbooks if the autostanby plugin is enabled.
The autostandby plugin does the same as Pocketbook firmware does on its own: it sets the CPU to sleep after two seconds.
It becomes aggressive when the battery is below a certain threeshold:
https://github.com/koreader/koreader...n/main.lua#L38
There's no obvious way to deal with it.
If you disable the autostandby plugin you'll get fairly worse battery time, since there's no standby at all unless requested by you by putting your device to sleep.
You'll get better results if you lower the "aggressive threesold" to
or even to
But again, the "aggresive threesold" just changes how time is added to the timeframe where the cpu is awake. And all functions that rely on "time ticking" will fail in the long run if the plugin is enabled.
But certainly, if you only see issues with battery below 60%, changing that parameter might help for your user case.