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

RE: Constant Crashes with Edge 510 and Bluetooth

Former Member
Former Member

Hi just sharing my findings of the edge 510, I think what is really to blame here is the choice of memory chips (RAM) that Garmin chooses to be in the device. My Edge 510 was bought in 2015, 2018 the problems start occurring, crashes, garbled screen overall an annoying experience when the device is meant to be a premium data recorder (why cheap memory chips? Perhaps Garmin's plan to ensure that we buy newer products). The edge 510 comes with about 21 megabytes of user memory, this is where the problem is, especially if you keep clearing the memory and deleting rides, the device will keep using the memory nodes/blocks from where the memory was last cleared. I was anal this way, I kept my device clear (the files are small anyway, there's really no need, but I have noticed that the system lag as with more records are stored, perhaps CPU limitations, hence why I kept mine clean). 2019, the edge 510 is crashing to a point that it is unusable. Decided to deep dive into the system, clicked on the error log file, realized that the system is logging RTL 'bad memory blocks error'. Seems that the ram chips node becomes lazy overtime causing bad reads, thus causing the system to crash. My solution was, plugged the device into a pc, defrag, created a folder and loaded .pdf files (user manuals etc.) till the space in the device is about half (I don't really need too much of a space, a few hours of riding data won't even take 500k, thus leaving 8 megs in space is sufficient for me). Why half? The theory here is simple, move the data storage point to a greener pasture, fresher bit of the ram that's probably was never use. Voila, the edge 510 is more responsive and felt like new, perhaps I got another 5 years on this kit with this routine. 

  • Former Member
    0 Former Member over 4 years ago

    I found that my Edge 510 was much more stable with Bluetooth switched off during a ride.  It seems to be a long standing bug that Garmin never fixed before they abandoned the Edge 510.

    Anyway, after six years of constant frustration, lost rides, hangs at "Loading profile", turning off mid ride and all the other common Edge 510 bugs, I've bought an Elemnt Roam.  It couldn't possibly be as flaky and unreliable as my Garmin.