Related
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.
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 have the dpx500bt, and I am trying to get an idea of whether or not the moto x will work well with it. I currently have an iphone, and kenwood seems to have gone out of their way to support that. With an android phone, it is unclear whether I will even be able to make/receive phone calls.
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.
In my moto g2014, i m having some problems in my audio jack... Actually some headphones are working with it and some not ...and those headphones which are not working but they work in another phone
When i insert the headphone and play songs then songs are played via speaker not in headphones...plss help
Same problem
Same problem here. only a touch on headphone plug and the song/audio stops, sometimes plays on speakers too.
ghustavus said:
Same problem here. only a touch on headphone plug and the song/audio stops, sometimes plays on speakers too.
Click to expand...
Click to collapse
headphone jack problem
I come with that problem too. It result it's a conector problem like it is said in motorola formus:
Thank you for providing me this information. I have gone back to our developers and confirmed a couple things. There are 2 different standards for headsets AJH and OMTP: http://recapmycalls.com/faq-page/headset-standards-ahj-omtp/. The most common is the AJH standard. The Moto G 2nd Generation is only compatible with AJH headsets. The 1st generation Moto G was able to automatically switch between AJH and OMTP. The Nokia headsets that you have use the OMTP standard and aren't compatible with the new Moto G 2nd Generation. I hope that clears things up. Please let me know if you have any additional questions or concerns. I'll be here to help however I can.
I'll buy an adapter this week and see if it works. If anyone can confirm that with an adapter work let us know here. thanks
More info: https://forums.lenovo.com/t5/MOTO-G...t-working-with-2nd-Moto-G/td-p/3038740/page/2
Hey there! I had the same problem. Check here friend: http://forum.xda-developers.com/moto-g-2014/help/moto-g-sy-t3002416/post60050528#post60050528
Same problem here but no solution.
Same here, touching the headphones sometimes get disconnected. seems to be h/w related issue.