Forerunner 945 Beta SW 3.08 is now available!

I have run the same route 4 times. Each time the elevation is different. Ranging from 7ft to 30ft. Anyone else notice this?

This beta has generally been working ok for me. The device connectivity now seems to be sorted out - previously I had to reboot.

First major issue though today - GPS was a total mess! I appreciate that running in London, with the tall buildings etc, is a major challenge. I'm not expecting a perfect track. However, the route I took was fairly clear of tall buildings for major parts. I then lost GPS totally for a portion, only getting it back when I realised the map hadnt updated and needed to work my way through Islington back onto Regents Canal. The map was zoomed out quite a way by default - is this an indication of poor GPS reception ??

connect.garmin.com/.../4136518646

So your route is flat, and the watch says so each time? Sounds pretty good to me :)

Bluetooth suddenly wasn't working on my S10+ either, not sure why... getting it to pair again was very hard as well. Not sure if it was the forerunner sw update, an update in connect, or something else. Will keep an eye on it...

Bluetooth seems quite slow, not sure if it's worse then before though

There is a big problem with GarminPay, from Garmin Connect mobilr app., in the device section I can't change anymore the pin code or modify anything in the cards section, Garmin connect tell me that the watch is disconnected but it isn't.

Can't quite see if this matches any other reports, but while cycling home last night (and listening to music over BT) the audio stopped and a few seconds later all the sensors went to "---", seemingly the radios crashed. I had to stop the activity, power off and on again and it all recovered, but it's the first time (and hoipefully the last) I've seen this.

Then, after the above, the battery consumption went mad and went down the 14% by bedtime (normally still above 50% after a typical cycling commute day) - I then charged it for a while before putting it back on for sleep monitor. It was 54% at that point but at some point overnight it died. Put it onto charge to 100% until after my morning wake-up and, hopefully, it's back to normal now.

pgalbavy said:

Can't quite see if this matches any other reports, but while cycling home last night (and listening to music over BT) the audio stopped and a few seconds later all the sensors went to "---", seemingly the radios crashed. I had to stop the activity, power off and on again and it all recovered, but it's the first time (and hoipefully the last) I've seen this.

Then, after the above, the battery consumption went mad and went down the 14% by bedtime (normally still above 50% after a typical cycling commute day) - I then charged it for a while before putting it back on for sleep monitor. It was 54% at that point but at some point overnight it died. Put it onto charge to 100% until after my morning wake-up and, hopefully, it's back to normal now.

looks like there is something wrong with BLT Sensor, or?

f|33tStA said:

yesterday i made a run with connected BLT headphones, finished run and pressed stop, then headphones disconnected and it looks like BLT on watch was dead, restarted watch, restarted mobile phone, no change, the pairing wasn't possible, after a hard reset of the watch the pairing went OK!

gesture for backlight on turning the wrist, does not work during activity at all.
it works randomly if it's also enabled for "not during activity" but by far not working in a useful way during a run.

Same thing happened to me several times. BT dead or all ANT sensors dropped. Only restart helps.