Battery drain when ConnectIQ app is not running

I've had several users mention that they believe the Activity Recorder app is responsible for battery drain that they are seeing since installing. In my mind this is not possible; the application would need to be active in some capacity for this to happen. I've audited my code and noticed that I enable sensor and position events in some cases, but do not explicitly disable them on app exit. I've since updated my code to do disable them, but I'm still curious if this could be the source of problems.

I'm guessing that they're both affected by some sort of Bluetooth or WiFi issue, but have no evidence at this point.

Any thoughts?
  • Trying to reproduce sensor this issues, does anyone have some code that can trigger the battery drain?

    do you still encounter the battery drain issue, if so, can you share some code to help us reproduce it?

  • Due to Garmin does not have a NDA and a PIIA with F3b, I cannot provide source code.   I could try to create a generic build or a debug build. 

    It is likely best if you contact me via the Forum messages.   Then we can start a phone call or teams meeting.

  • The bug can be in firmware...

    I've noticed several cases with battery drain after finishing activity (f7 16.22). I can't reproduce every time but I think it' can be problem with GPS.

    As I remember

    - battery is low - about 10%

    - choose activity with gps (my case was with walking) outside and wait for GPS

    - start (I use only one, my,  custom DF and read info.currentLocationAccuracy)

    - after about  40 minutes (typical my activity) go inside the building - and wait for loosing GPS

    - wait a few minutes and end activity (still without GPS)

    probably from time to time system tries to fix gps