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

Edge 1030 frozen during ride

Former Member over 7 years ago

For the first long ride with my new Edge 1030, i have a bug.

The screen was frozen after 1h33 of ride : the only way to regain control was to reset the Edge 1030.

You can see the result of the activitie on the photo uploaded : During the time the device was frozen, no data was recorded.
The version of my Edge 1030 is : 3.90.

Is there any correction for this problem ? ciq.forums.garmin.com/.../1324197.jpg

0 Former Member over 6 years ago

I'd love a reply to this also as it's now happening to me on rides every other day.

0 Martin868 over 6 years ago

This is somewhat frequent I think mothers have reported this. I experienced it myself as well. About 90min into an activity is common. Personally when I turn off Bluetooth on my iPhone so the edge cannot connect it becomes much more reliable.

0 Martin868 over 6 years ago

This is somewhat frequent I think others have reported this. I experienced it myself as well. About 90min into an activity is common. Personally when I turn off Bluetooth on my iPhone so the edge cannot connect it becomes much more reliable and I have no crash.

0 Former Member over 6 years ago

Happened to me twice in three rides; in my case, the device freezes during the first minute of activity. On 4.24 beta.

0 pdxfisher over 6 years ago

Except for livetrack, my 1030 works great on beta 4.24. One thing I started doing early on that seemed to help is that I do not have wifi enabled on the 1030 and I turn wifi off on my phone before I connect. I discovered early on that when I had wifi enabled on my phone (even with it off on the1030) that I had problems with my connection to my 1030. I am not sure if it is applicable to your situation (or if it still makes a difference) but I religiously do this and seem to have no real problems. For what its worth my phone is Samsung s7e (not sure if what I suggest applies to any other phone).

However, I will also say that I typically ride 45 minutes to an hour so if the problem only pops up after 90 minutes then I may have the issue and not know it.

Best of luck.

0 Former Member over 4 years ago

The screen froze midway my ride... I am not sure if I can recover my data or it did even record the rest the ride.

0 jgforrest over 4 years ago in reply to Former Member

Is this on the latest firmware (10)? My 830 did that on Sunday, about 3 hours into a 7 hour ride. Had to hold the power button down to reset it but at least was able to continue the ride. No storage corruption (ran chkdsk) and so I think it's a bug in 6 (equivalent 830 version to 10 on the 1030).

0 hotdogpartysausage over 4 years ago in reply to jgforrest

Mine locked up once during a ride at the weekend. (F/W 10.00) It happened on completion of a ClimbPro climb as the edge switched back to the previous data screen, which was the course elevation profile.

It appears to be just the display that's locking up as I was still getting radar alert tones (though no on-screen indications). The 10-second power button reset was enough to bring it back to life though it can take a good couple of minutes for it to fully start up.

I suggest you file a support request with Garmin. I'm feeding it back as part of an ongoing support request from the beta. If Garmin don't get many reports though they won't do anything about it.

0 krazyeone over 4 years ago in reply to hotdogpartysausage

I think that in some situation garmin cannot handle in the same time multiple screens notifications

Mine froze while almost enter in stand by and get the count down, 3 , 2 ,1 and second notification "off segment" , somehow in the backgroud somwthing was running but screen and keys where frozen, after several power button press, device restarted eventually

0 run50 over 4 years ago in reply to jgforrest

My 1030 has been locking up 4 to 5 times during a ride. I’m currently in Leadville riding over weekend and today it locked up 6 times over a 3 hr ride. And yes, this only started happening since software upgrade 10.0.