First run with firmware 3.90 and...

Yesterday I received new fw v3.90 and it seems there is something really wrong with battery consumption: I charged watch before to go to sleep so when I went to bed I had 100% charged and this morning I found at 10% and after 20min watch was completely discharged... Does anyone have same problem?

Generally with two GPS run of 90mins and other activities I was able to use watch for 8 days approx

Definitely something is wrong on fw 3.90

You know GPS was not updated in this firmware...

For me, with it, riding bikes, comparing to other Garmin/Strava users, everything is fine.

The problema Is that the watch completely discharged during the night from 100% to 0% while I was sleeping and no activities were active....

There was a GPS update together also!

And the altimeter is not GPS dependant...

My first run with 3.9FW took 25 mins for a GPS lock and didn't really lock.  My pace and distance was wild during the run.  According to Garmin I did a combination of sprint, walk, stop and teleporting.  I really hope they fix this one quick.  GPS/HR mess ups are not good for a $800 GPS/HR watch.  

sdantasbvi said:

And the altimeter is not GPS dependant...

Did you calibrate both the altimeter and barometer prior to your run?  What was the pressure reading at start and finish?  Your graph looks like your barometer had a steady decline in pressure.  If your barometer was off at the start, this is what would be expected on a flat surface as it's correcting itself during your run and the watch "thinks" the change in pressure is because you're running uphill.

CaptDisaster said:

My first run with 3.9FW took 25 mins for a GPS lock and didn't really lock. 

There’s your problem right there, Not Garmin’s fault, yours. If you don’t get a good lock before you start then it won’t work as intended. Question is why did it take so long to get a lock? New watch? Not synced to GCM or GE? There’s a file in the REMOTESW folder called CPE.bin. This needs updating regularly as it holds the positions of the satellites to enable a quick lock. If that’s out of date it can take some time to get a lock.

But if you don’t have a good lock on satellites BEFORE you start, there’s nothing Garmin can do for you.

I have been using this watch for many months with little issue on the GPS lock.   The only change was the firmware. Since that run it still takes a lot more time for a fix.  The only conclusion i can think of is that they made a change to the GPS and it seems that others might be similar boat.  There may be an issue here.  

For my situation i should be a bit more clearer.  I started with 45 mins of tinkering to get a fix prior to my run, turned off and on a couple times.   Then i got a "fix" notification and started running .   25 mins into my run it beeped again saying i got a fix again.  Throughout the run was terrible pace and distance data.  I can only conclude it never got a decent fix in the first place.  To also note it was a sunny day on a hill, and I was in a clear building free area where i have run for years without an issue on GPS fix.  

Do you know for certain that your CPE.bin file is current? Go to System, About and click right through to the end. What do you see? 

CaptDisaster said:

For my situation i should be a bit more clearer. 

Yes that always helps. Have you tried getting a fix subsequently? Was it any faster?