Is there any update? Heat map on Android app !!! please

Since 9 months the app was not out.

In my opinion manual laps and intervals can be seen as the same thing…I know they are considered different on other platforms, but I never saw the need to make such difference.

@Dimitrios-Kanellopoulos what is interesting that after few sec for same activity speed has changed, miracles happens some filtering applied?

@Ze-Stuart I hope so.

@jthomi had a user with this issue. @Thomas-Bellos Keep me posted

@Jani-Kaikkonen Well that’s fair enough …

@hanta not at all to be honest. If it is I’ll make a plan and include the users here

@Václav-Král let me report that

@valdis830 be patient with an update it doesn’t happen very frequently, vocation period is still active

@Jose-Luis For long distance it is important and would be very helpful.

Hello, Great, thanks.

Here you go: https://forum.suunto.com/post/2847

Both of which would be great on iOS (top time chart on a distance - not a given route, and similar route comparison) Do we know if that will be inlcuded in the next beta version (and when a new iOS beta version will be available?) Thanks!

I just switched to Android, checking this is still pending, and I’m not missing something…

Well … I can’t reproduce the “zombie” issue, but I’m almost sure it was due to a mix of enabling/disabling/renaming operation (img attached) It’s possible to have routes with the same name in SA (guess it’s intentional) but this can create some trouble due to the previously identified data problem *** Boring Test ALERT *** *** Skip the rest of the message if you’re not interested in nerdy debug stuff *** Starting point : Previous post Renamed Route A -> Aren Sync - 9 Routes in watch - Route Aren in watch Disabled Route Aren - OK (Toggle off) Sync - 8 Route in watch - Route Aren removed from the watch Renamed Route B -> Bren Enabled Route Bren Sync - 9 Routes in watch - Route Bren in watch Enabled Route Aren - OK (Toggle on) Sync - 9 Routes in watch - Route Aren in watch, Route Bren disappeared Renamed Route Aren -> Aren2 Sync - 9 Routes in watch - Route Aren2 in watch Disabled Route Bren - OK (Toggle off) Sync - 8 Route in watch - Route Aren removed from the watch Enabled Bren - OK Renamed Bren -> A Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off) Renamed Aren2 -> A Sync - 8 Route in watch - But in SA Route A (Toggle on) Enabled Route A (the one was Bren) - OK Sync - 9 Routes in watch - Route A (the one was Bren) in watch but now it’s not possible to know which one from SA was sent as both toggle are on and data are messed up “cleaned” the SA routes Disabled Route A (the one was Bren) - OK (Toggle off) Sync - 8 Route in watch Disabled Route A - OK (Toggle off) Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off) Deleted all SA routes Sync - 8 Routes in watch Sync via Suuntolink … now it’s time to move

@suzzlo you can check yourself altitude graph starting time and you will discover that it is never ever 00:00’00 because of 0 altitude few milliseconds which is filtered by MC which = middleware solution and you don’t need even to know the code…! So to permanently fix this watch FW needs to be corrected and that watch minor freeze solved ASAP if as Dimitrios said cannot be workaround at middleware as now is

@Mi_chael I also thought that it is always a belt, change 2 in 1 year. Lately sensor too. HR remains frozen or watch stop receiving HR data. Relocating the battery on the fly sometimes helps, but it fails again and again. Today I opened repair ticket. I’m fed up

@Armin-S I agree that this should be fixed, but there are more important bugs to be smashed, that is my point

@SlaSh I’m pretty sure we get a new version for iOS in less than 33d, but a valid point and noted.

My app is also syncing in the background, that is no problem. It was syncing while completely off and that behaviour was new. But seems like its gone already, now App & Watch only sync when app is running, front or background doesn’t matter. @Brad_Olwin said in Strange behavior or lack of knowledge?: @jthomi my app is syncing in the background. Occasionally, it does not and I need to force quit the app. When the app fails to automatically sync, if I check the watch connection it usually cannot connect to the watch. This is rare and either an app force quit or iPhone reboot solves the problem. I do not think this is an app problem but a BT communication issue. When this occurs, my notifications are often missing too.

@Dimitrios-Kanellopoulos Pal, ass no. Then we are all hahaha

Against the communication in this release note, the Custom Sport modes are not yet visible for the user in this release. My apologies for this ‘teaser’.

@johan6504 I am also having issues with the belt. Last activity was flat for some reason. Will investigate more. Funny previous ones in the pool were ok

@jthomi My procedure is: unpair watch, uninstall MC app, install first SuuntoApp (beta), pair watch, synchronize. Then close app (multitask). Install MC app. Synchronize watch without pairing. And voila!! As a preventive measure, close the app from multitask before opening the second one. Both apss opened may cause a watch reset. I tried the process in inverted order starting with MC app and it did´t work for me

@WEM_t Suunto won’t communicate it to public as its not a timed decision. I don’t think movescount will be stopped if we are stuck with the current status of the apps. No way.

@valdis830 thanks a lot. I’ll do it.

Great, it’s a correct solution. At least for iOS through iCloud Drive

It seems our support is quite busy if they have not been able to reply. This sounds like a stack corruption on UI transition. The 12s reset should fix it, but I’d be really interested to hear your SW version and language you were using and so on, can you reproduce it. If you can it will be easy to fix… You could also sent log to us with Suuntolink or Suunto app and ping me about the time you did sent the logs and the watch serial number.

Late at the party. Polar and fit support is bad. I am using it and its not good. Same for Strava Also AFAIK, google fit is being slowly killed and its api has not been good for so long. Has a lot of flows to be honest and its mainly supported for wear devices. Google fit was good , its not any longer.

@SlaSh done that thanks. Hopefully that will solve it. Thanks.

@badboy1997 Fitbit is not open source that’s the reason and suunto with Fitbit are competitive companies…Imagine Fitbit allows to sync from suunto for free, so it is like shooting to your foot

@Brad_Olwin Me too

@aldnet especially on weekends

@pdxbrothaman I was Garmin user and same thing with them as well. Apple Watch is having more access to HealthKit to write data than other brands. Indoor workout marked as outdoor, no average hr and other sort of issues…