945 Latest Firmware Bugs, Issues and Missing Features

I'm on 2.30 sensor hub now. Was on 2.32 before, but rolled back the watch firmware because of the problems I had with all day OHR.

I've reproduced the all-day tracking problem combined with cycling twice today. During the first 10 minutes of a bike ride OHR stays around 85, I then start a cycling activity and immediately the OHR in the activity goes way up. Then I stop the activity and the all-day tracking stays accurate (as far as OHR / cycling can be) for the remaining 30 minutes (at around 130-140 bpm). It's like the all-day tracking is 'asleep' and doesn't register the rise in heart rate or activity when cycling and has to be 'woken up' manually. Battery preserving mode thats too strict? I think this is clearly a bug.

How did you roll back the sensorhub!? My watch shipped with 2.32 and I wonder if thatswhy the pulse ox doesn't work (some seem to have the issue with 2.30 so maybe not?). Worth a go. 

I reinstalled 2.50 firmware and sensor hub 2.20, that came with the 2.64 beta. Download and instructions can be found in the thread. Then I installed 2.70 and sensor hub 2.30 was installed at the same time.

Your watch will be reset to factory settings though.

AN update from my end - so I ended up doing the same workouts on August 13th and 16th (added a few extra sets today but otherwise at the same pace, weights, same time of the day, similar sleep/food intake prior) and the comparisons are ridiculous. As you can see August 16 OHR is a lot more choppier (something I've observed today when the HR magically drops off the cliff and climbs in a sec) and much much lower. Also realized that while doing some wrist curls the HR magically jumped over 140bpm (for the first time in the day today) which made no sense to me.

I tried deleting the Activity, Monitor, New files folder as suggested y the CS rep in the chat yesterday but it didn't help this morning at all. This is disappointing given I try to compete against myself and looking at ridiculous stats is such a drag when you know you're close to dropping on the floor.

I suppose the next step is for me to try and do a manual restore to an older version.

I hope someone from Garmin is looking at this and realizing there might be an issue with 2.70.

Added to the first post.

2.70: Seems speed value is not being recorded in the FIT data file for runs - tried GPS and footpod as source with the same results

2.70. osm map. Track builded in Basecamp, transfered via garmin explore.. Didnt happen on 2.60.

1) When navigating on track, even i am on track i got 0m (it should be distance to end, or distance to track)

2) Course off alert even if set to off it still working and alerting. Sometimes putting in on and off again helps.

2.70

Can someone confirm this bug? Weather wedged always shows old weather state, like 3-4 hours past. For example, it says that it's 16* Celcius, but when I open this widget (press Start), I see in next hour temp 21*. 16 was in the early morning, but not now. Looks like widget not updated regarding current time

My weather widget is current and displaying the same information as the weather app on my phone. Your widget displays data it receives from your phone.   Perhaps your issue is with the information the phone is receiving.