Android Auto not woking

Question

Android Auto not woking

Opened this issue 8 months ago · 7 comments

I tried to see if wireless Android Auto works. However, as soon as I turn it on, there's no music anymore.

I still have to test it with a cable. I will write an update here to let you know if it works with that.

Answer 1 · 2023-11-07T12:25:35.000Z

I have similar problem too. When I activate jamesdsp while connected to Android Auto wirelessly, the sound starts coming out of the phone's internal speaker.

Answer 2 · 2023-11-07T17:45:15.000Z

I have now also tested it via cable. Unfortunately it doesn't work either. I can't hear anything whether via cable or wireless. I don't hear anything from my phone either

Answer 3 · 2023-11-11T19:02:36.000Z

with a cable I also hear it from the phone's internal speaker.

Answer 4 · 2023-12-02T14:05:43.000Z

I just tried the root version on my older android phone with AA, it works both wirelessly and wired. So it could be possible that AA processing isn't possible with the rootless option. Viper4Android also works with AA, not sure if this is possible without root. Wavelet does work with AA, but is lacking in effects though.

Answer 5 · 2023-12-17T03:41:36.000Z

Any way to disable the app when Android auto is active (or maybe only activate it when our headphones are active)

Answer 6 · 2024-01-13T04:09:15.000Z

I am experiencing the same issue (running under Shizuku). It seems AA uses a different audio "pathway" compared to a regular car Bluetooth-based media output connection.
My car actually shows an AA connection and a BT one (for the same phone) as distinct media source selections. Another relevant system-level difference I've noticed is that under AA, the media output device remains the internal speaker, with the car BT system not even showing up as an available output device. This obviously causes RootlessJamesDSP to stay on the "Internal Speaker" profile, with the additional wrinkle of breaking the AA audio connection and rerouting the audio to the phone speaker.

Answer 7 · 2024-01-13T06:19:20.000Z

I am experiencing the same issue (running under Shizuku). It seems AA uses a different audio "pathway" compared to a regular car Bluetooth-based media output connection. My car actually shows an AA connection and a BT one (for the same phone) as distinct media source selections. Another relevant system-level difference I've noticed is that under AA, the media output device remains the internal speaker, with the car BT system not even showing up as an available output device. This obviously causes RootlessJamesDSP to stay on the "Internal Speaker" profile, with the additional wrinkle of breaking the AA audio connection and rerouting the audio to the phone speaker.

you are absolutely right