Garmin Bug Notice

GPS Data is being including in CIQ Applications that are not using the Module: Toybox.Position.

The result is a Map and tracks are included in Connect post activity.

This GPS data error is only seen when Module: Toybox.FitContributor is used. If Toybox.FitContributor is not used the GPS data is not included.

Known Affected devices:

-Forerunner 55, Forerunner 955 and Venu 2 Family.


Affects all CIQ applications by adding GPS tracks to the activity data.

Bug – GPS Data being recorded in Non-GPS CIQ Applications – Connect IQ Bug Reports – Connect IQ – Garmin Forums

SwimSports+ Update

SwimSports+ v3.5

  • Bug in 3.4, Enables Lap Swim pool turn detection in:
    • (VA3, VAHR, FR935, FR245, FR645 FR735,Fenix5 and Fenix 6 nonPro).
  • ERA Corrections
    • Venu 2 Plus, Vívoactive 4, Venu Sq. Music
  • Using Garmin CIQ SDK 4.1.7-2022-11-21-562b8a195


Brian Brown

F3b Notice: Battery drain


*** Update 08-30-2023

All F3b apps we updated to used Connect IQ SDK 6.3.0, which included several fixes from Garmin to address a Battery burn issue.

– All Applications were recompile with 6.3.0, no source changes.

– Using Connect IQ SDK Mac 6.3.0-2023-08-29-fc81ed416

— 6.3.0 for battery burn issue.

–(Garmin) Fix a bug where getRegisteredSensors() would not return the correct enabled states for onboard hear-rate and onboard pulse-ox sensors.

–(Garmin) Fix a bug where setEnabledSensors() did not work correctly for onboard heart-rate and onboard pulse-ox sensors.

**** Update from Garmin Engineering

This will be rolled out to all f3b applications

From: Travis <>
Date: Friday, August 11, 2023 at 4:16 PM
To: brian brown <>
Cc:  Brandon <>
Subject: RE: GARMIN Connect IQ – New review(s) for your app “F3b Inline Skating+” – Connect IQ Notification

Brian,I did some investigating and found a bug in the sensor our shutdown process where we were not decrementing a counter if an app exits without explicitly unregistering the sensor event callback. This resulted in the system keeping a periodic timer alive, sending a wakeup message to the VM thread to do some processing that isn’t needed. I have not yet confirmed that this resolves the battery drain issue entirely, but I have confirmed that it is a problem and is causing unnecessary battery drain. I have a patch for this issue that should make it into our Q4 release.

That said, you should be able to avoid the issue by ensuring that the sensor event callback is set to null when you no longer want to receive sensor data. Simply disabling the sensor or changing the enabled sensors is not sufficient. You need to clear the callback as well.


I think that you will find that if you paste that into the bottom of your quitSensors method, the battery drain will be reduced or eliminated entirely.



There is a new Garmin bug within the Venu2 family, FR55 and FR955 that is affecting battery drain. The Garmin issues have been acknowledged and there are bug ticket numbers assigned. The Garmin bug tickets can be viewed in the https:\\

F3b has made several workarounds and improvements to each app to further reduce battery drain and there are a few things you can to reduce your watch battery drain.

  • Use Garmin Express ( to verify if there are any pending updates for your watch.
    • A pending updates will cause extreme battery drains.
    • I recommend, using Garmin Express for installing All CIQ apps or Garmin Software updates.
  • Restart the watch after any CIQ app install or Garmin Software update.
  • Set the SaO2 sensor to “Manual Check” or “On Demand”. The default is ‘Always’ or ‘All Day’.
  • Use a less intensive widgets and watch face. These types of Garmin Apps typically use Garmin Background service and is continually running in the background and will increase battery drain.
  • Remove all unused apps, watchfaces, and widgets.
  • Restart the watch after an activity.


-Brian B.

Garmin Express ->

Garmin Forums ->