Battery LIfe

olymay

@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.

Nigel Taylor 0

@olymay said in Battery LIfe:

@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?).

I find it very simple.

You’ve created your route and added the directions you want with shorthand text in the description “LEFT” etc - just add a ‘symbol’, then export from Plotaroute with the ‘POI’ option (all directions you’ve added a symbol to will be included).

Then click on https://quantified-self.io/services - click on the route icon and drag your exported file on. DONE.

Or - if you use Runalyze, just click here - https://runalyze.com/my/suunto/route-upload - choose your file and likewise, DONE.

Route will be immediately synced to watch…and next time you stick watch on charger, maps surrounding the route will be downloaded if they aren’t already part of your local downloaded area.

olymay

@nigel-taylor-0 Cheers! I’ll have to give it a go

Steff

Thank you all for the answers.

@Brad_Olwin your TBT Route loaded with Best GPS estimation seams exactly as mine, so if FusedTrack will last 10-13h is very good

@olymay

This seams to be the best option.

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).

Are you sure about this ? When I received the watch I made some tests and in Best GPS mode with no route loaded, the difference between airplane mode and phone connected was about 3 hours of battery.
I also saw a lot of similar reports on this forum.

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)

3%/hour difference means about 2 hours of battery. For me 2 hours is a lot.

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?

I will try next time.

Try the same route, but with superfluous waypoints removed and the GPS set to ‘good’ and see if the battery life is any better

Steff

I did another hike today, 4h50min, best GPS, airplane mode on, no route loaded, I only checked the map 2 times(max 10sec in total) and it consumed 76% battery.

This means 15.72%/hour, even more than last time when I had a route loaded with lots of waypoints.

I don’t know what happen.
I also noticed that in the first 30 minutes, that watch had a hard time to lock on my HR. It fluctuated a lot between 100 and 160, even though I was a climbing so my HR should have been constantly above 140-150.

I’m a little disappointed about the battery life.

When I got the watch in January this year, I made several walking/running tests and I was getting 11-12%/hour with the above settings, which means 8-9 hours of battery.

90% of my hikes are under 8 hours so I though it will be enough.
Now I get 6 hours at best…

And no, good GPS it’s not always an option.
Most of the paths from my hikes are very twisty and sampling GPS every 10sec creates a total mess.

Brad_Olwin

@steff 6h is OK but 8 should be possible if fully charged and you do not go to Navigation very often.

Steff

I made another test today, a walk through the city, so possible worst GPS reception, same conditions as above (best GPS, airplane mode on, no route) and in 1h43min it used 20% battery.

This means 11.65%/hour so ~8.5 hours of battery.

I don’t understand from where is the difference.

I start to believe that is something relating with hiking profile.
I will try next using the hiking profile.

Brad_Olwin

@steff I will test hiking as well, I rarely use that.

isazi

Lots of talking about the S7 this week, so I got curious and decided to dedicate the week at testing the S7. Focus will be on battery and ascent/descent. In this thread I will report battery stats.

Monday, walking for 59m 39s. No much interaction with the watch, except looking at it once. Connected to my phone, receiving notifications. No map use, just one complete walk of all screens. Autolap notifications every 1k (no way to disable them). Best possible GPS settings, never used the other one.

Battery consumption: 10%. Estimated battery life: 09h 56m 13s .

Steff

@isazi I also just got home after testing if FusedTrack is different from one profile to another.

First I did 30 min, hiking profile, 4% battery.
Second I did 41min, running profile, 5% battery.

Both cases walking, with airplane mode, no route loaded, no interaction with the watch, 10sec GPS.

In total it means 7.6%/hour and 13.15 hours battery life.

I don’t know how you managed to get 9%/hour with 1 sec GPS and watch connected to phone.

Tomorrow I will try to make the exact test as youres.
What profile did you used?

Regarding FusedTrack, it seams there is no noticeable difference between hiking and running profiles.
In both cases I got good results, much better than what I got during the 6h hours hike.

isazi

@steff said in Battery LIfe:

What profile did you used?

Walking.

I will do a longer walk on Wednesday, as longer activities should give better (i.e. more realistic and precise) estimates.

Brad_Olwin

@isazi @Steff I have quite a few examples of S7 with and without FusedTrack. All of my runs/ski: S7 in Airplane mode, that is it, I do not use the maps much but will look at them occasionally. I have a few other apps installed but am using the watch normally. None of these is with a route loaded, that will cut down the FusedTrack time to ~10-13h and Best to ~4-5h. These are from QS estimates, and you cannot get good estimates without a decently long exercise so do not try to extrapolate from a short 2h exercise.

Last Saturday Best

Here is a bit older one from last summer on FusedTrack:

Steff

@brad_olwin how did you get the battery estimates in QS?

Brad_Olwin

@steff From json files.

Steff

@brad_olwin thank you, very nice, I didn’t know about this, I was wondering if there is a more precise way than remembering the percentages when starting and when stopping

Brad_Olwin

@steff if you have an Android phone you may be able to extract them but these estimates are fairly good. Again, attempting to estimate from short exercises will not provide accurate estimates.

Steff

@brad_olwin yes, I saw how.

@isazi Today I made almost exactly your test: 1h12min walking, best GPS, connected to phone, no route loaded, no interaction with the watch.
Additionally I put the watch in DND to not receive notifications and also autolaps notifications were without sound and vibrations.

These are the results

A big difference from your results.

isazi

@steff every test is different. I have a new test with elevation planned for tomorrow.

Brad_Olwin

@steff We do not know what 3rd party apps you have or what watch faces, these may have elements that cause the watch to search for data and reduce battery life. I had an altimeter app installed that seemed to dramatically reduce my overall battery life.

pilleus

@brad_olwin said in Battery LIfe:

cause the watch to search for data and reduce battery life

I do not install apps which need the permission for location service. As soon as the airplane mode is activated the app will use internal GPS to find the location. That is a real problem for battery life.