smartdevicelink/sdl_hmi

sdl_hmi's Issues

[SDL 0209]-Static Icon Capability

Proposal: Static Icon Capability

Add a capability for app developers to know if static icons are available on a connected head unit.

Review: smartdevicelink/sdl_evolution#636

Steering Committee Decision:

The Steering Committee voted to accept this proposal with the revisions on 2018-12-11. The author will alter his proposal to match his last comment but with the array maximum size as 1000.

The author has made the requested revisions on 2018-12-20

[SDL 0211] Service Status Update to HMI

Proposal: Service Status Update to HMI

This proposal is about adding a new RPC called 'OnServiceUpdate' which will be used by the HMI layer to know the status of certain services from SDL Core.

Review: smartdevicelink/sdl_evolution#641

Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions on 2018-12-18. The author is to update the proposal to include both the Audio and RPC services discussed in this comment and adding an optional 'appID' parameter to the OnServiceUpdate RPC as noted in this comment.

Revisions were made on 2018-12-20

[SDL 0181] SDL shall not put RC applications to HMI level NONE when user disables RC in HMI

Proposal: SDL shall not put RC applications to HMI level NONE when user disables RC in HMI

SDL shall not put REMOTE_CONTROL appHMIType applications to HMI level NONE when user disables remote control in HMI.

Review: smartdevicelink/sdl_evolution#531

SDL HMI does not support remote control SEAT by default

Bug Report

HMI does not support remote control SEAT in capability

Reproduction Steps

1. register and activate a remote control app
2. send a valid GetInteriorVehilceData request regarding SEAT moduleType

Expected Behavior

App get SEAT module data

Observed Behavior

app get UNSUPPORTED_RESOURCE error.
Also there is no seat related capability in the GetSystemCapability response

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: https://github.com/smartdevicelink/sdl_core/tree/5.0.0_RC2
• test remote control regarding SEAT

HMI doesn't add HTTP header to SDL policy table snapshot in case of EXTERNAL_PROPRIETARY flow

Bug Report

Currently there is the following communication between SDL and HMI during Policy Table Update sequence in case of EXTERNAL_PROPRIETARY flow.
SDL->HMI: BC.PolicyUpdate(file)
HMI->SDL: BC.OnSystemRequest(file)

where file is path to policy table snapshot file

It is assumed for EXTERNAL_PROPRIETARY that HTTP header is added by HMI
However for PROPRIETARY this header is added by SDL Core

Occurrences

Always

Reproduction Steps

1. Run SDL which was built with EXTERNAL_PROPRIETARY flow
2. Connect and device and register new App => PTU is triggered
3. Check the PTS file that is provided in BC.OnSystemRequest from HMI

Expected Behavior

PTS file contains HTTP header

Observed Behavior

PTS file does not contain HTTP header => SPT is unable to send appropriate SystemRequest

Notes:

HTTP header is

{
    "HTTPRequest": {
        "body": "<policy_table>",
        "headers": {
            "ConnectTimeout": <int value from policy table:timeout_after_x_seconds>,
            "Content-Length": <value of the length of the "body" string>,
            "ContentType": "application/json",
            "DoInput": true,
            "DoOutput": true,
            "InstanceFollowRedirects": false,
            "ReadTimeout": <int value from policy table:timeout_after_x_seconds>,
            "RequestMethod": "POST",
            "UseCaches": false,
            "charset": "utf-8"
        }
    }
}

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: Release 5.0.0
• Testing Against: HMI version: develop

Resumption.Application data is not restored on HMI after unexpected disconnect and connect are performed

Bug Report

Resumption.Application data is not restored on HMI after unexpected disconnect and connect are performed

Steps

1.SDL and HMI are started
2. App1is registered
3. App1 added AddCommand
4. Unexpected disconnect and connect are performed

Expected Behavior

SDL sends data for resuming after sending "BasicCommunication.OnAppRegistered" to the HMI

Actual result:

SDL sends data for resuming before sending "BasicCommunication.OnAppRegistered" to the HMI and On HMI does not display all data for applications

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: same_app_from_multiple_devices ( 708b042 )
• HMI version: develop (78b2d45 )
  SPT: 20190122 Nightly-Android

Attachments

