D2 Charlie - version 4.20

I now own a D2 Charlie (as well as the D2 Bravo) so I am now maintaining a list of bugs, feature requests and such. I've moved the old issue list over from the 4.00 thread to this one, have reconfirmed all the issues below and will attempt to maintain a list of issues that remain and/or appear in version 4.20 along with any requests. I've bolded anything that would generally consider to be a serious issue that impedes use of the watch or included functionality (ie. reboots versus display or other issues). Reply below with comments and I'll keep the list updated.

Outstanding issues / bugs:

• [WATCH] Altimeter hardware does not seem to properly handle rapid elevation changes, either from lag or hanging (also affects Fenix 5X)
  
• [WATCH] Battery drain in FW 4.20 is much higher than normal (also affects Fenix 5X)
  
• [GPS] cannot receive a GPS fix within the flight deck of an Airbus A-320 (and several other aircraft)
  
• [APPS] Fly app uses watch setting for vertical speed rather than using "Aviation Units" configuration
  
• [WIDGETS] Altimeter widget ignores the widget configuration for display units of "feet" when general watch config is set to metric
  
• [WIDGETS] METAR widget uses watch setting for METAR visibility -- add configuration option for "visibility" to "Aviation Units" section
  
• [WIDGETS] METAR widget displays blanks screen if station (nearest or manually entered) does not have a published METAR (eg. CYCZ)
  
• [WIDGETS] Temperature widget does not display the proper density altitude when using metric units on the watch
  
• [CONNEXT] Garmin Pilot does not receive the altitude from the watch
  

Feature requests:

• [WATCH] add support for Galileo GNSS
  
• [WATCH] don't display the Nav Data status at the end of the "About" section, but instead display it
  
• [WATCH] add configuration option for "visibility" to "Aviation Units" section, to allow selection of SM, meters or kilometers
  
• [WIDGETS] METAR widget only displays cloud coverage (sky) information when there is a measured ceiling but should display FEW and SCT when no ceiling is present
  
• [WIDGETS] METAR widget "Use Nearest" function should retrieve an active GPS fix rather than using the last known position
  

Fixed issues:

• [WATCH] REM sleep tracking does not appear to be reported to Connect -- fixed after 4.20 but without FW update (backend/server fix)
  
• [APPS] Vertical speed not working in Fly app when the watch is set to GPS altitude -- fixed in 3.10
  
• [WIDGETS] METAR widget doesn't properly display visibility values when less than 1 SM or 1 km -- fixed in 3.20
  
• [WIDGETS] Altimeter widget doesn't allow O2 Alert altitude to be configured (O2 use regulations vary between countries) -- fixed in 3.10
  
• [WIDGETS] METAR widget doesn't properly display a vertical visibility on either the METAR display or the TAF display -- fixed in 3.10
  
• [CONNECT IQ] BehaviourDelegates does not function as expected when invoking onNextPage(), onPreviousPage(), etc -- fixed in 3.20
  

Old Issues [could not be confirmed or appear to work as expected]:

• none at this time
  

Thank you, Douglas. I hope this release addresses the altimeter insensitivity to rapid changing elevation issue that I reported previously. I was suggested to change the barometer mode to "altimeter" to see if the altimeter becomes more sensitive...here is my track from yesterday: https://connect.garmin.com/modern/activity/2792394373. The field elevation is roughly 1000 feet. The altimeter readings were off by about 1000 feet as you can see. The altimeter did not catch-up with the field elevation at least 5 minutes after landing..

If i understand well, this new release doesn't include GPS + GALILEO support...Strange, it's now available (beta version) for the fenix 5 models...

Thank you, Douglas. I hope this release addresses the altimeter insensitivity to rapid changing elevation issue that I reported previously. I was suggested to change the barometer mode to "altimeter" to see if the altimeter becomes more sensitive...here is my track from yesterday: https://connect.garmin.com/modern/activity/2792394373. The field elevation is roughly 1000 feet. The altimeter readings were off by about 1000 feet as you can see. The altimeter did not catch-up with the field elevation at least 5 minutes after landing..

I'm updating the list of bugs and such and will be emailing the support lead this afternoon to try and get an update on all the things -- will keep you posted.

