Related
So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.
There are threads that discuss the problem with different releases of android releases that are missing bluetooth capability over 2 years ago, nothing since Dec. 2011.
That said I have had a Motorola Photon running 3.2.2 gingerbread that would sync with my ford MySync for audio and display and read SMS txt messages.
So getting a brand spankn new Nexus 4 with Jelly Bean, I was very disappointed to see that all I can sync via bluetooth is the phone and directory.. so old hat now days, they all do that.
It seems that this should be a big enough problem that it would have been fixed long ago, but I can notspelling understand why going from an older version that works, is broken or missing in a much later version.. :crying:
Does anyone know what is going on?
Same here, I would have thought the Nexus 4 would have sent the metadata for the music that I was streaming via bluetooth to my car as well. But nope, just the music no artist info, name and or the ability to browse my playlist.
I use poweramp and poweramp supports this feature as well. Guess we have to wait for custom roms to support this.
same here but at least the disconnection issue has been fixed
xdviper said:
Same here, I would have thought the Nexus 4 would have sent the metadata for the music that I was streaming via bluetooth to my car as well. But nope, just the music no artist info, name and or the ability to browse my playlist.
I use poweramp and poweramp supports this feature as well. Guess we have to wait for custom roms to support this.
Click to expand...
Click to collapse
Oh and I did forget a Charge only setting. When I connect it by USB to the car, I have to set it to picture mode only as the music player setting is not recognized.. never had that problem with gingerbread,
eastrader said:
Oh and I did forget a Charge only setting. When I connect it by USB to the car, I have to set it to picture mode only as the music player setting is not recognized.. never had that problem with gingerbread,
Click to expand...
Click to collapse
what do you mean charge only setting? how do you get that?
eastrader said:
There are threads that discuss the problem with different releases of android releases that are missing bluetooth capability over 2 years ago, nothing since Dec. 2011.
That said I have had a Motorola Photon running 3.2.2 gingerbread that would sync with my ford MySync for audio and display and read SMS txt messages.
So getting a brand spankn new Nexus 4 with Jelly Bean, I was very disappointed to see that all I can sync via bluetooth is the phone and directory.. so old hat now days, they all do that.
It seems that this should be a big enough problem that it would have been fixed long ago, but I can no understand why going from an older version that works, is broken or missing in a much later version.. :crying:
Does anyone know what is going on?
Click to expand...
Click to collapse
I get the same thing, but since BT 4.0 is relatively new, there is an update for my car to support this bt version. Im waiting to change the oil to ask my dealer to update my BT software.
Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..
mailrachit said:
Hi fellow xda'ers
I got the 4.3 OTA today for my Nexus 4 and the problem of stuttering bluetooth audio persists for me.
This is in reference to the bug described here: http://code.google.com/p/android/issues/detail?id=39633
I also unpaired my phone and re-paired it but still facing the same problem.
So, just wanted to ask around...
1. Is anyone still facing this same bluetooth audio bug like me in Android 4.3?
2. Can anyone who had this bug in 4.2.2 confirm that it got resolved for them in Android 4.3?
Thanks..
Click to expand...
Click to collapse
Mine is great..plus the track name is one there now....but i never had problems in 4.2 either so.
what do you have for a stereo?
I use mine in my car (sony stereo) and i also have a bluetooth radio for my patio i got at home depot that works just fine
Every thing is fine with mine too
Sent from my Nexus 4 using XDA Premium HD app
Never had suffer stutter
Sent from my Nexus 4 using Tapatalk 4 Beta
I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..
Worked fine for me in 4.2.2 .... now in 4.3 LOTS of stutter and occasional drops. Very annoying and probably related to the change of Bluetooth in 4.3 ... hope someone comes up with a fix, otherwise I'll need to go back to 4.2.2 as I use Bluetooth for music lots. Anyone that can help ... ??
I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
mailrachit said:
I am using my phone with a Clarion car stereo.
The issue now is much rarer than it was before.
I guess I need to test it out for a few more days.
Thanks..
Click to expand...
Click to collapse
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...
I've never had issues...I have a Sony stereo and I also play in my buddies new toyota truck and plays fine. I would try on other devices..my guess would be your problem is with the stereo than the phone
Sent from my Nexus 4 using xda app-developers app
sn0warmy said:
I was excited to see that as soon as I upgraded from 4.2.2 to 4.3 my bluetooth streaming worked flawlessly in my car for a 2 hour drive into the mountains. However, a couple days later the stuttering came back, just as you described.
This was the one thing I was looking forward to for 4.3 but it looks like we've been let down.
Odd, I also have a Clarion stereo. I'll be curious to try it out in another car with a different brand of stereo to see if it may just be that our phones don't play well with Clarion...
Click to expand...
Click to collapse
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.
mailrachit said:
I'm not really sure, what's happening.
I tried earlier on with Poweramp Player (third party app) and Google Play Music, I had stuttering in both the apps.
Then I decided to unpair the phone/stereo, change the phone name and then re-pair. Just wanted a fresh start..
After that, I had the stuttering problem whenever I used Poweramp player. The problem happens within 5-7 min. However, when I use Google Play Music, it seems to work fine. However, I haven't tested it for long. Maybe 1 hour max, so can't say if my hypothesis is correct but I'm keeping my fingers crossed. After 7 months with this phone, I really need to get Bluetooth working.
Click to expand...
Click to collapse
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one
mailrachit said:
At the same time have you checked the reverse? Any other phones that work fine with your stereo?
I have and I can say all other phones have worked fine with my Clarion stereo.
If N4 continues to have problems with the Clarion stereo, it could be easier for me to sell the N4 and get another phone, unfortunately a non-Nexus one
Click to expand...
Click to collapse
sn0warmy said:
I'm in the same boat. But I really am wondering if looking at the software/apps used is the wrong method. I've been doing the same thing. Over the past 7 months I've tried various ROMs, kernels, radios etc. and nothing changes it. I've talked about it with various friends with Nexus 4's and none of them seem to have any issues.
At this point my money is on the Clarion stereo being the issue but I still have not tested the phone with another stereo. This weekend we are visiting my parents. I will try using the phone with the bluetooth on my Mom's 2013 4Runner and my Dad's 2010 F150 to see if I can replicate the problem. If it works with both their cars then I will be in the market for a new stereo. :laugh:
Click to expand...
Click to collapse
I was wrong btw. The problem came back for Play Music too :crying:
Don't know what to do...
Using all stock 4.3 and btooth working perfectly. Using it right now. I just have a $50 lg headset but have no issues.
Not sure what's up with your device man
Sent from my Nexus 4 using xda app-developers app
@sn0warmy
It seems the problem is with our Clarion car stereo indeed. A lot of Clarion stereos have bluetooth issues:
http://www.fixya.com/support/t12082313-bluetooth_audio_streaming_breaks_up
http://community.crutchfield.com/car_audio_and_video/f/27/receivers/t/22006/clarion-cx501-bluetooth
Phones like iPhone 4, Lumia 920 and Moto Razr also seem to have these problems.
My stereo CX501 doesn't have any bluetooth firmware upgrade too. Though, they have provided some firmware update for some other stereos like NX501 and so on. So you should check out on their site for a firmware upgrade.
http://www.clarion.com/us/en/support/compatibility/bluetooth/index.html
I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...
sn0warmy said:
I really think you're right. I tried streaming music through my girlfriend's car stereo last night and had absolutely no issues. I've also read the threads you linked to as well as a few others and the consensus is that Clarion keeps trying to pin the blame on the phones and not their receivers. Looks like it's time to change stereos...
Click to expand...
Click to collapse
You should at least check if there is a firmware upgrade available for you on Clarion's support site before spending on a new stereo.
Unfortunately, it's not available for my stereo CX501.
I have stuttering too on both my A2DP devices. Both are cheap: one is from DX, th eother is from a local 'dollar store' (where it was 10 euro or so).
The one from the dollar store seems to work fine after pairing, but not when connecting again.
The one from DX (z nice plug for the aux in of the car, with a mic and henadsfree speakers through the car audio) seems to stop stuttering after a few minutes. The audio level is a lot better with 4.3.
But no difference in stuttering beween 4.2.2 and 4.3.
Problems remain
I have found no improvement with my Nexus 7 with Android 4.3. I get stuttering every minute or so. I've done a bit of reading and found that Bluetooth is hellishly complex - and would be very difficult to debug. For instance to set up audio streaming, both devices need to agree on a codec to use. There is a default base level codec. As I have found that the issue is worse on some bluetooth receivers than others, I can only guess that the issue relates to Android's selection of a codec or other parameter on some devices. I certainly have no issue with any device streaming from my windows laptop (no matter how busy it is).
I have the exact same issues with bluetooth stuttering.
Using 4.2.2 PACman rom on my Note 2 with a Sony MW600 bluetooth adapter, the audio would switch off for a second every minute or so, whether using Google Play music or PowerAmp, but it seemed to happen less on the former.
Updating to 4.3 has made it worse, the audio now switches off for at least 5 seconds to the point where i have to check if the phone or app has crashed each time.
I never had an issue with the Revolution HD rom (I think its called?) but I believe that's mostly stock?
It kinda feels like the bluetooth can't handle the bandwidth depending on the size of the file. I think there's less stuttering on lower quality files - could just be in my head though.
I have a Galaxy S3 i747 running latest 4.3 CM10 rom. My audio stuttering actually got worse when upgrading from 4.2.2. Using platronics 903+ and a bluetooth stereo unit for my motorycle helmet.
Very disappointed. My work iPhone doesnt skip a beat.
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
I am guessing that it isn't built on the 444 kernel, so, don't get too discouraged yet
Sent from my Nexus 7 using Tapatalk
ghstudio said:
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
Click to expand...
Click to collapse
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
jaykresge said:
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
Click to expand...
Click to collapse
It is 4.4.4 kernel. I think I've found the issue and it's unique to "techies". I have a pebble smart watch which uses google...the connection to the car system (2014 MB) uses bluetooth. If I don't wear my watch, the connection to the car works...no loops/etc. When I wear the watch in the car, the car/phone link goes all screwy. I suspect that one of the bluetooth stacks doesn't like to share....and I'd bet it's the moto-x stack which can either use the bluetooth or the car link, but not manage both together, even though everything is paired correctly. I haven't checked to see if pebble and the MB use the same protocols...it may be that they both share txt even though I only need phone on the car link.
I'll post more when I get further into this....I just stumbled on the cause today when I didn't wear the watch and repaired the phone with the 4.4.4 kernel.
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
abuttino said:
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
Click to expand...
Click to collapse
I've heard them all, but we've had precisely zero issues with the Fusion, and one with the Edge that was fixed free of charge due to silent recall.
My only issue with Sync is that my Fusion has the Gen 1 version, and the most recent software update removed the key reason I chose this car over the then comparable Sonata. Without that feature, I would have gone with the Sonata.
Hello all,
I have tried Googling but a working solution hasn't come up for me yet. Ever since getting my S7 Edge in April I've had issues getting AVRCP to work correctly with in car head unit.
It's an Alpine CDE-133BT (actually, I have two of them both with the same problem) supporting AVRCP v1.3 and it worked perfectly on my old HTC One M8 and HTC One X before it (makes me wonder why I ever changed to a Samsung). I've tried clearing the cache as described everywhere online but no luck and I'm getting bored of keep having to manually control my music on my phone. Not only is it dangerous, but also highly irritating.
The only 'control' I can get it work is Pause/Play but only once I have manually started music playing on Google Play Music. Forward and Back don't work, and I certainly can't get any metadata.
I was hoping that Samsung would have fixed this by now; clearly not.
Any advise?
Dave.
Forgot to add; I also hear some loud 'clicking' sounds when listening to something quiet at high volumes.
Anybody?
dsgoody said:
Hello all,
I have tried Googling but a working solution hasn't come up for me yet. Ever since getting my S7 Edge in April I've had issues getting AVRCP to work correctly with in car head unit.
It's an Alpine CDE-133BT (actually, I have two of them both with the same problem) supporting AVRCP v1.3 and it worked perfectly on my old HTC One M8 and HTC One X before it (makes me wonder why I ever changed to a Samsung). I've tried clearing the cache as described everywhere online but no luck and I'm getting bored of keep having to manually control my music on my phone. Not only is it dangerous, but also highly irritating.
The only 'control' I can get it work is Pause/Play but only once I have manually started music playing on Google Play Music. Forward and Back don't work, and I certainly can't get any metadata.
I was hoping that Samsung would have fixed this by now; clearly not.
Any advise?
Dave.
Click to expand...
Click to collapse
did you try updating the software on your alpine, it may not recognize the marshmellow.
I have a 2012 VW Golf and AVRCP works perfectly fine on my end. I don't think it's the phone. Possibly try repairing the phone and make sure to hit allow when the phone prompts you to, to allow your car access to contacts, music, etc... when pairing it.
Sent from my SGP612 using Tapatalk
Cosmic Blue said:
did you try updating the software on your alpine, it may not recognize the marshmellow.
Click to expand...
Click to collapse
My understanding was the AVRCP was a standard protocol; not unique in anyway to the different versions of OS. My old HTC One M8 had Marshmallow on it towards the end of it's life and it worked fine.
While Alpine do provide updates; the mechanism for applying them appears to be very buggy and almost unusable as I have tried it in the past.
siphyn said:
I have a 2012 VW Golf and AVRCP works perfectly fine on my end. I don't think it's the phone. Possibly try repairing the phone and make sure to hit allow when the phone prompts you to, to allow your car access to contacts, music, etc... when pairing it.
Sent from my SGP612 using Tapatalk
Click to expand...
Click to collapse
What version of AVRCP does your car support? The reason I ask is because I borrowed an almost brand new Mazda3 towards the end of last week and AVRCP worked perfectly; but the car supported AVRCP 1.4 (possibly higher - I was able to browse track lists).
Is it possible that AVRCP 1.3 is broken? I'm not alone in this issue after months of Googling; and I have tried all of that previously multiple times but thanks for the suggestion.
dsgoody said:
What version of AVRCP does your car support? The reason I ask is because I borrowed an almost brand new Mazda3 towards the end of last week and AVRCP worked perfectly; but the car supported AVRCP 1.4 (possibly higher - I was able to browse track lists).
Is it possible that AVRCP 1.3 is broken? I'm not alone in this issue after months of Googling; and I have tried all of that previously multiple times but thanks for the suggestion.
Click to expand...
Click to collapse
It supports avrcp 1.3. No track lists for me. Just song, track, album info and ability to use steering wheel controls. My head unit is the stock VW RNS-315.
Sent from my SM-G935U using Tapatalk