Firmware 4.3

My feeling is that firmwares for initial launches of devices are prepared by one dev team and updates of firmwares are done by second one. And the second team is lame or there isn't proper communication between both of them. Thats my only explanation why Garmin still selling devices and they are not working how they should in real life...

Garmin just released ANOTHER fitness device. The Vivosmart HR+. Come on Garmin. People are clearly still having issues with their current, more expensive devices. I'm someone who always installs the latest updates with any of my electronics but now even I'm reluctant to install 4.3.

Last running. Something like 'half cadence lock':

https://connect.garmin.com/modern/activity/1167726047

4.3 is no good. Before it I had no problems at all.

Now that's a weird one... Haven't seen that before.

For me the 4.3 seems to really have improved things fortunately, hardly any cadence lock issues and hr seems way more realistic now. Also no strange spikes/readings most of the time.

That said, today the cadence lock appeared again only to disappear after tightening the watch by one more notch (thought it was pretty tight already). Something I'll keep an eye on the next times it may occur again...

I took my replacement 235 (sent my "broken" one back a few weeks ago) for a long run over the weekend and the results for me were pretty good. Not perfect, but probably as good as I would expect for an optical HRM; certainly in line with my Rhythm+ strap.

I got the watch to lock onto my heart rate after 20 seconds or so, then started my run. I ran for 12.5 miles at my long distance pace (7:50ish min/mile). I was expecting my heart rate to be around 150 for the first part of the run, then gradually creep up to upper 160's and stay there. It ended up creeping up to low 170's, but I was tired and the weather was hot, so the conditions were probably the reason for my higher than normal heart rate.

The two dips in the attached heart rate graph were stops at a water fountain.

The only anomalies (from my untrained eye) are:
1. Minor drop out around the 8:00 minute mark.
2. Cadence lock around the 17:00 minute mark.
3. Possible* cadence lock around the 55:00 minute mark.
4. Possible* cadence lock in the last few minutes of the run, although it's hard to tell because I was slowing down my pace for a cool-down, and my cadence was dropping below 180 while my heart rate stayed in the low 170's (according to the watch).

If the HRM continues to perform at this level or slightly better, I'll be happy. I consider myself one of the lucky ones at this point.

Blaaaah

I've had terrible luck with both the 4.2/2.6 firmware and the 4.3/2.6 combination. Specifically, the OHR drop out for extended periods of time. I've tried the usual Soft and Hard Resets, Defaults, etc. Garmin sent me a replacement 235 for my first unit and the replacement did the exact same thing on its first outing from the box. It had 3.6 from the factory - I wish I had tried not applying any updates. Prior to 4.2 the device at least worked consistently for me. I've contact Garmin again about the replacement unit not performing - it took some doing to finally talk to a supervisor. I'm sending the replacement unit back and the supervisor assisted me in upgrading to a 735 due to some extenuating circumstances. I'm more optimistic about the 735 working than trying another 235 that I've had two already. In the meantime, I've gone back to the 225 that's always worked very well for me. I wish Garmin would fix the 235 since I technically have/had two of them - my wife has a 235 that she hasn't noticed freeze yet. A side note there - both my black/grey 235 have had the OHR freeze. The wife's purple version hasn't. I wonder if they are different production runs? Just a random theory....

I haven't had this much trouble with a gadget since the UP24. I'm a long time FitBit convert on activity trackers. I hope Garmin starts fixing problems before I turn into a Suunto convert too.

Man, I wish Garmin had never issued this update. Apart from rebooting and losing HRM data a thousand times a day, my FR235 froze tonight for hours, so i wasn't even able to use it for simply seeing what time it is. I have never seen this before.
Fortunately i was able to reboot the watch by holding the power button for a long time.. Because of course, if you want it to reboot, it doesn't, whereas it reboots continuously if you don't want it to. Please give me back 4.2!

Hi,
It seems my VO2 max is no more sync. with GC using fw 4.3.
I did a run yesterday, my vo2 max increased from 55 to 56. On the watch, it's display 56 but always 55 on the phone and there is no dot on vo2 Max for this day...
All other information are well sync.

Is anyone have the same issue ?

Thanks.

Yes, I did, even a few days before the update. After the update the bluetooth is no longer working for pairing with connect mobile?! ....

These are the problems I have noted since the 4.3 update:
RHR is just wrong this feature no long accurately records a reasonable value when considering the heart rate readings being taken.
VO2 max does not update in Garmin connect (Fortunately this is convenient considering the last inaccurate VO2 max reading taken)
The watch has taken a VO2 max reading moving me from 53 to 45 (and I took a run with the GPS turned off?). It now say I need 48 mins to run 10k when my best time on the treadmill is 42minutes?

Please Garmin make this work again. I have specifically registered with the forum so I can voice my concerns with this new firmware update. Hopefully my next post will be more positive.