[Alan_S]

Well, it really took a time for me to write this post, which is a good thing.

Some of you probably noticed that battery doesn't lasts that long when device is suspended. That's the reason I usually shut device off when not reading it. I suspended it only when I know I'll read it really soon.

And I heard here that if you use koreader with CoolReader's suspend script, battery problem seems solved. For a long time I didn't bothered to test it out. But, for some reason, I deceided to test it out for myself.

First I tested koreader and it's own suspend script. As some might remember, on very first day of testing there was drop from 100% to 82%, which obviously isn't good. I admit, it isn't always so drastic. But also it points that koreader's own suspend script still doesn't suspend device properly for whatever reason.

I stopped testing koreader's suspend script and uploaded instead CoolReader's suspend script on 4.12 and reported that here tomorrow (5.12). Since that day I only suspended my device and waited to see when battery would need charging.

By now you can guess, that moment has arrived. Yesterday I charged my device, and it's about 50 days that battery lasted suspending device with CoolReader's suspend script. There was again noticeable that with lower percentage battery lasts shorter and shorter times.

For example, I had 100% for first 4 or 5 days, after that there was more or less "linear" drop in percentage, but under about 40% battery was dropping faster and faster. We can say that battery should be charged when it reaches 40% or lower, just to be sure and to avoid deep cycles (which aren't good for batteries, except from time to time).

I don't know why, but there's obvious difference in CoolReader's suspend script and it seems that it really suspends device properly.

It would be really great if reason why is that so could be found out, but on the other hand, it's not too big problem to manually exchange koreader's suspend script with CoolReader's.