Live location S+ app
-
I was just wondering why my Track Live keeps cutting out after about 2–3 hours every time…
Have you signed up for a subscription since the latest update, and does the free plan include 45 minutes of tracking?
-
@Adrian.S not realy
discribe it here - https://forum.suunto.com/post/193011 -
Hey guys!
If anyone faced up with issue when S+ app turn black and disconnect from the app. could you please try latest 1.8 R9 (it should be in the suunto store already) and let me know if it works
also i can confirm that it wont work alongside with structured workouts
structured workout also quite greedy of heap mem. live.τ too. -
@Nikolai-Simonov I just submitted two screenshand associated SIDs to the support email. 2 recent 5 mile runs are getting truncated shortly after starting. Duration is saved correctly but pace and distance way off.
Vertical 1 Ti Solar with current FW and app
Suunto App latest beta
LiveT app updated. Happened July 8 and today.
-
Wanna share a little update on [dis/re]connection issues.
I’ve received a noticeable number of reports lately from users whose connection was lost somewhere in the middle of an activity. Sometimes it recovered, but in other cases the watch remained in “reconnecting” state until the application or even the watch was restarted.
A special thanx to @larrybbaker for detailed reports that encouraged me to investigate the problem much deeper!
After investigating the issue, I learned that there could be a few issues in AURA:
AURA is Suunto’s native BLE management layer between Duktape and Zephyr BLE stack, managing connections to external sensors if i understood correctly.
-
AURA may try to create a connection while Zephyr still has an existing connection object for the same device. Instead of safely waiting, reusing it, or cancelling the old connection, the observed path reaches an internal assertion. AURA then restarts, potentially interrupting connections to the phone, HR belt, power meter, foot pod, and other sensors. Automatic recovery may then enter the same failing path again.
-
AURA uses a fixed pool of write requests. The analysis indicates that one completion path may fail to release a request when the associated client connection has already disappeared. If this happens repeatedly, the pool can eventually become exhausted and subsequent writes can fail or stop completing.
To be honest, this evidence based just on log analysis and available firmware bins without any access to internals of AURA it could be a false positive. But 90 percent sure it’s not.
From our side, app could reduce BLE pressure, avoid aggressive retries, and we’ve made this. We lost in reconnection reliability, however, wins in lower BLE pressure. However, it won’t resolve an inconsistent native connection state or release resources retained inside AURA.
I’ve shared a much more detailed technical report with Suunto, including the relevant logs, and step-by-step reasoning. So, hope it gives the Suunto team a useful starting point.
Apart of that, because AURA is shared by multiple BLE functions, this problem may not be limited to our application. It could also be relevant to reports of external sensors disconnecting during activities, such as those discussed in that thread - https://forum.suunto.com/topic/15629/hr-chest-strap-disconnected-during-activity - symptoms are really similar.
-
-
@Nikolai-Simonov I asked “internally” if there are more reports of the disconnects, and shared this post.
-
@nikolai-simonov Thank you for all your effort you are putting into this app! I really like your features and ideas and especially the UI is really nice.
I’m having serious trouble to get it to work properly though. I’m aware of the BT stack issue that Suunto has in general (which is really ridiculous from Suunto IMHO, especially their apparent unwillingness to fix such a critical bug). But I don’t have connection issues with my HR belt which is having a reliable connection over hours. If I get your app to work in the first place it also just works fine for hours. Hence I think this is another issue.
Most of the times I experience the following:
- I start the app on my iPhone and enable the watch connection button
- I go to the activity screen of my Race (1) watch and enable the Live app in the Suunto Plus menu.
- The watch tries to connect to the app on the phone
- Connection usually first times out, then immediately after the failure message on the watch it connects to the phone
- Both watch and phone show a working connection, I can already see my HR beeing shown in the app
- Immediately when I press “Start” on the watch the connection to the app on the phone breaks and can’t be restored
Any ideas what this might be? Anyone else who has experienced this behavior?
-
@jahudi @nikolai-simonov
I experienced EXACTLY the same problem this week-end when starting a race! -
I now have the described behaviour every single time I try to use the Live app. So for me it is sadly unusable
-
I had not been using the live track for a while (even if it’s convenient there is obviously few occasions when I really need it).
Today I had a race with friends (4 loops relay). I have started it in middle of my race. Worked like a charm the next 3 hours of race ! -
@jahudi, thanks for the kind words about the ui, I tried my best! I appreciate it!
The behaviour you describe actually looks very similar to the “aura” btle middleware issue I mentioned before.
The fact that your HR belt stays connected doesn’t necessarily rule it out, because the S+ app connection could uses a different btle path, as far i understand the aura midleware it’s S+ midleware only to connect ducktape and zephyr’s stack. i could be wrong, but.
I sent suunto a fairly detailed report about aura’s behaviour back in june, including the connection/disconnection cases I was seeing. They replied that they would look into it.
Unfortunately, my later attempts to ask whether there had been any progress, or even whether my report had been useful, were basically ghosted.
As far as I can see, the latest firmware didn’t change anything in the btle stack either the btle module still has the same version.
I really wanted to promote and grow Live.τ further, but it’s difficult when there are connection issues that I can’t fix on my side, and I don’t even know whether or when they’ll be addressed by suunto.
So yeah, I’m a bit frustrated about the situation.
-
@Nikolai-Simonov Thank you for your response. Ok then this is probably yet again an issue where their firmware is to blame.
I followed your updates on the topic and I can so much understand your frustration! What I can’t understand is Suuntos apparent unwillingness (or inability) to do sth about it. Looking around in this forum it becomes quite clear that they have massive problems with their software quality in general.
So I guess for me this was my first and last Suunto watch, which is sad because I love the aesthetics but that doesn’t help if the software is rubbish.
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