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

Battery fault not solely down to firmware

For what it's worth to people to know, it would seem that the commonly seen battery fault isn't the sole issue of the firmware. I have 2 vivoactive3 devices, one without issues and one with a battery fault. 

Now, the device without issues has some scratching to the display that the faulty one didn't, so I thought, seeing as they are both out of warranty anyway, I might as well do some experimenting. I disassembled both devices and found 2 things, firstly.the main PCB in the device is what holds the pairing/installed widgets information, this moved between watches when I changed them over, and secondly, the screen/display and it's potted PCB is where the issue lays with the battery!

No matter what combination of parts I reassembled the watchs with, the unit that got the "good" display, ALWAYS displayed the battery issue,  (24hrs tops)and my old natty display continued to get a good 4/5 days battery life.

Both devices got the same firmware installed to them, and both were tried with all swappable hardware to determine this.

My next step is to ask someone who might have a bit more knowledge on the hardware, is there any information that would be useful that is accessible either via PC connection or via the built in diagnostics, what would help determine what the hardware differences are between the 2 displays? I ask, as I'm sure the combination of hardware AND firmware is to blame! It might help Garmin find a solution perhaps?

  • I am not sure what you are asking, you can put the watch in test mode and it shows the firmware verisions of the watch, can't remember if it shows anything on the display, that is all I know. Secondly there is a usage.log in \Garmin\debug that might contain a hint. I think the only thing actually using power in the display is the backlight, but can't imagine why it would be so different. 

  • I suspect the possibility of different hardware on the board. I've seen similar issues in other products where PCBs/hardware has been revised where subsequent firmware causes issues on the older hardware

  • The test mode will tell you the firmware revision of the board I think, at least that is what it does on the VA3M. I notiiced that my revision did not have the problems some users reported with a previous one, so I guess I think you are on track there.