This all said, every time I see Garmin mention that the US Air Force has chosen the D2 Charlie I'm wondering if the Air Force really did chose the D2C or if it's a pure marketing play because if I was an AF pilot I'd be wondering why I just went vertical to 50,000 feet in my F16 and my watch still shows me on the ground at aerodrome elevation.

Cheers,
Douglas

If i understand well, this new release doesn't include GPS + GALILEO support...Strange, it's now available (beta version) for the fenix 5 models...

Although the D2 series is based on the Fenix platform, the features on the D2C always lag behind those found on the base platform. In the case of the D2 Charlie, which is based on the Fenix 5X, it is a good sign that Galileo is included in the latest F5X beta. However, because of the way the aviation industry is from a legal/liability perspective, we might not see the Galileo support added right away, even after it's been added to the production release firmware of the F5X.

Cheers,
Douglas

I see REM sleep support was added in 4.20. However, I've upgraded and Garmin Connect seems to indicate that my device doesn't support REM sleep. Just me or are others seeing the same thing?

John

I see REM sleep support was added in 4.20. However, I've upgraded and Garmin Connect seems to indicate that my device doesn't support REM sleep. Just me or are others seeing the same thing?

John

My GC initially said my device supports advanced sleep. However, when i looked at that actual data, it says your device did not monitor advanced sleep data. I reported this issue to garmin aviation support.

I see REM sleep support was added in 4.20. However, I've upgraded and Garmin Connect seems to indicate that my device doesn't support REM sleep. Just me or are others seeing the same thing?

REM sleep tracking doesn't work for me either. I've added that to the bug list and reported it to the D2 team.

Thank you, Douglas. I hope this release addresses the altimeter insensitivity to rapid changing elevation issue that I reported previously. I was suggested to change the barometer mode to "altimeter" to see if the altimeter becomes more sensitive...here is my track from yesterday: https://connect.garmin.com/modern/activity/2792394373. The field elevation is roughly 1000 feet. The altimeter readings were off by about 1000 feet as you can see. The altimeter did not catch-up with the field elevation at least 5 minutes after landing..

It's strange. I definitely do not have this issue. But then I messed with all my watch's settings, especially while developing my GliderSK app (for which altimeter correctness was a must).
Maybe you can check:
- Barometer Widget -> Watch Mode = Altimeter
- Altimeter Widget -> Auto Calibration = Off
- FLY App -> Altimeter = Pressure
The Altimeter widget displays accurate elevation variation even when climbing/descending a single floor in my house.

EDITED: It'd be interesting to know whether the misbehavior happens in the FLY App only or also the Altimeter widget

EDITED 2: There's definitely something at play with the FLY App that does not happen when accessing the altimeter reading via ConnectIQ: altitude appears to be smoothed in the FLY App (e.g. some circuits at LSGS: https://connect.garmin.com/modern/activity/2718692922 ) but not in my app (e.g. a bad day at LSGB: https://connect.garmin.com/modern/activity/2767162444 )

It's strange. I definitely do not have this issue. But then I messed with all my watch's settings, especially while developing my GliderSK app (for which altimeter correctness was a must).
Maybe you can check:
- Barometer Widget -> Watch Mode = Altimeter
- Altimeter Widget -> Auto Calibration = Off
- FLY App -> Altimeter = Pressure
The Altimeter widget displays accurate elevation variation even when climbing/descending a single floor in my house.

EDITED: It'd be interesting to know whether the misbehavior happens in the FLY App only or also the Altimeter widget

EDITED 2: There's definitely something at play with the FLY App that does not happen when accessing the altimeter reading via ConnectIQ: altitude appears to be smoothed in the FLY App (e.g. some circuits at LSGS: https://connect.garmin.com/modern/activity/2718692922 ) but not in my app (e.g. a bad day at LSGB: https://connect.garmin.com/modern/activity/2767162444 )

Cedric,
On your pattern work, assuming that you were doing touch and go's, the recorded altitude did not seem to catch up with the ground speed. It looks like the airport elevation is roughly 1500 ft. But you were off by 400 feet or so during your landings each time. is that right?