-
Notifications
You must be signed in to change notification settings - Fork 243
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
Add SDL version info in BasicCommunication.GetSystemInfo Response #9
Comments
What type do you think system version should be? |
Something like "SDL_RB_B3.6_{build number}", I can see a CCPU version left blank in system info response. Is it intended to indicate the SDL version? |
Oops, I didn't realize this was already an issue. I would suggest we also add a new field alongside syncMsgVersion so we can eventually deprecate that field which will indicate the version in the register app interface response. |
We added sdl version and system software version to register app interface response to communicate this information. It sounds like the proposal is to also add this information to be sent to the HMI. |
@henry-fan Can you let us know if that information in the register app interface being communicated to the application is enough for your system diagnosis purposes or whether it needs to be on the hmi? |
@justinjdickow |
@henry-fan Do you know if this was ever resolved? |
@justinjdickow |
Media manager build fixed
Media manager build fixed Related-issues: APPLINK-22713, APPLINK-22716
REVSDL-881: fix on RSDL's side: close client's port.
@henry-fan I think this is partly covered by https://github.com/smartdevicelink/sdl_evolution/blob/master/proposals/0096-deliver-build-configuration.md If this solution does not satisfy your needs please consider submitting a proposal to the sdl evolution repository. |
…in_request_SubscribeButton Missed mandatory parameter `appID` in request SubscribeButton was added.
Head unit wants to show SDL version in system diagnosis. Suggest we add SDL version in HMI protocol GetSystemInfo.
The text was updated successfully, but these errors were encountered: