@Dimitrios-Kanellopoulos I rebooted the phone and flushed the app’s cache, and now it’s working properly again. I’m still having the missing Mapbox terrain maps (and satellite maps too since a few days ago) issue from the previous version, but that wasn’t something that I expected would be fixed with this incremental update, anyway.
Sure, I’m not saying it’s wrong, but that the graph looks weird.
Despite the scale values, all the points should be drawn inside the graph, or the line shouldn’t be drawn.
It should be considered that the BMR will be reached by the end of the day, so on Monday we are on a limit / special case
@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?
@sartoric had to delete, reinstall the app and pair the watch again and the steps and calories were there. Well, only for the previous week and this one. Unfortunately, there’s no history before the 2nd Feb but at least it syncs now.
@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 ?
The same story is on Movescount. The problem is not the watch, not the Movescount, not the Suunto app. The problem is missing data - altitude data in database. You can see very jagged line for altitude CREATED in movescount. The movescount measured 860 m
of altitude for that 64 km track. Movescount takes neares altitude point for created track, the result is jagged line an a lot of altitude for that small climbs. But when I measure track with watch, barometer and barometer is very precise and not very
accurate, but barometer measure all hills. So when I was at the higghest point - blue arrow, s9b showed that i had another 600 m of altitude to overcome. Why, because ACTUAL- MEASURED 260 m was behind me (in the watch) and created route has still 600 to the end ( 860-260 = 600)
actual altitude was 314, movescount calculation is 860 m
@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.