Mobileread
Glo HD Glo HD Battery Replacement didnt work
#11  NiLuJe 07-15-2019, 06:26 PM
This is not a Kindle. I've never heard of a corrupt book causing anything untoward at runtime, except rendering/navigation issues in that specific book.

What might happen with a broken book is the importing process failing on that specific book, which you can check in the system logs. But it has a fairly obvious tell: you get the "importing content" screen on eject even when you haven't imported any new content .
Reply 

#12  Thargor 07-15-2019, 08:03 PM
Quote NiLuJe
This is not a Kindle. I've never heard of a corrupt book causing anything untoward at runtime, except rendering/navigation issues in that specific book.

What might happen with a broken book is the importing process failing on that specific book, which you can check in the system logs. But it has a fairly obvious tell: you get the "importing content" screen on eject even when you haven't imported any new content .
Okay thats good to know thanks.
Reply 

#13  davidfor 07-15-2019, 11:25 PM
Quote NiLuJe
This is not a Kindle. I've never heard of a corrupt book causing anything untoward at runtime, except rendering/navigation issues in that specific book.

What might happen with a broken book is the importing process failing on that specific book, which you can check in the system logs. But it has a fairly obvious tell: you get the "importing content" screen on eject even when you haven't imported any new content .
There have been cases reported where after reading a particular book, the battery drains. Restart the device and reading something else, and everything is OK. Open that book, read and close it and the battery runs down.

I assume what is happening is that a process gets started for something in the book and it doesn't end. I haven't caught it happening myself, just the occasional report here. And I think a conversion in calibre fixes it. So, it is probably some bad code in the book. I don't think I've seen one recently, so it might have been fixed with other changes.
Reply 

#14  NiLuJe 07-15-2019, 11:29 PM
Oh, possibly with straight ePubs then, since that does spawn Adobe's backend, and I imagine they have somewhat less control over it if it goes bonkers.
Reply 

#15  Thargor 07-16-2019, 06:03 PM
So I should give converting the collection to Kepubs a go? Or whats the next best thing to epub to tell Callibre to convert to? All my collection is epub.
Reply 

#16  Quoth 07-16-2019, 06:20 PM
Epubs are fine and will work on other readers and phone/tablet apps. Kepubs are Kobo specific. Sometimes the margin indent is wrong on kepubs.
You can even convert epub to epub to have Calibre settings change things.
Reply 

#17  Thargor 07-16-2019, 07:00 PM
Whats the best alternative to epub to test if thats my battery issue though?
Reply 

#18  davidfor 07-16-2019, 10:50 PM
Quote Thargor
Whats the best alternative to epub to test if thats my battery issue though?
Probably kepub. But, just convert a few. Or use the KoboTouchExtended driver to do it when you send the book.

But, rereading your description of the problem, it doesn't sound like it is book related. It sounds like it is sitting idle when the battery discharge is happening. And after a restart. The situation with a book causing the problem is when reading or leaving the device idle after reading. The times this has been reported, restarting the device stops the battery drain, until the book is opened again.

For your case, I'm wondering if the device is going to sleep. The battery that you describe could happen if the device is awake the whole time. If something is blocking the sleep, or it is disabled or being woken, then the battery will drain. And if for some reason it constantly sleeping and waking, the battery usage will probably be high.

There have been a few reasons for this. A magnet or something metal nearby can affect the sleep. The Glo HD has IR touch, so something touching the screen can prevent it sleeping. And will use the battery faster. A badly fitting sleep cover, or one with something inside touching the screen can also do this.

The WiFi will also use battery. For a long time I had a bad internet connection. Sometimes this would cause the overnight sync to not work properly and drain the battery.

If it was happening after sideloading new books, it could be related to the import or cover generation. These do open the book to to extract the metadata and then to render the cover. For epubs and PDFs the cover generation uses the Adobe RMSDK, so if there is a problem in the book, it could trigger what I described before.

Some things you can try:

- Turning of the cover detection an manually putting the device to sleep.
- Checking if something is touching the screen when sleep should happen.
- Turn off WiFi for a while.
- If you get a battery drain, reboot and see if it keeps happening.
- If it happens after reading, check the book using the calibre editor, Sigil or ePubCheck.
Reply 

#19  TechniSol 07-19-2019, 02:12 PM
I'm assuming *CRINGE* that you didn't upgrade the firmware or perform any other jiggery-pokery prior to the problem surfacing? Absolutely no patches, customizations, Satanic, Wiccan, Druidic, Labour Party, Democratic Party, Republican Party, Freemasons, Shriners, or even ecumenical rituals, etc... ;-)

