-
Notifications
You must be signed in to change notification settings - Fork 90
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
Wireless AA over CMU hosted access point #172
Comments
Okay, I see that last year auto detection of phone IP was added with netstat function and some regex. It overwrites the IP in headunit.json which I assume is later used to connect to phone. Is there any clean way to hardcode phone IP at this moment? |
Okay. I tried replacing But it didn't seem to do the trick although arp -an returns proper list of devices connected to wifi AP. Ideas anyone? |
Would love to see this feature as putting your phone into wifi hotspot every time is a pain and having it automatically connect to the car AP would be great. |
I am looking into this, as https://github.com/opencardev/openauto/blob/crankshaft-ng/src/btservice/ looks like they have managed to implement it, so the Android Auto communication part has been solved. I have some code in testing that sets up the needed bluetooth service, and I am working on getting it to the part of actually communicating the access point name and settings to AA on the phone. The other major change is I believe the way AA works is it will open a connection to the head unit, which is the opposite of the way we do it now. |
I have a proof of concept of this working, I think :D |
@silverchris can you share some of the steps you followed? |
Not entirely sure if it's an issue or intended behaviour but while wireless AA works with hotspot provided by phone it won't connect if hotspot is provided by CMU using AIO AP settings. I was able to successfully connect my phone to this AP but using "Start server..." in AA application on phone yielded no result. Can this be implemented in future?
The text was updated successfully, but these errors were encountered: