Live location S+ app
-
@Nikolai-Simonov said in Live location S+ app:
On Android, it’s bit more flexible, if the app is installed outside of Google Play (via direct APK or APKPure), it can send SMS messages directly from the device, without going through our cloud, this option simply isn’t available on iOS due to system restrictions.
Thank you for this useful app, I tried it for the first time yesterday.
However, I couldn’t get SMS sending to work with the direct APK version.
Whether I defined direct SMS or cloud SMS, I got a message saying something like: “No SMS number defined for SOS.” That may not be the exact wording, as I don’t have the message right in front of me.
I tried it with french phone number, with international format (+33) or national format. -
@Anthony-Guillemette Thanx for using it! and reporting a bug.
Could you tell what app version? it will helps me localize an issue. -
@Nikolai-Simonov version 1.0.13-ext (77)
And a strange thing is that I don’t have a save button even if I fill it with a phone number
When I use the return button, sometimes it saves the number filled, and sometimes not. I also tried to select a contact instead of fill it manually.
-
@Anthony-Guillemette Oh! so stupid bug! i’ve just checked. Actually, there’s the save button in appbar… but! it’s the same color like an appbar
please try to tap on the right top corner, it should works.
thanx to point it out
-
said in Live location S+ app:
sometimes it saves the number filled, and sometimes not
Maybe it’s because I tapped all over the screen, and sometimes on that invisible button… ^^
But even though it’s saved, the SMS still doesn’t work… -
@Anthony-Guillemette make sure if SMS permission is enabled and what phone do you use?
-
@Nikolai-Simonov phone number is correctly defined and sms authorization toot, but sms is still in error. I have an Huawei P30.
-
@Anthony-Guillemette I investigated an issue, unfortunatelly there was a real bug.
TLDR; what happend - misconfiguration of CI/CD leads to non googlePlay version was built with google play internals without sms sending module
so, could you try the latest preview build?
https://artifact.fra1.digitaloceanspaces.com/live-t/apk/btle/live-t.apk
should be - 1.0.16 (101)And again thanx a lot for point out this issue!
-
@Nikolai-Simonov I’ve downloaded the version
First of all, the graphical improvements look really nice
However :
- The button to save a phone number is now visible
- SMS is still not working : “SOS message failed”
- Linking the Suunto account doesn’t work (error 400: invalid redirect_uri)
Another problem I encounter: when LiveTracking SuuntoPlus app is enabled by default on the training mode, I have to disable and then re-enable it, otherwise the watch is not detected by the application (“device search”).
- The button to save a phone number is now visible
-
@Anthony-Guillemette said in Live location S+ app:
SMS is still not working : “SOS message failed”
i see an error, looks like missed implementation for pre-android12 telphony. I’ll publish new version today.
@Anthony-Guillemette said in Live location S+ app:
Linking the Suunto account doesn’t work (error 400: invalid redirect_uri)
Oh! thanx for pointing out! Just checked suunto api profile, and they clear all api integration data!!! 🤯 ridiculous! won’t be difficult to restore but…
@Anthony-Guillemette said in Live location S+ app:
Another problem I encounter: when LiveTracking SuuntoPlus app is enabled by default on the training mode, I have to disable and then re-enable it, otherwise the watch is not detected by the application (“device search”).
It’s not a bug but feature! you don’t need to re-connect it each time, just take a 5-15 sec to connect.
TLDR;
“Looking for watch…” - it’s a “cold start” during this time watch allocate memory and register all btle services.
after that you could see “waiting S+ application…” at this stage s+ app is connected and waiting for handshake between mobile app and s+ app… but connection already happend!
after that you could see the green text with a S+ app version.splitting connection on these three steps allows us immediatelly reconect to watch if service on phone has dropped or connection lost for some time, watch still registered on the gatt services, and we can try to restore it when connection back.
you could check how it works, connect to the watch, than during workout disable service for a few second and enable it back, the watch should instantly reconnect.
because every time on android we start from the fsecond phase, and if watch are registred in our GATT table, we fire handshake event imediatelly, if it pass we ready to work in miliseconds.
if we just start a workout watch initially is unsubscribed from our gatt services, so in fact of this we need to proceed through the cold start.
however, i agree it could look like a bug, but it should be solved in UX way… i’ll think about it…
-
@Nikolai-Simonov said in Live location S+ app:
It’s not a bug but feature! you don’t need to re-connect it each time, just take a 5-15 sec to connect.
Thanks for all the explanations.
The Bluetooth connection to the watch is a bit unclear to me, but I understand the general principle.And I confirm your explanation: even if the app says “waiting for S+ application…”, it will turn green as soon as the activity starts.
However, I tried the live tracking again this evening during a run, but unfortunately, it didn’t work very well - version 1.0.16-ext (102)
First, I had trouble activating tracking: the watch said it was connected (I had the GPS coordinates on the dedicated screen) and the app indicated a connection with the watch. But I still wasn’t located on the app’s map, either at the start or after a short movement.
I had to stop the activity, disconnect and reconnect the app and the watch, and start a new activity to finally be located on the map and see my movement.
Several kilometers later, I checked and the watch was disconnected (“DISCONECTED state:99”). I’m not entirely sure, but I think the app still indicated a connection with the watch. I tried disabling the Suunto app on the watch and then re-enabling it, disconnecting from the app and re-enabling it, several times, in various orders, but still without success. I finally gave up on LiveTracking.
Last weekend, I also had some issues with version 1.0.13-ext (77) where I experienced a disconnection for a few kilometers, but the connection was restored afterward and the tracking resumed (with a long straight line corresponding to the disconnection).
As I work in software development myself, I imagine it can be very difficult to diagnose with just this text information, sorry
