smartdevicelink / sdl_core

SmartDeviceLink In-Vehicle Software and Sample HMI
BSD 3-Clause "New" or "Revised" License
241 stars 244 forks source link

Navigation app must be activated during active embedded audio source and "MixingAudioSupported" = true #1906

Closed GetmanetsIrina closed 4 years ago

GetmanetsIrina commented 6 years ago

Occurrence: Always

Description

Navigation app must be activated during active embedded audio source and "MixingAudioSupported" = true.

Preconditions

Steps to reproduce

Actual result

SDL does not set required HMILevel and audioStreamingState.

Expected result

SDL must send OnHMIStatus (FULL, AUDIBLE) to mobile app.

Environment

Attachments

Expected delivery

dboltovskyi commented 6 years ago

Priority was set to Medium. Issue is related to setting wrong HMI level and/or audioStreamingState for activated application in some specific cases. May affect correct permissions calculation for Navigation application during active embedded navigation.

HSavynetska commented 6 years ago

Verified: SDL build: develop branch ( 45109a0 ) ATF: develop branch

Status: Defect is reproduced.

To current requirement item 5.1 in https://github.com/smartdevicelink/sdl_evolution/blob/master/proposals/0150-video-streaming-state.md (audioStreamingState must be "NOT_AUDIBLE" due/during to active embedded audio source)

But in the precondition described steps lead to new sdl defect:

Actual result Navigation app in BACKGROUND and NOT_AUDIBLE due to active embedded audio source

Expected result Navigation app in LIMITED and NOT_AUDIBLE due to active embedded audio source

Script: https://github.com/smartdevicelink/sdl_atf_test_scripts/pull/1977

HSavynetska commented 4 years ago

The defect is reproduced on the current develop

Environment: Script: https://github.com/smartdevicelink/sdl_atf_test_scripts/pull/1977 SDL build: [https://github.com/smartdevicelink/sdl_core/tree/develop] (891497b ) ATF: develop branch

E-SAITO-TMC commented 4 years ago

@joeygrover -san @theresalech -san This issue is a top priority for Toyota. Can the reproduction steps described (or this test script) actually reproduce this issue? Also, Does this issue occur in the latest version?

theresalech commented 4 years ago

Hi @E-SAITO-TMC, we have documented that this is priority for Toyota, and will include for Steering Committee review and vote when planning the contents for the Q4 Core release. This planning will take place in June. @HSavynetska, can you please advise if you are seeing this issue when using Core 6.1?

dboltovskyi commented 4 years ago

@theresalech Please notice issue is still actual for Core 6.1 ATF script and logs: 2020-06-04_15-45-57_1906.tar.gz

theresalech commented 4 years ago

Hi @dboltovskyi, thank you for the additional information. Will Luxoft be submitting a PR to resolve this issue?

dboltovskyi commented 4 years ago

@theresalech Please notice we're not planning to create the fix in scope of 6.2, though will try to do as much as possible

jacobkeeler commented 4 years ago

Duplicate of #1608