Skip to content
New issue

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

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

Already on GitHub? # to your account

Expose pcmCapabilities Parameter #714

Closed
theresalech opened this issue Aug 28, 2017 · 0 comments
Closed

Expose pcmCapabilities Parameter #714

theresalech opened this issue Aug 28, 2017 · 0 comments
Labels
bug A defect in the library
Milestone

Comments

@theresalech
Copy link
Contributor

We need to expose the pcmCapabilities parameter from the RegisterAppInterface response.

This was decided during the August 22 Steering Committee Meeting.

Additional details:

smartdevicelink/sdl_core@88e0560

This parameter is an extension of AudioPassThru capabilities used for mobile navigation. The system sends separate capabilities in case the channel has something different than AudioPassThru. Core does send this information back, but the mobile SDK is not consuming and/or making available. By default, the expectation with moblile navigation partners is 16khz and 16 bit. Ford recommends formally exposing this through APIs in SDKs.

@joeljfischer joeljfischer added this to the 5.0.0 milestone Aug 28, 2017
@joeljfischer joeljfischer added enhancement bug A defect in the library and removed enhancement labels Aug 28, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug A defect in the library
Projects
None yet
Development

No branches or pull requests

2 participants