-
Notifications
You must be signed in to change notification settings - Fork 32
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
Does not get recognized by Car Head Unit #32
Comments
@PatrickChenHZ @tomasz-grobelny It's most likely due to the expired phone key: f6c2338 . As the commit message says: |
see also #15 (comment) |
Don't believe it is a Phone Key issue, I actually had to use a non-expired key that I asked from someone in the #15 to get it recognized by Android Desktop Head Unit, though interstingly after updating the key the walmart radio starts attempting to negotiate, just never succeeds. The two actual car I mentioned above demonstrates exactly the same behavior as before. |
Any progress? |
I was able to get it recognized by Google's official Desktop Head Unit (DHU), and all negotiations went through, but it would stuck at "waiting phone" with no image displayed at all(I am testing without anbox so I modified the script to have the image test pattern feed into the video pipeline).
I assumed it is an issue with DHU so I went out to try it on my two cars and they would just either never recognize AAServer at all(2022 Chevy Bolt), or recognize AAServer and it is compatible with Android Auto but never start AA negotiation(2023 Mercedes). And Server.log verify that in these cases negotiation never started, only
I assumed my cars might be "too" modern and went out to buy a Walmart Radio to test it on, and got a head unit that was released 2020 with wired AA/Carplay support. And it does the same thing as my Chevy, which is it just never sees AAServer. I tried to modify the USB PID&VID to the same as my Samsung phone, assuming the head unit think AAServer is not legit. but it did nothing.
Anybody had a similar experience with it? Or any possible solution to resolve it?
Thanks,
The text was updated successfully, but these errors were encountered: