This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Beta Version 6.83 Now Available!

Former Member over 7 years ago

A new Beta software for the Forerunner 935 has been released. Full change log, instructions, and software for installing the beta can be found here.

[h=4]Changes made from version 6.78 to 6.83:[/h]

Added support for Connect IQ SDK 2.4.1.
Improved Training Status and Training Load now updated with heart rate data that is stored on an HRM-Tri or HRM-swim and sent to the watch.
Improved Compass steadiness when still and responsiveness when moving.
Fixed an issue causing the backlight to remain on while on the charging page.
Fixed issue causing the Start/Stop and Lap keys to only clear notifications when they are displayed instead of also performing their general function (for example, starting the timer and recording a lap).
Fixed an issue preventing Work from being displayed on Varia Vision.
Fixed an issue preventing Lap HR % Max from being displayed on Varia Vision.
Fixed an issue causing the Best Power personal record to be displayed incorrectly.

[h=2]Installation Instructions[/h]

Connect your Forerunner 935 to your computer using the USB cable.
Download and unzip Forerunner935Beta.zip. Place the GUPDATE.GCD file in the \GARMIN folder of your device's internal storage drive and the GUP2665.GCD file in the \GARMIN\REMOTESW folder.
Disconnect your device from the computer, approve the update on the watch, and wait for the update to finish.
If you would like to revert to the last public release software, follow the above steps but place the GUPDATE-610.GCD file in the \GARMIN folder and GUP2665-410.GCD in the \GARMIN\REMOTESW folder. Rename GUPDATE-610.GCD to GUPDATE.GCD and GUP2665-410.GCD to GUP2665.GCD before disconnecting your device. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.

Please feel free to discuss this beta version in this thread, but be sure to also submit any feedback to [EMAIL="[email protected]"][email protected][/EMAIL].

0 2goBeyond over 7 years ago

Just to be clear, there wasn't a sensor hub update with beta 6.83 so whatever HR issues people are having is with the current sensor live release (which was a few months ago). If anything the error is with beta interacting with the current Sensor Hub improperly and not a change to the sensors themselves.

Will that translate to a sensor hub update? Eventually, but until then i'm going to take an educated guess that the beta as a whole is a mess.

0 MrTim over 7 years ago

I wasn't happy with OHR on this beta either - rolled the firmware (and sensor hub) back to 6.10.

Same here, 'downgraded' to 6.10 this morning.

0 Bit over 7 years ago

The time-in-hr-zones in biking activities with power is fixed now, thank you beta team!

0 MrTim over 7 years ago

So I downgraded to 6.10, it reset everything but I did a second full reset as well. Unpaired from my iPhone, paired again, set everything back up fresh. Now, I create an alarm on the phone, sync, alarm gone. I create an alarm on the 935, sync, alarm gone. Really Garmin? Not cool for a $500 device. My $30 Timex has reliable alarms. Yah, I'm a bit frustrated.

0 chrisdr2 over 7 years ago

Just to be clear, there wasn't a sensor hub update with beta 6.83 so whatever HR issues people are having is with the current sensor live release (which was a few months ago). If anything the error is with beta interacting with the current Sensor Hub improperly and not a change to the sensors themselves.

Will that translate to a sensor hub update? Eventually, but until then i'm going to take an educated guess that the beta as a whole is a mess.

Ah, my mistake - If not sensor hub, then what is the GUP2665.GCD file in the beta? I note that the F5 got a whole bunch of similar updates with their beta.

Certainly agree that this beta process is a bit messy, will hang tight and wait for the next stable release.

0 chrisdr2 over 7 years ago

So I downgraded to 6.10, it reset everything but I did a second full reset as well. Unpaired from my iPhone, paired again, set everything back up fresh. Now, I create an alarm on the phone, sync, alarm gone. I create an alarm on the 935, sync, alarm gone. Really Garmin? Not cool for a $500 device. My $30 Timex has reliable alarms. Yah, I'm a bit frustrated.

Until there is a proper fix for this, I am setting alarms in Garmin Connect and synching via WiFi or USB. It seems to be the only way of guaranteeing that the alarms stay set.

0 MrTim over 7 years ago

Until there is a proper fix for this, I am setting alarms in Garmin Connect and synching via WiFi or USB. It seems to be the only way of guaranteeing that the alarms stay set.

I tried those methods, doesn't work for me - alarms disappear almost instantly. Garmin should be ashamed.

0 chrisdr2 over 7 years ago

Just to be clear, I am referring to the Garmin Connect website, rather than the mobile app. I set a new alarm earlier and it synched to both GCM and the watch.

0 Former Member over 7 years ago

My BLE/ANT is still 5.21 after updating. I tried several times to move the gupdate.gcd into the garmin folder and the gup2665.gcd into the remotesw folder but I doesn't update anymore.

Is there any ohter way to force a new update or to install the BLE/ANT-firmware separately?

I don't want to revert to 6.10 because I don't want to lose my settings

0 Former Member over 7 years ago

LTHR has been "broken" for me since 6.75 with detected data that doesn't make sense and this week a guided test that stopped after only two steps. Hopefully this update will fix it...or the next one !

Yep I have exactly the same issues with LTHR values. Detected values are totally out of range. The 2 first measurement were fine but after it became totally crazy. The worst being the value mentionned in GCM 46BPM lower than my resting rate :-) ). I hope we will have more consistency with the new release. By the way I wonder how this wrong LTHR values influence the Training effect calculation???? Any idea?