I upgraded to s22 ultra from s21. When I get into my car my Bluetooth pairs with my phone for CALLS automatically, however not for AUDIO (both connect on its own once in a while) . I have to manually go into Bluetooth settings and switch on manually. This is annoying since I have a job where I'm in and out of my car. This was never an issue with my previous phone (S21)
Things I have tried but no luck.
In Bluetooth app settings clear data.
In Bluetooth app setting unpair and delete every device in memory.
In Bluetooth agent setting - change battery saving mode to unrestricted from optimized
Hmmm that seems strange.. Maybe try making sure auto is checked in the bluetooth seetings. I have the same phone and I'm not experiencing audio issues.
maybe try running a routine for the bluetooth
There is definitely something wrong with BT in the latest firmware. I occasionally get volume drops and those are huge drops. This bug happened in one or two previous firmware too, got sorted out, but in the latest there is it again. I hope it will be fixed ASAP.
Is it a Ford ?
You have to manually select the phone in Source to play audio or anything else.
Calls take priority over any setting, so they work always without an issue.
JazonX said:
Is it a Ford ?
You have to manually select the phone in Source to play audio or anything else.
Calls take priority over any setting, so they work always without an issue.
Click to expand...
Click to collapse
It's an aftermarket Bluetooth added to an old Honda via peripheral plugged into the stock cd player unit. I am going to try and disconnecting the battery terminals for 30 mins so I can reset the Bluetooth unit itself.
When I have my car bluetooth device connected as "audio" only, then I have to manually connect to it from my phone.
When I have my car bluetooth device connected as "audio & calls" , then the s22 ultra connects automatically
I recall reading that audio+calls connects automatically
Audio only requires manual connection
I drive a 2017 Ford F150 but I think its not a Ford issue
Related
OK, so I am curious as to whether or not anyone else is having issues with the A2DP performance on this guy. When it works its great, sounds pretty good for BT. But here are two issues I have found.
When playing music over bluetooth, get/make a call it switches to handsfree fine, but when is switches back it the music clips on and off.
2nd. It seems to only pair with one A2DP device. I have a blackberry bluetooth gateway which works great. But when I pair it to my pioneer head unit, it only connects to the hands free profile, not A2DP. My deck works fine on all my other devices. I have to delete both pairings, reboot, and re-pair.
Idk but are they Bluetooth 4.0 compatible?
Hey,
So I do not have my HOX yet but your problem reminds me of another issue with bluetooth on some other phones.
Try this when you set up your pairings make sure you pair it FIRST whit the device you want to do A2DP streaming on (probably your head unit) then set it up with any other devices. Some times some phones or bluetooth head units will only connect A2DP with the first devices that it is paired with (what is some times considered the primary device).
Also when it cuts out on your rather than messing with your phone shut off your head unit or BT mount for like 15 seconds and turn it back on. Also toggle it off on your phone then toggle it on after the units are powered up. I had that bug with music after a call happen a lot in the past but it turned out it was my BT unit on my visor (it needed a firmware update) but still shutting it off would usually fix it.
EDIT
Also see if you can update the firmware on your BT units. If the phone is using 4.0 and they are using 3.0 there could be some comparability issues.
I have issues with my bluetooth also. Sometimes it just won't connect to my car's bluetooth. Usually it seems like it happens when it connects then i turn off the car, then when i go back in the car(like running in to the store real quick then coming back out) and it wont' reconnect unless I restart the phone. Not sure what the problem is.
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
crabapples said:
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
Click to expand...
Click to collapse
I feel ya, in the past, all I had to do was toggle BT on and go, now there's two or three extra steps which almost defeats the use of a toggle.
I just started searching for some answers and am honestly surprised no one else has made a big deal about this. If I find something, I'll post it up... For now, going to take a look at some system files and build.prop stuff, but it's not really my department.
Got some NFC tags and NFC Task Launcher hoping I could circumvent the BS with a hardware hack. But no, the best this does is auto toggle the BT radio and open the device selection screen where 2 more taps are required to actually use the device for media audio. Any new insight out there? Considering Tasker app but it is rather expensive and no free version to see if it does the trick.
My Bluetooth Auto Corrects Just fine to my cars Bluetooth... Toggle on and go. Running AOKP currently but it worked properly on stock, stock rooted, and Synergy as well.
I haven't gotten a chance to try this yet but I probably will tomorrow.
Tasker forum post indicating the problem is well known, prevalent and hardly any fixes exist:
https://groups.google.com/forum/?fromgroups=#!searchin/tasker/bluetooth$20audio/tasker/TLsjT9Exle8/ZLlgvEn5vUUJ
An app that forces the connection amongst other things:
https://play.google.com/store/apps/details?id=a2dp.Vol
A Tasker plugin leveraging the force connect code which happens to be GPL'd in case any of our fine developers would like to start making ROMs that address this major drawback of using a S3:
http://code.google.com/p/a2dp-connect/
crabapples said:
I haven't gotten a chance to try this yet but I probably will tomorrow.
Tasker forum post indicating the problem is well known, prevalent and hardly any fixes exist:
https://groups.google.com/forum/?fromgroups=#!searchin/tasker/bluetooth$20audio/tasker/TLsjT9Exle8/ZLlgvEn5vUUJ
An app that forces the connection amongst other things:
https://play.google.com/store/apps/details?id=a2dp.Vol
A Tasker plugin leveraging the force connect code which happens to be GPL'd in case any of our fine developers would like to start making ROMs that address this major drawback of using a S3:
http://code.google.com/p/a2dp-connect/
Click to expand...
Click to collapse
I haven't had any trouble with bluetooth devices reconnecting to my phone as soon as I power them on. I'm running cyanogenmod 10 rom.
Also you can get free trial of tasker from here tasker.dinglisch.net/download.html
zxsix said:
I haven't had any trouble with bluetooth devices reconnecting to my phone as soon as I power them on. I'm running cyanogenmod 10 rom.
Click to expand...
Click to collapse
It seems the issue may be primarily with BT Audio Gateways. I don't have this issue with my laptop at all and I'm imagining car head units rarely see this problem.
That said A2DP Volume App fixed this issue for me. Once configured I did have to manually set the device to use media audio one last time before A2DP Volume started doing it for me. I configured NFC Task Launcher to kill wifi, enable BT and launch A2DP volume when it contacts the tag in my car and it works perfectly. Since NFC Task Launcher front ends into Tasker and Tasker has the A2DP force connect plugin available I'm seriously considering getting Tasker for all the other cool features it can do besides scratching this particular itch.
crabapples said:
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
Click to expand...
Click to collapse
You can fix this relatively easy by getting the app Tasker. I use it to do things like automatically start the music player I want when headphones are plugged in, to turning up the brightness automatically when I am getting an incoming call, etc. I am fairly certain you could set up the program to do whatever you want via bluetooth if you fiddle with it.
Gluck!
mdt73 said:
You can fix this relatively easy by getting the app Tasker. I use it to do things like automatically start the music player I want when headphones are plugged in, to turning up the brightness automatically when I am getting an incoming call, etc. I am fairly certain you could set up the program to do whatever you want via bluetooth if you fiddle with it.
Gluck!
Click to expand...
Click to collapse
LOL, if you had only read the rest of the thread...
Yeah, Tasker cannot do this OTB but with the A2DP Connect Plugin it can. Or you can just run the A2DP Volume app and do the same for free.
That the A2DP Connect code is GPL it would be super sweet if our developers incorporated the magic into the ROMs so that a base install didn't need apps to do something so simple as automatically route media audio to BT gateways.
This happens to me when I use the wrong settings in my cars head unit. My Toyota gives me the option to pair as a multimedia device, a phone or both. If you set it up as just a multimedia device then you won't have some functionality. Check your head unit manual and try to re-pair. You might have to delete the existing pairing for it to work right.
rfmodeler said:
This happens to me when I use the wrong settings in my cars head unit. My Toyota gives me the option to pair as a multimedia device, a phone or both. If you set it up as just a multimedia device then you won't have some functionality. Check your head unit manual and try to re-pair. You might have to delete the existing pairing for it to work right.
Click to expand...
Click to collapse
Yeah, it's not a head unit, it's an audio gateway that basically is just a BT receiver with a stereo out and no interface so it is what it is with no configuration options. This issue with the S3 appears to be primarily related to these types of devices.
crabapples said:
Yeah, it's not a head unit, it's an audio gateway that basically is just a BT receiver with a stereo out and no interface so it is what it is with no configuration options. This issue with the S3 appears to be primarily related to these types of devices.
Click to expand...
Click to collapse
Oh okay. When I look under the bluetooth menu in CM10 I have a paired connection that I named Car Multi-Media and if I look at its settings I see profiles called Phone audio and Media audio. I'm guessing you just have a Media audio profile. Not sure how to help you there. Sorry.
Whenever I connect my phone by Bluetooth to my car's stereo, only the front speakers work, nothing from the 2 rear speakers. I've tried adjusting the fade and checking settings in poweramp but still nothing. I'm not sure if this would be an issue with my phone, the ROM, or the car audio system. I'm thinking it's an issue with the car's audio but I figured I'd ask here in case somebody else has had the same issue. I am on liquid smooth 3.0 April 24th build with elemental x kernel but I had the same issue with my galaxy s4
Sent from my Nexus 5 using XDA Premium 4 mobile app
Audio !!
Digital_Fidelity said:
Whenever I connect my phone by Bluetooth to my car's stereo, only the front speakers work, nothing from the 2 rear speakers. I've tried adjusting the fade and checking settings in poweramp but still nothing. I'm not sure if this would be an issue with my phone, the ROM, or the car audio system. I'm thinking it's an issue with the car's audio but I figured I'd ask here in case somebody else has had the same issue. I am on liquid smooth 3.0 April 24th build with elemental x kernel but I had the same issue with my galaxy s4
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no problem with nexus 5 and my car Bluetooth connectivity.
Make sure that your audio system, GPS and make and model are compatible with the bluetooth from the phone. Some other connectivity issues are that the car kit cannot decode the Bluetooth device that it is trying to connect. This decode means that the system cannot recognize the name. This is a frequent problem when devices have been upgraded. While your system may have worked fine before, upgrades can cause problems because the compatibility all of a sudden changes. This is an issue that has not really been addressed by the manufacturers.
Another frequent problem that can occur is that the Bluetooth will connect but then it will not stay connected and only one speaker is running,. Many times this can be a hardware issue.
So the bluetooth device can connect but it does not work properly. In this case there is an issue with the stereo connection to the Bluetooth unit. There is nothing actually wrong with the bluetooth or devices but this is a software issue. To fix it see if the manufacturer is offering any updates. If one person has had the issue then you can bet that many people will have the problem. This is a problem with the car kit software as no matter which phone or earpiece you use the audio will not play from the speakers. Check that the vehicle supports bluetooth audio as some only will support bluetooth phone calls. These are 2 very different things.
Most of the time, look into the settings for the bluetooth and the car system. If the car battery should die then the system may reset to the defaults. This means that all of the current settings will be lost and need to be reset. Not only will you need to check the settings in the car system but also in your phone or other bluetooth device. In order to correct the bluetooth settings the device will need to be connected to the computer.
joannn said:
I have no problem with nexus 5 and my car Bluetooth connectivity.
Make sure that your audio system, GPS and make and model are compatible with the bluetooth from the phone. Some other connectivity issues are that the car kit cannot decode the Bluetooth device that it is trying to connect. This decode means that the system cannot recognize the name. This is a frequent problem when devices have been upgraded. While your system may have worked fine before, upgrades can cause problems because the compatibility all of a sudden changes. This is an issue that has not really been addressed by the manufacturers.
Another frequent problem that can occur is that the Bluetooth will connect but then it will not stay connected and only one speaker is running,. Many times this can be a hardware issue.
So the bluetooth device can connect but it does not work properly. In this case there is an issue with the stereo connection to the Bluetooth unit. There is nothing actually wrong with the bluetooth or devices but this is a software issue. To fix it see if the manufacturer is offering any updates. If one person has had the issue then you can bet that many people will have the problem. This is a problem with the car kit software as no matter which phone or earpiece you use the audio will not play from the speakers. Check that the vehicle supports bluetooth audio as some only will support bluetooth phone calls. These are 2 very different things.
Most of the time, look into the settings for the bluetooth and the car system. If the car battery should die then the system may reset to the defaults. This means that all of the current settings will be lost and need to be reset. Not only will you need to check the settings in the car system but also in your phone or other bluetooth device. In order to correct the bluetooth settings the device will need to be connected to the computer.
Click to expand...
Click to collapse
I have an aftermarket Kenwood double DIN deck with Bluetooth 2.1. It connects perfectly fine, shows up with Nexus 5 when pairing, shows the song title, shows the name of the person calling... It works great when plugged in through the aux port, but of course doesn't show me any information that way. When I had the S4 it showed up as SGH-M919. It stays connected just fine and I had it playing for a while before I tried turning up the volume and noticed it didn't sound right and figured out the rear speakers weren't playing.
I just checked and noticed there is a somewhat recent update on Kenwood's site but it was still about 3 weeks before I bought the deck... I'll try doing that though. (edit) just checked again and the update isn't for my model, there's no software for it
Thank you for answering since I'm pretty sure now that it's a problem with the stereo and nothing to do with Android lol
Kind of embarrassed to admit it but...I did have Car Toys install it so... they probably didn't do a very great job. I knew I should have had either Best Buy do it or tracked down a friend that could do it. Oh well
Hi, I recently flashed my phone (Galaxy Note 3) with CM 11 and my Galaxy Gear with null_23.
I connected the two of them via Bluetooth and everything seemed to work perfectly, until someone called me...
That was when I noticed that my phone forwards my audio to my gear speakers as it counts equivalently to any bluetooth earpiece. I tried unchecking Phone audio profile in bluetoth device settings but that completely disconnects my gear. (I should probably also mention the reason I want them connected is cause I'm using Bluetooth tethering for internet access on my gear).
I tried using an app I found called SoundAbout that forced audio device but it did so by (unchecking phone audio profile?) disconnecting the gear entirely.. which is not preferable.
I have been trying to search around for any info on how to do this, but all I've ever found has been to do the opposite, force bluetooth over other outputs.
Currently I have to change the output manually every time I answer/call someone, which takes a few sec where the other party wonders why I'm not responding..
I thought I would be able to change default phone audio output in my phone app or something, but no, no such setting is available.. its frustrating to be stuck with so little customisation even after invreasing it with a custom ROM... dang..
Thanks for any help!
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.
I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.
Car connections too but was not present in omni
I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.