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 Kfahren1 over 4 years ago in reply to Garmin-Blake

1. ERR_LOG.BAC
3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3994602072
06/25/19 21:24:47
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: 20578727

2. Android - Samsung Galaxy S8

3. It seems to happen most with text messages through the Verizon messages app. It is when I get more than one or two right in a row. I have had it happen in the middle of an activity.

4. yes

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

One additional observation I've made with the crashes: Often (if not every time, but I don't remember tat) the Connect app will not recognize the watch after the crash/reboot. I have to close and restart the Connect app or even to activate flight mode in iOS for some seconcs. Rebooting the watch doesn't help. I assume it also has to do with GCM.

I suggest to also look into the Garmin Connect Mobile side of things if any change to notification handling have been made there.

0 BachAddict over 4 years ago in reply to Garmin-Blake

Sorry Garmin but I cannot trust that you ask people to not downgrade in they have a problem in order to give you some logs...

We are not your Beta Tester...

If I had not dowgraded my Watch, I would have sent it back to the reseller.

I am coming from an Apple Watch for a Garmin Forerunner because I love its functionnality, but you can let your customers with such an usable Watch for so long (even if it impacts only some and not everyone); such things never happened with my apple Watch.

I am a software engineer, and I also have to face such kind of problem with my customers, but I would never say to my customers to accept such situation for 3 weeks...

Please continue producing such wonderful gears for runners and cyclist, but improve your test and Customer Policy.

0 floppyrom over 4 years ago in reply to BachAddict

I find it mind blowing how the manufactures of the watch and the coders of the firmware cannot reproduce such a BLOCKING issue and one that is reproduced easily by any user of this watch with firmware 2.70. Just try to access the notifications 2-3 times and the watch will crash. Voila!

0 Garmin-Blake over 4 years ago in reply to floppyrom

First, I don't have another way to say that we understand the frustration this issue is causing and do apologize for it. I realize apologies only go so far when you are still experiencing this, but the sentiment is true.

Second, to say all users are seeing this and it is universally reproduced is not accurate. Our internal and external beta testers did not see this symptom during testing which is why 2.70 was released without concern. We have tried extensively to reproduce this internally and cannot which is why we have reached out to the community for help. Again, I understand my stating this does not take away from the fact that it is occurring for several users.

Of course we do not want to treat customers as beta testers and hate to ask for error logs from users who have not installed a beta, but in situations like this it is necessary. This issue is being addressed with a high priority and we hope to have good news much sooner than later.

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

Well - I guess it's frustrating for all sides. Let's hope the developers can get rid of this bug quickly.

Next crash happened a few minutes ago upon opening the notification widget which should have displayed 4 Signal messages, 3 text messages and 1 photo, so that's my 4th error log. (I noticed that .txt files can be uploaded contrary to .bak files)

err_log.txt

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/26/19 21:31:24
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
	0x000487b1
	0x001134ed
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
	0x00000000
Uptime: 79638345

As usually, after the reboot the message could be opened without another crash.

0 twolfcorner2009 over 4 years ago

I literally got my brand new 245 right as this popped up in the forum. Worked great for a couple days, and then the watch started to restart multiple times a day on a wide array of notifications (text messages, Nest cam notifications, MyQ notifications, calendar reminders, etc.). When this happens, I lose all data since the last sync. Some days I lose 1/3-1/2 of my data to these stupid crashes. Not sure if it's related, but my body battery and sleep metrics are basically useless at this point as well since the watch has so little data, I consistently am missing entire nights worth of sleep tracking. It's essentially useless at this point.

0 8400518 over 4 years ago in reply to Garmin-Blake

4744.err_log.txt

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993704024
06/26/19 14:59:21
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: 20774250

Android Pixel 3XL

COnnection to Bluetooth. I have the Bluetooth connection notification on.

0 andrewkbarrett over 4 years ago in reply to Garmin-Blake

1. reverted back to 2.60 to avoid the problem - so I don't think my debug folder will be of use. after reverting, I had zero problems.

2. IOS (iPhone 8 with lastest IOS and garmin connect)

3. Email and txt messages. txt message was the one that sealed the deal in rolling back. lost an entire mornings activities.

4. shouldn't be required == not needed. I do not allow permissions to my account.

This should be pretty easy to repro. 2.7 firmware, have someone do activities, throw alerts at them until it pops. seems like there are enough customers experiencing this, that it should be super easy for ya.

For those who are having the problem, just rollback until a new patch comes out. it's the best way forward at this point.

0 7590727 over 4 years ago in reply to twolfcorner2009

turn off all notifications (smart notifications slider in connectiq app), then you should be able to survive until they can fix it.