[davidfor]

Originally Posted by Zaroff

First, thanks for the lengthy addressing of the various problems, and thanks to all trying to help here.

So:
-I woke up the device, and since I've become rather wary, started by checking the battery level from the home page, which was then 72%. I opened the book I currently have ongoing, which was like 20 seconds after waking up, checked again, 72%. I didn't time it, but between 2 or 3 minutes after reading proper started, I rechecked, and it was then at 61%.

How long was it sleeping? And did it keep going down at that rate?

After waking, the device does do a few things such as attempt to sync the status for the current book. That shouldn't use that much battery, so I'm tending towards it taking more than a few seconds before it gets the battery level. Unfortunately, I can't think of an easy way to prove it.

-I was wondering about that. How is the SN structured? Maybe that can be easily determined.

The first four characters should be the model number. The rest, I don't know. But, the more similar they are, especially if only the last two or three characters are different, the more likely they are from the same batch.

-I'm not sure what I could be doing that would trigger the faults I observed; I've wondered about that too. I sideload 99% of the books I read, and after that, basically do nothing but open and close books. That's it. No fancy stuff, no internet browsing, no OverDrive, etc. When I'm done reading, I put it to sleep, and that's it.

Nothing unusual in that. There have been some problems with books with errors that trigger a problem and leave a background task running. Or killing a background task. Until the device is restarted, the background task is using power.

Also, a book with unusually large internal files would probably use more CPU when rendering a chapter. That shouldn't be the case here, but it could be an attributing factor.

-And that's the interesting thing: did you observe anything alike to such problems on the Glo HD at all? If not, then it would suggest to me that at least a sizeable portion of the KA1 out there have a faulty battery controller, which would make it a hardware issue. And that's much more of a problem than eventually waiting for a FW correction.

I saw the problems related to sync that were being reported. There were one or two other things that happened to drain the battery quickly, but, they always happened at a time I couldn't do any investigation. In all cases, restarting the device stopped the drain for a while. Of course, if it is a hardware fault in the Aura ONE, then comparing to the other devices won't help.