This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

23.09 broken "last ride" image

jrc_
10 months ago

I went for a short ride, came back, accepted 22.18, checked to see if routing was still broken (it is, guilford ct to new haven union station over 21 miles!), and then accepted 23.09.

First obvious bug is the scrambled image it shows for "last ride" now.

And routing still useless, worse than edge 1000, my phone or anything else i've seen.

  • 0 10 months ago

    Use bug report forum for bug reports, those are monitored, discussions are not.

  • 0 10 months ago in reply to Ch4rvel

    thanks. will do.

  • 0 10 months ago in reply to Ch4rvel

    thought about deleting it here, but the useless routing, worse than edge 1000, if not monitored by garmin, at least serves as a warning to the unsuspecting buyer.

  • 0 10 months ago in reply to jrc_

    Unsuspecting buyers are not affected by any bugs in 23.09.
    YOU chose actively to take part in the beta program and assigned your device to it. It was also you who said yes when the device asked you to install the beta.

    I don’t understand people: installing beta to get the „latest“ features and then complaining the beta isn’t final.

  • 0 10 months ago in reply to BeneGi

    and - btw - it‘s not broken! I‘m on 23.09 too.

  • 0 10 months ago in reply to mcinner1

    i did a 230km/8hs+ ride with routing, without any problem. (840 and 23.09). But if possible, a moderator should move this post to the beta section 

  • 0 10 months ago in reply to mcinner1

    very helpful - let me send you my address so we can swap units.  :-)

    Are you saying I photoshopped the picture I took - it is kaputt on mine. It might be affecting just a ride taken on a different version right before the update.

    There are a lot of things that work for me while others report problems - I leave it alone or post HELPFUL suggestions.   VTNC.

  • 0 10 months ago in reply to Luko79

    I did 300mi with routing before, on an edge 1000, very reasonable routing. just needed external usb battery.


    on the edge 1040 (great battery life!) simple routing that the 1000 would figure out quickly, the 1040 wants to take me for extra mileage and elevation, no matter what settings I try (avoidances, popularity, distance/time/elevation, road/mountain).

    One example is Guilford Marina to New Haven Union Station, which the 1000 comes up with a reasonable 16.6mi route, while the 1040 insists on 21mi+ routes no matter what settings.  In fact often you change from "minimize distance" to "minimizing elevation" and it gets you extra climbs!

    "without any problems" has many shades of gray - could be "it didn't crash once", could be "didn't lose the ride data", the low bars we have been accustomed to accept.

    I tried reporting it to garmin, on beta fora. Crickets.  OTOH finally they did something about the climb grade, another pet peeve of mine where the 1000 outshone the 1040 miserably.  I will start a separate thread, for user feedback/support on 1040 routing, exchange of ideas and experiences - maybe I am doing something stupid, maybe it is OSM with some unroutable corner, just trying to figure it out.

    Maybe it is just me, but after 8 years with the 1000, and paying over $500 for the 'latest and greatest' I do expect it to be BETTER, not worse.

  • 0 10 months ago in reply to BeneGi

    the beta announcement had not been posted, nor a 23 forum started at that point. ch4rvel useful post pointed to it, i posted there.

    the glitch last ride doesnt bother me much, but the routing deficiency affects EVERY single buyer of garmin's touted routing unit.  alpha, beta or omega - it sucks while "old gen" units without a myriad of dont-care-for features like the 1000 handle the basics like routing just fine.

    i am not "complaining" but helping by reporting a problem.

    vtnc