Live location S+ app

halajos

@Nikolai-Simonov thanks for the efforts, looks very interesting. Any chance to reduce the power consumption on the phone, for instance by limiting the update frequency to let’s say once per minute? I’m using the built-in location sharing on Android, which is far less accurate but doesn’t eat the battery.

Tieutieu

@halajos I’m with you. the consumption I observed yesteday during testing is to high. for Now I would choose to use live tracking :

for small races or journey under 5 hours max
or launch it during longer activities only when needed

Egika

@halajos said in Live location S+ app:

@Nikolai-Simonov thanks for the efforts, looks very interesting. Any chance to reduce the power consumption on the phone, for instance by limiting the update frequency to let’s say once per minute? I’m using the built-in location sharing on Android, which is far less accurate but doesn’t eat the battery.

hm. I thought the original idea of the app was, to reduce power consumption of the phone. Like BT connection uses less energy than the phone’s GPS chip…?
Seems not to be the case for you then…

Tieutieu

@Egika as phone need to send position through mobile network, it consumes data and battery, and as I observed lot of time, phone consumes more battery especially when mobile network is weak and the phone tries to reach it.
But I’m sure it uses less battery than if using phone GPS chipset.

Egika

@Tieutieu I undertood, that @halajos compared built in location sharing from the phone with the new setup and watch connection.
Maybe he can clarify, if the mobile network reception was comparable…

sebchastang

@halajos Thanks a lot for your work @Nikolai-Simonov
Ideally it would be nice to choose the update frequency (for exemple 1s, 5s, 10s, 30s, 1min, 2min, 5min, 10min, 30min) so we can save battery on both watch and smartphone.

halajos

@Egika I didn’t compare, I just have past experience with location sharing on Android during a 11-hour run. If I extrapolate the 19% in about 2 hours with Live.t mentioned by @Tieutieu, it would deplete the battery completely in 11 hours. I don’t recall how much Google location sharing consumed within that 11 hours, but it was definitely far from full discharge.

Gunnar

@halajos Android can show the battery consumption per app, does iOs this too?

Egika

@halajos I would really like to see a real world comparison in phone battery effect under comparable situations. Maybe someone can test.

Miroslava

@Nikolai-Simonov So either I’m stupid or it doesn’t work I went for a run yesterday, I set everything up, just like you sent me in the instructions, I’m attaching a photo. It registered the position but nothing happened, no movement, no data, nothing. Today I went out to the street to try walking to work. I’m not exaggerating but I had to press the button 10 times because the device was not found. On the 11th attempt it connected, I say ok I sent my location to my friend, let her follow me, I even tried an SOS SMS, all this is ok I send a photo of the walk
but I have basically three questions

why do I have to press the button on the watch 10 times before the device finds it? Is it a problem with android or what?
it didn’t show my heart rate, only my movement speed
every minute I got a notification on my phone that the watch was connected (can I turn it off somehow? this was very annoying). During a walk that lasted 2.5km, I got those notifications about 15 times.
I have no idea what I’m doing wrong

Nikolai Simonov

@Miroslava
Thanks for trying it out and for the detailed message!

What button are you pressing 10 times?
To see heart rate in the tracking view, make sure the “Additional metrics” option is enabled in the app settings.
Repeated “watch connected” notifications
Those shouldn’t appear constantly. That sounds like an issue possibly a phone-specific behavior. Could you let me know what phone model and Android version you’re using?

Tieutieu

@Nikolai-Simonov Thanks. I just edited my test report to specify that sending metrics was off and that i had continious gnss ON.
I’ll test again with notifications off, gnss off and additional metrics on

Miroslava

@Nikolai-Simonov

1. I pressed the top button 10 times today until it connected
1. I already understood that it’s in the settings
Motorola edge neo 30 i think android 14
tommorow i go run and try it again

Dimitrios Kanellopoulos

Is the web made with react ?

Francesco Pagano

@Nikolai-Simonov said in Live location S+ app:

Repeated “watch connected” notifications

I can confirm on Android 14 I see repeated notifications “watch connected / watch disconnected”, every 30 seconds or so

Miroslava

@Francesco-Pagano exactly as me

Nikolai Simonov

Hi @Miroslava @Francesco-Pagano
Thanks a lot for helping test and report this!

I was able to reproduce the issue — on some devices, it looks like there’s a conflict with the Suunto App (SA). Roughly once per minute, SA causes the disconnection between Live.t and the S+ app on watch and that’s why you’re seeing repeated connection notifications.

I still need a bit of time to fully investigate what’s going on, but in the meantime:

Good news:
The SuuntoPlus app handles reconnection correctly, so even with these interruptions, tracking should continue to work well.

Temporary workaround:
You can mute notifications from the Live.t app in your phone’s system settings. That should make it less annoying until the fix is ready.

I’ll publish a small hotfix soon to make the connection notification silent by default.

Thanks again for your help in tracking down this weird bug really appreciate it!

Nikolai Simonov

@Dimitrios-Kanellopoulos nope, it’s svelte

Miroslava

@Nikolai-Simonov I’m super glad I helped you catch the mistakes, we’ll see how it goes after the fix, when I try it out

Dušan Ković

@Nikolai-Simonov Would adding different intervals between data pings be beneficial for mobile phone battery life? For example - 1min, 2min, 5min, 10min, 15min, 30min, 1 hour, etc. On a lot of activities you don’t need real-time (1sec pings) tracking