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

Garmin 405 will not reset and transfer always fails

Former Member over 14 years ago

I've done everything on these forums to try and fix the transfer failing issue. the ANT finds my forefunner, begins the transfer, gets to "tracks" and fails every time. I have all the latest software, tried force sending, tried deleting plist files, tried rebooting. Now I'm trying a hard reset of the 405 and holding down both buttons does nothing. I could hold them down for 5 minutes and nothing happens, it will not turn off. I"m about ready to drive my car over this thing.

When I go to garmin connect, it finds my 405 but sees no new activities, even though the "history" on the watch shows multiple new activities.:mad:

0 Former Member over 14 years ago

I have the exact same problem. Today is the first time I've had any problems with the ANT agent after owning the Forerunner 405CX for two months.

One thing was unique to this last run though. Before I went out, I checked the battery. It said 58% remaining, so I thought that'll do. But after transferring a custom workout from Garmin Training Center, the battery meter actually displayed 0%, so I thought I'd better charge it. Eager to get out, I let it charge until it read 30% before going out. I did the whole run and everything seemed to be fine with the Forerunner. When I got back, the battery meter once again read 0%, so I set it to charge again. It's been sitting in the charger now for an 1.5 hours and it keeps trying to sync, but always fails on either laps or tracks. In the charger it's located about 7-8 feet from the Ant stick, so I tried putting the watch next to the stick and let it sync. I also thought maybe it was having a hard time syncing and charging at the same time, but it still failed. It's had maybe 10-12 failed attempts since then.

For one, it does seem like there is a problem with the battery drain status calculation. I don't know if that might also lead the watch to think it has more juice than it actually has, so it keeps going when it really should stop the timer, save the run and shut off to prevent corrupt data. Having experienced this 58-0% situation in 10 minutes, leads me to believe that.

0 Former Member over 14 years ago

I want to add that the syncing time up to the point where it fails is drastically longer than what I'm used to.