This is the second time this has happened and it's really starting to get on my nerves.
This time when I woke up, though, instead of my phone being kept awake from around 730 am to 9 am, losing about 20%-30% battery life, it was kept awake from around 2 am to 9 am, going from 67% battery life to 8% battery life.
The first time this happened I posted about it here http://forums.androidcentral.com/htc-one-m8/407498-google-keeping-phone-awake.html#post3747607. I noticed that google+ had kept my phone awake for over an hour in the usage report. I knew something was not right, but no one else seemed to be experiencing what I was talking about so I chalked it up as an anomaly and just disabled google+ hoping this would never happen again.
Until about an hour ago when I woke up to the sound of my phone alerting me that I had less than 10% battery life when I had not even used the phone since 1am this morning, about 7-8 hours ago. When I checked the history report I read that it had been kept awake again since around the time I went to sleep which, again, was 7-8 hours ago. I don't remember doing anything with the phone that could have triggered it to stay awake for as long as it did.
The only thing I was doing on the phone before going to bed and turning the screen off was browsing reddit and then setting an alarm for 9 am. When i stopped redditing i exited the app and even cleared it from the recent apps list. Also in the usage report it said that reddit was not keeping the phone awake, so I do not think it was that. The only other thing that I did was set an alarm but that wouldn't keep my phone awake would it?
One thing I did notice when I checked the usage report was that no apps listed in the report showed keeping the phone awake for more than a minute. So I could not actually see what app kept the phone awake for so long. I did check the running services and noticed that amazon had been running for 11 hours, which I thought was pretty unusual, so I went ahead and disabled that app as well.
Can anyone help me figure out what is going on here or has anyone else experienced something like this?
Any and all help would be greatly appreciated.
This time when I woke up, though, instead of my phone being kept awake from around 730 am to 9 am, losing about 20%-30% battery life, it was kept awake from around 2 am to 9 am, going from 67% battery life to 8% battery life.
The first time this happened I posted about it here http://forums.androidcentral.com/htc-one-m8/407498-google-keeping-phone-awake.html#post3747607. I noticed that google+ had kept my phone awake for over an hour in the usage report. I knew something was not right, but no one else seemed to be experiencing what I was talking about so I chalked it up as an anomaly and just disabled google+ hoping this would never happen again.
Until about an hour ago when I woke up to the sound of my phone alerting me that I had less than 10% battery life when I had not even used the phone since 1am this morning, about 7-8 hours ago. When I checked the history report I read that it had been kept awake again since around the time I went to sleep which, again, was 7-8 hours ago. I don't remember doing anything with the phone that could have triggered it to stay awake for as long as it did.
The only thing I was doing on the phone before going to bed and turning the screen off was browsing reddit and then setting an alarm for 9 am. When i stopped redditing i exited the app and even cleared it from the recent apps list. Also in the usage report it said that reddit was not keeping the phone awake, so I do not think it was that. The only other thing that I did was set an alarm but that wouldn't keep my phone awake would it?
One thing I did notice when I checked the usage report was that no apps listed in the report showed keeping the phone awake for more than a minute. So I could not actually see what app kept the phone awake for so long. I did check the running services and noticed that amazon had been running for 11 hours, which I thought was pretty unusual, so I went ahead and disabled that app as well.
Can anyone help me figure out what is going on here or has anyone else experienced something like this?
Any and all help would be greatly appreciated.