![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Dec. 14th, 2016 11:28 amWould anyone out there who has a Reddit account be willing to comment in a thread for me? I have a different model of Kindle, but seem to be having the same problem as this user about the battery life on my Kindle Fire being terrible after the update to Fire OS 5.3.2 was pushed last month, draining quickly even when the device is supposedly in sleep mode, which also means it charges slowly. (There's very little on that thread, but that seems to be the story anywhere on the internet; I would think if this problem were widespread it would be easy to find complaints, but that hasn't seemed to be the case. :-/ ) I would like to ask the OP if they ever sorted it out.
5.3.2 is the update that included Alexa, Amazon's answer to Siri or Cortana, which I immediately disabled, so I don't think it's that Alexa is listening all the time. It's not the wifi (turning that off has no effect, and leaving it on all night was never a problem before) or Bluetooth. A battery monitor and wakelock detector reveal that there's no particular app doing the battery suck, it's just that the CPU is being held awake large percentages of time (90% in the case of last night) for... no reason I can determine, leading to 20-30% battery drain overnight instead of ~5% as had previously been the case. The native email app is the worst offender as far as the number of times it wakes the CPU (it must be something like twice or three times a second), but it only gets ~10 minutes total wake time over an 8 hour night and accounts for only a couple percent of the battery drain. A lot of the wakelocking seems to be by the kernel and I just can't fathom what's going on.
5.3.2 is the update that included Alexa, Amazon's answer to Siri or Cortana, which I immediately disabled, so I don't think it's that Alexa is listening all the time. It's not the wifi (turning that off has no effect, and leaving it on all night was never a problem before) or Bluetooth. A battery monitor and wakelock detector reveal that there's no particular app doing the battery suck, it's just that the CPU is being held awake large percentages of time (90% in the case of last night) for... no reason I can determine, leading to 20-30% battery drain overnight instead of ~5% as had previously been the case. The native email app is the worst offender as far as the number of times it wakes the CPU (it must be something like twice or three times a second), but it only gets ~10 minutes total wake time over an 8 hour night and accounts for only a couple percent of the battery drain. A lot of the wakelocking seems to be by the kernel and I just can't fathom what's going on.