Driver Distraction Notification does not include Lock Screen Dismissal information when state=DD_OFF

[joeljfischer]

Bug Report

When connecting to the Generic_HMI, an initial driver distraction notification is sent, but that DD notification doesn't include the lock screen dismissal enabled parameter, nor lock screen text. This information should be included so that lock screen dismissal is enabled before a second DD notification is received.

Reproduction Steps

1. Watch for the first DD notification
2. Connect to Core + generic_hmi
3. View the DD notification
4. Toggle DD
5. View the second DD notification

Expected Behavior

The initial DD notification should include lock screen dismissal information

Observed Behavior

The initial DD notification does not include lock screen dismissal information, but the second DD notification does

Browser & Version Information

• Browser and Version: Chromium 95.0
• RPC Sent: n/a
• Output Received: n/a
• Generic HMI Version: v0.11.0 / v0.10.0
• Testing Against: Core v8.0.0 / Manticore (Core v7.1.1)

Test Case, Sample Code, and / or Example App

n/a

[jacobkeeler]

The Generic HMI doesn't provide these values. They are provided by Core using the policy table, and these values are only sent in the DD_ON case, per Core's logic. Are you setting DD_ON before connecting the app?

[joeljfischer]

@jacobkeeler Sorry, this should have included more information and is on the wrong repository. Even when Driver Distraction is off, the lock screen dismissibility information should be included because an app can present the lock screen even when driver distraction is OFF but may want to be dismissible if the head unit allows it. This is a fringe case, but it is one in our smoke test sheet.

[jacobkeeler]

Closed via #3842