Originally Posted by
Athens80
If you've updated the firmware then the first thing I'd do would be to return the 500 to the seller for a working replacement. No need to keep collecting statistics about how 60% of the ride recordings fail.
It came with 3.30 firmware.
Originally Posted by
gregf83
Your unit is either defective or your settings are not correct. I've had an 800 for a couple of years with about 800 rides and no data loss. I turn it off as soon as my ride is over and usually plug it into a computer shortly after.
perhaps yours is looking for a sensor that isn't there or isn't found?
I had someone else's to test first and it truncated my first ride also. I put that down to human error, as I didn't know how to complete the ride, so stopped it and then held the start/stop (thought that was how) that started it again, tried that a few times and a few other buttons and then read the manual and did it properly. The ride summary never showed the data. I think the next 2 rides worked fine.
So I bought my own a week ago. Did two rides Saturday and one Sunday (yesterday). All ride summaries were there on the device. I had turned it off between rides, didn't charge it.
I thought I'd plug it into my phone this time to grab the data using an OTG cable (to see the work flow of getting rides off and uploaded while out). As it mounted, the cable fell out, so an unsafe unmount. Plugged it in again and all rides were 72bytes, 0 basically. No other files were truncated that I could see, just rides. Safety unmounted it and powered it up. All rides were there but all 0 values for everything as expected based on how I found the files. The totals were still right though (121km and 4:35 hours).
I did some dummy activities last night to workout where the issue was. Lost one of the first and thought I had a solutiuon but then all ensuing activities would not truncate no matter how hard I tried; even an unsafe unmount didn't do it.
I am going to mount the Garmin read-only on my computer the next few rides to see if it is the mounting process. I also ran a file system check on the FAT32 file system and it had.... "0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt."
So fixed that.
We'll see. So glad I didn't trust it and continued to record with my phone.