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

Strange you have another update overnight

Did you turned off the auto update on the Watch AND in the App ?

Normally they should be in sync, but just to be sure that one does not overwrite the other...

Moreover, as I said earlier in this post, do no connect your Watch to your PC (or MAC) if garmin express is installed....if so, whatever is your choice, it will update automatically the Watch

Hope this could help

Mine is working fine in 2.60 with no more stupid automatic updates....

0 Garmin-Blake over 4 years ago

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 issue so everyone here is experiencing it obviously. There are reports from iOS and Android users, as well as some users with third party apps/watch faces installed while others are not using Connect IQ. Some users are seeing this after email notifications, while others get it on phone calls and texts.

In short, there's little pattern so far.

To help us out further, we would like to request users experiencing this to reply to this post in the below format.

Attached error log from the Debug folder if possible (This is the most important part as logs are all we have to go on)
Are you using iOS or Android
Any notifications that have caused the reboot
Permission to add you internally to our engineering ticket/permission to access your Garmin Connect account
1. This shouldn't be required given the symptom on this issue

We truly appreciate everyone's patience and cooperation while we investigate this.

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

1. not in a place to get that right now, plus to make the watch even useable, I had to disable all notifications to stop the dang watch from rebooting and losing data. Since disabling notifications I have not experienced a reboot.

2. Android, pixel 2 xl, latest android OS available, all security patches installed.

3. ANY notification can cause it. I've specifically noticed: calendar reminders, gmail, hangouts (chat/text) and even game notifications.

4. You may access my garmin connect data. But understand what I said above in 1. I have disabled all notifications to prevent this from happening. I will NOT re-enable them until a new software update is pushed.

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

2. Android, Galaxy S7

3. Seems most common with text messages received through Google Hangouts.

4. Sure

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

1. Can't get that right now,

2. iOS

3. Mostly random, but most recent reboot was caused by a push notification from my security camera system

4. Sure

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

Rolling back software and not generating error logs will not help us resolve this issue. Again, I truly understand the frustration of experiencing this, but since such a small percentage of users are seeing this symptom, we need as much information as possible to help resolve it.

Rolling back software is not recommended for users who are not participating in the beta program and does not help us find a solution.

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

1) Sorry i'm not bothering. I've spent SO much money on Garmin products (I'm a pilot that should tell you a little something about money spent) I want it fixed and NOW!!!!

2) iOS

3) today while running, when it really angers me, it was a calendar 'reminder' that came up. I did nothing for probably 10 seconds. As soon as I touched a button on the watch it reboot. Not until then. 245 no music. No extra faces, IQ anything, loaded on watch. Make a version 2.71 that reverts back to whenever the problem wasn't there. Figure it out, fix it, then go to 2.80 or whatever. That's what I want!!!

4) no problem

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

1. Can't upload .BAK files, so here's the output of ERR_LOG.BAK:

3076 (Forerunner 245) SW ver: 270
Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/24/19 07:07:29
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x00000000
r2: 0x00000000
r3: 0x00000000
r4: 0x00000001
r5: 0x00000001
r6: 0x0000006d
r7: 0x2001a940
r8: 0x000000ff
r9: 0x68789ac3
r10: 0x000000ef
r11: 0x687899d4
r12: 0x2001a9cc
r13: 0x00000000
r14: 0x2001a0b0
r15: 0x00000082
r16: 0x046db554
r17: 0x21000000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019ff0
Call Stack - SP at 0x20019ff0:
0x000eb651
0x0000333f
0x046b6b9d
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
0x00000000
Uptime: 35442766

2. latest iOS release

3. Mostly text messages, coming from different applications (SMS and Signal), but also one message that contained just two emojis

4. Permission granted.

It's frustrating that I've lost step data at least one time due to the crash but if it's of any help for finding the cause of this bug I will re-enable notifications.

One question, however: Is the error log overwritten every time or does the watch generate a new file every time? I.e. do I have to hurry to copy the .BAK file after each crash?

Also, it would be great if the forum software would allow to attach .BAK files to postings.

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

Enabled notifications, scrolled to notifications, pressed Start - boom, the next crash. This time, however, the error log wasn't written to ERR_LOG.BAK (all uppercase) but to err_log.txt (all lowercase). Strange. Here's the output:

3076 (Forerunner 245) SW ver: 270

Build Type: RELEASE
Commit:d28e49c92e51e1a66b37b7dfc2877b41bf4e09f5
ESN: 3993836109
06/25/19 23:24:04
RTL
errnum: 0x034
r0: 0x2001a220
r1: 0x00000000
r2: 0x00000000
r3: 0x00000000
r4: 0x00000001
r5: 0x00000001
r6: 0x0000006d
r7: 0x2001a940
r8: 0x000000ff
r9: 0x68789ac3
r10: 0x000000ef
r11: 0x687899d4
r12: 0x2001a9cc
r13: 0x00000000
r14: 0x2001a0b0
r15: 0x00000082
r16: 0x046db554
r17: 0x210f0000
r18: 0x40000000
r19: 0x00000400
r20: 0xe000ed38
r21: 0xe000ed34
r22: 0x00000000
Stack frame PC, SP: 0x0015ef11, 0x20019ff0
Call Stack - SP at 0x20019ff0:
0x000eb651
0x0000333f
0x046b6b9d
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
0x00000000
0x00000000
Uptime: 137604090

Edit: This time I've had three messages. Two from Garmin Connect telling me that my activities are ready to view. One from Oura with the hint "Time to stretch your legs a bit?"

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

I started this thread 17 days ago, a lot of people here and across other forums are still complaining about this firmware, garmin didn't bother to stop this release.

If you can't replicate the problem, maybe you don't spend enough time with a 245 connected with a smartphone at garmin headquarters.

I know this isn't a 945 or 5 value watch but is still considerably expensive to have this sort of problems.

I had a 910xt that "auto destroyed" himself in the buttons but never had a firmware problem for 6 years. Now I don't need a multisport watch but I Nedd one that is reliable.

I also had a xiaomi amazfit pace and never had a problem, i was a beta tester in firmware for them and eaven the beta didn't have a problem as serious as this.

The reboot, on the beginning, only happened after notifications, any notification, no metter the app, the content or the time of day, completely random.

Than garmin release some sort of new firmware, still named 2.70 and the reboot could happen after a notification or if I tried to open and read the notification on the watch.

I can't give you the files cause I lost patience and downgrade the firmware back to good old stable 2.60.