Suppress Lap Notification when adding Laps in a Device App

I'm using ActivityRecording.Session and addLap() to mark laps in a Device App.  Is there a way to suppress the lap notification message that shows up on the device?  The notification message blocks over half the screen on the Edge 540 and it blocks information that the user needs to see.

  • I think the user can enable or disable the lap alerts, but you can't from code

  • I've found where the user can disable AUTO lap.  This will prevent the device from creating a lap every mile or km.  But it doesn't stop the lap message when addLap() is called.

    On the Edge 540, I've also found where you can reduce the number of fields displayed in the lap message which at least makes the lap notification smaller.  But this can only be applied to a native activity like Indoor.  The setting doesn't seem to carry over to the lap message on a ConnectIQ Device App.  It would help a lot if the message was just smaller.

  • I don't see this on any watches. Is this only on (some) Edge devices?  I don't see this message with a device app on a 530..

  • Hi Jim,  Thanks for responding.  It's been a while since I've worked on Device Apps but I had recalled that previous devices did not show the native lap message when addLap() was called in a Device App.  In fact some of my older code has a home cooked lap message for when I DID want the message to show.

    Here's what it looks like on the Edge 540 right now.  It takes up about 2/3 of the screen for about 10 seconds.  Even if I press the Up/Down arrows, it doesn't dismiss it.  My screens just change behind it.

    It is also interesting that the Edge 540 is showing the native start green arrow and native stop red square when the activity is started or stopped.  Here too, I had coded my own green arrow and red square in apps that I worked on several years ago.

    I did some work on a different Device App a few months ago that also marked laps and I recall that it did not pop up a native lap message either.  That was on this same Edge540 device.

    So is this a bug in the Edge 540 (version 26.18) or is this intended functionality?