Suunto Vertical | Extreme Lag During Phone Call | pool id:1 full! | FW 2.50.28
-
Good Morning All,
I’ve noticed the my Suunto Vertical experiences extreme lagginess whilst a call was in progress for my son - taken in another room & have found what looks like useful diagnostics in the log.
The incoming call started at 18:57 & had a countdown timer running ( for dinner )
Here’s me checking the timer ( as a pinned widget ) & it completely hangs for a very long time :
SV1 VLAGGY DURING CALL
https://youtu.be/KVknsGD0fU4Once the call had finished there was no lag at all :
SV1 NOT LAGGY AFTER CALL FINISHED
https://youtu.be/dAk-iZBCjH4log events, showing the onset of issues at 18:57:
#197475 22.10.2026 18:49:00 : EVT <Unknown> : EveryTenMinutes Step:5106 #197476 22.10.2026 18:50:52 : EVT ANALYTICS : #sf R:5 A:Rostock-fw_2.50.28.30094-O-ef839f46 #197477 22.10.2026 18:57:11 : EVT BLE : ANCS #1553907314 S02 C1 f02 t1792695430 s1 #197478 22.10.2026 18:57:40 : WRN WBMAIN : pool id:1 full! (M 24/24) #197479 22.10.2026 18:57:40 : ERR WBMAIN : (0) Removed 40 non critical - size now=4 #197480 22.10.2026 18:57:40 : ERR WBMAIN : 0: app 12749 Event 37 80001204 #197481 22.10.2026 18:57:40 : ERR WBMAIN : *1: mea 502 DPC 3 0013fa8d #197482 22.10.2026 18:57:40 : ERR WBMAIN : 2: ui 3 Proc 0 00000000 #197483 22.10.2026 18:57:52 : WRN WBMAIN : pool id:1 full! (M 24/24) #197484 22.10.2026 18:57:52 : ERR WBMAIN : (0) Removed 39 non critical - size now=4 #197485 22.10.2026 18:57:52 : ERR WBMAIN : 0: app 24749 Event 37 80001204 #197486 22.10.2026 18:57:52 : ERR WBMAIN : *1: mea 502 DPC 3 0013fa8d #197487 22.10.2026 18:57:52 : ERR WBMAIN : 2: ui 4 Proc 0 00000000 #197488 22.10.2026 18:58:04 : WRN WBMAIN : pool id:1 full! (M 24/24) #197489 22.10.2026 18:58:04 : ERR WBMAIN : (0) Removed 42 non critical - size now=11 #197490 22.10.2026 18:58:04 : ERR WBMAIN : 0: app 36749 Event 37 80001204 #197491 22.10.2026 18:58:04 : ERR WBMAIN : *1: mea 502 DPC 3 0013fa8d #197492 22.10.2026 18:58:04 : ERR WBMAIN : 2: ui 3 Proc 0 00000000 #197493 22.10.2026 18:58:16 : WRN WBMAIN : pool id:1 full! (M 24/24) #197494 22.10.2026 18:58:16 : ERR WBMAIN : (2) Removed 0 non critical - size now=0 #197495 22.10.2026 18:58:17 : WRN WBMAIN : pool id:1 full! (M 24/24) #197496 22.10.2026 18:58:17 : ERR WBMAIN : Notify fail 507(lid=6d01->cli=80870021, ctx=1->2) #197497 22.10.2026 18:58:17 : ERR WBMAIN : prv=1c4e1c, cli=1c8b2c #197498 22.10.2026 18:58:17 : WRN WBMAIN : pool id:1 full! (M 24/24)I hope this helps diagnose the issue as I wouldn’t think that beyond the initial “incoming call” popup anything else needs to be done on the watch side.
Martin
-
@Woodster Hi, how did you get the logs? I’m looking a way to connect to my ocean watch internals.
-
@koiraloko in VSCode using the SuuntoPlus Editor Extension:
Then you click once on “View System Events”
-
@Woodster interesting! Some of us have problems with the incoming call notification, which does not automatically disappear and when manually dismissed may lead to few seconds of freezing and instability (see here https://forum.suunto.com/post/198932). Your findings may be related
-
@SergioB Also, in some cases an incoming call during an activity resulted in the watch crashing and restarting. I wonder if there is a connection?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login