View Single Post
Old 12-28-2013, 08:30 PM   #17
speakingtohe
Wizard
speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.speakingtohe ought to be getting tired of karma fortunes by now.
 
Posts: 4,812
Karma: 26912940
Join Date: Apr 2010
Device: sony PRS-T1 and T3, Kobo Mini and Aura HD, Tablet
Quote:
Originally Posted by icallaci View Post
Yes, I tried a factory reset to see if that would correct the battery discharge problem, but it didn't. I've been on FW 2.8.1b for more than 24 hours now, and I read for about an hour and a half today (on the reader that was discharging ~25% after 8-10 hours under FW 3.1.1) and my battery is still at 100%. So I am sure that there is a problem with 3.1.1 (and 3.1.0), but I am %#&@ if I know what it is or how to find it. A runaway process somewhere?
I always (perhaps wrongly) suspect unassigned pointers and/or absolute jumps/calls. Can't think why it would differ so much between different identical devices with identical firmware. Maybe back in the days when they hand soldered everything.

Helen
speakingtohe is offline   Reply With Quote