Is this just a coincidence or is there something that I could have broken?

Hi,

I have a mature app that has a fair number of contented users... and it displays values from various sensors (heart, cadence etc.) using a standard Garmin activity session.

Trouble is, one customer recently described the following on his Fenix3 (non-HR version):

1. He had been using a heart rate strap, and using it successfully for some time

2. He installed my app

3. The HR strap worked with my app but no longer worked with anything else

I only have the one report of this, and it doesn't make sense to me in any case.

Has anybody heard of anything similar and / or do they have any suggestions of what might cause it?

And...

Is there anything I either can do or should do to alleviate it?

AFAIK, I am enabling and disabling sensors correctly when I start and stop activity tracking.

Top Replies

_psx_ over 3 years ago +1

How do you disable sensor? Probably by calling disableSensorType, you don't need it. Maybe disabling is a problem because it has influence on whole system .

In my app, to use external HR sensor I use…

All Replies

0 _psx_ over 3 years ago

How do you disable sensor? Probably by calling disableSensorType, you don't need it. Maybe disabling is a problem because it has influence on whole system .

In my app, to use external HR sensor I use only one line:

SEN.setEnabledSensors( [SEN.SENSOR_HEARTRATE] );

and no disabling.

And reading HR from getActivityInfo().currentHeartRate

0 9635560 over 3 years ago in reply to _psx_

Yes, I was explicitly disabling sensors.

I will check if not doing so fixes the issue.

0 FitzgeraldKrudde over 2 years ago

I am having trouble to turn the (wrist) heart rate sensor OFF.

I can turn it ON with Sensor.enableSensorType(Sensor.SENSOR_ONBOARD_HEARTRATE);

but when I call:

Sensor.disableSensorType(Sensor.SENSOR_ONBOARD_HEARTRATE);

the (wrist) heart rate sensor is NOT turned OFF.

I am clueless at the moment why this call does not work..

0 FitzgeraldKrudde over 2 years ago in reply to FitzgeraldKrudde

Root cause unknown but after I restarted my watch the API calls work as expected,,