This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Shot down icon on the screen after shot down procedure

Former Member
Former Member

After updating to 8.00 I have the problem that when I do the shot down procedure (left key+soft key shotdown) the 1030 does not shot down completely as before. It stays online with a shotdown icon on the screen and keeps draining the battery.

Do you have any suggestions of how to solve this ?

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    Garmin support found a fix for me...I removed my SD card and restarted...worked a treat and then popped the card back in with no further issues :-)

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    No SD card fitted

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    ...god damn it :-( ...maybe one for Garmin's live chat, they're pretty good!

  • Former Member
    No SD card fitted

    In my experience, not-switching-off-issue indicates a file error.

    If you have no SD card inserted, i suggest to delete (backup on PC) all activity-files and all course-files.

  • Former Member
    0 Former Member over 5 years ago in reply to mcinner1

    Unrelated to any activity. It'll fail to properly shutdown at times  just turning on then off. 

    Never used to only after a past V8 FW update. Gone through the backup device reset process as I hadn't done that since new. Still the same but not every time it's shut down. Just have to make sure it's properly shut done each time other wise your greeted with a flat battery when you go to use it. 

  • Same issue here using FW 8.0 and 8.08 - it never happened previously. I've turned off the device and not noticed it froze on the shutdown screen. The next time I went to use the device it was at 0% battery. I assume it sat there and drained the battery.

    Looks like 8.11 is available but the release notes don't mention this issue. I'll update to see if there are any improvements though.