Firmware 4.3

Now, I wonder who to blame "Drink" or "Update 4.3".. :confused:

I just checked, my RHR for last night (a good night's sleep at that) was 72. That's high for me too. I'll have to check tomorrow.

Mine RHR shot up to 74 after the update. Initially, I was confused as I had a drink (very small quantity) just after the update and when I woke (slept for 3 hours), the RHR was showing 74 (mine is usually between 44-55). next day ran for an hour, had proper sleep and food. And now it came down to 54. But, it scared me, as i thought that small drink (I drink once or twice a year only) cause the spike in RHR.

Now, I wonder who to blame "Drink" or "Update 4.3".. :confused:

haha - quite a coincidence I had updated mine to 4.3 and had 4 pints of beer after a long break that evening. Found it at 75-80 at midnight too and was worried the next morning (its usually around 60 at sleep).

But then I was reminded that RHR in 235 is really meh with its infrequent polling. I see polling as low as once in 2 hours when asleep. I am contemplating using the 235 just for runs and maybe get the scosche for heart rate tracking. I think garmin should just give up on its tryst with OHR.

Now, I wonder who to blame "Drink" or "Update 4.3".. :confused:

Definitely the update. I too got a bit of a fright. 3 weeks before Comrades, I was terrified I was coming down with something major. Glad its not just me.

Garmin OHR is just a toy

I am not updating my Garmin 235. Each update cause bugs. Garmin dev team are really sucks
Can't believe that a 350$ product can be such a buggy.

All the problems with the RHR are very annoying and frustrating that they can't seem to get it right, but I cannot believe that after the update to 4.30 my HR still doesn't start tracking at the beginning of a workout. On my 45 minute run today it took 4:21 before it started recording a HR. I started seeing this problem with 4.20 and thought for sure that would be a priority to fix in the next update, but apparently I was wrong. One thing that this completely breaks is VO2 Max. How can it be accurate when your HR over a run is skewed by having several minutes with effectively no HR. I hate to call out developers and engineers, but it seems like things just keep getting worse instead of better.

Mine RHR shot up to 74 after the update. Initially, I was confused as I had a drink (very small quantity) just after the update and when I woke (slept for 3 hours), the RHR was showing 74 (mine is usually between 44-55). next day ran for an hour, had proper sleep and food. And now it came down to 54. But, it scared me, as i thought that small drink (I drink once or twice a year only) cause the spike in RHR.

Now, I wonder who to blame "Drink" or "Update 4.3".. :confused:

Mine was 70 too! I updated mine later in the evening (10pm). After the update it restarted and my RHR was 70 (usually 55) ... incidentally, the same as my HR at the time. My HR stayed around 70 until that day ended (midnight). My belief is that when it restarted it grabbed my current HR and used that as my RHR. I've seen this happen before, each week in fact. I usually charge my watch via USB on Sun evenings and each time I put it back on, my RHR is way off (way high).

Max

Forerunner 235 /w 4.30 crashed during my 10k race

It was the first race in my life, started watch by first switching to HR widget for a few minutes, then run and start, seems had a good HR lock on "Runner HUD"( 5 starts by the way).
The built in running app crashed and watch rebooted after about 1 minute my wave have passed the gate. I was surprised it then asked me if I want to resume the activity. I said yes, had no problem for the rest of the race. Lost about 1 minute tracking however.

Well, to me , expressing hate has no use, frustration might help a bit but not a lot, we all on same boat, like it or not, I'm not ready to discard my 500 dollar watch yet. so I did a factory reset and re-pairing, re-setup and everything this morning, now I'm running the watch with 0 Connect IQ app, smart notification off, for now.
I will post my experience later.

I have a few suggestions for Gamin and owners.

If we can make it the firmware upgrade optional. This would help a lot, at least when a newer version is out. This would gives us a few days to see how well it goes for whose who are willing to update. But right now, each time there is a newer firmware, it gets automatically uploaded to the watch, and asks me if I want to upgrade, please, at least make "No" as default. A "Do you want to upgrade" check box in Garmin Express would be ideal.

Please provide a way to back up/restore data from the watch, so that we can do a factory reset after a firmware upgrade. If you have played with routers long enough, you probably have already known that factory reset is always suggested. We can do a reset now, but not lossless. I lost all my history data after that.

Garmin, I do think you guys need do more tests, I feel being treated as beta tester. If there can be some beta program to sign up. Rolling firmware to release only when major bugs reported by beta tester have been resolved. I'm sure we all will benefit. The "Check for beta software" link on product page links me to the general software download page. I didn't see a beta program to sign up.

Make version rollback official. I would like to see a note, posted on support page, step by step, guide us to revert the firmware to previous versions if I choose.

Sincerely hope we have a better next version.

Have you guys tried turning off the HR momentarily to let it reset? When mine stays in the stratosphere for an extended period, that seems to put it back in the reasonable ballpark. Just turn the HR off, wait a few beats, then turn back on. Might not work for you, but worth a try.

Mine was 70 too! I updated mine later in the evening (10pm). After the update it restarted and my RHR was 70 (usually 55) ... incidentally, the same as my HR at the time. My HR stayed around 70 until that day ended (midnight). My belief is that when it restarted it grabbed my current HR and used that as my RHR. I've seen this happen before, each week in fact. I usually charge my watch via USB on Sun evenings and each time I put it back on, my RHR is way off (way high).

Max

I woke up this morning and synced my watch on my computer. My RHR was 51 from the night before. I then updated to 4.3. While downloading, I was thinking to myself "What's this update going to screw up?" Garmin never fails to disappoint. My RHR and the 7 day graph now show 70 for the day. I can't wait to see what 4.4 is going to mess up!

Mine was 70 too! I updated mine later in the evening (10pm). After the update it restarted and my RHR was 70 (usually 55) ... incidentally, the same as my HR at the time. My HR stayed around 70 until that day ended (midnight). My belief is that when it restarted it grabbed my current HR and used that as my RHR. I've seen this happen before, each week in fact. I usually charge my watch via USB on Sun evenings and each time I put it back on, my RHR is way off (way high).

I was thinking to myself "What's this update going to screw up?" Garmin never fails to disappoint. My RHR and the 7 day graph now show 70 for the day. I can't wait to see what 4.4 is going to mess up!

Nothing is messed up, it just doesn't have the immediate widget data history. The firmware updates effectively erases the onboard history of RHR which is mostly just a temporary storage value for that widget.... After the update, your RHR is whatever low value you have when it first boots up, at least until you're resting enough for it to get a good RHR reading.