My battery level ist stuck at 15% since approx. 8 hours of operation in smartwatch mode. Never had such an issue before. Firmware version 4.64. I'll keep on observing that bug...
Same issue for me... stuck on 59%. Any workarounds? I installed a battery widget but it just shows the same ...
Since i bought the 5 plus i have the same issue. When i am done charging the Fenix i always turn it off and on again otherwise the battery level does not do anything.....huge bug in the software of this watch. How can a watch with this price have such poor software? The bugs keep on coming in this watch.
They know about the broken fuel gauge but have not done anything about it, as I have reported it several months ago shortly after launch and many people in the battery life thread confirm it. Also, it turns out 88% is actually 100% on the battery meter.
I will resend the data to Garmin, but it is easily reproduced as I had 3 units (one of which was returned due to a button defect, and another of a relative) and they all behave the same, when you charge to 77% it will run for 3 days without the battery level moving from 77%.
Hmmm not sure if this will work for anyone else but instead of rebooting the watch turn the power off completely. Leave for a minute then power back on.
My battery ‘had been stuck’ at 59% then...
88% at 05.43 86% at 09.32 85% at 10.34 84% at 11.45 83% at 13.13 81% at 17.02 80% at 19.09 79% at 23.21
- Bluetooth/phone connection off - No activities done today - occasional skipping through the menus but little use otherwise - no music played
Turned off and on at 05.40 which reset battery % from 59% to 88%
Everyone, we are still looking into this here at Garmin but we are having a hard time reproducing it in house. If anyone can provide me with the steps on how to reproduce what you are experence, I would be happy to try it myself and even pass it on.
Everyone, we are still looking into this here at Garmin but we are having a hard time reproducing it in house. If anyone can provide me with the steps on how to reproduce what you are experence, I would be happy to try it myself and even pass it on.
Just try to charge until 100% and leave it plugged for another 1 or 2 hours, than unplug it an see how long it lasts sticked at 100%. Another bug can be reproduced charging the watch until 100% than reboot it: it will drop to 94 or 93%.
renton82 I have tried to do it that way and no luck. What are you plugging your device into to charge it? Computer, PC or Mac? USB 1,2,3..? Or if you are plugging it into a wall charger, which type, what is the voltage.
What I'm trying to do with all these questions is to figure out what is the key fact I am missing. Plus not everyone is experiencing this too, and the devices I bring in with this issue I can not reproduce here. So, everyone, I'm listening to you, and I care, but can some of you try to give me any small detail that you can think of that might cause your device in front of you be different than mine or someone else that is not seeing this?
Everyone, we are still looking into this here at Garmin but we are having a hard time reproducing it in house. If anyone can provide me with the steps on how to reproduce what you are experence, I would be happy to try it myself and even pass it on.
Why don't you parse through your code and algorithm again in a bigger team of developers and track down the bug instead of waiting for reproducability? The bug is there! Don't just waste time, siting there helplessly waiting untill you see it too. Read your sourcecode again - it's there, nowhere else!!!
I'm pretty sure he's a product support guy, not a software developer. Getting a big group of engineers to dig through all the code in the hopes of finding a bug is a pretty poor way to find a bug. If you can't reproduce it regularly, is it really a bug? Also, the fact that they are getting watches returned for this "Issue", and then they can't reproduce it on those units, makes it suspiciously like a hardware/environment/use bug rather than a pure coding error. The first step in any troubleshooting or maintenance action is always to "verify the fault".
