Getting Low Battery warning when plugging into AC adapter and watch won't charge Part 2

Referencing this locked thread:

forums.garmin.com/.../1310011

While the hard reset seems to have worked for awhile, my Instinct started giving that error again when plugging it in. So I just performed the Factor Master Reset, and we'll see how that goes.

-John

  • I started getting the same issue after upgrading to v14.40 (but I skipped a couple versions so I can't confirm it was introduced in v14.40). It happens when plugging it in with 2 or fewer bars, and it will not charge. If I keep trying it will eventually start charging.

    I haven't tried on the latest version yet. There are too many cases of basic functionality breaking with an upgrade, so I like to upgrade only when something has been in use for a while with no reported issues.

  • Scott, I'm on version 16.00. But yeah, 2 or fewer bars and I've got that problem. It does eventually charge, but it seems as if I need to get the cable just right. Still not sure if it's hardware or software, but seeming more like software.

  • I had this so bought a new charging cable which sorted it out for a few months.  Then I started experiencing the same with the new cable.  Instead of buying a new cable I just squeezed the outside connector with a small pliers so it gives a good clunk when connecting to the watch and this seems to be the fix.  I just think the cable gets loose after a while.

  • FWIW, I'm having the same issue with two cables, one of which is less than a year old. And both cables work fine on the wife's watch. Physical cable issue also doesn't really explain how it only happens down in the 2-bar range and with a higher charge

  • The information provided in the original now locked thread conversation remains the same. I am sorry you continue to have a charging issue. Your troubleshooting has been thorough and there are no more steps that can be tried.

    Please reach out to Outdoor Product Support. We will be happy to assist you further. Thank you.

  • thanks Chris. It does seems to be working now after the Factory Reset, but I'll give it a few more cycles to make sure.

    Reason for reopening the thread was to note that the hard reset didn't fix the issue even tho it appeared to at first, in case anyone else sees a similar issue.

    If it happens again I'll contact support.

    Thanks.