@Dimitrios-Kanellopoulos said in Android 3.42.0 : Generic Comment:
@WEM_t what do you mean ? Its beta due to testing if the fixes are OK and there are no crashes.
Yes! Everything works fine for me like before the update. No improvement in performance found but did also not have issues before…
But maybe this is exaclty what Suunto wants to know. (testubg on Samsung S8)
@ChubbyCrusher said in POI upload to watch discontinued.....:
I’ve been completely blown away by how Suunto has totally disregarded the primary user group they had a clear lead with: hikers/skiers/Backcountry navigators.
I totally agree.
I was considering switching to SA since Suuntolink suggests that SA is the future…
Lucky me that read the FAQ and this thread. Given that moving to SA apparently will disable upload of POIs to my Spartan makes Suuntos “suggestion” very difficult to understand.
How can Suunto recommend something that would disable a key function for navigation?
@Mff73 said in Android 4.15.200 : Generic Comments:
these maps are people’s contributions, anyone can contribute to make them properly set
I will spend some time to do further testing and will send the findings to mapbox.
The point with setting follow path or road etc is good. But it is not intuitive. When I have selected footpath (?) and instead of following a street between houses it routes me to the front doors…
I think it is a setting of roads that are banned from motorized vehicles and real private roads
If I try to edit a route (GPS inactive) the map is not centered on the route and is shown at the the lowest zoom level.
Same issue with active GPS
If I rotate the phone while in edit mode, at each rotation it does something
center map to route
looks like it stop zooming at a certain point (doesn’t seem to be the max zoom level)
Maybe is a map refresh issue ?
Is it just my problem ?
@borgelkranz said in Blockers to full SA adoption:
What I miss:
Training plans and planned moves
Connection with Stryd
Several metrics, e.g., power
Customization for interval screens
A web page or desktop variant (also for Linux)
I stick with borgelkranz (and others).
I thing that I’ve noticed in this version is that pace graph scale now seems to be fixed at arbitrary scale with 2 min/mile at the top and 14 min/mile at the bottom. This is only marginally better than it was before. The range is arbitrary and not very suitable for something like trail running on mountainous terrains. I’ve had plenty of trail runs on steep terrain where my average pace was slower than 14 min/mile meaning that a large part of an actual range gets cut off, including all climbs. At the same time 2 min/mile at the top is unreachable by anyone. That is 48 km/h. SA developers should look at how pace graph is done in Movescount (web version) and copy that. It is done the right way there.
I have problem with heart rate zones. I have set them in Movescount like this:
zone 4: 164-183
zone 5: 183-205
but in Suuntoapp they look like this:
zone 4: 144-162
zone 5: 162-188
I have Ambit 3 so I can’t set heart rate zones in my watch.
Max heart rate is set to 205 and age to 23.
@Dimitrios-Kanellopoulos said in Start of week not updated on SA.:
@Brad_Olwin Hi UK still has the week on Monday.
Please select for example finland.
I just tested this with the region and works for me
Yes it works but herein is the problem as it changes many other settings including currency etc. Here is a photo in iOS of my settings, which SA for some reason does not respect.
@hanta said in Incorrect HR zones on Suunto App:
@sartoric said in Incorrect HR zones on Suunto App:
Do you mean, still there in 4.9 ?
@Dimitrios-Kanellopoulos mentioned something it might be caching (server side?) issue.
I was missing sleep tracking in Suunto App since I’ve updated to 4.9 (about 2 weeks ago).
Yesterday I just turn off sleep tracking in the watch, and turn it ON again, set up the same start and end hours, and today I’ve got the same hours, deep sleep, HR,… on wach and in App.
Don’t know if you have tried it already.