I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
mpkrcl said:
I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
Click to expand...
Click to collapse
I just changed from a 2.3 device to a droid mini running 4.4. I have the same problem. I've contacted Isimple to open a ticket and hopefully see if they will release a patch to flash the isimple connect gateway with. The droid mini works without issue with a bluetooth speaker that I connect to - but does not work properly in the car.
The symptoms are slowed audio, and crackling.
mpkrcl said:
I just got a new VZW Moto X, (4.2.2) and while trying to stream bluetooth audio to my car stereo via an isimple connect kit (ISHD651), I get a very annoying static/crackling sound, which makes listening unusable. My old phone (HTC Droid Incredible 2) (2.3.7) worked great, with no issue whatsoever. However, the Moto X does work fine with my wife's car stereo (Pioneer DEH-X9500BHS). This seemed very strange, so I did a bit of investigating with a bunch of our devices. The Droid Inc2 (2.3.7), Nexus 7 (4.3), and Wikipad 7 (4.1.1), all worked fine. My Acer A500 (4.0.3?) and the Moto X both exhibited this crackling with my iSimple Connect car kit, but worked fine when streaming to other devices.
Has anyone else seen this problem? Is anyone smarter on bluetooth a2dp that could explain what might be happening here? Are there any other ideas of what I can try?
This is extremely frustrating, as I bought and installed the iSimple kit specifically for this purpose, so I could stream audio and control play/skip from my car stereo, and it was working great with my Incredible 2, but that phone was showing its age.
I've seen some info about other 4.2.x devices having bluetooth audio quality issues, but I wasn't sure if it was the same problem or not.
Any ideas?
Click to expand...
Click to collapse
Update your device to 4.4.2
MOTO X SLAPPED
jmel said:
I just changed from a 2.3 device to a droid mini running 4.4. I have the same problem. I've contacted Isimple to open a ticket and hopefully see if they will release a patch to flash the isimple connect gateway with. The droid mini works without issue with a bluetooth speaker that I connect to - but does not work properly in the car.
The symptoms are slowed audio, and crackling.
Click to expand...
Click to collapse
I've tried pursuing the problem from both the PAC(ISimple) and Motorola ends. Never got anywhere. 4.4.2 on my Moto X doesn't fix the problem either. I've pretty much just given up on it working. I guess I'm just stuck with using a AUX cable for music. Voice calling works fine, but bluetooth would be much more convenient
mpkrcl said:
I've tried pursuing the problem from both the PAC(ISimple) and Motorola ends. Never got anywhere. 4.4.2 on my Moto X doesn't fix the problem either. I've pretty much just given up on it working. I guess I'm just stuck with using a AUX cable for music. Voice calling works fine, but bluetooth would be much more convenient
Click to expand...
Click to collapse
I have a ticket in with PAC. I told them the whole issue, mentioned this thread, and even offered to beta test a patch.
I suggest you do the same. Call them again, open a ticket. They acted like no one had called before about it.Speak to them on the phone.
I'm using aux for now, but surely this can be fixed. I don't think 4.4.2 would have fixed it... 4.4.3? maybe... isimple isn't the only device that got broken from 4.4 though.
jmel said:
I have a ticket in with PAC. I told them the whole issue, mentioned this thread, and even offered to beta test a patch.
I suggest you do the same. Call them again, open a ticket. They acted like no one had called before about it.Speak to them on the phone.
I'm using aux for now, but surely this can be fixed. I don't think 4.4.2 would have fixed it... 4.4.3? maybe... isimple isn't the only device that got broken from 4.4 though.
Click to expand...
Click to collapse
Unfortunately, I had some issues with technical support this past friday. I have gotten no indication they have even tested the device, nor that they even want to. They have tested ios7 though, and released a document on how to deal with some connectivity issues with ios7 and the isimple.
PAC is blaming google, and says to contact motorola, but we all know that this is futile.
Looks like I might be ditching this thing soon. I am unimpressed with their willingness to even understand the problem, let alone try and fix it. If anyone else has 4.4 and an isimple connect, I urge you to call in and voice any problems you are having.
Just Talked with PAC
So I just got off the phone with PAC as I was experiencing the exact same issues on my 2007 Classic Chev 2500HD. I spoke with tech support and they told me they were unaware of any such issue. I mentioned this forum, but still said that this is the first they herd of it. I do not have the Moto X, but I am having the same problems with my Note 3 Running 5.1.1 CM. If anyone does find a solution this would be truly helpful.
Related
Hello Everyone I am here to find some answers (hopefully)...
So I got the HTC One Coming from the Iphone 5. I've had numerous Android devices before, and apple products. I just recently also purchased a subaru wrx, it has bluetooth radio. When I had my iphone 5, i synced perfectly with the radio, hands free worked Awesome. When i got into the car my spotify or pandora would immediately start playing..
Now i get my htc one, and i pair my phone with the car, but my hands free audio sounds terrible, i can barely understand what the other person is saying. On top of that i have to manually connect the phone to bluetooth everytime i turn on my car, its very annoying. I have tried many different roms, and kernels, and i even went back to stock but i can't seem what the problem is. I am about to change the radio in the car thinking its not very user friendly with android devices.
If anyone can point me in the right direction that would be awesome. I am pulling my hairs, i love the htc one, but i miss my handsfree bluetooth functionality. I have tried searching the forums, but i haven't found any answers that worked.
I am having the same issue with having to manually confirm the Bluetooth connection in my car. Mines on a Toyota 86 with the GPS in dash, I believe it's made by eclipse who supply Subaru?
Sent from my HTC_PN071 using Tapatalk 2
I have to manually connect each time to my bluetooth nakamichi speaker.
I too am having same issues. I also have a 2011 WRX with original radio. With my prior phone (GS2) I connected without problem and automatically every time I started the car. I have to manually connect the HTC one every time. Many others seem to not have this problem with other vehicles, so I'm starting to think it's the Subaru radio not playing nice with the phone. Please post if you find a solution.
Sent from my HTC One using xda app-developers app
I installed an app called Bluetooth file transfer that fixed the issue somehow.
Sent from my HTC_PN071 using Tapatalk 2
I had similar problems in my car with an alpine radio, but with my galaxy s3.
In fact the thing is that when you register a phone on your radio (in my case) the radio just looks for the first one defined and registered to autoconnect.
Now, if in your radio you clear registered devices list, and try to register your htc, i am pretty convinced that it will autoconnect all the time.
Hope it helps,
Regards,
Nicolas.
My HTCone synched immediately with the OEM bluetooth in my 2011 Kia Forte. No problema, in fact, it is a much better connection (clarity) than with the old EVO 4g, which initially required a bit of fiddling to make work. Hands free phone call system on the KIA works very well too. FWIW.
Tobz said:
I installed an app called Bluetooth file transfer that fixed the issue somehow.
Sent from my HTC_PN071 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that. I sorted out how to BTconnect my HTCone<--> Macbook, but could only do so, one file at a time. The app you mentioned works great (!) and allows me to push multiple files at ne time. Reviews say it is also a great file manager, that I have yet to determine but if so, an added bonus.
I am also having a problem with the HTC One bluetooth in my car. The phone connects to the car’s bluetooth system, pairs properly, although very slow, it uploads the phone book and call history. The problem is the call quality. The people I am calling complain about the sound, they feel the volume is too high and this distorts the sound, as well as there is too much noise added to the voice, or something like that. As soon as I switch to the phone speaker the sound that they hear gets better. This makes me think the bluetooth on this phone sucks. One person suggested the interaction between the noise canceling and main microphone is mixed up, but if I am using my car's sound system it should not use the phone's microphones anyway, or maybe it does? I guess what I am trying to say is that when I am using the car's stereo it should use only the car's microphones and speakers , but sound like the phone noise canceling microphone is still active.
If anybody has ideas for fixes, or suggestion for further tests, I will do it.
P.S. I didn't have any problems with my car's bluetooth with my iPhone 4 or Nexus 4.
Same for me. Sometimes the problem disappears. I assume the problem comes from the BTstack. In fact, the one is the only Android phone I know that use a different BT stack than blueZ. This stack is HTC one. It allows us having avrcp 1.3 (The name of the song displayed on our car audio). I hope the HTC one Google edition use blueZ stack. I will try a Rom based ion that. If the problem disappears, it will confirm the problem come from HTC stack.
ljam said:
I am also having a problem with the HTC One bluetooth in my car. The phone connects to the car’s bluetooth system, pairs properly, although very slow, it uploads the phone book and call history. The problem is the call quality. The people I am calling complain about the sound, they feel the volume is too high and this distorts the sound, as well as there is too much noise added to the voice, or something like that. As soon as I switch to the phone speaker the sound that they hear gets better. This makes me think the bluetooth on this phone sucks. One person suggested the interaction between the noise canceling and main microphone is mixed up, but if I am using my car's sound system it should not use the phone's microphones anyway, or maybe it does? I guess what I am trying to say is that when I am using the car's stereo it should use only the car's microphones and speakers , but sound like the phone noise canceling microphone is still active.
If anybody has ideas for fixes, or suggestion for further tests, I will do it.
P.S. I didn't have any problems with my car's bluetooth with my iPhone 4 or Nexus 4.
Click to expand...
Click to collapse
BT problem
Hi,
I'm also having a problem with my BT while paired to the BT in my awesome Volkswagen sirocco.
I don't see any contact or missed calls or recent calls. The log is empty.
Any help will be much appreciated.
Blankzz said:
Hello Everyone I am here to find some answers (hopefully)...
So I got the HTC One Coming from the Iphone 5. I've had numerous Android devices before, and apple products. I just recently also purchased a subaru wrx, it has bluetooth radio. When I had my iphone 5, i synced perfectly with the radio, hands free worked Awesome. When i got into the car my spotify or pandora would immediately start playing..
Now i get my htc one, and i pair my phone with the car, but my hands free audio sounds terrible, i can barely understand what the other person is saying. On top of that i have to manually connect the phone to bluetooth everytime i turn on my car, its very annoying. I have tried many different roms, and kernels, and i even went back to stock but i can't seem what the problem is. I am about to change the radio in the car thinking its not very user friendly with android devices.
If anyone can point me in the right direction that would be awesome. I am pulling my hairs, i love the htc one, but i miss my handsfree bluetooth functionality. I have tried searching the forums, but i haven't found any answers that worked.
Click to expand...
Click to collapse
I am having the same issue...I had the Motorola Atrix 4g and it paired immediately with my Pioneer deck. That phone always reconnected and like you mentioned, pulled up Pandora etc. Now I have the HTC One, and it paired and connected but it refuses to play audio. Handsfree works (kinda sloppily, also like you mentioned), but the Media Audio portion doesn't work even though the phone reports that it is connected. My stereo says no device detected when I switch to BT Audio. I hope you find a resolution to this issue, I have searched everywhere and of course I saved the best for last and decided to finally check here @ XDA.
I posted earlier in the thread that I was having difficulties pairing my One with my Subaru WRX factory radio. I could not get it to automatically connect with the phone each time I started the car. I could manually get it to connect but that was a pain every time I got in the car. I was able to solve my issue by deleting every other pairing the radio had with other prior phones. I deleted any pairing my One had previously and then paired it with the car radio before any other device. It now connects regularly every time I start the car, and both audio and phone functions work perfectly. I would recommend anyone having blue-tooth issues to try the same. The Subaru radio also had a weird menu system that was different whether I was pairing the phone by using voice commands or trying to do it with physical buttons on the radio. Very confusing but going through the hands free voice command menu seemed to pair both audio and phone functions, where I could only pair audio functions when using the physical buttons on the radio. Seemed like two different systems.
Been having crappy noise issues with my 09 Acura TSX. I emailed HTC regarding this problem but, of course, their response was to 'check with the car manufacturer'. Will try that method and see how it goes.
My problem is a bit different. My htc One connects flawlessly with my JVC unit that too automatically. But it keeps disconnecting and reconnecting. And that is a major issue. The phone also gets insanely hot in this process and today the OS crashed two times and i had to do a Hard Reset.
I am coming from an iPhone 5 on which bluetooth streaming was flawless.
Anyway to stop the auto-disconnect and re-connect going on.
My Bluetooth is mess up.
It can pair up, but the Address Book is not showing up on the car screen menu now. I don't know what happened. When I play music on my phone to the Bluetooth in the car, it is silence.
Does anyone know what is going on?
HTC One Bluetooth Problem in BMW
I am having the same problem.
My HTC One connects, I can make calls from the phone and the calls are clear, but I cannot see my contacts.
I have emailed HTC and they say it is the car (BMW 5 series). I have checked with BMW and there isn't an update for my car available. I am therefore, using the latest software. I previously used the HTC sensation which worked fine in the same car.
I am wondering if one could install an older version of the Bluetooth and A2DP software as the those on the HTC One do not work in my car and I cannot see BMW developing any updates and if they did, the cost could be as much as the phone.
Would appreciate any help
HTC One Bluetooth CONTACT Problem in BMW !!!SOLVED!!!
ulticomp said:
I am having the same problem.
My HTC One connects, I can make calls from the phone and the calls are clear, but I cannot see my contacts.
I have emailed HTC and they say it is the car (BMW 5 series). I have checked with BMW and there isn't an update for my car available. I am therefore, using the latest software. I previously used the HTC sensation which worked fine in the same car.
I am wondering if one could install an older version of the Bluetooth and A2DP software as the those on the HTC One do not work in my car and I cannot see BMW developing any updates and if they did, the cost could be as much as the phone.
Would appreciate any help
Click to expand...
Click to collapse
I can now see my contacts after more than a month!
I did many things, some of which I do not believe had anything to do with the process required.So I will stick with the main points and if this does not work I will include all that I can remember.
I unpaired all phones in the car (including the HTC One)
Pair the HTC One
Look out for the message BMW wants......................... contacts
Select yes
Wait for the contacts to load, this took a couple of minutes at least.
The credits goes to another post somewhere on this forum!!:crying:
have
Been trying to find out for the longest time the definite set of codecs that the One supports over bluetooth. Besides SBC and AptX, does it also support MP3 and AAC??
The reason I'm asking is that I'm coming from a (company supplied) iphone and have been generally very happy with the bluetooth audio quality to my car's audio system (Audi) and Bose Soundlink Mini speaker. I know for sure the iphone supports AAC and due to the quality suspect it is used in both cases.
The Bose at least does *not* support AptX, however getting a definite codec list for the Bose is also impossible. I only managed to find buried in the offfical bluetooth certification pages that it is a BT2.1 device.
Why do all these manufacturer's hide this documentation?
Very disappointed to find out that the Bose Soundlink Mini negotiates a link with the HTC One using SBC...
These are both premium devices for which top dollars are paid, and they still shovel this **** on me.
I'm not sure on where to place the blame here, HTC for only(???) supporting AptX next to SBC, or Bose for only supporting SBC(???)
As mentioned, both are not transparent in their devices capabilities - isn't there an app to find out these things?
Beats is at least more clear: "Bluetooth 2.1 audio and supports SBC, aptX, AAC Codecs for high quality streaming"
Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.
I haven't noticed poor quality streaming at all... I have used it a lot.
Sent from my XT1058 using xda app-developers app
nonotechnology said:
Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.
Click to expand...
Click to collapse
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:
I have the same issue with poor sound quality when I stream music to my 2013 Subaru Legacy stereo. The problem seems to be that the sound is overly compressed and when a lot is going on it becomes especially noticeable. Part of the issue revolves around devices that don't support the newer APT-X codec, if the device supports that codec the sound is said to be fine however any device that uses straight A2DP will experience this issue.
djp952 said:
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Click to expand...
Click to collapse
I have had the same experience as you. I have tried my Moto X with about 10 different bluetooth receivers. I have had nothing but excellent sound quality.
djp952 said:
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:
Click to expand...
Click to collapse
I'm experiencing the same crappy BT audio I was with my galaxy nexus prior to your fix (thanks a lot BTW) on my moto x with the same BT receiver in my car. I've got a couple others I will try and report back later.
Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?
hyatari said:
Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?
Click to expand...
Click to collapse
I'm not sure either It's a good bet the Bose one does since its brand new. Seems like a pretty good theory!
I think I still have a really really old Scosche receiver kicking around somewhere I can try for you guys and compare it with an AOSP bluedroid-based phone.
http://www.csr.com/gogroove-bluesync-portable-bluetooth-speaker
Forgot to test on that which does have apt-x though I don't think it specifies in the manufacture or amazon site but that's the actual apt-x website. Can confirm that it definitely sounds better than my other devices.
Some Test Info if it helps
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.
mpkrcl said:
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.
Click to expand...
Click to collapse
I don't see any indication that states that deck supports apt-x. I read on the android bug report page that one user running 4.4 claims they've finally fixed this issue so I guess we wait for 4.4 now.
The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.
seh6183 said:
The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.
Click to expand...
Click to collapse
My Bose Infiniti head unit sounds amazing streaming Bluetooth from my wife's iphone4s and a load of rubbish while streaming from my motoX.
I'm very close to just saying screw it, giving in, and buying an iPhone.
Buy the iphone
Sent from my XT1056 using XDA Premium 4 mobile app
I apologize if this has been asked and answered already, but doing a quick search of this forum, I didn't find my answer.
I am considering picking up a Moto X because it's frankly an awesome phone (I really like the touchless controls and other pizzazz that Moto added to it, but when it first came out it was too pricey for me).
My question is: is the Moto X plagued with the same bluetooth issues that the Nexus 4 and 5 are on Kit Kat? Specifically I want to know if the 5-second delay, on both calls and stereo audio, is also an issue on the X, and whether the bluetooth process has a tendency to crash on the X when connected either to car audio or bluetooth headset?
If any current X owners on a stock rom could weigh in, I would really appreciate it!
If you'll describe what the five second delay problem is I'll tell you if I ever experienced it. I have never seen my Bluetooth process crash. I have to repair with my car sometimes but not with my headsets so I assume that's my car's fault.
Yes... Bluetooth has a number of issues in Android 4.4 and 4.4.2. Surprising that a search didn't return a number of topics regarding it.
I have issues with crackling/stuttering on bluetooth. If I am driving and using bluetooth, resting my hand on my pants over my phone can even cause it to stutter for a few seconds. Using apps while listening to bluetooth is also not generally a good idea.
I happen to be the type of user that this doesn't impact, but I could see it being a major issue for plenty of users that I know. It may also have something to do with the music player I am using (shuttle), as I haven't tested it out with other players.
I have an att moto x and upgraded to 4.4 as soon as it came.. Trust me on 4.4 there are a hell lot of issues with bluetooth. My headset gets disconnected and reconnects too often.. while talking on phone it is such a pain. I never experienced the same issues on 4.2.2. So i downgraded back again to jelly bean and now its fine again. If you want to use kitkat stay away from this phone from my experience. Baterry life is also ruined with this update. May be they fixed these issues on 4.4.2, i dont know, i didnt dare to update as we cannot downgrade from 4.4.2
I'm another user who has stopped using my moto-x bluetooth with my car because of constant connecting/disconnecting and "picket fencing" of sound....I'm on 4.4.2 and I think it's even worse than 4.4....I'm a bleeding edger though, so I refuse to go back to 4.2. Hopefully 4.4.3 will fix the bluetooth issues if it ever gets here. Otherwise I love the phone.
ghstudio said:
I'm another user who has stopped using my moto-x bluetooth with my car because of constant connecting/disconnecting and "picket fencing" of sound....I'm on 4.4.2 and I think it's even worse than 4.4....I'm a bleeding edger though, so I refuse to go back to 4.2. Hopefully 4.4.3 will fix the bluetooth issues if it ever gets here. Otherwise I love the phone.
Click to expand...
Click to collapse
According to the log, 4.4.3 will indeed address the BT issues that some users in 4.4.2 are experiencing as well as several other bugs.
I'm on 4.4.2 stock and the bluetooth connection to my car for audio streaming is ok. It still stutters randomly, especially if I have other apps running like navigation. Didn't have any problems with disconnects. I was also on CM11 nightly builds but the stutter was really bad and more frequent so I went back to stock Kitkat.
I'm on stock KitKat 4.4 with my second Moto X ( first on AT&T, now on Verizon) and haven't had the afore-mentioned issues. I connect to a Sony MEX-BT in my car and a pair of RF-MAB2 headphones at work; both work great.
I too was worried after seeing all the posts about the Nexus but I think you should be fine with the Moto.
Thanks all for the replies. I know that there are indeed bluetooth issues with Kit Kat, but my research into my Nexus 4 issues seemed to point to issues with the drivers for the bluetooth chipset in the Nexus 4. It's interesting to me that some people have issues on the X, while others don't (perhaps different chipset revisions?).
With regards to my 5-second delay, the amount of time between when something happens on my phone (i.e. skip track, or button press on the dialer) and when I hear the result on a connected bluetooth device can be up to 5 seconds. My concern is mostly for phone calls, being behind on the "real time" conversation, but perhaps this is one of the many issues they plan to fix with 4.4.3.
I guess for now I'll wait until 4.4.3 to see if bluetooth gets any better for me on the Nexus. It's crazy to me that Google has let this go unpatched for so long. Here's hoping 4.4.3 starts rolling out in the next few weeks.
Been having bluetooth audio stuttering issues with the Moto X when playing music/podcasts. Only seems to happen in my car with the Chevy MyLink system (Blackberry QNX-based). Works fine with a regular set of bluetooth headphones.
I've tried:
Disabling Wifi
Rebooting Directly Before Connecting to Bluetooth
Re-pairing the device
Turning off NFC
Un-pairing all other bluetooth devices
Turning on the developer option to leave the screen on when plugged in, to force the phone to not sleep
Moving the phone to different places in the car (assuming it was a reception issue)
Disabling the phone profile in bluetooth, leaving only the media profile
Different music players
Playing music from local storage rather than streaming it
None of it seems to help. The only real difference I can see is that the car bluetooth stereo supports AVRCP 1.3 (Track information, song/album title) and the other bluetooth streaming devices I've tested don't.
Does the Moto X just have a buggy bluetooth stack? (this worked fine on my old Note 3) Anyone else have this issue (and possible have a fix)?
I just started using my phone in my car to stream music today, using a CoolStream Bluetooth adapter and noticed the same thing. I have two CoolStream devices, so I was going to do some testing before posting anything (I used the other in my office today without issue). I just received a replacement Moto X (for another reason) today, so I will try it out tomorrow.
Sent from my XT1096 using Tapatalk
Funnily even I have Bluetooth issues.. I own a pair of bluebuds x and after pairing the device the audio was still playing through phone. I have to disconnect Bluetooth and restart bluebuds x and immediately start playing music after connection is established. if I wait for 2 mins again same problem.
From the motorola forums, there is a suspicion that this is related to the charger that is being used. Can you confirm if this happens if you are using bluetooth music on battery?
toddbecker said:
From the motorola forums, there is a suspicion that this is related to the charger that is being used. Can you confirm if this happens if you are using bluetooth music on battery?
Click to expand...
Click to collapse
This happens even when the phone is on battery.
That being said, it does seem worse when I'm using my Belkin 2.1 amp car charger.
Hmm, definitely starting to sound like a bluetooth software problem, hoping this gets some visibility @ Moto.
Works well for me
No issues at all for me in my 2014 Hyundai Tucson.
Huge problems mine connects then disconnects every 30 seconds have called Motorola 3 times going to call again ask for exchange or refund.
Sent from my XT1096 using Xparent BlueTapatalk 2
I was having the stuttering problem when using Bluetooth in my car (Subaru Imprezza). I use the PowerAMP audio player. Going into headset/bluetooth settings (in PowerAMP) and enabling the "High Priority" setting fixed this.
On my BT headset, it's always been fine. (i use the Motorola S11-HD)
I got in touch with Motorola support. They are replacing the phone. We'll see if the new one does the same thing.
stargzrr11 said:
I got in touch with Motorola support. They are replacing the phone. We'll see if the new one does the same thing.
Click to expand...
Click to collapse
I am on my second phone, it is better than the first, but the problem still exists.
This sounds like a major problem - I have a Sony Smartwatch 3 and it keeps dropping. I haven't tried anything else yet but this is already not looking good. Anyone with any answers running Lollipop?
same if not worse
I went from a moto x 2013 to a 2014 and uograded to lolipop. The stuttering is still on lolipop and i have othwr issues as well. When I try to play a vox it doesnt pause audio and is silent. It also fails to auto connect about 50% of the time. And wven when it does the audio is muted and i have to disconnect and re connect. Using an Alpine ute-42BT
I've been using my Moto X 2014 with a 2011 BMW and I have no issues with stuttering. The version of the car's Bluetooth stack supports AVRCP 1.4. I had some quirks with it and my previous LG G3 (time display was off, and previous/next controls from car didn't work properly). With the Moto X, everything works well and all information is displayed properly.
Does anyone know what version of AVRCP the Moto X has when running Lollipop? It seems like stock Lollipop is still stuck on 1.3 (I can't get a clear answer), but with the time being reported properly, I suspect 1.4 is being used on my Moto X.
I also have issues w Bluetooth. Stutters randomly w my Subaru Impreza, as well as my 2 UE Boom Speakers. Using Google Play Music All Access.
In addition, the Jawbone UP24 wouldn't sync w my phone. Had to restart the phone to push a sync through.
My phone was working fine until today. I was able to pause, play, and skip with my bluetooth receiver, but the audio was still coming out of my phone. This is terribly frustrating. I can't believe such a large issue has been going on for months with no announcement from Motorola.
My pure edition on lollipop stutters when the active display goes off on Bluetooth. Only send to happen then
I've notice using Bluetooth headphones none have the range they are suppose to. I've used Power beats 2 wireless, JBL Synchro's wireless, and Moto Hint. The range and Bluetooth auto seem to lack badly. Using a Bluetooth to aux adapter in my work van I've noticed it skipping as well. Hope this gets fixed its apparent that its a issue with the Moto X Bluetooth.
my bluetooth audio has become worthless. so much stuttering, calls sound like they are under water, moto assist voice in the car is so quiet
i can't stand it.
I've had my Nexus 6 since Jan. 1, upgrading from an HTC One M7 GPE running 5.0 Lollipop. I experienced Bluetooth connectivity issues with the HTC One after upgrading to 5.0L from 4.4KK, and I knew they were 5.0 related, so I expected somewhat of the same when getting the N6. My problem is, even after upgrading my N6 to 5.01 and then 5.1, most of my Bluetooth issues still exist. I'm trying to figure out if they are indeed software related, or if maybe I have a defective BT radio. I'm rooted, running stock 5.1 LMY47M, with ElementalX Kernel and Nova Launcher. Here is a list of the issues I'm having with my N6 and Bluetooth:
1. Constant dropped connection to my car's bluetooth. Will connect when car is first powered on, then drops connection after about 20 seconds only to reconnect 30 seconds after that, then drop again within 30 seconds. Sometimes it will connect and stay connected for hours. This issue didn't exist with my HTC One running 4.4KK, but did happen intermittently after upgrading it to 5.0L. This issue also doesn't seem to exist when connecting my wife's N5 running 5.1 LMY47D.
2. Problem #1 also seems to exist when connecting my N6 to my Nvidia Shield Tablet running 5.0L, but not as persistent as with Car BT.
3. When my N6 does connect to my Nvidia Shield Tablet, I can send messages using joaoapps' AutoRemote over Bluetooth from my N6 to my Tablet, but not from my Tablet to my N6. Both phone and tablet are configured correctly. This one has me completely stumped and I've spent hours troubleshooting it before just giving up.
3. Audio stuttering when connected to my BT headphones. Again no issue when using said headphones with HTC One 4.4KK or wife's N5 5.1 LMY47D.
3. Bluetooth seems to turn off randomly. At first I thought it was one of my Tasker profiles, but problem still exists even after uninstalling Tasker.
4. My N6 will not connect to my BT OBDII adapter. N6 pairs with adapter, but adapter does not work with Torque or any other ODBII app. HTC One 4.4KK, wife's N5 5.1 LMY47D, and my Nvidia Shield tablet running 5.0L all connect with no issue.
I have tried every suggestion on threads (Reboot, clear Bluetooth Share cache, clear Bluetooth Share Data, forget all connections and re-pair, Bluetooth Auto Connect app) with no luck. I love my N6, but I've hated these BT issues since day one and I've crossed my fingers with every Lollipop update that they would be resolved, to no avail. I'm wondering if anyone (or everyone) is experiencing similar issues with BT, or is it just my N6, and I should return it for a new one before warranty expires. Thanks.
I only use my N6 Bluetooth with my car (ford sync) and occasionally my home phone. I haven't had any issues. Use it everyday on my commute to and from work.
Since you're experiencing this with multiple devices id assume its you phone too. Maybe contact google for warranty replacement?
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Bluetooth is different on the Nexus 6 for sure.
lords8n said:
No, not using a smartwatch yet. Holding off on purchasing one until I can get this bluetooth mess figured out. I did another factory wipe and rolled back to 5.01, this time staying encrypted (used no force before). Seems to be a little more stable this time, although I have no way of telling if it's because of encryption or just luck. I think it's just coincidental, I don't see how encryption would have any effect either way. I applied the 5.1 update to LMY47M and so far much more stable than before. Again, I don't know why. I can say I am rather disappointed with Google and the Nexus 6. My wife's Nexus 5 is far more stable and I can't believe Google would allow a 'flagship' device to remain this buggy. I never had any of these issues with my HTC One. I traded up to the Nexus 6 for the Google experience, no bloatware, fast updates, etc., thinking that meant more stability. It seems that trading bloatware for the Nexus experience has an unexpected consequence of being a beta-tester for Google.
Click to expand...
Click to collapse
I also use Ford Sync system. For years it has been reliable and worked flawlessly. But starting with the Nexus 6, some of the common applications I use when mobile started crashing the bluetooth stack and giving the error, "Bluetooth Sharing as stopped working."
Before the Nexus 6 which is the first device I've owned with Lollipop, this never happened. The developer of the SMS texting app that is the main one affected by this, has tried everything to resolve the issue but he and I are now beginning to believe it is something baked either into the phone or lollipop, but before this device I never had any problems with bluetooth. I even went as far as to replace my HU in the car with the new pioneer that supports Android Auto, but to my chagrin, it still crashes on that head unit whenever the SMS reader trys to log off and switch back the stream to media. And unfortunately Android Auto currently does not support Pandora which is a must have for me. Pandora runs perfect on the new HU as it did on the Ford Sync as well, but the SMS reader causes BT sharing to error on both devices since the Nexus 6 and Lollipop, so there is something going on with the bluetooth stack and unfortunately no one I can find has any information about what has changed. Hoping Android Auto will soon add Pandora, but Pandora has not given any time estimation about when that will happen.
Mit Hipster said:
Are you by any chance wearing a smartwatch? I had similar problem with my OnePlus One and narrowed the problem down to my Moto 360 smartwatch connection. If I didn't have my smartwatch on while in the car, my auto connection worked fine.
Recently, I switched to a Nexus 6 and find bluetooth to be even worse with this phone. Seems as if the signal being broadcast is too weak. Headset audio will start to breakup, with a clear LOS, after just 10-12 ft. Also, just putting my phone in my pocket will case choppiness. With this phone, however, I have yet to determine whether it is my smartwatch that is causing the problems as well or not.
Click to expand...
Click to collapse
Funny that you mention that. Previously used my Nexus 6 in the car with no issues. Only thing that changed is that I started pairing with a smartwatch in addition, and now my Nexus 6 crashes a few minutes into using Spotify over bluetooth. Complete automatic reboot.
EDIT: Yep, can definitely confirm the combination of the smartwatch and bluetooth audio device kills my phone. Had no trouble without the smartwatch.
EDIT 2: Turns out Google just sucks at bluetooth. Phone can crash regardless, it's just more likely with the smartwatch.
EDIT 3: RMA'd the phone and the new one works perfectly. Turns out it wasn't the software after all, or maybe the watch update helped.
I don't know if this is the same issue or not, but....
Ever since I got my Nexus 6 I have had bluetooth issues with both my cars. One has a Pioneer headunit (2014 model, not Android Auto), the other is a 2014 Subaru Forester with stock head unit.
In both cases there are days when it works perfectly. Then there are other times when it's a nightmare.
With the Pioneer headunit, bluetooth audio will be playing for a brief period (maybe 30 seconds?) and then something will happen and the headunit will play a repeated beep (bing bing bing bing bing bing) till I turn off bluetooth on the phone, wait a minute or two and reconnect.
With the Forester's headunit, similar situation - i'll be playing audio and it will just drop out. Maybe 60 seconds later it may come back (sometimes). Same applies to telephone calls via the headunit with bluetooth.
The same 'issue' appears with both headunits with one playing a beep when it happens the other dead silence, but both dropping in and out whether it's bluetooth audio or a call.
N6 running latest firmware. Problem has existed since I got it last year. Recently unlocked and rooted, but hasn't made a difference.
I don't know if this is the same as my problem, but it is the closest thread I could find, so I'll post here.
I've had my Nexus 6 about a week. Running 5.1.1, unlocked bootloader and rooted. I've been using a bluetooth headset for phone audio and media audio. It had been working, though I have experienced some audio dropout and stuttering with media audio. I had not been able to determine if that was a bluetooth problem or an app problem, but now I am leaning towards thinking it was a bluetooth problem because of what is now happening.
Today, media audio just stopped playing through my headset. Phone audio is working. I've tried rebooting, I've tried forgetting and re-pairing, I've tried a different headset and I cannot get media audio to play over bluetooth.
I am having the same problem with Nexus6 I have tried two different Plantronics voyager bt headsets and a Motorola Sliver. Motorola said it may be a bluetooth antenna problem
Did a resit on phone and Motorola Bluetooth
I really need bluetooth connectivity so I am stuck
Only other option is either find someone to open up the phone and check the antenna or do it myself maybe replace it myself or look for another phone and use this one as a backup
What would you all suggest?
Thanks