Watchapp failing after launch #96

jumper047 · 2016-06-18T11:11:07Z

Beta version from G+ with icons, OG Pebble. It works fine over the day, but at some moment just vibrates at launch and falls back to menu. After reinstall of watchapp it works some time, and same thing beans again.

matejdro · 2016-06-18T12:35:16Z

Can you give me the logs of the Android app from the crash?

jumper047 · 2016-06-19T08:43:58Z

Sorry, i can't find logs. Logging in settings enabled.

jumper047 · 2016-06-20T09:53:01Z

0:45:29:117D Creating Notification Listener...
0:45:29:118D Finished creating Notification Listener...
0:45:36:840D Got new jellybean notification
0:45:36:842I Processing notification 0|android|17039424|null|1000
0:45:36:865D Discarding notification because FLAG_ONGOING_EVENT is set.
0:45:58:145D ACK 48
0:45:58:146W Got invalid ACK
0:46:59:710D Got jellybean dismiss 0|android|17039424|null|1000
0:46:59:721D got dismiss: 0|android|17039424|null|1000 true
0:46:59:723D SyncDismissUp: true
0:49:35:766D Got new jellybean notification
0:49:35:770I Processing notification 0|android|17039424|null|1000
0:49:35:777D Discarding notification because FLAG_ONGOING_EVENT is set.
0:49:47:134D Got jellybean dismiss 0|android|17039424|null|1000
0:49:47:151D got dismiss: 0|android|17039424|null|1000 true
0:49:47:155D SyncDismissUp: true
0:49:48:653D Got new jellybean notification
0:49:48:655I Processing notification 0|android|17039424|null|1000
0:49:48:656D Discarding notification because FLAG_ONGOING_EVENT is set.
0:50:10:794D Got new jellybean notification
0:50:10:795I Processing notification 0|com.viber.voip|-1003|message|10070
0:50:10:939D wear group: true false aggregated_group
0:50:10:961D Got new jellybean notification
0:50:10:964I Processing notification 0|com.viber.voip|2|message|10070
0:50:10:971D wear group: false false aggregated_group
0:50:10:976D notify internal
0:50:11:121D got dismiss: 0|com.viber.voip|2|message|10070 false
0:50:11:122D SyncDismissUp: true
0:50:11:123D DismissSimilarWear 0|com.viber.voip|2|message|10070 1 aggregated_group
0:50:11:602D Current app:
0:50:11:624D SendNC
0:50:11:635D BeginSend 214505925 Viber something 11
0:50:11:661D SendNext CommBusy:false
0:50:11:663D SendNextModule NotificationSendingModule
0:50:11:665D Initial notify packet 214505925
0:50:11:672D MinInterval: 0
0:50:11:674D LastVib: null
0:50:11:735D SENT 0
0:50:11:747D notify internal
0:50:11:773D group notify failed - summary with existing non-summary notifications
0:50:11:774D notify failed - group
0:50:11:816D NACK 0
0:50:11:816D Retrying last message for the first time...
0:50:12:18D SENT 1
0:50:12:48D NACK 1
0:50:12:49D Retrying last message for the second time...
0:50:12:652D SENT 2
0:50:12:683D Pebble packet for 0
0:50:12:684D system packet 0
0:50:12:685D Version 38
0:50:12:686D SendNext CommBusy:false
0:50:12:686D SendNextModule SystemModule
0:50:12:723D Sending config...
0:50:12:730D SENT 3
0:50:12:740D NACK 2
0:50:12:742W Got invalid NACK
0:50:12:780D NACK 3
0:50:12:781D Retrying last message for the first time...
0:50:12:982D SENT 4
0:50:13:35D ACK 4
0:50:13:36D SendNext CommBusy:false
0:50:13:38D SendNextModule SystemModule
0:50:13:39D SendNextModule NotificationSendingModule
0:50:13:40D Initial notify packet 214505925
0:50:13:41D MinInterval: 0
0:50:13:41D LastVib: null
0:50:13:51D SENT 5
0:50:13:134D ACK 5
0:50:13:135D SendNext CommBusy:false
0:50:13:136D SendNextModule NotificationSendingModule
0:50:13:136D Sending icon
0:50:13:137D SENT 6
0:50:13:196D ACK 6
0:50:13:197D SendNext CommBusy:false
0:50:13:198D SendNextModule NotificationSendingModule
0:50:13:199D Sending more text... 214505925 0
0:50:13:202D SENT 7

jumper047 · 2016-06-20T14:54:24Z

Seems like it crashes when message is too long. Right now I get some notifications from conference in viber. They append one to another.And on fifth or sixth it crashes.

matejdro · 2016-06-21T08:42:08Z

Thanks for the info. Can you try the new beta I just posted into G+ group?

jumper047 · 2016-06-21T18:50:12Z

