search

nisargjhaveri / WirelessAndroidAutoDongle

Use Wireless Android Auto with a car that supports only wired Android Auto using a Raspberry Pi.
MIT License
331 stars 43 forks source link

Re-connect doesn't work properly #23

Closed gamelaster closed 4 months ago

gamelaster commented 7 months ago

(will add description later, just adding it on phone so I don't forget :D)

GreenZeeGuy commented 7 months ago

Many thanks to the global team for this fantastic project!! I have been facing the reconnect failing issue a few times with the v0. 2.0 release . Looking forward to the new release with the fixes!

nisargjhaveri commented 7 months ago

@gamelaster, @GreenZeeGuy Could you please add some more info on the issue you're facing? What do you mean by reconnect in this case?

gamelaster commented 7 months ago

@nisargjhaveri Of course I forgot, sorry :rofl: . The thing is, that sometimes, when connection drops, or initial connection times out, the re-connect mechanism (if there is any for specific situation), will not kick in, and only solution is to re-plug the device.

GreenZeeGuy commented 7 months ago

@nisargjhaveri I am facing the same issue that @gamelaster mentioned. I see that there a couple of changes / updates where merged... I will be happy to test out a new release image on the RPi Zero 2W once it becomes available ...

nisargjhaveri commented 7 months ago

For the initial connection timeout, there is no re-connect mechanism as of now, need to fix this. If the connection drops due to USB failure, it is supposed to reconnect. TCP failures are not yet handled very well. Though, if you can get the logs out when it fails to reconnect after connection drop, it'd be super useful to know which scenario is failing.

GreenZeeGuy commented 7 months ago

I am in my car and see that now the AAwireless Bluetooth device does not even show up in my phone scans... I see that there is a AAwireless Dongle Wifi AP in the phones list... How can I get you the logs?

nisargjhaveri commented 4 months ago

The initial connection failures are handled better with some of the recent commits in main. And handling disconnection after a successful connection is tracked with #26.

Closing this for now. Feel free to reopen if you still face this with builds from latest main.