sdl.log.and.hmi.log.zip

HMI does not provide Seat capabilities

Steps to reproduce:

1. SEAT module type is preset in preloaded_pt, "Remote_control" is assigned to app
2. Register RC app and activate it
3. Send GetSystemCapability (remote_control)

Expected result: HMI sends seat capabilities in GetSystemCapability response
Actual result: HMI does not send seat capabilities in GetSystemCapability response

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: https://github.com/smartdevicelink/sdl_core/tree/5.0.0_RC2
• HMI: develop branch 51a4ace

Tip: Enable Github Pages

If in this repository the GitHub pages are enabled (go to repository Settings) to serve up Master branch then automagically the index.html herein will be reachable from the Web for evaluation, like this: https://smartdevicelink.github.io/sdl_hmi/

See the example on my fork: https://gunnarx.github.io/sdl_hmi/
which is nothing more than the repo itself: https://github.com/gunnarx/sdl_hmi/

Add turn signal status to sdl_hmi

sdl_hmi implementation of https://github.com/smartdevicelink/sdl_evolution/blob/master/proposals/0107-New-vehicle-data-turnSignal.md

[SDL 0042] SDL must transfer RPC’s with invalid image reference parameters to the HMI

Proposal: SDL must transfer RPC’s with invalid image reference parameters to the HMI

Update SDL Core behavior to more gracefully handle RPC requests that provide an invalid image reference. Any RPC that provides a reference to an image that is not located in the AppStoreFolder is considered invalid (the AppStoreFolder is specified in the SmartDeviceLink.ini.)

Review: smartdevicelink/sdl_evolution#128

Steering Committee Decision:

The Steering Committee has agreed to accept this proposal. They also recommended that an additional proposal be submitted for the additional post loading of content.

[SDL 0213]- Remote Control - Radio and Climate Parameter Update

Proposal: Remote Control - Radio and Climate Parameter Update

This proposal changes the minimum index of HD radio sub-channels from 1 to 0.
In addition, we propose to add a new parameter climateEnable to ClimateControlData which will allow an application to power climate control on or off.

smartdevicelink/sdl_evolution#643

Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions. The author is to update this proposal to state that availableHDs and availableHdsAvailable are deprecated entirely if the functionality is subsumed by availableHDChannels as finalized in this comment.

Revisions were made on 2019-01-02

[SDL 0115] CloseApplication RPC

Proposal: CloseApplication RPC

This proposal is about adding a new RPC called CloseApplication which can be used by an app to send itself into HMI_NONE.

Review: smartdevicelink/sdl_evolution#351

mb_tcpserver.cpp:96 Received 4096 actual data length 4916

When I connect android phone with sdl core, the error occurred while playing music from the phone apk. The errors are follow:

ERROR!!! /usr/src/debug/sdl-core/4.4.1-r0/git/src/3rd_party-static/message_broker/src/server/mb_tcpserver.cpp:96 Received 4096 actual data length 4916
ERROR!!! /usr/src/debug/sdl-core/4.4.1-r0/git/src/3rd_party-static/message_broker/src/server/mb_tcpserver.cpp:97 Incomplete messageERROR!!!

How to solve the problem?
The sdl-core was runned on AGL platform.
sdl core version is : 4.4.0

Thanks

HMI sends OnDriverDistraction notification to SDL twice

Preconditions:

1. Start SDL and HMI
2. Connect mobile device via any transport
3. Register app and activate app

Steps to reproduce:

1. Check the “DD” box
2. Uncheck “DD”

Actual result:

HMI sends an OnDriverDistraction notification to the SDL twice, and the mobile application receives two notifications

- HMI→SDL: "OnDriverDistraction"( "DD_ON" )

• HMI→SDL: "OnDriverDistraction"( "DD_ON" )

• SDL→MOB: "OnDriverDistraction"( "DD_ON")

• SDL→MOB: "OnDriverDistraction"( "DD_ON")

• HMI→SDL: "OnDriverDistraction"( "DD_OFF" )

• HMI→SDL: "OnDriverDistraction"( "DD_OFF" )

• SDL→MOB: "OnDriverDistraction"( "DD_OFF")

• SDL→MOB: "OnDriverDistraction"( "DD_OFF")