Oh, i tested it. No crashes at this moment, but its sad anyway:(. Wait version with gestures and tertiary. By the way, if i disable icons in previous beta, is it reduce memory consumption?

matejdro · 2016-06-21T19:22:04Z

Just disabling icons reduces the memory usage somewhat, but deleting them from the firmware altogether frees up even more memory.

matejdro · 2016-08-05T18:45:58Z

@jumper047 Can you test the new beta with gestures, but not with icons?

jumper047 · 2016-08-07T23:32:44Z

@matejdro Sorry for long answer:(. I tries it. I don't have "bootloops" (when app starts from menu and crashes after that), but some times it hanging up when notification come, or on exit. I have same issues with custom build, with gestures and icons. May be trouble in gestures, and not in icons?

matejdro · 2016-08-08T06:07:30Z

But no gestures version was working fine?

jumper047 · 2016-08-08T06:19:33Z

May be,I am not sure. I'll test it later.

8 августа 2016 г. 9:07:31 GMT+03:00, "Matej Drobnič" [email protected] пишет:

But no gestures version was working fine?

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#96 (comment)

Простите за краткость, создано в K-9 Mail.

matejdro · 2016-10-17T14:51:34Z

Any news on this bug? Does it still happen on latest version?

jumper047 · 2016-10-25T18:47:03Z

Sorry for silence. Yes, this bug is still there. Some times app crashes at
new notification. But now i can view them in history without any trouble.
When i opened a issue, app crashes in history too.

2016-10-17 17:51 GMT+03:00 Matej Drobnič [email protected]:

Any news on this bug?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#96 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABV7Xhd7USPiMJhr-NaAlokLEpLrVMhbks5q04t3gaJpZM4I47Nn
.

matejdro · 2016-10-25T20:35:02Z

Does it also happen when you open crashy notification from Active?

jumper047 · 2016-10-25T22:19:30Z

From Active everything works fine. It affects only fresh notifications

25 октября 2016 г. 23:35:02 GMT+03:00, "Matej Drobnič" [email protected] пишет:

Does it also happen when you open notification from Active?

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#96 (comment)

Простите за краткость, создано в K-9 Mail.

matejdro · 2016-10-26T14:31:24Z

That is with latest beta right? Or latest stable?

jumper047 · 2016-10-27T15:43:09Z

Beta, now I have 2.9B910 installed.

26 октября 2016 г. 17:31:24 GMT+03:00, "Matej Drobnič" [email protected] пишет:

That is with latest beta right? Or latest stable?

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#96 (comment)

Простите за краткость, создано в K-9 Mail.

matejdro · 2016-10-28T19:21:44Z

Do all other symptoms still apply (for example it only crashes on long messages)?

jumper047 · 2016-10-30T23:03:25Z

Hmm, no. Some times it happens with not-so-big notifications. For example,
today it happens with android's low battery notify. Ill watch on it next
few days.

2016-10-28 22:21 GMT+03:00 Matej Drobnič [email protected]:

Do all other symptoms still apply (for example it only crashes on long
messages)?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#96 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABV7XnOF8NvoHoR79JtAL1moouO43chvks5q4ktKgaJpZM4I47Nn
.

matejdro · 2016-10-31T08:23:51Z

Does it happen on all low battery notifications for example or is it more random?

jumper047 · 2016-10-31T08:26:49Z

It's random. Week ago watchapp shows them without issues.

Простите за краткость, создано в K-9 Mail.

matejdro · 2016-11-03T18:24:26Z

Do you actually need to reinstall the watchapp or does it work when you manually open it?

matejdro added needs more info bug labels Sep 23, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Watchapp failing after launch #96

Watchapp failing after launch #96

jumper047 commented Jun 18, 2016

matejdro commented Jun 18, 2016

jumper047 commented Jun 19, 2016

jumper047 commented Jun 20, 2016

jumper047 commented Jun 20, 2016

matejdro commented Jun 21, 2016

jumper047 commented Jun 21, 2016

matejdro commented Jun 21, 2016

matejdro commented Aug 5, 2016

jumper047 commented Aug 7, 2016

matejdro commented Aug 8, 2016

jumper047 commented Aug 8, 2016

matejdro commented Oct 17, 2016 •

edited

Loading

jumper047 commented Oct 25, 2016

matejdro commented Oct 25, 2016 •

edited

Loading

jumper047 commented Oct 25, 2016

matejdro commented Oct 26, 2016

jumper047 commented Oct 27, 2016

matejdro commented Oct 28, 2016

jumper047 commented Oct 30, 2016

matejdro commented Oct 31, 2016

jumper047 commented Oct 31, 2016

matejdro commented Nov 3, 2016

Watchapp failing after launch #96

Watchapp failing after launch #96

Comments

jumper047 commented Jun 18, 2016

matejdro commented Jun 18, 2016

jumper047 commented Jun 19, 2016

jumper047 commented Jun 20, 2016

jumper047 commented Jun 20, 2016

matejdro commented Jun 21, 2016

jumper047 commented Jun 21, 2016

matejdro commented Jun 21, 2016

matejdro commented Aug 5, 2016

jumper047 commented Aug 7, 2016

matejdro commented Aug 8, 2016

jumper047 commented Aug 8, 2016

matejdro commented Oct 17, 2016 • edited Loading

jumper047 commented Oct 25, 2016

matejdro commented Oct 25, 2016 • edited Loading

jumper047 commented Oct 25, 2016

matejdro commented Oct 26, 2016

jumper047 commented Oct 27, 2016

matejdro commented Oct 28, 2016

jumper047 commented Oct 30, 2016

matejdro commented Oct 31, 2016

jumper047 commented Oct 31, 2016

It's random. Week ago watchapp shows them without issues.

matejdro commented Nov 3, 2016

matejdro commented Oct 17, 2016 •

edited

Loading

matejdro commented Oct 25, 2016 •

edited

Loading