This problem was allready reported in the beta version by different users.
The scale should be 14443 m or 14.4 km
Fenix 6X Sapphire
This problem was allready reported in the beta version by different users.
The scale should be 14443 m or 14.4 km
Fenix 6X Sapphire
Why ? Isn't that obvious. They don't care. There can not be any other explanation.
Please be nice in our forums. If you personally knew the engineers, saw the hours they work, and…
The issue is resolved with the v25.00 software update.
https://forums.garmin.com/members/af7e41af518b479984b3757ab539b01f
You seem to be a good guy, anyway, G-Chris. It is not your fault what the general outcome of all these issues are.
And frankly speaking…
The engineers are not the problem. Having worked as a software developer over 7 years for several companies now, it's mostly unrealistic planning or unrealistic demands that screw things up. If you ask a dev to deliver a fixed feature set in fixed time, things can only go wrong. Same for not allotting enough time to fix bugs because features sell better.
I don't know which is it with Garmin, but probably some of the reasons stated above. The engineers/devs are the ones who always get the blame though.
It's not just the engineers. Software development is a process that involves several stages to ensure quality control. Why didn't this get caught in testing? And how did it make it into the official release even after it got past testing, made it into beta, got reported there and was then ignored?
More than just the software engineers dropped the ball. This is basic software engineering. And it reflects poorly on Garmin.
What is it that gets dropped first when you constantly don't have or given enough time? Exactly, QA.
Though in this case, it's just a translation error, probably because it's outsourced and the translator has no context to work with. Not really that big of a deal, there are other things that are far more annoying.
1. Can somebody please tell me what “altitude profile in activity status” exactly means?
I use Elevation as one of the data screens in all of my gps-enabled outdoor activity profiles, but this screen has a chart whose X-axis is time and it cannot be configured to be distance, instead.
In Altitude widget the scale of X-axis is 4 hours, so time again.
2. I used the first navigation with sw 24.00 and Climbpro page gave me this nonsense. Unfortunately the unit of X-axis is unvisible.
Hey, maybe Garmin can try themself ?
- Our engineering team is not in our forums.
- The reason I am moderating and taking the time vs. ignoring this thread is my hope to learn as much as possible that may lead to a quicker resolution of the issue.
I appreciate sarcasm but also understand, the more details I can add into the escalated tracking case for engineering, the quicker an issue gets resolved for everyone.
Thank you to everyone providing information.
https://forums.garmin.com/members/af7e41af518b479984b3757ab539b01f
You seem to be a good guy, anyway, G-Chris. It is not your fault what the general outcome of all these issues are.
And frankly speaking to be a lightning rod (as we say in Hungarian when somebody is in the front to ger the punches instead of the others being in the background) is not a grateful job.
In the history -> Activities -> (Select an Activity) -> (Select) -> Scroll from All Stats, Training Effect etc down to Elevation Plot, (Select)
I'm not sure what's up with your Climbpro page, looks as if you have no course set or a very long one? Last time I used that page was on 23.84 beta and that worked well (trail run activity, while navigating back to start).
Thx, so “activity status” in the opening post seems to be activity stats. Strange that this typo confused only me.
So me is experiencing it.