Skip to content

[OnDriverDistraction] SDL does not send notification to app right after this app changes level from NONE to any other #1881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
6 of 9 tasks
LitvinenkoIra opened this issue Nov 23, 2017 · 2 comments
Assignees
Labels

Comments

@LitvinenkoIra
Copy link
Contributor

LitvinenkoIra commented Nov 23, 2017

Occurrence:

Always

Steps to reproduce:

  1. Make sure SDL is built with default flags
  2. Start SDL and HMI
  3. Connect mobile device
  4. Register new application → it gets NONE HMI level and SDL receives OnDriverDistraction () fom HMI
  5. Change HMI level to any other than NONE: (FULL, BACKGROUND, LIMITED)
  6. Check that 'OnDriverDistraction' notification is sent to application

Expected result:

SDL must transfer the last known (actual) OnDriverDistraction () to the mobile app right after this mobile app changes HMI level to any other than NONE.

Actual result:

N/A

Test script:

1881_OnDriverDistraction_After_changing_HMIlevel_from_NONE.lua

Environment:

Attachments:

Note: Extract attached folder with script to test_scripts folder.
Defects.zip

Expected delivery

  • Source code updates
  • Code comments
  • UTs add/update (not required)
  • ATF tests add/update
  • Manual tests (not required)
  • Add/update CI plans/jobs (not required)
  • SDD updates (not required)
  • Guidelines update (sdl_core_guides) (not required)
  • Guidelines update (sdl_hmi_integration_guidelines) (not required)
@LitvinenkoIra LitvinenkoIra changed the title SDL does not send notification to app right after this app changes level from NONE to any other [OnDriverDistraction] SDL does not send notification to app right after this app changes level from NONE to any other Nov 23, 2017
@aderiabin
Copy link

Contributor priority is set High with reason: Currently the newly registered applications know nothing about Driver Distraction mode, but only after it changes, the issue fixes this case.

@dboltovskyi
Copy link
Contributor

Issue is reproduced on develop (0b19cf4) and fixed in #1970

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants