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

2.70 restarts after some notifications

Updated yesterday via USB and garmin express and since then, it is randomly restarting after some notifications, already happened 4 times since last night. Anyone else?

Top Replies

Garmin-Blake over 4 years ago +7 verified

There is an open ticket with our engineering team that is being investigated. We have gathered error logs from users that are affected and hope to have a resolution soon. This continues to be an issue…
Garmin-Blake over 4 years ago +0 verified

We wanted to touch base with everyone as we are still looking into this issue. I know there have been questions as to why we are not able to reproduce this internally. This is a thread dedicated to this…
Garmin-Blake over 4 years ago +1 verified

We have released a beta to address this issue which can be found here. We will be closing this thread and monitoring feedback in the sticky post linked.

The changes in the above linked beta will be rolled…
chrisoff over 4 years ago in reply to Garmin-Blake +5

This was my data yesterday. The first gap is overnight and I wasn't wearing the watch. The second gap from 8:30am to 3:50pm I was wearing the watch the entire time and after receiving a notification at…
CrisJH over 4 years ago +4

I disabled most notifications (left calendar reminders on), and have still had 2 reboots this morning. I also have the missing sections in my 'graphs' as others have described. This OS update is…

All Replies

0 twolfcorner2009 over 4 years ago in reply to 7590727

Understood, but that defeats the entire purpose of a "smart watch". If I wanted to just track my steps and tell the time, I'd go to Walmart and spend $6 and walk out with a cheapo digital watch and pedometer that you wear on your waistband.

+1 PALIREK over 4 years ago in reply to Garmin-Blake

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3995915341
06/26/19 22:12:11
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x3400e9dc
r2: 0x3400e9dc
r3: 0x00000010
r4: 0x00000010
r5: 0x00000000
r6: 0x000000f0
r7: 0x40404040
r8: 0x2003fd00
r9: 0x3400e9cc
r10: 0x00000000
r11: 0x000000ef
r12: 0x00000000
r13: 0x3400eabc
r14: 0x2001a098
r15: 0x3400eabc
r16: 0x00189610
r17: 0x01000000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019fd8
Call Stack - SP at 0x20019fd8:
	0x000eb651
	0x0000333f
	0x0018058b
	0x046b6b91
	0x00004c85
	0x000c097d
	0x00044e1b
	0x000485bd
	0x000486dd
	0x001134ed
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
Uptime: 221744879

€]nc027d43  
       ˙˙˙˙                                                                                @                                                                                                                               €]nc027d43  
       ˙˙˙˙                                                                                @                                                                                                                               €]nccf46d1     
 ˙˙˙˙‚ó   ¨Ś "'  B     "'  ţ\ ţ\ \V \V                                     
    ©Ś         ..\..\..\hwm\hwm_iop.c                                                                                      €]nccf46d1     uö˙˙˙˙‚ó   ě(  Đ  ţ\ ^>  ^>  ţ\ \V î  î  ü   \V                             
    Ň;          ..\..\..\hwm\hwm_iop.c

2) iOS

3) no idea, seems restarting spontanuous without eny notification

4) yes

0 KentuckyHouse over 4 years ago in reply to twolfcorner2009

The real fix for now is to roll back to 2.60 firmware. That completely fixes the issue and you're not missing anything from the 2.70 update.

I rolled back about a week ago (maybe a little more) and I've yet to have a reboot since.

Download the 2.66 beta file here https://www8.garmin.com/support/download_details.jsp?id=14935

