"Changes made from 9.40 to 9.50:
- Fixed BLE sensor connection issue with CIQ data fields."
Is that really the only change?
"Changes made from 9.40 to 9.50:
Is that really the only change?
Probably. These units have probably reached their limit as far as features go and all they/re trying to do is make sure we can use them into the future. I expect new models to come out shortly. Actually I'm anxious to see what comes out next. The jump from my 520 to my 530 was really nice. I wonder what's waiting around the corner
Let me highlight that there are bugs, even some that were reported by average users, but were confirmed by advanced users. I raised only one bug of this sort, and it was reported to Support by an advanced user, but was not fixed yet, though.
I have read your other thread. I do admit that it does seem like a simple thing and wouldn't be that difficult for Garmin to answer. I mean, it's either restricted by memory or the table that contains this data has a limitation. I have done database design (a long time ago) and the answer should be obvious to anyone who designed it. It wouldn't take the senior designer hours to research it. I really don't see Garmin correcting something like that this late in the game.
Hi - did my first tour today with 9.50. No single auto-climb triggered when there are usually 3 on the same route (did a recalc of the route before this run). Wonderinf if anyone else has issues with auto-climb? same for my favourite strava segments - not a single one showed up.
I was just simply trying to express that if they would like to “close” 530 as a product and focus on the launch of a successor, then the easy wins should have been done while the complicated ones may be fully abandoned.. But this bug I mentioned is really not something that disturbs me, because I can create anytime a fake waypoint being on the very opposite point of the Earth.
Updated to 9.5, and Strava segments seemed to work fine. Didn't try the auto-climb yet.