New release 18.2s with hardly any reported bug from the beta fixed.

I think I read that the public release is just a roll-up of all previous beta builds, so effectively it's the last beta (18.21?) - which are marked as release candidates anyway - re-released as public stable. So, nothing is going to be fixed 'extra' over the last beta. There's so many bugs they need ot pause it and stop adding stuff but take a long hard look at fixing the massive list of issues we're having.

All “beta” versions are marked as release candidates. Look at the announcement of the first 18.xx version. Or the versions before that. Release candidate means garmin thinks it’s of good enough quality. And the  a few people try it out and find a sh*tload of bugs. This can only mean, garmin didn’t test at all.

And I talk about all bugs found since the first 18.xx version. And also the ones found since version 4.xx. So many are still not solved.

I really think garmin developers are only allowed to spend a tiny bit of their time on bug fixes or software quality ingeneral.

They are forced to spend their time on something like a sleep coach, with tells me every day I have to sleep less and I have to sleep 7 hours 20 minutes. Even after a night I could only sleep for 4 hours and felt exhausted next day. It’s so ridiculous.

I don’t have a need for more bs function. I have a need for working basic features. Only today I did a bike ride with navigation. Auto zoom doesn’t work. The default zoom is to far out and if you adjust zoon it ignore that setting the moment you exit zoom mode. 

My previous watch, a forerunner 935 didn’t had so many problems. 

Agreed 100%. For me the Fenix line was super solid firmware wise. The 965 is like a sking on a Java app, janky, crashes, nothing works properly, nothing feels 'native', there's so many bugs it's a wonder how it shipped, nothing gets fixed apart from a mneu spelling or new pointless broken feature like Sleep, meanwhile my barometer is like a firework, up down up down, thus latitude is trash. Maps don't download, we get black screens on reboot introduced, maps not showing, meanwhile garbage inplementations of Sleep get added and immediately, rightly, slammed. Please, for our sanity and your brand, Garmin, halt the new stuff and fully fix the absolute ton of bugs we've reported. None of these should have reached beta let alone RC.

I was looking at the Epix line but now I'm checking out Suunto and Polar. I just can't waste more time on Garmin

This is so true! 

Every night my sleep has this gaps of 30-60 minutes and my every night my sleep shorter and everyday my metrics are off because of this. 

The HRV status is also soooo buggy. This gaps makes this feature so useless.... during 8 hours of sleep it measures only like 50 to 70% of HRV data the rest is empty..... 

I ask my self why I even wear this watch for my daily health. 

Only useful for sports nothing else unfortunately. And this for 650€...

It makes me wonder why people take Garmin readings as gospel - like so you're hrv is X, but are you sure? Sleep score is 95. Really? It's just so speicifically unreliable. I use the navigation part more than anything and it's an absolute shitshow, alerts not alerting, climb off, pace off, because I know what a disatance + pace per specific route is/are and it's not what Garmin says. I know they're not medical devices but there should be some degree of accuracy applied in the metrics otherwise a 5k PR is essentially to be taken with a boulder of salt.

Edit. I feel like I'm talking to a brick wall for @garmin here. Only when things are massively off are issues pointed out, so what about people taking their readings as read? No variance/error allowance? Because as all Garmin's it's taken as exact when really esp without a hrm it's as good as Garmin can do, but I keep seeing posts about 100 sleep score or other report and think really it's statistically just error because the data is so impared. /rant

Its not about things being off. It's about things don't work. Look at my HRV status: gaps everywhere. 

My sleep also has gaps? How is this

possible? 

Bonkers! I disabled all the hrm etc. due to not wanting it, not wanting the battery hit, and finding it so inaccurate - I mean, what does anyone have to realy compare it to at a medical-level? These disjoints are ridiculous. Have you the band tight enough? <-- I hate these quetions as really they nailed this in the previous FR, Ep, and F devices yet on this flaky device it's trash.

So how can anyone really say for eg the peak/trough is anything but an error? Unreliable , false accuracy, and deceptive data. I just don't know where to turn, epix or fenix or Suunto? Just what's the point in all of this specific data if it's unreliable at best, gapless at worst, or otherwise wrong?

I tried different bands. I tried different tightness of strap adjustment. I have already a second watch from Garmin bc if this problem...

How can a sleep stage be from deep sleep to "not measurable"  and then 30 minutes nothing and then sleep again? 

There should be a code in the sleeptracking that this never happens, bc it's more inaccurate then choosing a wrong sleep stage for the watch. 

So easy things not working. Even a 40€ band can make my sleep duration better than this watch. Bc there are not this bugs. 

Exactly. I wish there was a 'report error/ where we could say, 'Hey, Garmin, this ain't right, here's my log' and point out what;s wrong and supply a log/data upload. As I keep banging on about, for me it's the barometer, for you sleep, for also me navigation/compass, but how many others are relying on their Garmin data as lore rather than imo a reading+fault+error+guess=score. Please, @Garmin, fix all the basic stuff and build on that, because currently there's no reliability to ground the data as the more you look the morewildly  inaccurate the data becomes.

The thing is it all seems fine and accurate until you really dig and check the data, then its the wild west as far as accuracy is concerned. These data are taken as gospel and imo are best guesses at best; at worst they're plain wrong. I'd recall the 965 and fix it.