Problem with my app, alert every minute I don't know how and why. A watch parameter ?

Hi,

Since a few month, my app is vibrating and biping every minute after the activity is started :

		ActiveSession = Fit.createSession({          // set up recording session
				:name=>"Sailing",                              // set session name
				:sport=>Activity.SPORT_SAILING,                // set sport type
				:subSport=>Activity.SUB_SPORT_SAIL_RACE          // set sub sport type
		});
		ActiveSession.start();                                     // call start session

The bip and the vibration are not made by my app (not the same sound and not the same duration)

I have looked in all my watch parameters, and deactivated all things like sound signal, but it's alaway biping every minute. I cannot find where this is coming from

Of course, the simulateur doesn't do that.

This is the only activity I often use. But others activities don't seem to do the same ...

Some help would be useful, thanks

My watch is EPIX 2, with 17.28 version

Top Replies

All Replies

0 flocsy🤠 over 1 year ago

If it's not from your app then maybe ask it on the epix2 forum. Sounds like some setting to alert you based on time, maybe auto lap.

0 pocolocos 2 months ago

same here - it's not a question of the device-type; you can switch it off in the general settings - but than you are also not able to hear the beeps of your app ;-(
any suggestions anyone?

0 flowstate 2 months ago in reply to pocolocos

This sounds like a problem where a CIQ app of a given type (in this case, sail racing) is inappropriately picking up settings/behaviour from the associated built-in activity.

In this case it seems like the watch is counting down the built-in regatta timer (which is ofc invisible to the CIQ app / user), and beeping every minute to notify you of this invisible countdown.

https://www8.garmin.com/manuals/webhelp/GUID-E5C62F3F-DCE3-4197-8CA5-E419B2A55D12/EN-US/GUID-73BD5ACF-0952-4FCE-9F09-EE12F1690563.html

You can use the device to help you cross the start line of a race exactly when the race begins. When you synchronize the regatta timer in the sail racing app with the official race countdown timer, you are alerted at one-minute intervals as the race start approaches. When you set the starting line, the device uses GPS data to indicate whether your boat will cross the start line before, after, or at the correct time to start the race.

https://www8.garmin.com/manuals/webhelp/GUID-E5C62F3F-DCE3-4197-8CA5-E419B2A55D12/EN-US/GUID-04BF36A7-7EB8-426E-893C-4148E6607F7F.html

https://www8.garmin.com/manuals/webhelp/GUID-E5C62F3F-DCE3-4197-8CA5-E419B2A55D12/EN-US/GUID-41507EC5-4E2F-43AA-A60A-F57BF1D81A9F.html

Idk what the default value is for the regatta timer since I don't own a Garmin that does sailing, but I bet that whatever the value is, you will continue to hear beeps once per minute until Garmin *thinks* you have crossed the start line.

e.g if the default regatta timer is set to 30 minutes, you'll hear beeps every minute for 30 minutes.

0 pocolocos 2 months ago in reply to flowstate

nope - the default Timer in the Garmin SailingApp (which is pretty useless) is set to 5 min.

0 flowstate 2 months ago in reply to pocolocos

Yeah, the 30 minutes default was just a guess.

The larger point is that there's a one minute alert in the built-in sailing app (according to the manual anyway), and that both of you are also seeing a one minute alert in your CIQ sailing apps. That seems like a big coincidence, especially considering that none of us knows of any other built-in alerts which repeat every minute.

First of all, it should be obvious that no matter what the default value for the regatta timer is in the built-in sailing app, the same timer (or associated alerts) should not be used in a CIQ sailing app (unless the API provides access to this behaviour/settings, which it does not).

Second, it's possible for there to be a bug (or bad design decision) which preserves the one minute alert while ditching the start line logic, meaning that from the watch's POV, you never reach the start line and the alert goes on indefinitely.

It's not the first time that settings/behaviour for one built-in activity has affected either other built-in activities, or CIQ apps which record the same activity type.

- Users mentioned that installing a data field such as stryd in one activity could cause it to be invisibly added to other activities (they could tell because of the data it recorded)

- People have seen auto laps that are set in the Walk activity being applied to Golf (which has no auto lap setting)

- flocsy mentioned something about how his CIQ device app which records a hike activity would cause data to be (silently) recorded by an unrelated CIQ data field that's installed in the built-in hike activity: https://forums.garmin.com/developer/connect-iq/f/discussion/400587/watch-app-records-a-hike-session-and-my-hike-activity-s-unrelated-ciq-datafield-is-also-running

The common thread is that Garmin is running code for one activity or CIQ app in the context of another activity or CIQ app, when it shouldn't be.

0 pocolocos 2 months ago in reply to flowstate

thx. for leading me in this direction - I just removed the optional SubSport (SUB_SPORT_SAIL_RACE) and the annoying Beeps are gone ;-)