Acknowledged

Fenix 6 reboots during kiteboarding activity and restarts with running activity

Fenix 6 reboots during kiteboarding activity and restarts with running activity. 

WOO Sports app WOO+Gps randomly changes kiting into running activity. Many users experience thisissue, super annoying.

Parents
  • Hi all, so my first post:

    I uploaded some files with different cases of Fenix 6 PRO resetting but also with Fore 245.

    Seems it is affecting mainly Fenix 6 but I would think all Garmin devices have the same issue, if there are not more cases it is due the fact of the WOO is disconected faster on Fenix 6 because weaker BLE signal but also because WOO device is used with GPS and it is water sport, so under water radio is not able to trasmit or receive, so less posibilities to have the issue than a Fore 245 e.g.

    The method I followed to reach this is the next one:

    I made an app disconnecting and reconnecting BLE to a device, like 5/10 times per minute, tested on simulator, Fenix 6 PRO and Fore245

    After a time, depending on how(the way) you are connecting/disconnectin, it could be from 140 to 1200 reconnections, both watches reset and Garmin simulator gets stuck

    Could be the memory overwriting because BLE stack reachs a limit, I cannot assure o.c.

    Also saw in simulator, if disconnects when trying to send BLE data, simulator gets stuck but also NRF52 DK is not able even to scan after this in some ocassions, I need to close the simulator, switch off the NRF52DK and start again.

    I can try to make my own connection FW for NRF52 to see some logs form BLE if needed, but by making a Garmin app disconnecting and reconnecting every 10 seconds you should be able to reproduce the issue, and for sure you have access to your FW and can debug it.

    Also noticed, because I was doing the test indoor but near of a window, if I have GPS , fenix 6 after resseting is going to running app, it is also could be because it is the first app in the list, but just guessing.

    if I don't have GPS the watch just resets, to the clock screen, but one day it was reset and my date was Jan 1 of year 1023 or sothing like that, cause of that I think some memory overwritting.

    That's all for now, don't hesitate to make any question if you have.

    King Regards,

    JM

Comment
  • Hi all, so my first post:

    I uploaded some files with different cases of Fenix 6 PRO resetting but also with Fore 245.

    Seems it is affecting mainly Fenix 6 but I would think all Garmin devices have the same issue, if there are not more cases it is due the fact of the WOO is disconected faster on Fenix 6 because weaker BLE signal but also because WOO device is used with GPS and it is water sport, so under water radio is not able to trasmit or receive, so less posibilities to have the issue than a Fore 245 e.g.

    The method I followed to reach this is the next one:

    I made an app disconnecting and reconnecting BLE to a device, like 5/10 times per minute, tested on simulator, Fenix 6 PRO and Fore245

    After a time, depending on how(the way) you are connecting/disconnectin, it could be from 140 to 1200 reconnections, both watches reset and Garmin simulator gets stuck

    Could be the memory overwriting because BLE stack reachs a limit, I cannot assure o.c.

    Also saw in simulator, if disconnects when trying to send BLE data, simulator gets stuck but also NRF52 DK is not able even to scan after this in some ocassions, I need to close the simulator, switch off the NRF52DK and start again.

    I can try to make my own connection FW for NRF52 to see some logs form BLE if needed, but by making a Garmin app disconnecting and reconnecting every 10 seconds you should be able to reproduce the issue, and for sure you have access to your FW and can debug it.

    Also noticed, because I was doing the test indoor but near of a window, if I have GPS , fenix 6 after resseting is going to running app, it is also could be because it is the first app in the list, but just guessing.

    if I don't have GPS the watch just resets, to the clock screen, but one day it was reset and my date was Jan 1 of year 1023 or sothing like that, cause of that I think some memory overwritting.

    That's all for now, don't hesitate to make any question if you have.

    King Regards,

    JM

Children
No Data