Fenix 6 Series - 17.73 Public Beta

I'll dig through some more. There's some correlation, we just have to find it!

You can tell I used to work in IT Support. I'm used to trying to pare away all the obviously wrong things to find the possible right ones :) :) 

Right I'll leave it here not to block this up any further but is this any use?

http://www.mygpsfiles.com/app/

It looks like you can load the GPX and the FIT into it and compare them directly?

6928399 said:

Garmin, looks like the battery drain issue was introduced with the 17.72 beta. I charged my 6s pro solar on Friday evening. Now it's Monday evening, about the same time. I have two days left, or 6 hrs of gps activity. Thus that's just 3 days and about 7 hours of GPS activity recorded. No pulse oxy, no music, bluetooth to minimum, no wifi, no vibrate, messages, other stuff that drains the battery, battery safer during night. Thus when I go on my long run tomorrow evening I probably have to recharge the watch beforehand, if it doesn't die at night.

Isn't that pretty normal, though?

A 6S only gets 9 days in smartwatch mode, or 25 hours of GPS. So logically if you use 7 hours of GPS (30% of the battery), you'll have about 6 days of battery remaining for smartwatch mode. You already used 3 of those days, so you should have about 3 days left, mathematically. And you're saying it's showing you've got 2 days left, so that's pretty close.

Hrm belt still disconnecting if I "disconnect " phone in  power manager. 

It's strange how you and others have this repeatable discrepancy, but others don't at all.  I brought a calibrated measuring wheel home from work to measure a fence line I need to do on my property.  I decided to try it on a walk in my neighborhood.  Too hot today to run and I figured the wheel would lose contact on the ground while running.  Anyway, watch on my left wrist, wheel in my right hand.  My development is surrounded by huge Fir and Cedar trees and for a good portion (35-40%) of the walk I was within 100-150 yards from them. GPS only. Max elevation 479 feet, minimum 464.  Watch measured 2.53 miles and the wheel measured just shy of 2.55.  I don't use anything like Strava, so I don't know if the discrepancy has anything to do with their calculations.  I don't know about pace as I use power with my Stryd and don't even have pace as a datafield. 

I get what you say. But I'd normally get 6 days with about 1hr of gps activity out of it. I did most of this activity time in Saturday, and pretty much nothing (few minutes here and there) on Sunday and today. This is where the remaining time plummeted.

I've created another thread where I've loaded the FIT and GPX into basecamp to compare directly. There's some elevation difference (quite a bit) and I THINK if I remember correctly exporting a GPX locks the track to the DEM model but I am trying to find where I read that

It's really strange! I only ran a slow 1763m today. Well, that's what I thougth, as the watch only gave me 1700m total. That's a difference of 63m over such a tiny distance. Yes, it's 'only' about 4%, but the influence on pace is massive. I have the correct length of the street from a building project. I'm sure the watch is wrong. When down- and reuploading the GPX I get 1730m. That's somewhat better, but again I've lost all the additional information.So what good is a sports watch that doesn't show additional information? And yeah, the odd breaks in pace are present in both the original and the reuploaded file, though exaggerated in the reupload

original

reupload

Which actually makes me wonder... do we have to deal with this *** because Garmin can't find a way to fix the gaps in the pace display? Thus the solution is to smooth it to bits and get a nice-looking graph with *** pace/distance just for visual representation?