Expected result:

HMI sends one OnDriverDistraction notification to the SDL, and the mobile application receives one notification:

- HMI→SDL: "OnDriverDistraction"( "DD_ON" )

• SDL→MOB: "OnDriverDistraction"( "DD_ON")

• HMI→SDL: "OnDriverDistraction"( "DD_OFF" )

• SDL→MOB: "OnDriverDistraction"( "DD_OFF")

'timestamp' of event is over the range of 'ts' that is for TouchEvent in Core.

sdl_hmi/app/model/sdl/Abstract/Model.js

Line 182 in 795be41

events[i].ts = [parseInt(event.timeStamp)];

In W3C, 'timestamp' of event is the number of milliseconds since midnight of January 1, 1970
(reference : https://www.w3schools.com/jsref/event_timestamp.asp)
However the max value 'ts' of TouchEvent that is for UI.OnTouchEvent is 2147483647. Maybe in Core, ts is seconds since midnight of January 1, 1970.
(reference : https://smartdevicelink.com/en/docs/hmi/master/common/structs/#touchevent)

The issue is that wrong value is passed to core when FFW.UI.onTouchEvent.

HMI does not remove the group entries in app permissions list

Precondition: SDL must be built with EXTERNAL_PROPRIETARY flag

Steps to reproduce:

1. Register app
2. Perform PTU with groups that needs the user consent( after app registration and activation send SystemRequest(PROPRIETARY) with required file for update )
3. After PTU there are 2 entries in app permissions list
4. Perform update without groups for user consent( Trigger the ptu from HMI vie UpdateSDL in Settings and send SystemRequest(PROPRIETARY) with required file for update )
5. Go to app permissions list

Expected result: The list of app permissions for defined app is empty

Actual result: The list contains 2 records from previous update and they can be pressed and HMI sends some invalid message {"jsonrpc":"2.0","method":"SDL.OnAppPermissionConsent","params":{"source":"GUI","consentedFunctions":[{"allowed":true},{}],"appID":0}}

SDL branch: smartdevicelink/sdl_core@17c3f51
Mobile app version: 4.6.3 20180912
OS version: Ubuntu 16.04
Files for update:
files_for_ptu.tar.gz

HMI does not update values in drop-down on SEAT form in case values are updated via SetInteriorVD

Bug Report

HMI does not update values in drop-down list on SEAT form in case values are updated via SetInteriorVD

Occurrences

Sometimes

Reproduction Steps

1. RC app is registered and activated
2. Go to SEAT form and change id to DRIVER
3. App requests SetInteriorVD with updated parameters for DRIVER id and for parameters in drop-down list

Expected Behavior

HMI must update values on SEAT form according to changes in SetInteriorVD requets

Observed Behavior

HMI does not update values on SEAT form, but sends actual values in OnInteriorVD and in SetInteriorVD response

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: smartdevicelink/sdl_core@c969797
• Testing Against: HMI version: 35e5c1a, SPT: 4.6.3

HMI does not show RC apps from second device

Steps to reproduce:

1. Connect device_1
2. Register RC app_1 from device_1
3. Connect device_2
4. Register RC app_2 from device_2

Expected result: all apps are registered and shown on HMI.
Actual result: App_2 from device_2 is registered, but is not shown on HMI.

ButtonPress: SOURCE Crashes HMI

Sending an RC.ButtonPress RPC for the radio button "SOURCE" leaves the HMI in a bad state. Any displayed text disappears and interacting with the app causes this error.

Controller.js:133 Uncaught TypeError: Cannot read property 'set' of null

Relevant logs:

Message received: {"id":65,"jsonrpc":"2.0","method":"Buttons.ButtonPress","params":{"appID":754384191,"buttonName":"SOURCE","buttonPressMode":"SHORT","moduleType":"RADIO"}}

ButtonsRPC.js:130 FFW.Buttons.onRPCRequest
ButtonsRPC.js:133 FFW.Buttons.ButtonPress Reqeust
BasicCommunicationRPC.js:1197 FFW.BasicCommunication.OnEventChanged
RPCClient.js:247 {"jsonrpc":"2.0","method":"BasicCommunication.OnEventChanged","params":{"eventName":"AUDIO_SOURCE","isActive":true}}
RPCClient.js:249 6:48:22:49
RCRPC.js:568 FFW.RC.OnInteriorVehicleData Notification
RPCClient.js:247 {"jsonrpc":"2.0","method":"RC.OnInteriorVehicleData","params":{"moduleData":{"moduleType":"AUDIO","audioControlData":{"source":"USB"}}}}
RPCClient.js:249 6:48:22:50
BasicCommunicationRPC.js:1197 FFW.BasicCommunication.OnEventChanged
RPCClient.js:247 {"jsonrpc":"2.0","method":"BasicCommunication.OnEventChanged","params":{"eventName":"AUDIO_SOURCE","isActive":false}}
RPCClient.js:249 6:48:22:56

SendLocation does not work

Get the error after receiving a send location request from core.

NavigationController.js:52 Uncaught TypeError: this.model.push is not a function

[SDL 0147] Template Improvements: Color Scheme

Proposal: Template Improvements: Color Scheme

This proposal enables apps to provide a custom color scheme. This will allow OEMs to still strictly control layout and design while allowing apps some amount of branding and customization.

Review: smartdevicelink/sdl_evolution#422

Steering Committee Decision:

The Steering Committee has voted to accept this proposal with the revisions noted in this comment.

The proposal .md was updated on March 21, 2018 to include the agreed upon revisions.

No LICENSE file

As the title says - what are the license conditions for the code (and images) in this repository?

Update: Some (most?) but not all files have headers with license information. It would still help to have a LICENSE file in the root. Also, what about the image files?

Cannot activate an app

in the Html HMI, after clicking the app "syncproxytest", a popup showing "Activation in progress...", but the app does not get activated.

[SDL 0224] Navigation Subscription Buttons

Proposal: Navigation Subscription Buttons

This proposal adds support for new subscription buttons (like the existing Play/Pause, Next, Previous, etc.) specifically designed for navigation scenarios.

Review: smartdevicelink/sdl_evolution#712

Steering Committee Decision:

The Steering Committee voted to accept this proposal with the following revisions:

• Incorporate this comment, with NAV_ROTATE including rotating left or right 90 degrees.
• Add button press to the Navigation Service's handled RPCs with these new button types.

Additionally, there was a question in the Steering Committee meeting about requiring applications to be compatible with this proposal. It was advised that this requirement is out of the scope of SDL, and OEMs would need to ask application developers to implement this proposal once it's available in the library for developers to implement.

The proposal .md file was updated to reflect these revisions on 5/20/19.

Web SDL HMI doesn't follow the HMI flow

From sandeepf184 (smartdevicelink/sdl_core#838):

According to the HMI flow, when we send messages like dialnumber it should check for high priority events like Alert and Emergency Call etc. But I have seen in web hmi that when alert message is displayed and made a request for dialnumber , the dialnumber popup is displayed over alert message. Can anyone please check with it and help me with that.

On HMI not displayed the second App

Bug Report

On HMI not displayed the second App

Steps

1. SDL and HMI are started
2. Connect mobile devices via any transport
3. App1 and App2 are registered with Remote_Control HMI type

Expected Behavior

HMI must update values on SEAT form according to changes in SetInteriorVD requets

Actual result:

On HMI displayed only one app of two

Expected result:

On HMI displayed both apps

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: same_app_from_multiple_devices ( 708b042 )
• HMI version: develop (78b2d45 )
  SPT: 20190122 Nightly-Android

[SDL 0198] - Media Skip Indicators

Proposal: Media Skip Indicators

This feature is similar to SDL-0109 Audio Streaming Indicator except that it affects the next and previous buttons. These buttons should have the ability to show time skip buttons that are commonly used by podcast & audiobook media.

Review: smartdevicelink/sdl_evolution#596

Steering Committee Decision:

The Steering Committee voted to accept this proposal with the following revisions:

• Incorporate the feedback agreed to in this comment by the author.
• Ensure that conditions of SeekIndicatorType are documented, as requested in this comment.

The proposal .md file was updated to reflect these revisions on 9/20/18.

[SDL 0192] Button Subscription response from HMI

Proposal: Button Subscription response from HMI

This proposal is to replace OnButtonSubscription notification
with SubscribeButton request/response,UnsubscribeButton request/response to HMI.

Review: smartdevicelink/sdl_evolution#568

Steering Committee Decision:

The Steering Committee voted to accept this proposal with the following revisions:

• Proposal will be updated to include the XML structure described in this comment
• References to "UnSubscribe" within XML should be updated to "Unsubscribe".

The proposal .md file was updated to reflect these revisions on 8/13/18.

HMI does not send heatingLevel in OnInteriorVehicleData after update from HMI

Bug Report

HMI does not send heatingLevel in OnInteriorVehicleData after update from HMI

Occurrences

Once

Reproduction Steps

1. RC app is registered and activated
2. App is subscribed to SEAT module
3. Update heating level on HMI and press Set button

Expected Behavior

HMI sends OnInteriorVehicleData notification with heatingLevel with updated value and SDL transfer notification to mobile app

Observed Behavior

HMI does not send heatingLevel in OnInteriorVehicleData after update

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: smartdevicelink/sdl_core@c969797
• Testing Against: HMI version: 35e5c1a, SPT: 4.6.3

[SDL 0199]-Adding-GPS-Shift-support

Proposal: Adding GPS Shift support

To add shifted param for GPS data struct so that HMI can communicate to app when GPS data is shifted using an algorithm

Review: smartdevicelink/sdl_evolution#598

Steering Committee Decision:

The Steering Committee fully agreed to accept this proposal on 2018-09-25.

[SDL 0212] - Add Ability to Reuse a SyncFileName for a PutFile

Proposal: Add Ability to Reuse a SyncFileName for a PutFile

Currently, when a developer tries to reuse the same syncFileName for a PutFile with image data, the HMI is not updated to show the new image. This is due to Core only sending a notification to the HMI when the PutFile is a system file. To remedy this issue, Core needs to send a notification to the HMI when it receives any type of PutFile.

smartdevicelink/sdl_evolution#642

Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions on 2018-12-18. The author is to updated this proposal to include an additional parameter name of the updated file to the HMI notification as called out in this comment.

Revisions were made on 1.17.19

Inaccurate supported text fields in DisplayCapability

HMI sometimes sends Inaccurate supported text fields in DisplayCapability in both RAI response and SetDisplayLayoutResponse. So for example, if we use MEDIA for the app HMI type, the display capability in RAI response says that textfield4 is supported. While practically, the default template cannot actually display the text field 4.

[SDL 0108] AutoCompleteList

Proposal: AutoCompleteList

The AutoCompleteList will give apps the ability to have multiple listing options while searching for things like destination and information; instead of giving a single suggestion.

Review: smartdevicelink/sdl_evolution#331

Cannot view video

When I use sdl_hmi as my hmi-level software, I cannot view the video.
Android APP: Sygic Car Navi.
Core version: 4.5.0
HMI version: newest now
Steps:
1, I edit the smartDeviceLink.ini and set 'VideoStreamConsumer = pipe' and 'AudioStreamConsumer = pipe ' and started up core using command: 'smartDeviceLinkCore'.
2, Then I used Chome and viewed the hmi 'sdl_hmi/index.html'.
3, Connect the android phone to PC with USB.
4, Click the ICON in sdl_hmi and activite the 'Sygic Car Navi' App.
No map or other video can be viewed.
Could anyone help to teach me where the steps above was wrong, or any suggestions?
Thanks a lot !

HMI responds 'REJECTED' to a request from SDL on RC.ButtonPress from the App2

Bug Report

HMI responds 'REJECTED' to a request from SDL on RC.ButtonPress from the App2

Precondotions

1. In sdl_preloaded_pt.json default app_policies groups: ["Base-4", "RemoteControl"], moduleType: ["RADIO", "CLIMATE"] HMI support new RC module
2. Start SDL and HMI
3. Connect mobile devices via any transport
4. Running the same application on the different devices with Remote_Control HMI type

Steps

1. App1 is activated and allocates module_RADIO via ButtonPress
2. App2 is activated and tries to allocate module_CLIMATE via ButtonPress

Expected Behavior

HMI must update values on SEAT form according to changes in SetInteriorVD requets

Actual result:

HMI responds 'REJECTED' to a request from SDL on RC.ButtonPress from the App2

Expected result:

HMI responds 'SUCCESS' to a request from SDL on RC.ButtonPress from the App2

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: same_app_from_multiple_devices ( 708b042 )
• HMI version: develop (78b2d45 )
  SPT: 20190122 Nightly-Android

What does this web HMI do?

Hello,

I am running SDL core on Ubuntu, and I have loaded the HTML page which shows the head unit mock-up. What exactly does this web HMI do? How do I know if this is connected with the running SDL core? And what I can do with this web HMI to demonstrate core functions?

Thank you!!

Add third_party file

Add markdown file containing list of third party libraries information used within repo.

HMI shall show media app template instead of Navigation Panel when activates a media remote control app

Bug Report

HMI shall show media app template instead of Navigation Panel when activates a media remote control app.

Reproduction Steps

1. run sdl core and sdl hmi
2. register a remote control media app with sdl core with TCP ocnnection
3. from HMI activate the app

Expected Behavior

HMI shows media app template

Observed Behavior

HMI shows Navigation Panel

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: 5.0.0RC2
• HMI version: develop commit f134a7a
• TCP connection from app to core

[SDL 0109] SetAudioStreamingIndicator RPC

Proposal: SetAudioStreamingIndicator RPC

The proposal is about adding a new RPC for media apps to indicate the action of a play/pause button.

Review: smartdevicelink/sdl_evolution#334

Steering Committee Decision:

The Steering Committee voted to accept this proposal with the revisions outlined in the last comment from kshala-ford.

<function name="SetMediaClockTimer" messagetype="request">
  <param name="audioStreamingIndicator" type="AudioStreamingIndicator" mandatory="false" />
   :
</function>

The Steering Committee also discussed the scenario when a head unit doesn't receive an update from the app, and it was determined that the head unit would fall back to old behavior in this case.

The proposal .md was updated on March 14, 2018 to include the agreed upon revisions.

[SDL 0063] Display name parameter

Proposal: Display name parameter

This proposal is about deprecating the parameter displayType and replace it with displayName.

Review: smartdevicelink/sdl_evolution#184

Steering Committee Decision:

This proposal has been accepted by the Steering Committee. After much discussion about the displayName parameter, it was decided that the parameter should be kept as there are specific use cases where the parameter is helpful for OEMs, notably OEM-created apps. In the future, we may want to have the displayNames for certified head units recorded publicly for reference.

HMI desn't remove root 'data' element from policy table update file

Bug Report

Currently there is the following communication between SDL and HMI during Policy Table Update sequence in case of PROPRIETARY and EXTERNAL_PROPRIETARY flows.
SDL->HMI: BC.SystemRequest(file)
HMI->SDL: SDL.OnReceivedPolicyUpdate(file)

where file is path to policy table update file

It is assumed that policy update file is provided by cloud with data root element in case of PROPRIETARY and EXTERNAL_PROPRIETARY flows.
And HMI has to remove this root data element before sending SDL.OnReceivedPolicyUpdate notification to SDL.

Occurrences

Always

Reproduction Steps

1. Run SDL which was built with PROPRIETARY or EXTERNAL_PROPRIETARY flow
2. Connect and device and register new App => PTU is triggered
3. Check the PTU file that is provided in SDL.OnReceivedPolicyUpdate from HMI

Expected Behavior

PTU file doesn't contain root data element

Observed Behavior

PTU file contains root data element => SDL couldn't apply PTU

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: Release 5.0.0
• Testing Against: HMI version: develop

HMI must put applications to HMI level "LIMITED"

Bug Report
HMI must put applications to HMI level "LIMITED"

Precondition:

1. SDL and HMI are started.
2. Mobile app is registered and activated, HMI level = FULL or BACKGROUND

Steps:
Go to menu Apps.

Expected Behavior:
HMI level of application becomes LIMITED

Observed Behavior:
HMI level of application still FULL or BACKGROUND

HMI requires acknowledgement of popup to respond to startstream request

When a navigation app connects and start streaming the HMI shows a popup (

sdl_hmi/ffw/NavigationRPC.js

Line 318 in 822b808

var text = "Would you like to start Video stream?";

) asking the user to accept the streaming. If the user does not press ok in roughly 4 seconds, sdl_core will cancel the streaming of video. The connection between the cancellation of streaming and the popup is not easily visible especially because the video streaming already starts, so the user can easily miss the popup.

We should remove the popup as it does not provide any benefit to the user.

SDL 0188 - Interior Vehicle Data Resumption

Proposal: Interior Vehicle Data Resumption

This proposal is to restore Interior data subscriptions on application registration after unexpected disconnect or ignition cycle.

Review: smartdevicelink/sdl_evolution#554

Steering Committee Decision:

The Steering Committee accepted this proposal with revisions on 8/1/2018. Revisions were made on 10/9/18.

SDL 0204- Support running the same app from multiple devices at the same time

Proposal: Support running the same app from multiple devices at the same time

This proposal proposes that SDL shall support running the same app from multiple devices at the same time. Currently, SDL only allows one instance of the same app to register with SDL. However, there are valid use cases for running the same app from two or more devices at the same time.

Review: smartdevicelink/sdl_evolution#618

Steering Committee Decision:

The Steering Committee voted to accept this proposal with revisions. The revisions will include updating the descriptions of ttName and vrSynonyms as discussed in this comment.
In addition, the author will address numbers 2 and 4 in this comment.
• 2. I would specify in proposal that after policy update, it will be applied for both of registered applications
• 4. Application on different device should share same usage statistics, because they use same policy app_id. this should be added to the proposal.

Revisions were made on 11/21/18

HMI does not update LIGHT rgb color

Bug Report

HMI does not update LIGHT rgb color

Reproduction Steps

1. register and activate a remote control app
2. send a valid SetInteriorVehilceData request to change color, for example

"moduleData":{"moduleType":"LIGHT","lightControlData":{"lightState":[{"id":"FRONT_LEFT_HIGH_BEAM","density":0,"sRGBColor":{"blue":0,"green":0,"red":0},"status":"ON"}]}}

Expected Behavior

color of FRONT_LEFT_HIGH_BEAM shall get updated on HMI

Observed Behavior

app get success response, but color is not update to new value.

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: https://github.com/smartdevicelink/sdl_core/tree/5.0.0_RC2
• test remote control regarding LIGHT

HMI shall not send a OnInteriorVehicleData notification if a parameter is included in the request but the value is the same as the current value

HMI shall not send a OnInteriorVehicleData notification if a parameter is included in the request but the value is the same as the current value (i.e. no change).
(This issue is applicable to all types of modules)

Steps:

1. mobile sends a valid SetInteriorVehicleData to HMI with some params that will be changed
2. HMI apply that changes and send OnInteriorVehicleData notification with changed parameters
3. mobile sends a valid SetInteriorVehicleData to HMI with the same params

Expected:
HMI doesn't send OnInteriorVehicleData notification because the params values are the same as the current values

Observed:
HMI send OnInteriorVehicleData notification

No DisplayLayout template "GRAPHIC_WITH_TEXT"

When app needs to SetDisplayLayout with template "GRAPHIC_WITH_TEXT", connected and tested with sdl_core and sdl_hmi, it response "UNSUPPORTED_REQUEST".
We searched in this repo, seems here only one template in UI.GetCapabilities that hmi can response for app request, whatever hmi_capabilities template supported in sdl_core side. Actually, totally 15 standard templates should be supported in hmi.

AlertManeuver pop-up with softButtons is not shown on HMI

Bug Report

AlertManeuver pop-up with softButtons is not shown on HMI

Reproduction Steps

1. HMI and SDL are started
2. Mobile app is registered and activated
3. Request AlertManeuver with softButtons

Expected Behavior

HMI shows AlertManeuver pop-up with softButtons

Observed Behavior

HMI does not show AlertManeuver pop-up with softButtons and sends response right after request is received.

OS & Version Information

• OS/Version: Ubuntu 16.04
• SDL Core Version: 5.0.1
• Testing Against: HMI 5.0.1

Add ElectronicParkBrakeStatus to sdl_hmi

Matches core issue: smartdevicelink/sdl_core#1815 and accepted evolution proposal smartdevicelink/sdl_evolution#303