Live location S+ app

Adrian.S

This year, I’ve already run 3 ultra races, each about 60-65 km (6-7 hours). Every time, I share my location via LiveT (Android, Pixel 8).

I ran the last one on Saturday.

On every run, after a few hours, my location stops being shared - it disconnects from the watch or something else happens. I don’t have time to figure this out while I’m running fast, so I just ignore it, but this is a major flaw for Suunto.

I use the Vertical 1.

I thought maybe it was because Android was killing the app in the background… So, as a last run, I made sure that battery saver mode was turned OFF and that the app could run in the background without any restrictions.

It didn’t help.

When I noticed that my location was no longer being shared, I opened the LiveT app on my phone and saw that the button was turned OFF.

I tapped the ON/OFF button to turn it ON, but it couldn’t connect to the watch anymore.

I think you’ll need logs from the watch or the app, but if you’re not a developer, it’ll be hard to fix this.

Tamon Yanagimoto

@Nikolai-Simonov yes I built a custom interval workout because I wanted to use navigation at the same time. If I use the built in intervals I cannot use navigation (this is known Suunto functionality)

Lazyjones

Hi. Thanks for the app, it works. It looks nice, like very good piece of software and I like it, but…
The map is horrible. Basically empty, with no usable points that could help somebody determining where actually I am. Like if anything happened deep in forest, mountains etc, it is impossible to precisely locate me, call help, navigate to, or so. No possibility to reflect position to any other mapping service. Even copy/paste coordinates fails. It is weird.
My point is: I use this app during my bike trips (often in the wild) to let my wife or friends know where I am. But they don’t in fact.

Nikolai Simonov

@Lazyjones thanx for feedback! copy/paste coordinates it’s really good catch!

regarding maps, for now we use openfreemap as a tile provider but i could agree outdoor / hiking maps is not their strong point. unfortunatelly major providers like a maptiler or mapbox significantly out of budget.

Now i’m looking to self-host tiles, let’s see.

Lazyjones

@Nikolai-Simonov Understood. Please allow to quick transfer coordinates to any other mapping service. The one who monitors the position will certainly have to do this several times. It should be quick and easy.
Thanks, cheers.

Adrian.S

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?

Nikolai Simonov

@Adrian.S not realy
discribe it here - https://forum.suunto.com/post/193011

Nikolai Simonov

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.

larrybbaker

@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.

Nikolai Simonov

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.