Database Users

Bluetooth A2DP issues w/ 2.1

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.

Bluetooth issues for 4.4

I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.

Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?

Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.

BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !

Mine is also a rev11, 303k. I guess that rules out hardware issue

Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.

I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !

paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:

My Continued Bluetooth Nightmare

OK,
So I'm trying to get some help regarding this issue. I will continue to try different ROM's and what not to see if it can be resolved. I'm simply at a loss to where the issue lies though, however as of today, every custom ROM has been giving me trouble. My plan for today is to flash a stock ROM via Odin and then if that works go for Imperium, however I'm hoping with your help I may be able to solve it on something like CM12 or what not because I prefer the flexibility of a proper custom ROM.
OK, so the issue I have:
I have a car head unit which has bluetooth built-in. Music plays fine through Bluetooth, no jitters or issues. However, when I try and call someone and I'm listening to the radio or something non-Bluetooth, the phone does not send the signal (?) to the head unit to switch to Bluetooth. This means the call will be made via the dialer app and while the audio IS being routed through the bluetooth channel, the head unit does not know about it because it hasn't received the signal to switch to Bluetooth. I can switch it manually to Bluetooth and make and receive calls, but this isn't convenient at all and probably quite dangerous when I'm driving a car. The same applies when receiving a call.
Here's the thing, if I go into Bluetooth, select CAR KIT and go configuration, if I disable Media Audio, then it works fine! The phone correctly sends the signal to switch to Bluetooth and the head unit does so. The call goes through and it all works fine. This is repeatable.
Therefore, the issue I'm having lies in the fact both Media and Phone Audio are enabled at the same time. Has anyone else had this issue and does anyone have a suggestion to fix it?
Before someone suggests "just disable media audio". My answer is no, this isn't convenient at all. I use Bluetooth media quite a lot, and simply disabling and re-enabling it everytime simply isn't an option.
So far, I've had this issue on:
CM12.1 Optimized
CM12.1 Nightly
Mokee ROM
DirtyUnicorns
CM12 Nightly
I'm yet to try a stock Lollipop ROM. I know for a fact however, that stock KitKat DOES work.
I really could do with some help here, so any suggestions would be awesome.

all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved

DSA said:
all the roms you have tried are aosp....aosp is not designed for the s4 as its not an officially supported device (its not a nexus) so things like bluetooth and the camera will always be broken as the required stuff needed is proprietary to samsung
go back to stock and your problem will be solved
Click to expand...
Click to collapse
The Bluetooth itself is fine. Audio quality is fine. Call quality is fine. It just seems like a tiny little thing that's causing all these issues for me, because if it could trigger my car head unit to switch, I wouldn't even dream of stock. Also the camera seems fine to be fair?
I'm not keen on going back to stock.... at all, so I'm thinking Imperium. It's a shame though because apart from this BT issue, CM12 is fantastic on this device. Takes a 2 year old phone and makes it feel like a brand new phone.
I really hope someone can fix that Bluetooth bug in CM12.1. I may even look myself, it must be something pretty small from a coding perspective because as I said, the functionality is clearly there as evidenced by the fact it works with Media audio turned off.
Regardless, thanks anyway

Changing the modem did not solve my problem.

When did you try the Optimized and the nightlies? There have been a lot of fixes lately regarding bluetooth.

Strange bluetooth problem after upgrading to 6.0

Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.

DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect, but calls still go though the speaker and I cannot change it to Bluetooth mode (my car, however, sees it). And when hanging up the phone, the phone will say "Hanging Up" yet still stay connected for what seems to be an indefinite amount of time - or until I restart the phone. Needless to say, callers on the other end cannot hear me. And, when playing music, the car's head unit does show that it's playing but again, music comes through the phone's speaker only.
Any advice? I've already tried flashing AOSP 6.0 and Kushan CM 13.0 and it's the same thing on both.
Thanks.
Click to expand...
Click to collapse
Simple
6.0 Rom bugs.
Wait until they are fixed

They all are based on the same code. So if one roms has it they all have it.
Keep in mind that MM is brand new so you just have to be patient for it to be fixed.

DJRepresent said:
Hello,
Where my bluetooth previously worked on Android 5.0, ever since upgrading my i9505 to 6, Bluetooth does seem to connect
Thanks.
Click to expand...
Click to collapse
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).

mr.b00tl00p said:
In a strange coincidence, I had all sorts of trouble on my i9505 with Bluetooth on 5 but is mostly resolved on 6 (CM 13 official).
Click to expand...
Click to collapse
same here, but now i have new one's like connecting my mi band at all :/

I also had problems with BT with the CM13 Official Nightlies, and also with the Resurrection Remix.
But I now use the JDCTeam 6.0.1 ROM, and I don't have BT issues, I only use my BT in car, but I can send and receive phone calls, and also stream my music via BT.
Furthermore, almost everyone complains about the no sound with the calling issues.
I also had those issues back to the official CM13 and the RR 6.0.1 versions.
For me, this ROM is really good, you would maybe give it a try.
I use an old bootloader, the FNB8, but it seems to work pretty fine.

ROM that doesn't have Bluetooth audio problems?

I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??

djmasters said:
I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
Click to expand...
Click to collapse
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!

djmasters said:
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
Click to expand...
Click to collapse
I was wrong, after a couple of days AICP started doing the same thing. Replaced XT1575 with an HTC 10, I wish the screen was larger but it's a really nice phone!!! And no Bluetooth troubles.

My phone is connected to my car radio any time I'm in the car, and not having this issue. I'm still on 5.1.1 stock but rooted. Headunit is a Alpine CDE-W235BT. I've had it hooked up 5+ hours at a time. No issues with media or phone calls.

Yeah, it works for some but not for others... I think it's more headunit dependent... my Clarion was OK for music but the phone was jacked up. Reverse with my Kenwood, phone OK but audio jacked. Either way, it had to go.....

Factory rom is the only one I can get to work properly with BT in my Mercedes

I haven't tried it on the Moto X Pure, but on the 2nd gen Moto X, Cyanogenmod had infinitely better bluetooth strength than the stock rom, or any other rom I tried. I'm not saying it's the same for the Pure, because they're probably maintained by different people, but worth looking into at least.

Bluetooth usually connects between my Moto X Pure and Mazda3, but there is a 35% chance that when I turn on my car the audio will connect in this really strange manner where tracks skip and the audio sounds horrific. The only solution is to disconnect and reconnect again, which takes another 30 seconds.
Every ROM I have tried on Moto X Pure has had this problem:
Stock, CM13, AICP
It's gotten so annoying that I've decided I am going to sell my Moto X Pure and revert to my Galaxy S4. Never have ANY problems with my old Galaxy.