View Single Post
Old 10-18-2020, 12:43 PM   #10
compurandom
Wizard
compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.compurandom ought to be getting tired of karma fortunes by now.
 
Posts: 1,014
Karma: 500000
Join Date: Jun 2015
Device: Rocketbook, kobo aura h2o, kobo forma, kobo libra color
Quote:
Originally Posted by jgoguen View Post
And most of the time the device is actually powered off when the battery is almost full and when I try to power it back on the next day (or two days later sometimes) it's dead.
If it is truly powered off and your battery is draining, then the battery is not holding its charge and may be at the end of its life. That is a typical failure mode.

Quote:
Originally Posted by davidfor View Post
The usual thought here is that something in the book leaves a process running and that drains the battery.

The problem that I don't think anyone knows what in the book causes this.
I've had problems with books containing javascript being slow and/or crashing the device. I figured the extra text was just causing the parser to work harder, but is it possible it is actually trying to run the javascript?

I can't imagine what else in a book would cause the cpu to chew and not actually fail to render too.
compurandom is offline   Reply With Quote