I've got serious problem with my FR230

So last days I've been working on DataField app to pace run against negative split technique ("Negative Split Pacer"). It was almost done and working as expected. Last thing I had to do was to provide some alerts to the runner when target pace changes during run so I have used 'Attention' demo code and copied&pasted some lines for vibration:

using Toybox.Attention as Attention;
var vibrateData = [
new Attention.VibeProfile( 25, 100 ),
new Attention.VibeProfile( 50, 100 ),
new Attention.VibeProfile( 75, 100 ),
new Attention.VibeProfile( 100, 100 ),
new Attention.VibeProfile( 75, 100 ),
new Attention.VibeProfile( 50, 100 ),
new Attention.VibeProfile( 25, 100 )
];

function initialize() {
...
DataField.initialize();

Attention.vibrate( vibrateData );
Ui.requestUpdate();
}


after I side uploaded binary watch started continous reset cycles ending up in "Garmin" welcome screen and going down again. Tried to upload older version but it doesn't come to the part where flashing interfaces are up so it wasn't possible. I only managed to turn it off permanently after I long pressed power button it shuts down after few cycles. Waking up again makes it to go into this reset cycles again.
Is there anything else I could do or I have to give it back to service? Am I going to be charged for that or it may be considred as not user's fault?

I already miss my watch :/

LR
  • I've brought my 920XT back from a similar state by:
    • Getting it in the Off State like you describe
    • Plugging it into the charging cradle which is connected to my PC
    • Turning the watch on while it's in the charging cradle and connected to the PC
  • I've brought my 920XT back from a similar state by:
    • Getting it in the Off State like you describe
    • Plugging it into the charging cradle which is connected to my PC
    • Turning the watch on while it's in the charging cradle and connected to the PC


    Not Quite Right

    I found my notes on this and apparently my memory isn't very good. The problem I had was on a Fenix3 and on a VivoActive and it's not quite the same as what you are seeing. None-the-less, hard resetting while on the cradle might be worth a try.

    Here are my notes as I wrote them.

    The 2 whole watch crashes yesterday on the Fenix 3 made the attached ERR_LOG.txt file. I don't know if this was related to the MO2Sensor crash or not.

    In both whole watch crashes, it just showed a Garmin logo. The watch was completely non-responsive until I held the power button down for 10 seconds. Then when I turned it back on, it just showed the Garmin logo and was still completely non-responsive. I left it this way for at least 3 minutes. In both cases, I did another 10 second power button hold and turned it back on and it was still unresponsive.

    I connected the watch to my PC by putting it in the USB cradle and did a 10 second power button hold with it in the cradle. Then it restarted and came up with the charging screen and was functional again.

    I have also observed this behavior on the VivoActive.

    I don't know the cause of the whole watch crashes, but it's generally occurred when I'm crashing ConnectIQ repeatedly while debugging a problem.
  • Ok so my case is slightly different with that it does not stay on Welcome screen, rather it goes down after few seconds and keeps resetting by itself. Although I've tried your way of recovery but it did not work for me.
    Anyway...
    Do you (or anybody else) have a clue of what might have went wrong? I definately would like to avoid this in the future. Could it be the line with screen update request in initialization function? It worked with no issues until I've added code for vibration.
  • Former Member
    Former Member over 8 years ago
    You should be able to reset your device by holding the two right buttons (start/lap) while powering the device on. After doing this, you should hear a tone. Once you have heard that tone, release the top (start) button while continuing to hold the lap button. You should hear a second tone. Once you have heard this tone, you can release the bottom (lap) button, and you device will be reset to the initial software configuration.

    I recommend removing the Attention code from your data field for now. I have created a ticket to investigate this issue.

    Also, FYI: Data Fields cannot request updates, and Ui.requestUpdate() has no effect in that app type.
  • Ok thank you very much. There are goods and bads. Good that it seems there is a way to reset device from such crash (thanks for tip), bad is that I will not be able to check it out as I've just sent device out to service - they said I'll get new one which really just confirms my good feelings about Garmin. (BTW this is my second watch).
    Also thank you for ticket submission - can I somehow follow it to see when I could go back to use Attention again?
    thx
    LR
  • What version of firmware is(was) on your watch? If it's 4.xx, that has a 1.2.x VM and Attention can't be used in data fields. (per the 1.2.x api doc)

    With the 5.xx (beta) versions of firmware, it's got a 1.3.x VM, and the 2.1.x api doc says it's now allowed in data fields, but I suspect that's only for 1.3.x and 2.1.x VMs.

    So trying to use it on a 1.2.x VM may have been the root of the problem. The watch crashed and when it comes back up it tries to restart the "run" or whatever with the data field and crashes again...

    this probably shouldn't cause a hard crash, but maybe it does,
  • It wasn't beta. I had 4.7 onboard.
  • It wasn't beta. I had 4.7 onboard.


    So it had the 1.2.x VM with doesn't allow Attention in data fields.. I think it should only cause a "IQ!" (CIQ crash), but it seems it caused a hard crash...
  • Could you pls point doc you mention? I've only found online documentation which says Attention is supported since 1.0.0 but it doesn't distinguish DataFields and others:
    https://developer.garmin.com/connect-iq/api-docs/
    thx
  • Right under "Since", it has "App Types" and only "widget" and (watch) "app" are listed (not watchfaces, not datafields).

    If you look at the doc for 2.1.0 (it's in the SDK) it adds "Data Fields" to "App Types" for this..