Seeing “Sleep Tracking” improvements with 11.10 and no extra battery drain.

Former Member over 5 years ago

I updated to 11.10 FW and all sensors two days ago. Since updating my Quatix 6,I have seen sleep tracking improvements. I am not seeing huge blocks of awake times and better accuracy for sleep and wake times. Also unlike other posts reporting excessive battery drain, I have not experienced any noticeable battery drain. Battery drain is stable and drain is normal.

The last 2 days I just happen to be in recovery so no activities recorded. I will test this through the weekend during my runs. As far as sleep tracking goes, my settings have remained the same from 10.10. Using sleep tracking with battery saver settings (everything disabled except WHR and Activity Tracking). This is also the first time since 10.10 I have seen “Body Battery” reach 100. All though out 10.10 It seem to be hindered by the exaggerated sleep awake times

As a side note to other posts as well, I have no issues with WiFi either. I have been recently disabling WiFi when not needed (previously always on). When I reconnect WiFi and sync, I have no issues.

I will continue to keep a eye on the battery as I do activity and see how sleep tracking plays out for the next week.

Top Replies

All Replies

0 tlindemans over 5 years ago in reply to muppetman

IMO the watch is working as expected and with enough accuracy to do what is its core functionality: tracking workouts. What I do think Garmin could improve upon and they still have not nailed is software quality. Personally, I can forgive them for the messy transition to the Firstbeat sleep algorithm. Now, a month later, it seems the crazy awake times issue has been solved. I also know that Garmin is super quick to fix issues that pop up down the road with new firmwares, so if something stops working, I’m almost certain it’ll get fixed in a few weeks/months.

What I don’t get, is why fixing A causes B (which was working fine before) to break. I know this happens to other companies as well, but not to the extent it happens to Garmin software, both on the watch, and on their iOS app. Will this make me leave Garmin? No, because the benefits of my Fenix (materials used, battery life, 3rd party integration, ...) and the GCM app outweigh these issues. Do I understand it frustrates others who spent €700-1000 on a watch? Yes.

0 Former Member over 5 years ago in reply to Former Member

Just a follow up to my own post -

13 hours ago I had 99.1%, right now I have 98.38%. Not seeing any problems. Note I don't use pulse ox other than to take a manual reading every now and then but it's always in the 90's so it seemed like pointless data for me. It does measure about 3% low compared to a hospital's pulse ox device on the 3 occasions I've had this year to do that comparison (stupid table saw). But other than that everything is normal power mode. BT, custom clock face, 8 widgets.

Again my watch goes down slower the higher the charge. I've used a datafield that writes the battery charge into the .fit file before to get numbers on the burn rate of running with no sensors turned on, GPS only, GPS + OHR, GPS+OHR+Music, GPS+OHR+Music+Livetrack to get the least power usage versus the most. (pace/distance comes from my stryd so GPS isn't needed for that).

But I saw it vary between 1.x% per hour at 100% to 2.x% per hour down in the 20% range which is one of the things that came out of that as with no changes in sensors my burn rate goes up as the battery goes down in power. It's a fairly steady progression, nothing egregious but it means it makes it really tough to do comparisons and I found I had to start at 100% every time to have a stable starting apples to apples point.

The only long term burn data point I have is I can say that last year in October during a 100 mile race I started at 100% with a Stryd for 18 hours and a Scosche for 22 hours and Livetrack for 24 hours I went from 100% at the start to something in the 30's at the 26 hour mark when I stopped. I also had backlight on for gestures at night.

Covid willing I'll get another data point in October, assuming Kansas Rails isn't canceled, for a long term activity with this firmware or any subsequent release.