This more than 8 months I bought and been informing you Garmin programmers (beta team) about this dummy course/strava segment problem:
When biking, according to the ascent /flat /descent we won't ride at the same speed, basically our instantaneous speed range from 5 to 100 km/h. Don't you know that???
So if I bike follow a course, or strava segment, long enough to have flat, up and down sections, it is more than likely than my average speed will fluctuate significantly along the course, specially at the begining.
So how dumb, and how many were you to calculate a "Time to End" remaining based on course/segment "average speed" and "Dist to End", and not taking into account the uploaded course/segment informations????
This used to be calculated just fine with edge 305 and 810 I owned : the calculate "Time to End" was based on the uploaded virtual pacer "Time to End" and not the avg speed from the beginning of the course. It was obviously an estimation because the edge (like no one yet i guess) can predict future, but at least it would be based on history/plan and so what "time to end" remained indeed for the virtual pacer.
So now that your varia radar is compatible with some Wahoo GPS (https://www.dcrainmaker.com/2019/08/hands-on-wahoo-adds-radar-support-for-elemnt-bolt-roam-confirms-trainerroad-connectivity.html), i don't see any good reason keeping up begging for firmware update , will just sold to the best my 820 as soon i have enough money to complete and get a wahoo elmnt, and will never come back to edge , based on your poor programming skills and reactivity
