Thread: Glo Bad battery?
View Single Post
Old 01-08-2013, 11:23 PM   #46
TechniSol
GranPohbah-Fezzes r cool!
TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.TechniSol ought to be getting tired of karma fortunes by now.
 
TechniSol's Avatar
 
Posts: 998
Karma: 3088870
Join Date: Jul 2010
Device: Nook STRs, Kobo Touch, Kobo Glo
I think you have to perform the occasional deep discharge for the battery metering to properly determine the remaining power capacity of the battery. The normal method is to account for power usage levels and uptime and build up a total current or watts available profile and then subtract during discharge. You can get fancier, but it's probably not worth the work.

The occasional deep discharge to shutdown should only help to recalibrate the profile. The shutdown should occur prior to any internal low voltage shutdown circuitry in the battery kicking in as long as Kobo left the proper wiggle room.

As to how the chapter size might effect current draw during sleep mode, what if the RAM being used is segmented and can be independently powered down if not being used? Buffer a small amount of text in memory and you have minimal current draw during sleep mode. STUPIDLY buffer multiple chapters and keep a lot of dynamic RAM refreshing and kiss your battery life goodbye. It's just a theory from a hardware dinosaur, but it might be relevant...

OTOH, if you're trying to get maximum battery life out of a device like these, and the processor is fast enough, why even bother to buffer text in between page turns? Just preserve a few pointers and grab the text and render on the fly. It would seem like the lowest power consumption based method?

Last edited by TechniSol; 01-08-2013 at 11:36 PM.
TechniSol is offline   Reply With Quote