I paired my phone with my car's bluetooth radio and noticed the following behavior:
- If I turn on my car radio and then turn bluetooth on on my One X, it will auto connect and start playing music.
- If I turn on bluetooth on my One X, get in my car and turn on the radio, my One X will not auto-connect. I have to go into the bluetooth settings screen and select my car's device name (CAR M_MEDIA) and then it connects and starts playing music.
I can turn on and off my One X's bluetooth repeatedly while in the car and it will connect each time, but it doesn't ever connect if I turn on and off the car's radio.
I tried a bunch of roms, including Stock, CleanROM and others in the development forum and finally I tried CM10. They all behave the exact same way.
Seeing that CM10 also has the issue caused me to give up and come here for help, because my Atrix 4G with CM9 never had this issue. I might try CM9 on my One X as a last resort.
Any help on this one?
What model/year car, and is it a manufacturer stereo, or a 3rd party head unit? Every stereo head unit and phone is a bit different, and some combinations simply don't play well together.
I have had the same issue with my 2012 Subaru Impreza, with factory stereo (non-nav version). Tried any of a variety of things (different ROMs, editing some of the BT config files), and nothing worked. Also have the issue that even when i manually connect it, it doesn't connect maybe 20% of the time. And when it does, the steering wheel controls to change the music track only works maybe half the time.
I called HTC support, had to escalate the issue to get anyone to listen to me, and they tried the usual (update phone firmware, safe mode) with no luck (not surprising). They said all they could do was log the issue, and hope that it gets addressed in a future update. Probably the most you can do is call HTC also, so they at least start to get the message that its a known issue. The HTC tech also mentioned it may be a feature that is disabled on purpose, due to a known security issue.
I think its a fault of the BT stack, which is HTC proprietary. On my old HTC Desire Z, newer versions of Sense seemed to work better with my car stereo BT. Unfortunately, with the One X, it seems they have taken a step backward. I also noticed on my old DZ that AOSP based ROMs worked better with my car stereo BT, and also displayed the track info (artist, title, etc) on my car stereo which is something that the HTC Bluetooth stack never does. So I assume it was a different non-HTC Bluetooth stack. So therefore, like you, I thought an AOSP ROM might fix the problem. I tried AOKP (ICS) but not CM9, and AOKP didn't help. Not being a dev, I'm not sure where the BT stack comes from in AOSP ROMs. On AOKP, the track info was not displayed on my car stereo, and the config files were the same as HTC stock, leading me to believe it was the HTC stack. Maybe somebody with more knowledge can shed some light on the matter of AOSP ROMs and the Bluetooth stack, as I've been wondering this.
My car is a 2011 Subaru Impreza. Coincidence? Probably not. I know the car does something different than my other Bluetooth headset because music starts when it connects to the car but not when it connects to my headset. I have to press play on my headset for the music to launch.
Also the headset auto connects reliably to my One X, no matter which one I turn on first, unlike my car. Perhaps a hint is there? Maybe some logs would shed some light on the problem?
Edit: just tried CM9, same result. I never did logcat so I'm not sure if that would help, would it?
Related
I'm looking at buying a new car and I tried playing music through a couple 2010 Toyota non-navigation radios. All the Android music/video players I tried would sound great for the first few seconds and then start a subtle warble/echo that continues until you pause/resume or switch tracks.
I've got an ADP1 currently running Cyanogen 4.2.11.1, but I saw the same problem with 4.2.9 and 1.6 (don't know about all the other various builds). I have several A2DP headsets and they always work fine (no warble).
I believe this Toyota radio is running Symbian OS from what I found on the web; and I'm going to try to see if Toyota has a software upgrade tomorrow. (I doubt it) Toyota does mention that most Bluetooth features are supported for the MyTouch, but doesn't mention A2DP either way. http://toyota.letstalk.com/brands/toyota-bt/home.htm
I'm downloading the whole Cyanogen tree and preparing to build it and then sniff through the code for buffer sizes and other likely suspects.
I just thought I'd pop this on XDA and see if anyone else has seen the same problem and found a solution.
Or does anyone know specifically where to look in the source to adjust buffer sizes and other things that might cause a warble with Bluetooth audio.
You should test before getting the car, ask the dealer if you can test the BT with the car when you get there.
I have been running A2DP on my Sony headunit for some time now. I have never experienced a warble on any of the roms I have used. I do get another issue however and maybe they are related. I can not stream stereo audio over BT to any device it seems, IF I also have my phones wifi enabled. As stated I do not get a warble, I get an audio drop for a few seconds every 30secs or so. This does not seem to happen if the headset is the only part connect, as soon as I connect the A2DP portions it starts up. Disabling wifi is my work around at present.
I have tried A2DP with/without WIFI enabled. No difference; still warbles.
Nothing interesting shows up in logcat.
I run A2DP through my ford focus with the microsoft sync system with no issues. Although the AVCRP does have issues. The control won't work after the phone goes to sleep.
The warble or echo may be due to an active system used to reduce road noise when using the phone hands free via bluetooth. Might check and see if there is a way of turning that off. Some of the foreign cars have active mics placed in the car that might cause this.
try an eclair rom (like manup456's 1.3)
BLUETOOTH IS IMPECCABLE ON THESE ROMS
it will work.
I tried turning off/on the auto volume; no help.
I'm not sure how to check/disable any bluetooth feedback; but it doesn't sound like that.
My friends Blackberry either worked fine (no warble) or was very very jerky (played quarter second, cut out a half second). And split its time about 50/50 between these modes.
I should mention the "warble" is not very pronounced, I can listen to most music without it making me crazy; but it bugs me.
Finally got all the stuff from git; now compiling the kernel.
I will try the compiled kernel tonight and if no luck there I may try the eclair rom mentioned; but I thought Steve's build already had most of the eclair stuff; maybe he is waiting on his experimental branch.
Edit:
oops, looks like a2dp stuff is not in the kernel....
I run A2DP on my kenwood deck. The only issue I experience is if I turn off the car and kill the stereo before killing my BT on my phone, my phone goes into freak out mode. I can't enable or disable BT untill I give a 3 finger salute and it just runs really slow. No warble, actually from CM 4.2.11.1 it sounds pretty damn decent.
I'm still trying to figure out how to compile the code from git; got the kernel and main tree compiled; but not the external apps (like a2dp).
Toyota gave me phone #s for Panasonic and somebody else who make the head units. So I am still pursuing a software update from that end as well. I'll call them next week after the holidays.
I've read thru the liba2dp.c code and have a couple ideas to try if I can figure out how to compile it (haven't really tried that hard, just looking for the official directions so I don't waste hours on something that is already known)
dude your doing too much work just try the eclair rom!!
Hey guys
Strange issue here. I paired my phone with my car through Bluetooth to make and receive calls using the car audio system. It works well.
However, if I fire Google Navigation, I can't here the spoken instructions through either the phone speaker or the car speakers.
I was not expecting navigation audio to be routed through Bluetooth audio, but I did expect the navigation instructions to come out of the phone speaker, as it does on the nexus one or the vibrant both running Android 2.2.
Is anybody else having this issue?
Thanks
Sent from my Nexus S using XDA App
bluetooth wont turn on
It just flashes the icon and does not turn on. From in settings same. Any ideas?
vapor311 said:
It just flashes the icon and does not turn on. From in settings same. Any ideas?
Click to expand...
Click to collapse
did you flash a new kernel or anything because the kernel in the dev thread is known to break bluetooth
if it does this stock out of the box try doing a system restore and then take it back if its still acting up because bluetooth should turn on
yea i used the pkg one that had SU etc on it. Suppose Ill have to flash back to stock arg.
just so peeps know with the bt issue flashing this fixed
http://forum.xda-developers.com/showthread.php?t=882333
Anyone?
Sent from my Nexus S using XDA App
Locking up slash rebooting while streaming bluetooth audio
Anyone else experiencing any sort of lockups rebooting streaming bluetooth audio. It seems like I can only get about 10 to 15 minutes streaming audio before the phone becomes completely unresponsive won't power on or anything
Sent from my Nexus S using XDA App
You should be thankful...I can't get more then 10 sec without it being cut off and play again...for...10 sec
what rom?
I had same issue once...i on CM7
Bluetooth doesn't stream audio to car - what's your experience
I've got a Ford Edge with the new Ford MyTouch/Sync system.
The Nexus S connects to the Bluetooth just fine; makes and receives calls perfectly. It will also connect to the Bluetooth Audio Stream for music playback, but won't play the audio over the car's speakers. Also, sometimes it connects, holds the connection for just a few seconds and then disconnects. My SGS and Nexus One work as expected, as does the iPhone, so it doesn't appear to be an issue with the car.
Seems like a bug in the NS to me.
I'm curious if others are streaming audio/music to their auto's BT system without issues?
It would be especially nice to know what anyone else with a new Ford/Lincoln is experiencing, but I'd also like to compile a list of what cars work and what don't.
I'm going to have to find some other BT device that I can test the stream on to see if my phone works with it or not. Maybe my Nexus One dock? I've never used that to stream audio even with the Nexus One.
In terms of troubleshooting my problem, I've already rebooted the phone and the car, un-paired and re-paired the phone with the car.
I've got a Mazda RX8 R3 and the NS will pair with the in-built car BT but drops the connection after a few minutes. It then refuses to connect again unless I re-pair, then a few minutes later it drops and we're back to square one.
The car's in-built BT worked fine with my HTC Desire, Hero, iPhone 3G and Blackberry 9700 so I'm guessing the Nexus S has a Bluetooth issue.
Mine works fine on my aftermarket Sony receiver.
having issues with bluetooth audio too, stream keeps breaking every now and then. Any fixes?
I've only streamed to the car stereo and had no issues. The phone is only about 10cms away.
Haven't tried my BT headphones yet, maybe range is the issue.
*On original ROM.
Mujja said:
I've only streamed to the car stereo and had no issues. The phone is only about 10cms away.
Haven't tried my BT headphones yet, maybe range is the issue.
*On original ROM.
Click to expand...
Click to collapse
tried placing the phone right next the the BT reciever and same problem. Only tried this once, maybe I'll try rebooting the phone.
no problem here
using Bionix 1.2
You're lucky, I can't even get BT music streaming to work with my car. No other BT devices to check with besides my Nexus One dock, which has no speakers.
BT works great for the phone, though, to make and receive calls.
Problem with Bluetooth
I cant get to work bluetooth on Nexus S.
When i enable it and try to send something from SGS to Nexus S it says me "This tranfer was canceled by the user" (Nexus S)
SGS says "Remote device rejected your request"
When i try send something from Nexus S, but use not function Send, i use function Bluetooth - it says me "The application Bluetooth Share (process com.android.bluetooth) has stopped unexpectedly. Please try again"
I tried factory reset, wipe cache, tried flash any other roms, but got NOTHING helpt me. I have this problem on 2 phones (2xNS).
Can someone give me files of BlueTooth share? (com.android.bluetooth)
That's an interesting problem you have. Mine did the same thing transfering from my computer to my NS. I just tried it again when I read your post (to make completely sure what the error was) and it has automagically fixed its self.
Well, seems i need a file \system\app\bluetooth.apk
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.
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
EDIT: KNOWN ISSUE https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/page/1/thread-id/299
Anyone else had any connectivity issues? 2013 Toyota 86 and i cant connect to the car stereo... may be time to get Android Auto, finally have a reason
But, in the meantime, i would love to hear from you if you've managed to connect.
2016 Ford Mustang GT with Sync 3. Android auto and bluetooth both work as expected with 0 issues (other than personally I think android auto blows monkey chunks.)
xkwizt said:
EDIT: KNOWN ISSUE https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/page/1/thread-id/299
Anyone else had any connectivity issues? 2013 Toyota 86 and i cant connect to the car stereo... may be time to get Android Auto, finally have a reason
But, in the meantime, i would love to hear from you if you've managed to connect.
Click to expand...
Click to collapse
Have a 2015 Camry Hybrid and don't have an issue connecting to my Entune Audio system.
14 Grand cherokee SRT with 8.4 Uconnect and no issues at all. My iphone 7 plus wont stream smoothly to my headunit (choppy audio) but the S8+ does.
No issues connecting to the aftermarket deck in my jeep or the factory system in my 2017 work Chevy Equinox.
No problem connecting with the radio on my 2016 RAV-4.
2011 civic. No issues other then it takes a little longer to connect than my last phone, and my car no longer displays artist/track info. Hopefully it'll get fixed in an update.
pizzlewizzle said:
2011 civic. No issues other then it takes a little longer to connect than my last phone, and my car no longer displays artist/track info. Hopefully it'll get fixed in an update.
Click to expand...
Click to collapse
Unfortunately, it won't happen. Samsung phones haven't displayed metadata on Civic stereos since the Note4. It's something about Samsung's custom Bluetooth stack when they upgraded it to Bluetooth 4.0; it doesn't offer full backwards compatibility. It will connect and play audio and even respond to controls via BT, but no metadata. And those apps that circumvent the issue by transmitting metadata in an alternate way, none of them work. We Samsung/Civic users have been fighting with this for a few years now to no avail.
And Honda doesn't put out updates for their stereos, so nothing will ever be fixed from their end. The only "solution" is to get a different stereo or a newer car. Or a new phone.
That's the worst part – every other phone works fine. iPhone, LG, Motorola, Pixel... It's just Samsung phones that don't play nice with older Honda stereos.
I am having an issue where call audio and contacts work between my T-Mobile S8 and Kia Optima EX 2012 with the Navigation/Infinity system, but no Streaming audio. There is no option on my phone for it, and I can Enable/Disable Streaming Audio on the car, pair, unpair, try different combinations, even factory reset the head unit and the Bluetooth on the head unit. Nothing so far. My car does show what's playing, but it still only plays through the phone and I can pause, skip, etc. from the car.
Anybody else had/has the same issue?
xkwizt said:
EDIT: KNOWN ISSUE https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/page/1/thread-id/299
Anyone else had any connectivity issues? 2013 Toyota 86 and i cant connect to the car stereo... may be time to get Android Auto, finally have a reason
But, in the meantime, i would love to hear from you if you've managed to connect.
Click to expand...
Click to collapse
I know you posted this a while ago - but I have never had issues connecting blue tooth to my personal car (BMW X1) - I also travel heavlily and I have never had issues connecting to a variety of different rental cars, Fords, Kias, Toyota, etc.
Hope you found a fix or got it working
Stock stereo in a 2014 Toyota FJ Cruiser. I have no problems connecting, streaming audio, or making phone calls. My audio streaming does play with a lot of cracks, but it still plays. I might mess with EQ settings but I haven't had a chance yet.
2015 WRX with stock stereo (no nav, non-Harmon version). Here are the seemingly random issues I have with bluetooth:
- Connects fine most of the time, but will sometimes connect and the audio will be muted and requires me to pause the track on my phone and then press play.
- Audio will cut out at times and revert to playing through the phone's speakers, but the phone will still be connected and call audio will play through the car speakers and I can still control the track next/previous with my steering wheel controls.
- Audio will not connect sometimes when my wife is in the car wearing her FitBit, even with my phone's auto discovery turned off and nearby devices turned off.
- Track info sometimes gets stuck on the currently playing track and will not change until the car is turned off, the app is closed and process killed, and connection is made again.
Like I said, these issues appear to be random and seem to get worse when someone else is in the car with me or when I'm wearing an Android Wear watch. I've played with every connection setting I can in my phone but I'm sure this all boils down to it being a crappy stereo system. Nothing like being on the freeway during the beginning of a long commute and having my music cut out on me and having to switch back over to the (ugh...) FM radio.
Sevael said:
Unfortunately, it won't happen. Samsung phones haven't displayed metadata on Civic stereos since the Note4. It's something about Samsung's custom Bluetooth stack when they upgraded it to Bluetooth 4.0; it doesn't offer full backwards compatibility. It will connect and play audio and even respond to controls via BT, but no metadata. And those apps that circumvent the issue by transmitting metadata in an alternate way, none of them work. We Samsung/Civic users have been fighting with this for a few years now to no avail.
And Honda doesn't put out updates for their stereos, so nothing will ever be fixed from their end. The only "solution" is to get a different stereo or a newer car. Or a new phone.
That's the worst part – every other phone works fine. iPhone, LG, Motorola, Pixel... It's just Samsung phones that don't play nice with older Honda stereos.
Click to expand...
Click to collapse
I have the same issue. Sound is clear, music plays fine, wheel commands work fine... even the contact list, which only showed partially (200 contacts or so), now shows all of them...
But Title/Artist/Album do not show up, only says Samsung S8.
How do I enable the metadata?
thunderdrome said:
How do I enable the metadata?
Click to expand...
Click to collapse
As I outlined in my post, you can't.
Why not?
I have the same issue, calls work, changing track, music playing, good quality of sound, contact info, full phonebook (on the S2 it was just 200 contacts or so).... but no media metadata! This is software issue and it seems that in other units than the Civic (maybe post AVCRP 1.3) it works...