Fenix 5X - 7.02 Beta Release

That is why it is also called beta

What value did this comment add?

A beta is provided so Garmin, and the community, can get feedback on issues.

Not aware of my Spartan or Ambit doing all that & they seem to manage much better.

My Casio F20 tries to do some of that via internet stuff & it doesn't really help.

(SSUMAB: I wouldn't quote Mark but I have to because the "@" gives the JSON2 error so, no other choice)

Of course Suunto has the upper hand because of manufacturing AND quality choices on hardware before the design phase even begins. In that case Suunto manages a lot better so if we want Garmin to beat it or at least equalize, the Prj. Lead needs to take radical choices and overturn choices that for the location and cheaper production costs produced bad results (or by the very least inferior to the expectations for a 750€ worth device) from the start (of the F3, not even the F5!).

The Wi-Fi locations can give the position to the GPS AND access to the local weather stations (i.e. once I set the weather stations on ST3 Weather Plugin, 90% ping positive, 10% don't answer but those that do give the exact wind, humidity and pressure). This stuff, inserted into the baro calculation would dramatically change things for the better for us).

It's basically countering what I see every day: loaded on 149m go back to 0 when I get to sea level. 10 minutes later I am back at 149 and I read 158. That's basically a 10m offset in just bare 10 minutes: not enough to have such a dramatic change in physical data... and it always happens, with any weather. The baro MAY be flawed but the calculations surely are and that's where the internet can help. Let's just stop forgetting there's more cell phones on the planet than living people right now and a guy who gets a 750€ watch surely doesn't own a Motorola 8700... he owns at the very least a compatible (BLE protocols) smart phone.

You know what makes me mad... it's that not only do we have the technlogy (it's been there for years) but that year after year they push out a new model and KEEP being defeated. Like... alright we've got thousands of users with great ideas, let's not give a damn about them.

The same I'm saying about the baro can be used for the GPS where probably it's a lot more needed (let's patent the EXO/chip again, who cares if we have 500 pages of complaints about GPS accuracy, right?). The cell phone antenna is tenfold compared to the Exo antenna (and I'm not talking just about giving INSTANT LOCK on the sats but actual better accuracy).

The engineers are very capable of making this happen: there is no equal counterpart for our dst accrual algorithm. They really saved the day back then with it and it hasn't been beaten yet (nor I think it can ever be). So, we have the tech, we have the guys all we need is that choice. There's no need to wait for the Fenix6 to be beaten again by Suunto: if they don't make the right choices NOW they will surely be beaten again, like it's happened REGULARLY in the past (in these 2 compartments).

With no changes in setup (mobile phone, apps, etc) besides going from 7.00 to 7.02 BT sync after activity takes forever.
Was pretty quick on beta 7.00

The swimming pool app bug is still here but i have discover that the bug starts when you customize swimming pool app (data field or pages) i resume however in what consist:" if you leave default setting in swimming pool app, the lengths count works normally, but if you customize data field or add/remove pages, the lengths count start to go crazy: for example, if you swim 2 lengths the watch report 25m (1 length) until u will press lap or stop than magically the lengths became 2! It's very annoying since you can't trust in lengths count until you have finished a repeated..."