10-13-2016 12:17
10-13-2016 12:17
I have a nexus 6 running android 6.0.1. About a month ago, I realized that my n6 was rebooting itself from time to time. I saw it actually do this once in the last year and a half so I thought it was a glitch and ignored it. I turned all background syncing between my n6 and my surge because of a power drain issue that I had read about. How do I know that the notification feature was causing this? Yesterday I turned notifications off because I noticed that it seemed related to text messages... not 100%. Not to mention apparent reboots when running with the surge and my bluetooth headphones (mercifully rare at least)... and guess what? My phone has been running steadily for more than 24 hours. Using a terminal emulator, and the unix "uptime" command, I was able to determine that over the last week my phone rebooted itself on the average of two to four times A DAY! Seems like a smoking gun to me... turn off notifications, ZERO reboots of my n6 for more than 24 hours.
What say you, fitbit people????
10-15-2016 11:39
10-15-2016 11:39
So it's now been THREE days without the notification feature of my surge turned on and I've had ZERO reboots of my nexus 6. I *really* think I've found the smoking gun here. I don't suppose the gnomes from fitbit that troll these pages have ANYTHING to say... How about it?
10-22-2016 07:41
10-22-2016 07:41
Hello @JayPsquared good to see you around. Í know in Android 6.0 there are a few changes. Due to Google permissions requirements for Bluetooth syncing, you must turn on location services to sync your tracker (Settings > Location). For more information about the latest Google permission requirements, see Google's Android 6.0 Changes document.
Although I would recommend the call notifications troubleshoot, as this is the first time I heard something similar.
Lets try this and keep me updated how it goes. I'll be around.
"Great things are done by a series of small things brought together.” What's Cooking?