Acknowledged
10 months ago

Instinct 2S completely hangs with BLE bg wf

i'm developing a BLE background watchface and am seeing complete watch hangs on Instinct 2S after about 1 to 2 days of running the wf (and I believe FR 965M but I have stopped testing that due to its inadequate battery.)

i'm not sure which connect iq calls are causing this but i will try to gather more info. since it happens so infrequently (i've seen it at least 3 times and have never been able to get past 2 days of runtime so i'm sure i'll see it again), i'm starting this bug report now anyway to see if others have seen it.

the only thing i can do to the watch after the hang is hold the light button for a long time to power it down, it responds to nothing else and does not update the wf at all.

Horsetooth
  • 9 months ago

    the fr165 hangs (complete watch hang) with scan-only mode just like the instinct2s did, which means anyone with my app should be able to see it, so if Garmin is listening they just have to reach out and i'll send them my source. i've wasted way too much time on this so am giving up on forerunner/instinct and will continue with the (super expensive) fenix option.

  • 9 months ago

    unbelievably the forerunner 165 also hangs at about 42 hours. it has software bundle 20.32, which was the latest according to express.

  • 10 months ago

    added Ble.setDelegate(null) before every bgnd exit but it didn't help, the watch still hangs around 42 hour mark.

    i'm done with instincts unless someone has another idea to try before i sell it.

  • 10 months ago

    the last thing i could think of to try has also hung... it was just doing BLE scans and never connecting or reading chars.

    so, given the scanning only hangs, the only thing i can think of that could be causing this is one of these calls:
    BleDelegate.initialize();
    Ble.setDelegate(myBLEDelagate);
    Ble.registerProfile( _envProfileDef );

    i may try to undo any of these that can be in one more last-attempt (think i saw in the docs you can set one of these to null to undo it, i'll check docs again.)

    also interestingly, since the onSensor timeout method was added the hangs are happening consistently at the 42 hour mark:
    42 hours to hang
    42.667 hours to hang
    42.25 hours to hang
    42.6 hours to hang

    before that i also clocked hangs at 37 to 40 hours.

  • 10 months ago

    as expected 17.01 still hangs also.

    i have one more thing to try, after that i will just sell the i2s, unless i hear from garmin that they care about it and would like me to try narrowing it down more.