Software release 2.30.26
-
@Michaël-POINTEAU Look in the initial part of the activity summary. There’s a “LAPS” banner with an arrow pointing right: in that place you can press middle button to enter the laps table.
Before update you could press middle button in every part of the summary, now is only in a specific part (LAPS) -
@Michaël-POINTEAU said in Software release 2.30.26:
@duffman19 I have found the menu on my trail race from Sunday. Manual (Climb) and Auto Laps but on my 10k race from previous Sunday there is no Lap Count despite I had 1km auto laps… bug…
Also no laps in Suunto App after syncing? Did you get the laps notification during the activity?
-
@Dimitrios-Kanellopoulos thanks for info
-
@Sergei-Ladeishchikov I believe out goes into power saving mode at that point and vibration is stopped?
SV Solar
iPhone 16 Pro -
@Jonathan-C I do see the weekly complication in the new watch face have not tried the others.
-
@Egika @larrybbaker thanks, needed a full reset to restore the complication. Hate to do it but seems necessary once in a while to clear out some obscure bugs.
Edit: Actually, I figured out that one can only choose between showing Weekly Training and Dual Time!
-
Found interesting glitch:
Burner (sport app), if previously selected, is not shown as selected upon re-entering into list of SuuntoPlus section.
However, if one will scroll down through the list (of sport apps) so that Burner no longer is shown on watch screen, and then will scroll back (to see Burner), then selection mark of Burner app would be shown as expected. -
Right now, my battery level is 10%. Battery estimate for Running (Basic) in Performance mode (no SuuntoPlus apps, etc.) is 4h. Shouldn’t this be closer to 6h according to expected 60h battery life on full charge?
SV: fingers crossed :D
S9 (non-baro): died after 2 months, replaced, holding strong since 03/20
Spartan Trainer: casing broke after 23 months, repaired, lost watertightness 5 months later, died
Despite some pretty bad luck, I still love Suunto! -
@larrybbaker At 12% charge, vibration becomes barely noticeable and then disappears completely. If you turn on sound, sound notifications work. The power saving mode is disabled (if I remember correctly, it automatically turns on when the charge is 2%, it also notifies when the power saving mode is turned on and the screen becomes dim). This error was present in the previous version of the software. This way it is very difficult to drain the SV battery to 0% because I will miss all notifications from the phone for 2-3 days. I would have thought that the problem was in the watch itself, but the previous watch was replaced under warranty and the situation has not changed. It is very strange that no one has noticed this yet in the new software, or has their clock not yet discharged to 12%?
-
@Sergei-Ladeishchikov I would avoid discharging the battery to 12% and below. As with mobile phones, the battery should be charged between 20 and 80 % so as not to shorten its life.
-
I have this morning a new issue that i have never seen before update (installed on 16th november): i can’t use touch screen anymore on my suunto vertical to change screen/menu, it doesn’t work, and it is only possible to use button.
A soft reset (12s on upper right button) solved the problem.Watch: Suunto vertical solar
-
@Antoine I have commented on this problem twice, once with the previous version and once with the current one.
-
@jjpaz i have never seen that with previous update. It was during the night when sleeping.
-
@inkognito said in Software release 2.30.26:
Right now, my battery level is 10%. Battery estimate for Running (Basic) in Performance mode (no SuuntoPlus apps, etc.) is 4h. Shouldn’t this be closer to 6h according to expected 60h battery life on full charge?
mine was at 9% yesterday before running, and my estimation was 4h (custom mode with touch screen activated).
I will deplete it fully today to charge it fully after the latest FW update and calibrate my battery.
Maybe yours has another “calibration” currently -
@Ars-Vitae said in Software release 2.30.26:
@Sergei-Ladeishchikov I would avoid discharging the battery to 12% and below. As with mobile phones, the battery should be charged between 20 and 80 % so as not to shorten its life.
for everyday life, yes, it seems to be a recommandation, but after FW update, and for battery gauge calibration, we also are recommanded to make a full charge cycle once : this unique one should not damage the battery, and when watch will announce 0%, it will just be 0% from the watch meter, and not a total battery discharge.
just my thinking from what i am hearing and reading everywhere.Suunto Spartan Ultra (since 2016) FW: 2.8.24 (retired)
Suunto Vertical all black
Wife : S9PP
SA: Always the latest beta :)
Android 13, Galaxy S205G -
Hi, I have a new Vertical. Slept with the watch yesterday. And at night I got a notification that I’ve been sitting for a long time and it’s time to move
If it was mentioned here, I’m sorry.Vertical All Black
ex:
Ambit2 Black
Ambit3 Peak Sapphire
Spartan Ultra Stealth Titanium
S9B All Black
>>> YouTube Channel <<< -
@Pavlas
did you setup your sleep times range in the watch ?Suunto Spartan Ultra (since 2016) FW: 2.8.24 (retired)
Suunto Vertical all black
Wife : S9PP
SA: Always the latest beta :)
Android 13, Galaxy S205G -
@Pavlas In my case, I have never had a notification about inactivity. At work I sit at a desk almost all the time, so it’s weird. My Polar Grit X would show me this notification from time to time.
-
@Mff73 Yes. And the latest firmware.
-
@Mff73 This procedure, calibration, is followed usually after replacing the battery with a new one and is usually done by a service technician. Unless you are replacing the battery yourself. We would have to calibrate the battery after every system update on the computer, and yet we don’t do that. Such a “calibration” also consumes the battery (I didn’t write, that it “damages”). In my case, a soft reset of the watch, that is restarting it, helped. For instance, I had a battery level of about 63%, which dropped from 68% in 24 hours. After a reboot it went back to 66%.
