Car Stereo Bluetooth Issue Remains

[CrymsonDawn]

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.

[realaud]

Why does Samsung have to address the issue?  You said in your original post that this has been reported across all brands and came with the Android update, which is solely on Google.  It is also a Bluetooth issue,  and Samsung neither owns nor controls Bluetooth.  So, it seems to me that *Android* is not playing nice with Bluetooth, not Samsung's UI or hardware.

Have you ever bothered putting in an error report?

[CrymsonDawn]

You've condescended to me before, not sure what makes you think that's constructive.

I've put in tens of reports, as recently as yesterday, to both Google and Samsung.
As the manufacturer, Samsung has responsibility to at the very least address that this is an issue that is occurring and explain how they are working with Google to fix it. They chose to go ahead with an intrinsically flawed Android version despite knowing about this major issue.

Please take your unhelpfulness and blind defense of irresponsible business practices elsewhere

[realaud]

If you feel condescended to by anyone who responds to you with a comment you don't accept, that's on you.  Perhaps they went ahead with this "intrinsically flawed" Android version because NO ONE reported during the beta.  And the fact remains, Google is responsible for Android - it's development and deployment.  If this was an issue ONLY affecting Samsung phones (and affecting EVERY) Samsung phone, then one could consider that Samsung holds responsibility. Since your own statement says that it's happening across  all manufacturers, then it is not strictly a Samsung issue.  Since the Android 16 update has been distributed to millions and millions of phones, and only a fraction of phones are affected by this, it may be harder to suss out the cause - especially if people are relegating themselves to complaining on reddit and not contacting their own manufacturers and/or Google.  

I would have no way of knowing whether  you put in any, or a thousand, error reports on this unless you stated as much.  Many people come here to write their complaints to Samsung without ever bothering to put in an error report.

[Andreeeeei]

What a clown? How can it not be Samsung's responsibility too? People paid for their device and it should work as inteded - in this case as it did pre-update.

If Google pushed Android 16.1 that rendered half your display useless and Samsung went along with it, you'd be fine with that?

🤡 

[realaud]

I would blame and contact the proper entity.  Not knowing which entity was responsible (unless there were complains across all manufacturers), I would put in a PROPER error report with both entities and wait for a fix.  I know what goes into reading code logs and programming, and recognize that fixes do not happen at the snap of the fingers, as much as users may want it to.  It's work, not magic.  Without logs being submitted to the programmers, they cannot determine a common denominator; without determining the common factor, they cannot issue a blanket fix.

[Andreeeeei]

This §hit needs to be fixed yesterday.

[TheDudebro]

Yes its all the time

[Tasha84]

My Galaxy S25 is not connecting to my Android Auto now. It did at one point today then plugged it back in and it didn't. It keeps saying make sure I'm using a port with the phone icon in it which I am. I'm not sure if this is an issue with the recent update? Android Auto will not even detect. I thought maybe it was a fuse to the port so completely changed it out and still didn't work. Unpaired and phone and deleted it in the system and readded and it and I still get the same message. I am only ae to connect using Bluetooth. 

[BlueSkies]

Have you tried change the cable? I would try to restart the phone and then try to connect. Sometimes a good restart will do the trick if it is previously working

[Tasha84]

Forgot to mention, I did restart my phone as well as tried a different cable. Neither changed the outcome.