Skip to content
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

Ending Communication Flow #3

Open
justinjdickow opened this issue Feb 25, 2015 · 0 comments
Open

Ending Communication Flow #3

justinjdickow opened this issue Feb 25, 2015 · 0 comments

Comments

@justinjdickow
Copy link
Contributor

Need to find out the following:

We know that services need to be closed with the end service control frame with 4 bytes in the payload that is the hashID. Does this hash ID always come from the payload of a StartServiceACK or is there some other way of getting it for different versions of the protocol?

Can a head unit close the communication session or does it always originate from the phone with an EndService? (What is the behavior when a vehicle turns off while the app is still connected?)

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

No branches or pull requests

1 participant