Battery LIfe
-
With GPS set to good/10 sec it seems to drain around 10% a hour for me, so 7 seems quite low. And mine was with the screen on.
-
@harboe did you keep bluetooth connected to smartphone?
-
I get consumption ~7-8%/ hour with the following settings,
-GPS 10s
-Airplane mode on
-Screen onI get this if I don’t have routing or glancing at the map because those obviously consume more battery.
For my training this is more than I need since I don’t do any ultras etc. -
@jantikainen understand, probably bluetooth connection and notifications drain more battery than I expect, I’ll do tomorrow a test with your settings and give a feedback just for comparison, thanks
-
@drunners yep connected to my phone and checking map a few times on the watch.
-
@harboe tried without bluetooth, reached 8 h…
…try to see how to exchange with suunto 9 -
Today I did six hours in airline mode and “Good”, starting at about 98%, ended up on 48%, following a route, with approx 25 WayPoint notifications on top of the 45 lap notifications, I looked at the map quite a few times in full power mode to get my bearings…I’d guess maybe 10 to 15 times of up to about 10-15 seconds.
The one odd thing I had at the end was Google Pay didn’t work, it said I had to enable NFC, but clicking did nothing, I toggled out of Airplane mode, and still NFC wouldn’t work, and couldn’t get to the setting in ‘Settings’/‘Connections’ either.
Paid for a drink with my phone, rebooted Watch and then NFC worked again. -
@drunners Do you run with your phone on you? If you do, then do not turn off Bluetooth or WiFi, as when connected to a phone they barely use any battery.
However, if the phone is not there, then the constant searching will drain the battery (in the same way a phone will drain it’s battery searching for a cellular signal when there is none).
If you do not take your phone with you, turn on Aeroplane mode on the watch.Getting just 8hrs of life while tracking an activity is not normal, so please don’t assume this is standard for the watch and write it off. There will be something unusual draining the battery.
As an aside, do you have any bluetooth devices connected to the watch? HR sensor, headphones, etc?
-
My current settings are AOD ON and touch to wake ON.
I get approx. 36-48hrs depending on the usage (activity, notifications, etc.)If I change the AOD OFF and power saver tilt ON, what is the effect on battery life?
This is just out of curiosity so not complaining about the current battery life.
-
@jantikainen: of course it will depend on usage, but at its worst its the same as AOD on / Touch to wake on, but generally you are 48hrs plus.
-
@jamie-bg being running the suunto marine watch face with AOD off, power tilt on, touch to wake on, 24/7HR, Resources and Sleep on.
Took off charger at 10am yesterday. Its is now 11am today and am at 54% battery. Tracked activity was before charge yesterday and haven’t had a chance to go out today yet, but I think that using these settings 2 days is probably pretty feasible. -
About battery life with the new features: https://www.uhrenundtouren.com/en/suunto-7-battery-life-with-sleep-tracking-daily-hr-body-resources/
-
The waypoints notifications are eating a lot of battery.
I did a 6 hours hike today following a course made in Komoot. The course had 24 waypoints(automatically generated by Komoot) so around 50 notifications (I saw that it displays a notification with 100m before and another on the turn).
I started with 93% battery, watch in airplane mode with best GPS mode, and after 5.5 hours I received a low battery notification and the battery was at 7%. Besides the waypoints notifications I checked the map 2 times for a few seconds.
15.45%/hour is a lot.
I usually get 12-13%/hour in the same conditions but with only 2-3 waypoints.Also, after I got the low battery notification I put the GPS in good mode and it continued for another 30 minutes after which the watch powered off resulting in saving the activity with some missing data(I posted more details in the Suunto 7 topic).
-
@steff I believe waypoints trigger the main processor.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi for sure, the problem is that it makes the Komoot integration somehow pointless.
On longer routes Komoot will generate a lot of waypoints which will drain the battery and you cannot finish the route.
If in best GPS mode the watch didn’t even last 6 hours I doubt it will last 10 hours in good GPS mode.
-
@steff well there is the option to not use those. It doesn’t make it useless.
Also staying on the map screen vs activity screen makes a huge diff
-
@steff Here are my battery estimates using TBT either on or off from many runs. I always place the watch in Airplane mode but all other settings are standard. I do occasionally scroll to the map screen but most of the time I am on the main display with the co-processor on.
No route loaded
Best 7-9h
FusedTrack 16-19hTBT Route Loaded
Best 4-6h
FusedTrack 10-13hYou had a lot of waypoints, I typically have 10-15.
-
@steff said in Battery LIfe:
The waypoints notifications are eating a lot of battery.
As confirmed by others, waypoint notifications do cause the watch to go into full power mode (same with any notifications from what I can tell)
I did a 6 hours hike today following a course made in Komoot. The course had 24 waypoints(automatically generated by Komoot) so around 50 notifications (I saw that it displays a notification with 100m before and another on the turn).
You can use the route editor in the Suunto App on your phone to remove any waypoints you don’t want/need. This may seem a faff, but it is still quicker to do this to an imported route from Komoot than it is to create the route in the Suunto App (in my experience anyway).
I started with 93% battery, watch in airplane mode with best GPS mode, and after 5.5 hours I received a low battery notification and the battery was at 7%. Besides the waypoints notifications I checked the map 2 times for a few seconds.
That seems excessive battery use.
If you have your phone on you there is no benefit from putting the watch onto Aeroplane mode (if you want to avoid notifications then do not disturb is plenty)
Also, for walking/hiking then ‘good’ GPS mode is more than accurate enough, and this should extend battery life by a fair bit.15.45%/hour is a lot.
I usually get 12-13%/hour in the same conditions but with only 2-3 waypoints.So the difference between 24 waypoints and 2-3 waypoints is roughly 3% battery drop per hour? That doesn’t seem significant to me? Or am I missing something?
Also, after I got the low battery notification I put the GPS in good mode and it continued for another 30 minutes after which the watch powered off resulting in saving the activity with some missing data(I posted more details in the Suunto 7 topic).
Try the same route, but with superfluous waypoints removed and the GPS set to ‘good’ and see if the battery life is any better
Suunto 7 Graphite Copper
Suunto App Beta (Android - Pixel 6 Pro) -
@olymay said in Battery LIfe:
@steff said in Battery LIfe:
The waypoints notifications are eating a lot of battery.
As confirmed by others, waypoint notifications do cause the watch to go into full power mode (same with any notifications from what I can tell)
I did a 6 hours hike today following a course made in Komoot. The course had 24 waypoints(automatically generated by Komoot) so around 50 notifications (I saw that it displays a notification with 100m before and another on the turn).
You can use the route editor in the Suunto App on your phone to remove any waypoints you don’t want/need.
Yup I find creating my own route in Plotaroute with my own RoutePoints is FAR better than the default Komoot TBT.
However, on the points quoted above, I think its a necessity that there is some config/customisation on which/when notifications are displayed which could result in dramatic improvement.
On that 24 WayPoints example…its actually more like 70+ notifications. You get the notification at the actual RoutePoint, then a few seconds after you get a notification telling you about the next WayPoint (no matter how near or far it is), then as you say, about 100metres before you get the pre-notification notification. So its about 3 notifications per RoutePoint.
For me I’d much rather have only the single ‘notification at the actual Routepoint’…I never ever miss the notifications, so no need for a ‘pre-warning’…I can imagine for cyclists the 100metre pre turn alert might be useful however. But the alert that comes “just after” you’ve passed a RoutePoint, I just don’t get that one at all.
Please can we have a config setting.
-
@nigel-taylor-0 I love Plotaroute but the method of exporting and then importing via Quantified Self is more of a faff I find (unless I am missing a trick?).
And yes, I agree that customisation of waypoints would be great.
Some people may only want a notification when they reach the waypoint (me included) some would like some warning. And depending whether you are walking, running, or cycling should determine how far away that warning is.
