New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags bluetooth, sensors, BLE

Application Locus Map 4

Comments 18

Subscribers 3

Votes 2

Bluetooth 4.0 Sensors - Connection troubles

Ulrich Kiermayr shared this problem ago

Solved

Hi.

Upfront: I am not 100% sure if this is a Locus Problem or related to Android 11 on my Galaxy S10.

I tried to connect to my Bluetooth Speed an Cadence Sensors. At initial Startup this works. But when the Connection is lost (e.q during some longer breaks) the sensors won't reconnect any more. The Sensor-Manager is stuck in the "Searching....." state. Closing down Locus and restarting the App fixes this issue most of the times.

At such times the "+" does not give any scan results for any BLE devices - just an empty list.

On a Side-Note: ANT+ is not affected.

And one more thing: The Invalid Data (no Zero-Values form Speed/Cadence Sensors) seems to be back: See here.

Greetings, Ulrich

The same problem 0

Replies (6)

Michael W ●

Hi,

I have exactly the same problem as Ulrich:

My Garnin HRM Duo and the Garmin speed and cadence sensors have always worked fine via ANT+ in conjunction with Galaxy S8.

Yesterday I made the first ride with new phone: Galaxy S20 FE 5G (Android 12) and as I had to find out, it unfortunately does not support ANT+. Thanks Samsung!

Therefore, I have the sensors then connected via BT LE, which was already a little "notchy":

I had to switch BT on / off in system settings and restart Locus, until all three sensors were properly connected.

But then it worked until a longer coffee break. After that I could not connect any of the three sensors again.

Turning BT on / off unfortunately did not help and I didn't want to restart Locus, because I wanted to record the track to the end.

The problem description of Ulrich fits 1:1 also with me, including the "invalid data" message.

Thanks for investigating!

KG,

Michael

URL

Ulrich Kiermayr ●

Just a Workaround: If you restart the phone while Locus is running, it lets you continue the recording *and* most of the time the sensors start working again (until the next break).

Greetings, Ulrich

URL

Michael W ●

Thx for this HINT!

URL

Menion ●

Hi Ulrich, Michael,

thanks for the bug report. I did not noticed this issue so far, weird. Anyway you are absolutely correct. App really has a problems with reconnecting. I've spend some time on testing and I believe I've found reason for this behavior. I'm sure, in the next app version (most probably next week), this should be finally fixed. Let me know after some testing. Thanks!

Jiří M. aka Menion

URL

Ulrich Kiermayr ●

Thanks.

I'll report back 👍

Greetings, Ulrich

URL

Michael W ●

Hey,

did you recognise my report at the bottom?

Don't want to hurry you, just asking because your last reply was that fast. ;)

URL

Michael W ●

Hi Menion,

thanks for fixing. I'll test after the next update and if there are still any issues, I'll report it here.

KG and have a nice rest of weekend,

Michael

URL

Michael W ●

Hi Menion,

unfortunately, the fix did not work it out. I tested it today on a short test ride:

The connection problems seem to be solved (in the Sensor Manager "Status: connected", and seems to reconnect properly if disconnect manually), but I no longer get any data displayed.

The status always says: no valid data. This regarding all three sensors.

In addition, Locus crashed several times during navigation and testing of the sensor mgmt, but this seems to be fixed with the 4.8.1 hotfix.

KG,

Michael

URL

Menion ●

Hello Michael,

yes I received your report, thanks for it. I was till then testing app quite a few times and was never able to simulate any problem.

Hmm what now. Latest version 4.8.2 probably does not bring any extra new benefit. You may give it a try but if there really was problem in 4.8.0, it will be still in 4.8.2. So only some Beta version with enabled logging of BT events should help here if you will be interested. Let me know. Thanks for the help!

URL

Michael W ●

Thx for your reply.

I'm confused, because no (just tested with 4.8.2) data is displayed any more.

With 4.7.x data was displayed, "only" reconnection probs.

Something in locus or android must have been changed?

Think all sensors work, because with ant+ I never hat a problem.

We can try beta version with logging with pleasure.

Additional I could test my old phone with bt and ant+ again with updated locus.

KG,

Michael

URL

Menion ●

Hi guys,

Ulrich, let me know in case, any remaining problems appear but seem to be finally working as expected.

Michael, we should continue in your new separate topic, thanks.

Menion

URL

Ulrich Kiermayr ●

Hi Menion,

I am not 100% sure: Reconnect works eventually. But sometimes I have the feeling that the (re-)connect takes a really long time (some 10min+). But for now I only have had some shorter rides to observe.

The Invalid Data bug is gone.

Cheers, Ulrich.

URL

Ulrich Kiermayr ●

Hi.

Observation from today: I saw quite a lot short disconnect/reconnect events from the speed sensor (short show of a - in the dashboard)

The cadence sensor did not show this behavior.

Greetings, Ulrich

URL

Menion ●

Hi, hm only visible "-" instead of measured value or also a visible "disconnected / connected" notifications? The measured speed value is valid for five seconds, so this should happen only in case of a lower frequency of new measurements. Is it possible?

URL

Ulrich Kiermayr ●

Hello,

I had the chance to observe the issues a little bit more over the last 2 days. I could not really reproduce the short hickups.

But

Sometimes some Sensors take *really* long to connect: In my case the speed-sensor took over an hour to finally connect. (Sensor manager was stuck in searching before). After that it worked. But after a break (flat tire) the speed sensor came back immediately but the cadence sensor then took a while to reconnect. I did not do anything to trigger the (re)connects. Locus was just sitting and recording.....

I did not find any pattern, when and why which sensor gets found and which not.

I have the graphs of the track for cadence and sensor speed attached, where you can see the gaps.

If there is anything I can/should do to further investigate, just let me know.

ed1e5c6222e3b312536ea354db262b62

3bbd82bf410933477a57b710b62b3547

URL

Ulrich Kiermayr ●

And yesterday: Same setup, no connection issues ....

No Idea where to look for more information..

URL

Menion ●

Hello Ulrich,

it is a complicated task. I was on the bike during weekend and no problem with connecting to sensors. Now from the office, I wanted to write to you that I see no problem, but! quick check on recording from morning ride to office = no connection to power sensor on the bike.

My version records logs and I simply see that app was not detecting sensor at all, weird. I'll be watching it and try to find out more. Currently I see nothing how you may help me with this quite unpredictable problem. Thanks for now.

URL

Ulrich Kiermayr ●

Ok. But at least I am not the only one with that issue 🤔

If I can be of any help, just let me know.

URL