I own a Fenix 6S Pro since February 2021. Overall, it's been a good experience, but not great. Sadly, I find that the GPS is still quite inaccurate after so many updates down the line, which IMO is the main selling point for a Fenix watch.
This is what my post is about, actually.
I'm still on FW 24.10 (more on this later). I went to ski for a week in late March, and noticed that the battery would not last for two days of activity. Every day, I would charge the watch to 100% before going to sleep, wake up with about 90-95% battery (I noticed a bit of drain during the first 1-2 hours after unplugging the watch from the charger), and then go for what is almost a "full ski day", meaning from around 8.30-9.00 AM and until 4.00 PM. This means around 7 hours of GPS-on time, give or take. After returning to the hotel, my battery would be around 45-50%, every single day. This means that the watch would not "survive" until the end of the next day. So I had to charge it again. Every single day, same story. Disappointing.
When I'm not using the GPS, but have BT enabled and connected, my watch would last for around 6 days, which I find about normal for my 6S Pro. So the GPS is the main issue for me.
So what do I think happened here? Garmin saw that the GPS is inaccurate and tried to optimize the SW around it as much as possible. They've been doing this with almost every single new major FW release, and is to be admired, honestly. But this in turn lead to more battery drain (perhaps due to additional computations made on-the-fly in order to correct for the inaccurate GPS), which I think is now "addressed" in the new FW - if a bit too aggressively.
Overall, FW 25.xx has proven to be a complete fiasco. I usually wait for a week or two on my "old" FW, after the new FW version has been offered for upgrade, and this attitude has proven to be perhaps life-saving for my 6S Pro, given the experience some forum members have been through with the newest 25.xx branch.
I think we can all call it a day for the Fenix 6 series. Garmin tried and tried, but there is only this much they can work around an inherently inaccurate GPS chip. One thing is bad though: the quality control on SW updates leaves a lot to be desired. Garmin should look at the whole FW 25.xx (starting with the still "stable" 25.10 which is still a mess, IMHO) and ensure that nothing like this happens again.
Cheers to all!
- sorry, English is not my first language