Follow the steps at the bottom of the page (particularly #5). The 2.60 firmware can be found in the zip folder as GUPDATE-260.GCD. Make sure to rename it to GUPDATE.GCD before disconnecting your watch from the PC or Mac. As soon as you disconnect, you'll see the update screen on the watch.

0 runner-33 over 4 years ago in reply to Garmin-Blake

Today I had three crashes. And I can offer one new insight.

The first crash went unnoticed at 9:14.

The second one happened at 13:06 after about 5 emails coming in through the native iOS mail program. There is a huge amount of data missing - no steps and heart rate between about 9:00 and 13:00.

I didn't notice the third crash but I guess it happened at 18:31 since that's the time stamp of ERR_LOG.BAK (pasted below). Shortly before I had receives about 5 Signal messages (text and one image).

Now, what's interesting: Data between 17:02 and 18:34 is missing from Garmin connect. However, I can still see it on the "last 4 hours" screen on the HR widget (current time as of writing is 19:55).

Which means: The data is NOT really lost. But it's not synced over to Garmin Connect. Why is this?

And are these error logs helpful?

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/27/19 09:14:14
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x3400e9dc
r2: 0x3400e9dc
r3: 0x00000010
r4: 0x00000010
r5: 0x00000000
r6: 0x000000f0
r7: 0x40404040
r8: 0x2003fd00
r9: 0x3400e9cc
r10: 0x00000000
r11: 0x000000ef
r12: 0x00000000
r13: 0x3400eabc
r14: 0x2001a098
r15: 0x3400eabc
r16: 0x00189610
r17: 0x01000000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019fd8
Call Stack - SP at 0x20019fd8:
0x000eb651
0x0000333f
0x0018058b
0x046b6b91
0x00154d55
0x00113ca5
0x00114195
0x00044e1b
0x00048c67
0x000485bd
0x000487b1
0x001134ed
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
Uptime: 42168241

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/27/19 13:02:42
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x3400e9dc
r2: 0x3400e9dc
r3: 0x00000010
r4: 0x00000010
r5: 0x00000000
r6: 0x000000f0
r7: 0x40404040
r8: 0x2003fd00
r9: 0x3400e9cc
r10: 0x00000000
r11: 0x000000ef
r12: 0x00000000
r13: 0x3400eabc
r14: 0x2001a098
r15: 0x3400eabc
r16: 0x00189610
r17: 0x01000000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019fd8
Call Stack - SP at 0x20019fd8:
0x000eb651
0x0000333f
0x0018058b
0x046b6b91
0x001a0abd
0x00113ca5
0x00114195
0x00044e1b
0x00048c67
0x000485bd
0x000487b1
0x001134ed
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
Uptime: 13706110

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/27/19 18:32:05
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x3400e9dc
r2: 0x3400e9dc
r3: 0x00000010
r4: 0x00000010
r5: 0x00000000
r6: 0x000000f0
r7: 0x40404040
r8: 0x2003fd00
r9: 0x3400e9cc
r10: 0x00000000
r11: 0x000000ef
r12: 0x00000000
r13: 0x3400eabc
r14: 0x2001a098
r15: 0x3400eabc
r16: 0x00189610
r17: 0x01000000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019fd8
Call Stack - SP at 0x20019fd8:
0x000eb651
0x0000333f
0x0018058b
0x046b6b91
0x00154d55
0x00113ca5
0x00114195
0x00044e1b
0x00048c67
0x000485bd
0x000487b1
0x001134ed
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
Uptime: 19761277

0 gadgetrants over 4 years ago in reply to twolfcorner2009

Greetings fellow frustrated 245 owners. As a former 235 owner, IIRC something similar happened with it as well, e.g.,

https://www.facebook.com/Garmin/posts/i-have-a-garmin-forerunner-235-twice-in-the-last-few-days-it-has-restarted-itsel/10154008181775706/

Definitely a hassle to see large chunks of your timeline disappear. OTOH I have faith in the Garmin firmware team and I'm confident they'll figure it out. Let's all try to stay chill and be as kind/helpful to our community service rep as possible. Remember they have to go home, make dinner, feed their dogs, get some sleep, and go to work the next day like the rest of us.

FWIW I have the Pixel 2 (like several others here!) and am also experiencing the random reboots on my shiny new 245. Thanks for the tip for firmware downgrading. It's good to know we have a fix of sorts if we have to go that route.

-Matt

0 9833328 over 4 years ago

Pretty poor, this. Got my FR245 yesterday. It updated overnight then multiple crashes this morning. I have removed the 3rd party watch face to see if that helps. I'm not faffing around rolling it back. This shouldn't be something we even have to think about doing. 3 weeks without a fix is way too long. I'm not sure Garmin are taking this seriously.

0 Garmin-Blake over 4 years ago

We have released a beta to address this issue which can be found here. We will be closing this thread and monitoring feedback in the sticky post linked.

The changes in the above linked beta will be rolled out to everyone very soon provided we find no other issues or causes for concern. Again, I cannot apologize to everyone enough for this issue and thank you all for your patience while we researched and worked on a permanent solution.