Fenix 3 v6.82 Public Beta

In case you hadn't noticed yet, we have a new v6.82 public beta for fenix 3 available for download, which some of you may want to try. Download it here:

https://www8.garmin.com/support/download_details.jsp?id=9505

I've highlighted some changes that specifically affect Connect IQ. This build should also address the problem many people have had connecting to sensors (e.g. heart rate monitor), which I know several Connect IQ developers have expressed frustration about. fenix 3 6.82 Beta Change Log :

Added support for Auto Lock. (Settings > System > Auto Lock)
Added support for previewing back light intensity as it is modified.
Improved the colors used for sensor bar status icons.
Improved the accuracy of floors climbed data.
Fixed a potential issue where the current CIQ watch face could change if one had multiple CIQ watch faces and was upgrading from before software version 6.50.
Fixed a potential issue where certain widgets could disappear from the widget loop after a software update.
Fixed a critical issue where the watch would reboot when trying to Track Back a really long activity.
Fixed an issue where auto lap distance for rowing was not being displayed in meters.
Fixed a potential issue where a user could configure their lap alert banners to choose 'Interval Time/Pace/Distance' data fields for non-Open Water Swim profiles.
Fixed a potential issue where Foot Pod was being used as a distance source in indoor Bike activities.
Fixed a potential issue where one couldn't toggle the GPS setting for Row activities after profile creation.
Fixed a potential issue where the steps history graph was displaying certain days twice.

There's a full set of release notes on the download page, but there are some additional things they've recommended folks check after the update:

Your Fenix 3 re-pairs with your smartphone
Your Fenix 3 re-pairs with sensors
Your CiQ watch face is still active
Widgets and Apps are still in order and present
Your CiQ data fields are still set properly
Your CiQ Apps and widgets are still set properly
You are able to Sync with Garmin Connect Mobile
Alarms or alerts continue to chime as you would expect
Vibrations and tones continue to alert you in the manner in which you have them setup
VO2Max and My Stats data is still present

mcbadger over 9 years ago

Pleased to see that! I note that when I select a ConnectIQ app, the heart rate does not appear before I start the activity recording. When I start recording, the HR appears a few seconds later, so it looks as though the watch isn't looking for the sensors until recording starts. Does that sound right?

jim_m_58 over 9 years ago

Pleased to see that! I note that when I select a ConnectIQ app, the heart rate does not appear before I start the activity recording. When I start recording, the HR appears a few seconds later, so it looks as though the watch isn't looking for the sensors until recording starts. Does that sound right?

This is actually based on how the CIQ app was written. There are two ways to get the heart rate - one, anytime after the sensor is enabled, and two when the recording is started. It's best to ask the developer of the app.

mcbadger over 9 years ago

That's clear, thank you. (I've written widgets using GPS and web access, but not apps, so not come across that nuance).

geniuswrist over 9 years ago

This is actually based on how the CIQ app was written. There are two ways to get the heart rate - one, anytime after the sensor is enabled, and two when the recording is started. It's best to ask the developer of the app.

That's correct, I just installed 6.82 and tested my app (Gym Timer - https://apps.garmin.com/en-us/apps/93d358c4-53d3-4a9d-a7c4-e6f9a49c0e31)

It picked the HR info without the need to start an activity.

I also alternated randonly between native and other CIQ apps and it seems the sensor issue is solved.

Cheers,

Robinson

dvp1963 over 9 years ago

Fixed a potential issue where Foot Pod was being used as a distance source in indoor Bike activities.

very interesting how to activate this on F3

mcbadger over 9 years ago

I think you may have misunderstood. It used to be that, if you were cycling and there was an active foot pod nearby (either because you have it on your shoe, or you've just used it on a treadmill before hopping on a turbo trainer, or whatever else), the data from that would mess up your cycling distance. The bug fix was to make sure that foot pod data are completely ignored during cycling, as they always should have been.