After updating to One UI 8.5 Beta 2, wireless Android Auto no longer stays connected. It launches normally, but within a few seconds the phone turns off Wi‑Fi, disconnects from the car, then reconnects and repeats the same loop.
This behavior did not occur on:
- One UI 8.5 Beta 1
- One UI 8.0
- One UI 7.x
- USB Android Auto (still works normally)
The issue appears to be Beta‑2‑specific Wi‑Fi Direct instability, as Wi‑Fi is shutting off automatically during the AA session.
Steps to reproduce:
1. Connect S24 Ultra to vehicle using wireless Android Auto
2. AA launches successfully
3. Within seconds, Wi‑Fi turns off automatically
4. Phone reconnects to Wi‑Fi → AA restarts → disconnects again
5. Loop repeats indefinitely
Expected result:
Wireless Android Auto maintains a stable Wi‑Fi Direct connection as in previous versions.
Actual result:
Wi‑Fi shuts off during the AA session, causing continuous disconnect/reconnect loops.
I believe that based upon the phones router log that it is actively deactivating the connection.
DEAUTH (TX) reason=3 [vdev_id=0]
So, your observation is totally worth exploring!
Quick Share (especially the “Apple device sharing” toggle) rides on top of the same underlying pieces that I found:
- Wi‑Fi Direct / P2P - Discovery / advertising - Background radio management
So in theory:
- If Beta 2 introduced new logic for Apple‑style sharing (AirDrop‑like behavior), - And that logic is buggy or overly aggressive about owning/recycling the P2P interface,
…it could be stepping on the Wi‑Fi Direct session that Android Auto is using and causing those local DEAUTH reason=3 events.
I'll report back what I find by toggling off the Apple sharing. Thank you!
Disabling ‘Share with Apple devices’ in Quick Share immediately stops the DEAUTH loop and restores stable Wireless Android Auto. This strongly suggests a conflict between the new Apple‑sharing P2P logic and Wi‑Fi Direct sessions.
So nice to have AA wireless back in action!
Team Samsung, I sent the system and WiFi logs. Your engineers now have a reproducible scenario and solution to follow and hopefully fix the issue in short order.
