Thats kinda funny because my wqtched behaved the exact same way today. Drained insanely fast, the. Right around 8ish seemed to normalize.
I wonder if there are background algorithms that run maintenance and system checks and data reorganization/restructuring. If there is, running through that data, analyzing for usage and what to prioritize (like where to allocate memory, how much to allocate, and optimizing access to that particular data) and all that crazy stuff could certainly impact battery life significantly.
In this product, i wouldnt be surprised if there was something like this going on given a seemingly limited capacity for resources. It could also explain why you may go from great battery life for a while, then a day or two of bad battery, then back to great again.
Anyone think im just talking crazy?
I wonder if there are background algorithms that run maintenance and system checks and data reorganization/restructuring. If there is, running through that data, analyzing for usage and what to prioritize (like where to allocate memory, how much to allocate, and optimizing access to that particular data) and all that crazy stuff could certainly impact battery life significantly.
In this product, i wouldnt be surprised if there was something like this going on given a seemingly limited capacity for resources. It could also explain why you may go from great battery life for a while, then a day or two of bad battery, then back to great again.
Anyone think im just talking crazy?