Quote:
Originally Posted by 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...