FW 5.00 issues

I have seen no such issues on 5.0 yet. If anything quite the opposite, the phone and watch ‘Snap’ together very solidly after being apart.
In the past I have seen a few times where the watch and Garmin Connect on iPhone would not connect. For me, this seems to be more of an iOS issue, since the fix would be to switch off Bluetooth on the phone, and switch it back on, then the watch would connect.

Went for a run, swim and walk yesterday. All activities were started by me and all tracked accurately.
Seems you always get the bad-deal Forerunner. But as it is only 48 hours after getting 5.0, so let’s see.

I had to kill the IOS app and restart it because the watch and phone stopped synchronizing. I could not even force a synchronize from the phone. After that, everything has been fine. I have experienced this a few times before, and I don't know if it was related to firmware 5.00 this time.

5.0 did nothting good for me. yesterday i took my fenix 5s plus out of the drawer of my nightstand after two weeks, updated to firmware 5.0 to only find out: sleep detection is still the lousiest in market. you get up and the sleep timer just continued to count. in the afternoon it told me that i slept for over 12 hours and have been 4 hours awake. stupid thing. the problem with virtual partner ist still not solved. i will stay with my fitbit ionic and did put the fenix back into the drawer. I think i will try to sell it for 600 €, I am sick of this lousy, overly expensive product.

So far, 5.0 has not caused any problems for my 5S Plus except during the upgrade process. Activities seem to work fine, GPS seems accurate, sleep is accurate, and HR also seems accurate. The new music player is easier to use while doing an activity. Connection with bluetooth headphones also continues to be good. Battery life remains at about 3.5 days which includes two 45 minute activities using GPS & music.

5.0 did nothting good for me. yesterday i took my fenix 5s plus out of the drawer of my nightstand after two weeks, updated to firmware 5.0 to only find out: sleep detection is still the lousiest in market. you get up and the sleep timer just continued to count. in the afternoon it told me that i slept for over 12 hours and have been 4 hours awake. stupid thing. the problem with virtual partner ist still not solved. i will stay with my fitbit ionic and did put the fenix back into the drawer. I think i will try to sell it for 600 €, I am sick of this lousy, overly expensive product.

I encountered this sleep issue with 5X Plus. However, using 5 Plus APAC with 4.2 firmware, i found that it has the best sleep detection. It can detect when i really woke up and when i only woke up to go to toilet. But during my time with 5X Plus, i did encounter horrible sleep tracking which i complained in this forum too.. However, 5 plus APAC has so far behaved very well. Even its beta feature (auto-reps in strength app) works very well.

Other issues to add:

- Wifi upload is completely broken (activity was not uploaded).
- Battery fuel gauge still horribly useless
- Sleep tracking still horrible, one night it works, another it shows 14+ hours of sleep
- Altitude drifts magically, I went to sleep at 104 meters and woke up without moving at 91 meters. I didn't know my house sank 13 meters in 7 hours.

I get the impression that the Garmin development team doesn't use these products or they are horribly incompetent.

As I bought from an amazing retailer, I have a very long time to return for a full refund, but I am still hoping they can fix it.

- Wifi upload is completely broken (activity was not uploaded).
- Battery fuel gauge still horribly useless....

- Altitude drifts magically,

Not magic. Physics.

The air pressure at your location changed during the night.

You can expect the watch to measure the air pressure correctly at all times - and it probably does.

You cannot expect the watch to translate the measured air pressure to an exact altitude at all times, since the relationship between air pressure and altitude is a moving target. The watch will need frequent calibration of the altimeter to keep track of this moving target. This is how a barometric altimeter works.

Not magic. Physics.

The air pressure at your location changed during the night.

You can expect the watch to measure the air pressure correctly at all times - and it probably does.

You cannot expect the watch to translate the measured air pressure to an exact altitude at all times, since the relationship between air pressure and altitude is a moving target. The watch will need frequent calibration of the altimeter to keep track of this moving target. This is how a barometric altimeter works.

Yes, I understand this, however the watch is only supposed to change the altitude during times when movement is detected, if the watch is in sleep mode or it is completely stationary the altimeter should be locked at a given altitude regardless of any pressure changes which are reflected in the barometer. This is why we have 3 modes for the barometric altimeter, auto, barometer and altimeter. When there is movement it attributes pressure changes to changes in altitude. When it is stationary it is simply a barometer and pressure changes don't have an effect on altitude. That would be auto mode, the others are self explanatory.

Hopefully I have clarified the expected behavior and why I believe that it's a bug.