Vivoactive4 Bikeradar RTL515 dual connection BUG

I'm currently developing a WatchApp using vivoactive4 and bikeradar RTL515 with ANT/ANT+ connection.

I try to start a specific vibration pattern once I detect a target from the radar, however my vibration pattern is not as expected and here are my findings:

- If I remove all vibrations commands from my application, I still have vibration occurring;

- If use the Varia app in a mobile, I can verify that watch vibrations occur when a new target is detected;

- If I use the radar debug mode, I receive targets in the mobile app but not in the ANT/ANT+ connection, thus the debug mode must be sending targets only through BLE;

- Even though may application has no messages in ANT/ANT+ connection, the vibrations are still occurring with the radar in debug mode;

I add:

- Bluetooth permission is not added in the app manifest;

- The watch settings tells me that the radar in connected through ANT;

- vivoactive4 software version: 6.3

- RTL515 software version: 3.32

- vivoactive3 does not have this problem and my vibration occur perfectly.

Did someone face the same problem and has a way to disable those "native" vibration that seems to come from a dual connection (ANT/ANT+ from the application and BLE from the firmware) with the radar?

Nikeow over 3 years ago

What are you trying to do? If you're trying to make the radar appear in a data field and the like, be aware that Garmin will not approve your app.

eg: https://www.youtube.com/watch?v=Zzt_6Ld7C-c

This was rejected on grounds of safety

but if you're using it for your OWN purpose and for your own use, then no issue

5774657 over 3 years ago in reply to Nikeow

Hi!

It is indeed a watchapp to alert of approaching targets using my own constraints. This being said, my alerts will differ a bit from those native alerts and the native vibration overriding my own pattern is really annoying!

Yep, it is a closed project and we do not foresee the need to put it to the store.
Also, I do not use datafield views if that is the only thing that would make the app to be rejected.

jim_m_58 over 3 years ago in reply to 5774657

Data field or device app makes no difference. See the wiki for approval exceptions: https://forums.garmin.com/developer/connect-iq/w/wiki/10/app-approval-exceptions

5774657 over 3 years ago in reply to jim_m_58

Thanks for the link.

As I said, I have no intentions to put it to the store and I still have the the annoying bug.

I see you comment a lot on this forum, did already face this problem or have any ideas of how to solve it?

jim_m_58 over 3 years ago in reply to 5774657

I've never done much with ANT, just BLE and I've never used radar.

Nikeow over 3 years ago in reply to 5774657

I do not understand your meaning of "debug mode", care to explain?

As for BLE, I have no idea as well.

For ANT+, IIRC, when the watch natively supports the sensor (eg: Radar / Power Meter) then these MUST be turned off and removed/deleted from the watch so that the datafield can connect directly to the sensor.

eg: For A Fenix3, no support for radar, I have no issue

for a Fenix 5 which natively supports radar, then radar MUST not be paired to the watch.