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

    well i wrote another reply yesterday and it was rejected as spam. i "appealed" so if you see it later just ignore.

    looks like the f7p is still working fine after almost 3 days, so i have to assume the i2s doesn't like something that i'm doing.

    if your i2s is still working more than 2 days can you tell me if you do any of the following? i'll try without these starting now...

    - turn off phone connection, wrist heartrate, and wifi (the latter might only be on the f7p) - i did this on the i2s via power manager but on the f7p i had to use individual settings to keep the watchface on.

    - use the saved (to storage) scan result instead of re-scanning each time

    - read 3 characteristics some of the time (at least every 30 minutes). this takes nearly all 30 seconds of bg process on the i2s, sometimes more so it is killed - the f7p is a lot quicker at this so doesn't get killed much if at all.  i'll reduce it to 1 to test.

Comment
  • 10 months ago

    well i wrote another reply yesterday and it was rejected as spam. i "appealed" so if you see it later just ignore.

    looks like the f7p is still working fine after almost 3 days, so i have to assume the i2s doesn't like something that i'm doing.

    if your i2s is still working more than 2 days can you tell me if you do any of the following? i'll try without these starting now...

    - turn off phone connection, wrist heartrate, and wifi (the latter might only be on the f7p) - i did this on the i2s via power manager but on the f7p i had to use individual settings to keep the watchface on.

    - use the saved (to storage) scan result instead of re-scanning each time

    - read 3 characteristics some of the time (at least every 30 minutes). this takes nearly all 30 seconds of bg process on the i2s, sometimes more so it is killed - the f7p is a lot quicker at this so doesn't get killed much if at all.  i'll reduce it to 1 to test.

Children
  • 10 months ago in reply to Horsetooth

    my i2s is still running fine.  

    With the sensor I'm using I read 2 characteristics every 5 minutes.  On the pi I'm using I turn on an LED when it's connected and log time connect/disconnect times.  Reading 2 takes one second.  If it's taking long with your sensor, I'd suspect the sensor.