One other thought if it continues to happen might be to wipe the ereader, remove all books and test for a day or so after fully charging, or perhaps charging/discharging for a cycle or two, then add a book you know you read before having the issue and see what happens... I'd do this with Wifi/Sync off and see how it behaves. It never hurts to strip something down to the bones if there are simply too many variables to account for and you can manage to do so without great heartache. It often gets rid of a lot of possibilities unlikely to be causing the problem, but likely to be wasting a lot of effort to eliminate them. If you can build it back up step by step while testing you may just find the culprit.

Best of luck, and I hope you enjoyed the humor. We can often do with a bit when frustrated while troubleshooting something...

Personally, my money is on the somewhat trippy fuel gauge on the eReaders which occasionally requires a swift kick by running it empty and then full so it can reclaim a zero(not sure it really gets one as it's likely hardcoded to shut down at a minimum voltage, but it may shut down due to a minimum voltage defined by hardware in the battery pack signaling the battery's eminent demise with an interrupt line while noting the minimum recorded voltage measured by an A/D converter) and top off point as my guess is that it may simply note top end voltage and extrapolates or interpolates, if you prefer, to scale that range to 100% with a predefined minimum voltage that serves to cause low power screen shutdown. I have no evidence of either way that I can think of, but both represent the two likeliest design possibilities. I'm leaning toward a preset low end voltage in software since I think there are only two battery lines and it seems unlikely they'd try to encode an AC waveform over the battery voltage to communicate anything, but stranger things have happened. Trump got elected... ;-)
Reply 

#20  Thargor 07-19-2019, 05:21 PM
Quote TechniSol
I'm assuming *CRINGE* that you didn't upgrade the firmware or perform any other jiggery-pokery prior to the problem surfacing? Absolutely no patches, customizations, Satanic, Wiccan, Druidic, Labour Party, Democratic Party, Republican Party, Freemasons, Shriners, or even ecumenical rituals, etc... ;-)

One other thought if it continues to happen might be to wipe the ereader, remove all books and test for a day or so after fully charging, or perhaps charging/discharging for a cycle or two, then add a book you know you read before having the issue and see what happens... I'd do this with Wifi/Sync off and see how it behaves. It never hurts to strip something down to the bones if there are simply too many variables to account for and you can manage to do so without great heartache. It often gets rid of a lot of possibilities unlikely to be causing the problem, but likely to be wasting a lot of effort to eliminate them. If you can build it back up step by step while testing you may just find the culprit.

Best of luck, and I hope you enjoyed the humor. We can often do with a bit when frustrated while troubleshooting something...

Personally, my money is on the somewhat trippy fuel gauge on the eReaders which occasionally requires a swift kick by running it empty and then full so it can reclaim a zero(not sure it really gets one as it's likely hardcoded to shut down at a minimum voltage, but it may shut down due to a minimum voltage defined by hardware in the battery pack signaling the battery's eminent demise with an interrupt line while noting the minimum recorded voltage measured by an A/D converter) and top off point as my guess is that it may simply note top end voltage and extrapolates or interpolates, if you prefer, to scale that range to 100% with a predefined minimum voltage that serves to cause low power screen shutdown. I have no evidence of either way that I can think of, but both represent the two likeliest design possibilities. I'm leaning toward a preset low end voltage in software since I think there are only two battery lines and it seems unlikely they'd try to encode an AC waveform over the battery voltage to communicate anything, but stranger things have happened. Trump got elected... ;-)
Ha, yeah Im currently in the middle of what you suggest, running the battery down and charging to 100% for a couple of cycles, only problem is I left it plugged in for 48 hours after letting it run flat and it wouldn't budge past 99%. It currently seems to be losing about 10-15% charge per day. Doesn't seem to lose anything while Im reading, maybe 1% an hour. Not ideal but bearable while I investigate.

It was synced and updated the day I bought it 3 years ago on initial setup, since then no updates, wi-fi permanently off, no rooting, no experimentation, no patches, nothing of any kind, just sending epubs over USB with Calibre and reading and charging as normal whenever it got to 40% or so with the original charger that came with it.

It just one day decided to stop connecting to any pc (device failed/not installed error), charging slowly, discharging ridiculously fast. The new battery seems to have improved things a bit but its still losing 10-15% overnight while asleep (well it says its sleeping).

The plan now is a few charging cycles to see if the meter re-calibrates, if that doesnt work Ill put the original battery back in, factory reset it and try it with one book at a time, Ill actually reread a couple of books I read previously that I know never caused any bother. If that doesnt work Ill try it again with the new battery, after that Ill buy another reader.

I cancelled the Kindle Oasis that Id ordered out of frustration when I heard you couldnt set the cover of your current book as the screensaver, thats a dealbreaker for me...
Reply 

 « First  « Prev Next »  Last »  (2/3)
Today's Posts | Search this Thread | Login | Register