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

Giving up on the 820; Garmin, I want a refund!

OK, I've finally had enough of this unit, and the constant software updates that don't seem to fix anything. I'm running 6.50 after a master reset and yesterday tried to ride a saved tcx course built and transferred from ridewithgps.com. Super annoying. The turn notices show up late, literally after I'm into or through the intersection. As a result, a few times I went off course and the darn unit recalculated -- notwithstanding that I had recalculated turned to off both in the profile and for the course. And if I tried to check where I was by zooming out from the map, the redraw is painfully slow and the map then jumps and loses my position, so it's completely worthless for this purpose. And the gradient display continues to both lag and be inaccurate. And, regardless of which sensitivity I put the touch screen on, the number of missed taps and swipes is ridiculous.

I like the unit's incident detection and integration with the Varia radar, but enough is enough. My 800 was much better in every respect mentioned above, but its battery no longer holds a charge long enough for more than a 4 to 6 hour ride.

Got home and ordered the Wahoo Element Bolt. Anyone want to buy a used 820?
  • I don't think it's an issue of memory. Long courses (40 km is not long) work fine on the 800. The 820 likely has much more memory than the 800.
  • I don't think it's an issue of memory. Long courses (40 km is not long) work fine on the 800. The 820 likely has much more memory than the 800.


    Like I say's I do not know if it is something about "Memory" but it is a fact that before you reach 40 Km the 820 works like it have to work, after it is stressy and being VERY carefully not leave the route I have draw with several possibilities: RWGPS, RouteYou, MapMyRide etc ... even with Basecamp!(I tell you this because I do not think it is a problem with this or that map)
    This is something the developers have to take in mind and as long they can tell me why my device is tired after 25 miles until then I will ride on routes I know very well when I go out there .
  • Like I say's I do not know if it is something about "Memory" but it is a fact that before you reach 40 Km the 820 works like it have to work, after it is stressy and being VERY carefully not leave the route I have draw...

    I'm not saying you aren't having the problem. I'm saying your hypothesis isn't likely the reason for it.

    ...with several possibilities: RWGPS, RouteYou, MapMyRide etc ... even with Basecamp!(I tell yoru this because I do not think it is a problem with this or that map .

    The route planner you use isn't the reason either.

    The different route planners all produce the same sort of file. Basecamp has no special magic.
  • I.. Basecamp has no special magic.


    The magic of Basecamp is it uses the very map that is on your device, so inconsistencies between what it uses and the map on your device can't be the reason for problems.
  • The magic of Basecamp is it uses the very map that is on your device, so inconsistencies between what it uses and the map on your device can't be the reason for problems.


    That's useful/important to be aware of. But it's not that big a deal. It's still not magic.

    The 820 has OSM maps. Most ride planners let you use OSM. There will generally be no differences.

    The units should be able handle minor mismatches of the track and the installed map.
  • The cap of 40 Km is probably not "magic" more sorcery ...
    But it is a fact !
    I spoke about Basecamp because it belongs to Garmin (it is supposed to work correctly) and all the route planners in my post are examples between others, I stay very sceptical that our issue is about maps, I try also with several other maps (some buyed Garmin, other downloaded)
  • ...The units should be able handle minor mismatches of the track and the installed map.


    ...among the many other routine things it should be able to handle but doesn't.
  • The ancient 800 does it reasonably well. (The newer units should work equally as well.)


    Given how bugs seem to appear, it seems a fair amount of code rearranging has to be done to shoehorn new features into the devices. If there is such shoehorning going on, it might be a consequence of using a low power CPU (which increases battery life). It's possible that the architecture of the devices is old (and hard to program).

    The Edges are compromise devices because they have to be (small and running for long periods).
  • The cap of 40 Km is probably not "magic" more sorcery ...
    But it is a fact !

    You are still misunderstanding me. I did not say you weren't having the problem. With "magic", I was referring only to Basecamp.

    I spoke about Basecamp because it belongs to Garmin (it is supposed to work correctly) and all the route planners in my post are examples between others, I stay very sceptical that our issue is about maps, I try also with several other maps (some buyed Garmin, other downloaded)

    I knew why spoke about it (you aren't the first person who had the thought).

    The fact that Basecamp "belongs" to Garmin doesn't matter. There is no magic due to it being a Garmin product.

    The route planner you use doesn't really matter since they all do the same thing.

    I don't know what is causing your problem. There isn't enough information about it.
  • I don't know what is causing your problem. There isn't enough information about it.


    You say "your" problem ... Now, I like to know if between the owners of an Edge 820 (only), there is one or more that can tell me his machine can afford a trip from ± 80 Km (50 Miles) without any problem with TbT (obviously with at last one "out of route" after 40 km or perhaps even before).
    Of course if most tell me they edge works perfectly ... then I have to give mine back and ask a replacement (but I do not think you are a lot out there)