After one ui 8 my car will no longer hold a connection via Bluetooth. (2010 Mazda 3) I've had this car for 15 years, never had a connection issue until now. My phone works with my work vehicle and my friends iPhone 13 has no issues with my Mazda. I can't figure out the conflict! I've tried removing the device and starting fresh, but nope. The weird part is my phone connection will connect, stay connected, but the audio toggle for music won't stay connected and takes multiple times to connect. If it does connect, after i turn off my car, it won't reconnect like before one ui 8. It always connected the 1st time and always connected if i turned my car off and on again. Sorry for the rant, but it's driving me crazy.
Same for me - Mitsubishi Outlander 2017 & S23. Was totally fine until the update so it's obviously something to do with that. Incredibly frustrating and makes me hate my phone & Samsung in general every time I get in my car now. Please fix it.
Hey all, so I have a 2012 Toyota Tundra, and "sometimes" I have Bluetooth Connection issues when connecting to the radio to play streaming music. Basically sometimes it connects and sometimes it doesn't and I have to unpair the Bluetooth and reconnect it, and then it usually works, however with a certain competitor it connects and stays connected flawlessly. What seems to be the problem, or is there a setting I need to change? Thank You.
If you've recently updated to the new OS, this is an issue that has been occurring since the first beta and no matter how many times I reported it they did not fix it
I reported this in every iteration of the beta for the S25+ and the issue has persisted into the stable release.
UI8 has a bug where Bluetooth connection to non-Android Auto vehicle stereo systems that use only Bluetooth is not functioning properly.
Auto connection never works and, on the occasions where it is able to connect after manual toggling, both audio and phone connections are prone to constant disconnecting.
This seems to be an issue on most non-Android Auto Bluetooth car stereos and is not limited to just Samsung devices, with Android 16 at large having this issue based on reports from Pixel users.
Despite months of reports from Android users of many manufacturers, this issue has persisted.
Could you explain the bug a little further because I have a old infotainment system with an s25 Ultra and the only problems I have had are with Android auto itself which has always been quite garbage and in fact have been needing to use my regular infotainment systems Bluetooth over the Android auto.... also in many cases the problem isn't actually the Bluetooth or your infotainment system it's actually Wi-Fi as the infotainment systems only connect the Bluetooth for basic functions but everything else is literally ran through Wi-Fi and that honestly has seems to be the issue but unfortunately there is nothing that Google or Samsung can do about that Wi-Fi is becoming an old source of material anyway in favor of NFC and newer technology it's kind of fading out as well as regular standard Bluetooth Stacks that we currently use if you're having an issue the only thing I can suggest is hardwiring for a while unless you give them much more detailed explanation on what's going on and I may be able to help you as this is what I do for a living
Like I said, this is about non Android Auto systems that connect solely through Bluetooth. The Auto connect function has ceased to work when it worked flawlessly pre update and disconnects constantly even when manually toggled to connect.
Usually phone calls might connect sometimes but audio will never work.
Could just be a flaw in that update that they'll fix in another system update other than that I'm not sure if it has nothing to do with Android auto itself or any Android infotainment systems unfortunately I've never used a non Android infotainment system before no car I ever purchased had one standard I've always used aftermarket the only thing I can suggest is maybe do a full system cash reset and try that if you don't know how to do that I can walk you through it
Already tried by myself and hundreds of others. It's definitely some issue baked into Android 16 itself that has yet to be solved and like I said, it's not relevant to Android Auto
