Dear friends,
After a very, very long time I finaly came across the solution to the BT problem on our DHD!
Especially, but not only, when trying to use the BT car kits with our DHD the BT connection drops after a very short time.
Please see the solution through this link [credits to the one who found it ]
Cheers
This is a very good tip.
Thanks
Sent from my Desire HD using XDA App
Hi, didn't work for me, still same problem.. tried different radio versions, but still same..
Have CoreDroid V5.4 and the 'M2' radio.
Which ROM are you using..?
Thanks
Related
Just flashed AR HD w/ no-sense for the first time last night, coming from MIUI and so far it's pretty good. I used Cyanogen for quite a while, then MIUI.us, which hasn't been able to get the code for Bluetooth A2DP yet. The "other" MIUI rom fortunately does have A2DP working, but since AR HD is the most popular ROM I'd thought I'd give it a try even though I'm not a fan of Sense.
Major dealbreaker is that I can't connect it to my car's Bluetooth stereo. I had no problems with stock, CM, or the "other" MIUI rom, but with this, I just can't connect to it.
Tried searching around, but couldn't find anything from anyone else having this problem, so I find it strange...
Any assistance would be appreciated, thanks!
CoolJunkie said:
Just flashed AR HD w/ no-sense for the first time last night, coming from MIUI and so far it's pretty good. I used Cyanogen for quite a while, then MIUI.us, which hasn't been able to get the code for Bluetooth A2DP yet. The "other" MIUI rom fortunately does have A2DP working, but since AR HD is the most popular ROM I'd thought I'd give it a try even though I'm not a fan of Sense.
Major dealbreaker is that I can't connect it to my car's Bluetooth stereo. I had no problems with stock, CM, or the "other" MIUI rom, but with this, I just can't connect to it.
Tried searching around, but couldn't find anything from anyone else having this problem, so I find it strange...
Any assistance would be appreciated, thanks!
Click to expand...
Click to collapse
Im running 3.6.7 and it quite happily connects to my built it Bluetooh in the car. Although this is for incoming phone calls and not A2DP so I dont know whether this makes any difference.
I ordered a Bluetooh Music receiver from Amazon last week to connect to my home cinema system and I was hoping to use my phone to wirelessly transmit music, now you have me worried! I will report back when it arrives and I have tested it.
Hoping to find it on the doormat when I get home from work today
Hi,
Bluetooth is notoriously poor with sense roms.
Cm7 has a very good bluetooth stack.
Hence you can work games controllers with it. And presumably your car equipment.
On sense roms, though, it can barely work my hands free ear piece.
So, if you use a lot of bluetooth, you are better off on cm7.
Thanks for your response! I've switched back to miui for now, but in searches for a2dp issues with ar HD, I couldn't find anyone having a similar problem...strange...
Sent from my TripNMiUI Pyramid using xda premium
now you found one
I have revolution hd 6.0.3 and it still doesnt work... tryed it with mercedes benz inbuilt BT ... Phoning worked music not ... trying with Sony Erricson MW600 ... not working ... pairing ok , mw600 is selectable in the sense music app ... but no sound ... still playng out of the inbuild speaker of the phone
I have the same problem with Android Revolution HD 6.0.3. Can anyone help please?
So I recently got Cyanogenmod 9 for my Sensation and I love it so much! However, I do in fact have one concern. Is there any way to fix the audio routing issue? Are there certain ICS Roms out there that don't have this issue? I flashed over from ARHD because of Bluetooth stack issues, that was good enough reason as it is. Now I have a whole-nother problem.
Every time I use an apparently that uses a microphone, the audio gets VERY quiet! Almost inaudible! I know that the Nightly CM builds currently have this issue, but are there any other stable ICS Tom's out there that don't have this issue? I love ICS a lot and don't want to abandon it. If I end up leaving CM until a stable build is released? Fine. But for now, I'd really appreciate some input to see if there is a way around all of this.
Thanks.
I use Ordroid with sense4 and I can confirm that the Mic works fine. Speaker is loud on speaker options. I don't have that issue. It's a Ics rom with sense4. It's a excellent rom however tethering does not work. Other than that It's fast and stable . Lots of customization options , aroma installer, and tweaks. I personally love it. You might want to try it if you can't find a fix.
Sent from my HTC Sensation 4G using xda premium
Does Bluetooth work? How about wifi hotspots? I use Sixaxis controller ALOT and want to make sure I can keep it that way. So Ordroid goes back to the original Sense look?
Bluetooth works on Ordroid, so i suppose six axis should work pretty well without an issue. as for WiFi hotspot, yes it does work, although wired tether doesn't.
the look of sense on it is sense 4, latest sense by hTC...that can be found on the One series.
Hello all, I got a question.
I recently bought a car, now the good thing is that it has a sony bluetooth radio (Handsfree calling). However I cannot get my phone paired to it, it won't recognize devices.
Radio: http://www.conrad.nl/ce/nl/product/373396/Sony-CD-tuner-MEX-BT3900U/0304001&ref=list
Phone: Sensation 4G
Rom: OrDroid 9.0.0
Would anybody be able to help me?
I'm having problems with Bluetooth audio too. Though, it solved itself.
Maybe a reflash will help.
all sense4 rom have problems with bluetooth audio i think...
try viper, thats based on the newest RUU and overall similar to Ordroid...
Hi. I haven't got the post count to ask this in the Jellybam thread, so though I'd give my problem a go in here.
Is there a known issue with the Bluetooth in the Jellybam roms? I've tried 3.0.0, 3.1.0 and 3.2.0 and with each one I can pair the phone with my car but the phone book wont load up and it phone keeps disconnecting. Also despite it being set to use the cars audio, it does not.
Previously to this I was using Stickman89's Jellybean JBMIUI rom with no issues.
A full wipe was done when switching from the JBMIUI rom.
Any ideas guys?
Cheers.
Can't help but can confirm the same issue, all day in the car it kept connecting and disconnecting to my Bluetooth car kit.
Have you noticed it keeps going into silent mode? I am sure its related.
Yes I am using jelly am 3.2.0.
Sent from my Sensation using xda app-developers app
bluetba said:
Can't help but can confirm the same issue, all day in the car it kept connecting and disconnecting to my Bluetooth car kit.
Have you noticed it keeps going into silent mode? I am sure its related.
Yes I am using jelly am 3.2.0.
Sent from my Sensation using xda app-developers app
Click to expand...
Click to collapse
Yes I had noticed that, but put it down to the constant connecting/disconnecting of the Bluetooth. I'm hoping a fix can be found as otherwise this is a great rom. If not I'll have to revert back to JBMIUI rom.
Jellybam is not the issue I believe. Android 4.2 changes now android uses Bluetooth and as such has broken a lot of things for people like we now cannot connect Wii remotes via Bluetooth as we'll get an error stating that the apps cannot find the path to it :thumbdown:
heavy_metal_man said:
Jellybam is not the issue I believe. Android 4.2 changes now android uses Bluetooth and as such has broken a lot of things for people like we now cannot connect Wii remotes via Bluetooth as we'll get an error stating that the apps cannot find the path to it :thumbdown:
Click to expand...
Click to collapse
Unless I'm missing something Jellybam is 4.1.2. So I'm pretty sure it's not the 4.2 Bluetooth problems I've been reading about.
Update.
I gave up on JellyBam (which is a shame as I liked every other aspect, but not JellyBams fault) and tried a couple of other Jelly Bean roms. Both of which had the same Bluetooth connection issues.
So it would seem the only Jelly Bean rom where the bluetooth works is Stickman89's JBMIUI rom (other JBMIUI roms may work also). Though due to me being bored of the MIUI rom now, I've gone to an ICS rom Elegancia sense 4.1 v3.2.0
I shall keep an eye on Jelly Bean as hopefully this Buetooth issue will be solved and I can go back to JellyBam at a later date.
I really like the new features of JB 4.2.2 based ROMs but i have one big issue:
NOWHERE the bluetooth Car Connection A2DB is working!!
I tried Vanilla Rootbox, Avatar, PAC and a few other 4.2.2 (CM10.1 based ) ROMs.
Streaming music to my car is working perfectly, i can sync my contacts to the car but a Phone call just makes "white noise".
I switched to Stock ICS 4.0.4 and here i can use the Car connection and audio is great - but Stock ICS this is abslutely not my taste.
For about 2 Weeks i'm searching for a solution now without any success
Anybody has any suggestion for a ROM, Hack or fix? <- PLEASE!
btw: Vanilla Rootbox 7 for Galaxy S is working - why not on Galaxy R??
Torpedro1978 said:
I really like the new features of JB 4.2.2 based ROMs but i have one big issue:
NOWHERE the bluetooth Car Connection A2DB is working!!
I tried Vanilla Rootbox, Avatar, PAC and a few other 4.2.2 (CM10.1 based ) ROMs.
Streaming music to my car is working perfectly, i can sync my contacts to the car but a Phone call just makes "white noise".
I switched to Stock ICS 4.0.4 and here i can use the Car connection and audio is great - but Stock ICS this is abslutely not my taste.
For about 2 Weeks i'm searching for a solution now without any success
Anybody has any suggestion for a ROM, Hack or fix? <- PLEASE!
btw: Vanilla Rootbox 7 for Galaxy S is working - why not on Galaxy R??
Click to expand...
Click to collapse
I think its known bug buddy. Let it be fixed.
Thin is a known bug since at least january!! I thought ast least one ROM could be there where this basic wefa
Don't get me wrong all the devs do a really great job here!!
But why is the priority if implementing the basic features so the ROM gets usable so extremely low??
Who do i have to donate to get this fixed?
I would be availabe as a tester for Car Bluetooth
Torpedro1978 said:
Thin is a known bug since at least january!! I thought ast least one ROM could be there where this basic wefa
Don't get me wrong all the devs do a really great job here!!
But why is the priority if implementing the basic features so the ROM gets usable so extremely low??
Who do i have to donate to get this fixed?
I would be availabe as a tester for Car Bluetooth
Click to expand...
Click to collapse
Who do i have to donate to get this fixed? - Buddy, Please elaborate this line.
Also, When Devs works over any project, then they fix Major problem, not the basic one.
So let Dev to handle this.
Devs r working on it..u just have to be patient n everyone knows dey can get it done..respect wat dey have done to our device which ll not be having 4.2.2 if dey wer not der..if ur desperate to use Bluetooth a2dp, den switch over to ics
Sent from my GT-I9103 using xda app-developers app
Disturbed™ said:
Who do i have to donate to get this fixed? - Buddy, Please elaborate this line.
Also, When Devs works over any project, then they fix Major problem, not the basic one.
So let Dev to handle this.
Click to expand...
Click to collapse
First thank you both for your answers!
I did not intend to offend somebody - sorry if it came over this way. I'm just telling my experiences and maybe i cannot write it in a polite enough manner (which is a known bug in my personal firmware).
I do respect all the devs! I already said they do a great job!
JB (CM10.1) based ROMs are great with battery life, usability, flexibility, features and everything works - except receiving calls an A2DB car hands free calling.
I tried serveral JB ROMs for a few months now, because i really like it - but my wife got crazy by now! She could almost never reach me, because the phone ignores incoming calls when it's in deep sleep or roaming - a known bug, i know. This one must be a lot harder to fix than a simple Bluetooth audio config which is 98% working anyway - thats way i just asked if there was a fix i didn't find.
On other Devices these features seem to be much easier than on the Galaxy R because both these issues are forking perfectly on our Galaxy S (1).
Regard Donation: Well, i thought the problem with this fix is that somebody might be missing a bluetooth headset to test it.
Since Media A2DB works but Hands free Calling does NOT i thought it might be just something VERY simple to fix and just the needed test-equipment is missing..
According to your recomendation i'm back to ICS Blueberry.
Thank you again!
I have the bluetooth handset.. And I know how to test Self... But no time...
Sent from my GT-I9103 using xda app-developers app