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
Parents
  • 10 months ago

    a little more info from the logs after today's hang... 

    there is no error in CIQ_LOG.YML (no errors in there for several days).

    the app .txt file (i had created one just to see what info it had about a hang) shows not much was going on, nothing BLE-wise, but it has some weird behavior at the hang time (the watchface hung showing 7:52AM on it) indicating the bg app (not just the bg process) died and attempted restart???

    App initialize 7:47
    onStart
    ...<watchface is working fine here>...
    onBackgroundData=[<redacted>] at 7:47
    myreturns=80
    curCtr was 242 changeCtr is 242
    <background process exited fine here, the last println is from onBackgroundData()>
    App initialize 7:52
    onStart
    getServiceDelegate: 7:52
    memory: total: 28688, used: 15744, free: 12944
    App initialize 7:42
    <time has flown backwards???>
    onStart
    devCode=<redacted>
    enabling scan
    <that message is from getInitialView(), so something restarted the whole bg app, but bg process isn't restarted>
    App initialize 7:43
    onStart
    devCode=<redacted>
    enabling scan
    <the whole bg app has attempted to restart a second time, but then nothing else at all, now we're hung>
    <i powered down and powered back up the watch here>
    App initialize 12:29
    ...<wf is back to normal>...

Comment
  • 10 months ago

    a little more info from the logs after today's hang... 

    there is no error in CIQ_LOG.YML (no errors in there for several days).

    the app .txt file (i had created one just to see what info it had about a hang) shows not much was going on, nothing BLE-wise, but it has some weird behavior at the hang time (the watchface hung showing 7:52AM on it) indicating the bg app (not just the bg process) died and attempted restart???

    App initialize 7:47
    onStart
    ...<watchface is working fine here>...
    onBackgroundData=[<redacted>] at 7:47
    myreturns=80
    curCtr was 242 changeCtr is 242
    <background process exited fine here, the last println is from onBackgroundData()>
    App initialize 7:52
    onStart
    getServiceDelegate: 7:52
    memory: total: 28688, used: 15744, free: 12944
    App initialize 7:42
    <time has flown backwards???>
    onStart
    devCode=<redacted>
    enabling scan
    <that message is from getInitialView(), so something restarted the whole bg app, but bg process isn't restarted>
    App initialize 7:43
    onStart
    devCode=<redacted>
    enabling scan
    <the whole bg app has attempted to restart a second time, but then nothing else at all, now we're hung>
    <i powered down and powered back up the watch here>
    App initialize 12:29
    ...<wf is back to normal>...

Children
No Data