Suunto Vertical: Bug Collection

Egika

@Iggge said in Suunto Vertical: Bug Collection:

Fix for the sleep tracking. I always sleep at least 6 hours, But the watch always says 2-4 hours, every night. As it stands now it is more or less useless to sleep with it…

Like in other thread: this is most likely not a bug, but related to the settings. Have you setup your personal rest heart rate to a value that equals you resting (and not minimum during sleep)?

Iggge

@Egika How do you do that? Suunto is The first brand that dont get this correct. Otherwise i like the Vertical

Iggge

@Iggge

Egika

@Iggge Settings - General - Personal - Rest HR

…I think we need an FAQ section in the forum…

Iggge

@Egika Done that. Have it on 60, and before that i had it on 65.

DrSilverthorn

@Egika said in Suunto Vertical: Bug Collection:

Like in other thread: this is most likely not a bug, but related to the settings. Have you setup your personal rest heart rate to a value that equals you resting (and not minimum during sleep)?

I too had this set to the wrong value. While it is called ‘resting’ heart rate, it is easily mistaken for minimum (sleeping) heart rate, because of its placement near the maximum heart rate settings. Maybe it should be in the sleep settings menu, although I’m not sure that would do it either. Interesting that I never made the distinction between the two numbers.

Since I have used Garmin devices it’s interesting that on Garmin, resting heart rate=minimum heart rate/sleeping heart rate. These numbers were automatically updated based on watch measurements. Polar gets the distinction right, but I never read that part of the manual (lol).

You learn something new each day… If sleep tracking works for me after this, I will really be impressed. I’d just resigned myself to the fact that it has never worked for me on any watch that I’ve owned (Garmin/Polar).

Antoine Lancrenon

hello,

I lost completly the touch capacity out of the blue… it is the second time it happens in 5 months, each time a doft reset fix the issue. it is judt weird, i dont think i sm doing anything special. i think i need to send the lig when it happens next time, it will help for byg tracking and solutions for future soft version.

is this bug reported already? only 2 times in 5 months, and I am using the watch every day with activities tracking, not that bad.
2 Crash from an activity also
and the battery drainage because of the suunto app

Those are my only issues for the past 5 months.
very good watxh, waiting the November update!!!

mikekoski490

@Antoine-Lancrenon Since my purchase in June this has happened twice in the past 2 months as well. Never during an activity. Soft reset fixed.

loopylou72

@loopylou72
Today my new SV:
-did not show the first two sport modes in the menu - were white
-would not connect to my Core even though no problem yesterday
-did not sync to the app at all, I disconnected from the app and then could not reconnect or pair my watch - firstly the app listed my watch but the connect option was not selectable; then I refreshed the app and my watch was not being discovered at all.

finally I had to reinstall the app and set up my watch again to connect
I have had issues connecting to devices previously connected OK
is there a Bluetooth bug?

BrunoH

This morning I experienced my first bug: SV woke me up at 7:00, but the watch screen was frozen and showing clock face at 6:59. The alarm kept buzzing and buzzing and none of the buttons worked. It kept doing this about 20-30 seconds, then it rebooted and came back to life showing my sleep summary screen.

Jonathan C

@Egika according to this page, aren’t we supposed to “use the lowest heart rate reading measured during your sleep as your Rest HR”?

jjpaz

@Antoine-Lancrenon Same here today. I woke up and the touchscreen was not working.
Also my battery level was 18% and I received the advice to connect to charger so, I have connected the SV to the charger and (oh! surprise) watch has rebooted himself…

New bugs before the “no issues” software??

Many “little” and random bugs, will be corrected?

Maryn

@jjpaz today I had a 20% drop over night. New device.

EzioAuditore

@Marcin-Byrtek I think the first few charges the battery ‘calibrates’ and the 20% drop is not actually ‘true’.

Brad_Olwin

@jjpaz It is possible the battery was lower than indicated, the touch was turned off. When very low these types of batteries can deplete quickly. So this may not be a bug as your watch may have shut down once on the charger.

jjpaz

@Brad_Olwin It didn’t turn off, it restarted. I didn’t touch the watch. And battery level when charging started from the level it was before restarting, 18%.
So, it’s not a bug but watch didn’t show the correct battery level? Is that right? So, according to this, I can’t trust the battery level the watch shows. Perfect!
I think the answer is easier: there was some issue that cause the touchscreen not working and the reboot.

Brad_Olwin

@jjpaz Could be. I’m not sure. Was just a suggestion.

mikekoski490

Just thought I would pop this in here, as I know some people have said “Im thinking of switching to Polar!” Just to put the big ecosystem of all watches have issues in perspective. Taken from the Polar users FB page:

Users of Polar Vantage V & V2 and V3.
· 2h ·
3 times during training my new V3 crashed (needed to setup as new device afterwards) - App and watch on newest release. Anybody experienced similar issues?

ChrisA

@mikekoski490 Polar watches were quite basic, relating to features (even less watch faces, no loadable apps, only four data fields and limited data to display etc.) But (at least mine) were running extremely stable! Could be, that with more and more features added, chances raise, that more and more things could go wrong. I recall somebody with IT background here in the forum saying, that adding a little bit here and a little bit there might sound easy to do, but isn’t so easy in reality .

jjpaz

@Brad_Olwin Thank you for the suggestion.
I explained the issue just for help if anybody suffers same behaviour.
For me, in case of that, is just a small bug because it hasn’t happened during activity.
“During activity” crashed are the worst issues (only happened once in more than 5 months using SV)