@sartoric I don’t found something related to HTC, but this topic which not resolved as well : https://forum.suunto.com/topic/1480/not-all-notifications-of-the-phone-can-be-pushed-to-watch/1

@margusl

It is not always the strap - at least in my case. I bought a new strap the first time these strange readings started happening because people on the Watchuseek forum suggested it and replacing the strap did nothing, I still had spontaneous bad readings, not every move, but totally random. Some FW updates were OK, others I had the problem … the pattern was usually every other update was bad for HR. Now I have two straps and two smart sensors at home and changing either just the strap or both sensor and strap doesn’t help. I don’t care much about HR anymore, it is just a guideline when I’m cycling uphill so I don’t overdo it, otherwise my legs give out sooner than my heart and lungs do. It is just something that bugs me and should be working OK-ish.

Either its already fixed or I need to put attention to this again. Could you check please with the latest app version?

@MatthiasKlug @Dimitrios-Kanellopoulos Based on my finding with Spartan Sport wrist hr baro, v 2.8.24, if you have auto laps ON, manual laps are not displayed in watch. When you switch auto laps OFF, then you are able to see the manual laps on watch. In both cases, even when you have auto laps ON and manual laps are not visible on watch, the manual laps are correctly shown on Suunto App. I think this sounds like bug or at least strange working feature. Ultimately it would be great if you have separate fields (in sport mode customization) for auto and manual laps.

@Mff73 You’re right, you’re right … Ah, the good ol’days I knew someone already found it

@Dimitrios-Kanellopoulos Great to know that! Thanks.

Watching. Reset could help.

Was this ever investigated, or is it considered “fixed”? I (briefly) installed SA, last week (v.4.2.4), and had a similar issue, it was pretty tough on the battery on two devices, an old Nexus 6P (Android 8.1), and a OnePlus 7 Pro (9.0, or Oxygen 9.5.8). My device(s) are both Ambit3(Peak) models. I was seeing a “bonus 12-15%/day”, which immediately reverted, when removed (the app). Given that it was taking 5+ minutes, per-activity, to sync my Ambit3 anyway (still, it’s always been like this), making it largely impractical to sync after an activity, particularly if I had several rides to sync, I uninstalled it for a variety of reasons. MovesCount isn’t really faster, but it also doesn’t The battery issue makes the app unusable, IMO, given the impact it has on the phone/device, in-general. @Dimitrios-Kanellopoulos Or are you saying that “10%/day” is considered “normal”, for SA? Thanks for any info/update here.

@Anders-Ljung You can open the route and deactivate it from the “details” view

@v-sacre said in Routes : 2 issues: @sartoric No So that’s strange. Have you tried to just disable it, just to see if they are duplicated once sent back to the watch ? Maybe unistall/install did the job for the point 2 too as my suspicion is related to app data/cache

I have ré installed an old version of SA, and splits laps are more correct for the same activity show previously. But total activity descent is 9m, and first 5 km splits say 3m descent (3x5=15 ) [image: 1562138118767-img_20190703_091321.jpg]

@Dimitrios-Kanellopoulos yes, you’re right, I tried changing that, learning that it is impossible with MC app and now did it thru the cable… at least in MC web it shows that the setting is on baro now. hope this solves it.

FW update without at least MC sync is possible only if you disconnected the watch from the SL app and do a FW update that way. Otherwise SL always syncs everything first, then lets you update the FW.

@fhegnor Thanks to confirm, I need to delete browser cache, and I have now the right behaviour. I could have checked before asking Solved.