Ability to change the Climb Pro climb criteria i.e. climb score -
Add next turn direction to navigation
Increase beep sound for navigation
Ability to change the Climb Pro climb criteria i.e. climb score -
Add next turn direction to navigation
Increase beep sound for navigation
I'm not sure how much can be done on the 1030 but for the next iteration (1040?) I'd like to see the following:
Hardware
Faster, always faster.
Better battery life
Add solar charging as in the…
Also, ability to edit and configure pages via PC Garmin Express or Phone would be awesome.
I'm not sure how much can be done on the 1030 but for the next iteration (1040?) I'd like to see the following:
Hardware
Faster, always faster.
Better battery life
Add solar charging as in the latest watches, this would work better on an edge than a watch due to it's position on the bars and would be awesome for bikepacking with limited ability to charge.
Improved sound output, it's too quiet to use as an alarm for example and can't always be heard above traffic. Would need volume control.
Better use of screen space (smaller bezels)
More variety in system sounds (opening the way to a ConnectIQ pull my finger app)
Software
Reliability, reliability, reliability. Major focus on stability and making existing features work as the highest priority.
Fix routing in the UK to take more notice of popular routes and stop avoiding some A roads (there are a few threads on this).
View popularity heatmap overlay on the map screen (available in latest watches)
Improve climbpro with a database of known climbs by name and maintain history of times on Connect.
Modify screen layouts on GCM as well as on-device.
Fix livetrack :-)
Sensitivity option for incident detection
Improve light control, I'd like battery saving options for my RTL 510 for all day rides for example.
When calculating a course, cache the result so it doesn't have to be calculated again next time.
Provide a backup/restore option for settings and config, preferably to both a PC/Mac and to Garmin Connect.
"When calculating a course, cache the result so it doesn't have to be calculated again next time."
This would add an additional fuzziness in behavior. A faster process reduces the utility for this. This probably isn't a strong value feature.
* It would have to recalculate after any map update.
* It would have to recalculate after changing between maps.
That would require too much power. The unit would have to be much larger.
Not that many people will want to spend a monthly fee for cell service.
The architecture used doesn't support Android. It would end up being a very basic phone.
Yes, many people doing the same route repeatedly might not use navigation.
Most of these sorts of repeated rides are likely to be on the short side where the calculation doesn't take as long.
I ride with a club and we sometimes do rides that are more-or-less the same.
But there are a lot of rides and the routes might be changed slightly.
I suspect the caching would work for some people but not for as many as one might think.
=================
Firmware upgrades might be another reason to recalculate routes.
I also run a cycling club and we publish our routes so if anyone gets dropped they know which variant we're taking. A typical 100K club route takes around 3 minutes to calculate, I suspect this would vary depending how many roads are in your local area. 3 minutes feels like a long time when you're waiting to head off.
Agree on firmware updates being another reason routes might need recalculating.