I noticed that Bluetooth was listed as a fix in the new rom. That's actually a problem I've been having. I have a Garmin GPS with Bluetooth that I use when I'm driving (speakerphone). I loved it with my old 8125, but I just got the mogul and speaker volume has been so low with it. Has anybody else experience this problem? What are the thoughts on bluetooth with the new rom for users who have tried it?
I had the same Bluetooth problems on older ROMs, but it works great on the unofficial 6.0 and 6.1 ROMs. I expect it to work as well, if not better on the official version.
Well, I tried it out on my way to work today. It was only my voicemail, but it sounded much better. Hopefully that will be the case when I get a phone call.
Well, when I just got Mogul and bought BT prepped car (never used BT before), I thought BT sucked reaaaly bad, since EVERYONE complained if I called from my car. Now, since unofficial ROMs, I get occasional complain here and there, but it is obvously tolearble to most of people I call. I also reduced volume on BT in my car after upgrade, so I think it should solve the problem.
I think part of it was that I was upgrading from 2.17 (not sure what has come since). But, it does seem pretty good now.
Related
First let me say thank you to those of you who have put so much into this forum and site. I have gleaned much from the questions, answers, and wiki for many months now, and there has always been an answer for my problems (or the explaination why it just won't work). However, I have run into an issue that I would like some input on.
I have an XDA IIs with the latest full ROM update from O2 (not a cooked ROM), with the following ROM specs:
ROM: 1.40.00 WWE
Radio: 1.12.00
ExtROM: 1.40.237 (Corporate Installation)
Broadcom BT Stack: 1.0.0 Build 3900 w/ optional patch for HQ Audio & keyboard
I use bluetooth for both a GPS device and a Motorola HS-850 hands-free headset. I have no reception issues whatsoever with my GPS device. I can also connect and use both devices simulataneously. However, I encounter some strange anomalies with the HS-850. When I am in my car or in a room in my house, the reception is fine within 10 feet. I can hear the other party, and they can hear me clearly without static. However, if I am outside or in a larger room of my house, the quality diminishes greatly, even to the point where neither me nor the other party is discernable. I wear the leather case included with the XDA IIs on my belt, and whether in or out of the case, the quality remains the same in both scenarios. The only way I can get the reception to be acceptable outside is to hold the phone within 1 foot of my headset.
I have read most of the posts and all the wiki regarding the Blue Angel's bluetooth capacity (or lack thereof), and I do not have the disconnect issue that others have discussed in this forum. My question is: have others experienced similar issues, and is it typical for the environment (closed vs. open) to have such a drastic change on bluetooth capability? It is almost as if the bluetooth reception is dependent upon whether or not the signal can be "held" within a room or vehicle. To make it stranger, I can leave my phone in the car during a call, close the car door, and walk around the car and retain an excellent signal and carry on conversations without any problem.
Any ideas or thoughts would be appreciated. I have not upgraded my ROM to the latest available Blue Angel ROM as the updates do not seem to have affected this issue specifically, and my PDA/phone works perfectly apart from this one issue. If anyone thinks this would help, I would be interested in updating.
Thanks for your time to read and consider my dilemma.
Update
I just wanted to update everyone.
I was able to acquire a Motorola HS-820 headset. After pairing, it worked much better than the HS-850. One comment from a friend was that it is "400% better than the other headset." The 820 is also a little louder, which makes it nice on my end as well.
I can now use my headset in and outdoors without losing or dropping my voice. Occasionaly it will break up when something gets between the phone and the headset, but for the most part, the headset works perfect even outside of direct line of sight.
So for all of you out there trying to decide on a headset, my recommendation is to try one that is known to work and then experiment if it doesn't. There were many on this forum who recommended the HS-850, and I purchased mine per their recommendation. Unfortunately, it didn't work well with my Blue Angel. After getting the HS-820, it worked very well, and I am now happy with the bluetooth capabilities of my XDA IIs.
On the other hand, I have also read on this site about those who have done the opposite of what I have: began with the HS-820 and moved up to the HS-850 due to problems with the HS-820. As we can see from the testimonies of many on this site, the Blue Angel's bluetooth capability is quite variable.
Thanks again to all those who have helped on this site. It is an excellent resource that I intend to pool from for a while to come.
BTW: I did not update the ROM at all during this time. I am still running the same config as posted above.
I am happy user of AP3.0. The only element of my Advantage that could do with improvement is the Bluetooth - which I think Pawel addressed in AP4.0. However, that particular route to upgrade is awaiting Pawel's release by the fiends in the Polaris forum that have been holding him hostage for such a long time.
Search as I have, I cannot find any other ROM that has tried to port the Widcomm stack into the Advantage. Can anyone let me know if they are looking in to this?
Thanks
Robert
I was tired of the bluetooth in HTC stock WM6 rom. I didn't work with my LG HBM-700 at all because bluetooth on my X7500 turned itself off every now and then. I also had lot of problems with a Jabra handsfree.
On Michy 1.88 it is a lot better, but I have experienced a few problems there too. Bluetooth turned itself off a few times the first day after I installed this rom, but that could be me. But one night after a weeks usage bluetooth turned itself off.
I wonder how irus 0mb rom works. I noticed it is using another bluetooth stack and seems to be more battery friendly for bluetooth devices. Any experience on this?
Bluetooth Reliability
I'm in the same boat. I'm using a Sony HBH-DS220 Headset and the only ROMs that use to work well with it are AP4.0 and AP5 Beta. In the last months alone I've gone through no less than 6 - 7 different ROMS from IRUS Vanilla to Michy 5.1 with the same or similar results. I'm hoping that Michy will have a look at this change the stack in his next ROM.
tazeemn said:
I'm in the same boat. I'm using a Sony HBH-DS220 Headset and the only ROMs that use to work well with it are AP4.0 and AP5 Beta. In the last months alone I've gone through no less than 6 - 7 different ROMS from IRUS Vanilla to Michy 5.1 with the same or similar results. I'm hoping that Michy will have a look at this change the stack in his next ROM.
Click to expand...
Click to collapse
What are the problems you are having? I am using a Sony DRC-BT15 - similar to your DS220s as well as a HBM-700 Styli with no trouble on Michy 4.1 (and 4.0).
Mrsums,
are you absolutely SURE that PK4 have Widcomm stack?
If i remember correctly, it also have the usual MS stack. Too lazy to reflash though to confirm.
I found out that certain combinations of ROMS and Kernels work better with my CAR Bluetooth then other combinations. For instance CM6 is not working perfect and is uncertain to reconnect to my Car system. On the other hand most Sense ROMS work better with my Car system.
So in this project I wanna track down first which components have influence on the bluetooth stack, and more important which specific parts of the kernel, software and other things are related.
This to improve the BT Car system of at least my Scenic but I have the feeling more Car systems have issues.
Please if you have info about this put it in this treath so we can make it better.
Nice initiative. My BT system in my car works flawlessly with WinMo, but as soon as I connect my nexus, my speakers begin shrieking like all hell breaks loose. Also, My Nexus the seems to lock up and I need to pull the battery for all misery to end.
LOL.
That was the first time I connected the bugger, so I wasprobably still running Eclair when I tried it.
6.1.1 works well for me, both bluetooth calling and a2dp.
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
PhantomRampage said:
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Click to expand...
Click to collapse
This happens to me too once every three or four songs, but it's such a small thing it doesn't bother me much. On the other hand, for the short while I was using MIUI, I felt it was happening much less, but I may have been imagining that
Heres my setup, and it works flawlessly every time i start the car.
Car Deck: JVC KD-R900 (Using the small bluetooth adapter that came with the unit mounted in the back USB port)
ROM: Enomthers TheOfficial Nexus1 v2.14.3
Kernel: 2.6.32.35-TheOfficial-AudioMOD-720p
Radio: 32.41.00.32U_5.08.00.04
OS Version: 2.2.1
Like i said earlier i have no problems with the audio quality or connecting to my unit. As soon as i turn my Bluetooth on it connects within about a minute.
Calling quality is good, audio quality is good and AVRCP works also (play/pause/next/prev)
If you need anymore info just let me know.
Its good to see there is some reaction on the start of this.....
My goal is to achieve and to find out which components are involved in the Bluetooth experience:
F.I. :
* Kernel modules and libs
* Application in the rom to actually making the connection
* Bluez configuration and settings
I have done some searching but found that even with the same Bluez settings there can be a difference between some roms in combination with kernel.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have the same issue on my Kenwood system.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Me too, same model. I've updated the firmware on the X993 and it seemed to help.
elfblackdeath said:
I have the same issue on my Kenwood system.
Click to expand...
Click to collapse
Same here on my DDX-812. Almost everything "works", I just get the drop-out when streaming music if it's not a fresh pairing.
The bluez stack was updated with Gingerbread...I'm hoping against hope that that fixes some things.
i have to use a no-audio-boost kernel with my jabra headset, otherwise the call quality is abysmal. lots of metallic clicking and other strange effects going on.
but i have seen no differences in the overall connection stability otherwise.
hmm i have a problem with my car dock and bluetooth i think. when using the navigation the voice plays via the phones speaker not the dock speaker. is this similar to the problem in the 1st post? if so, would love a fix!
I'm on CyanogenMod Nightlies with the included Kernel and have a Kenwood DDX8024BT with built in bluetooth. It connects up perfectly when I turn the ignition on and seems fine when in call. I don't use the A2DP much but when I have I've not had any problems.
Slightly OT, the only problem I have is with reading contacts from the phone. I have two phones paired. I usually have the Nexus connected but occasionally switch to my work phone (a Tocco Lite). At some point it took the contacts from my work phone and then wouldn't redownload the Nexus contacts when it was reconnected. It's now done it at some point but there's a handful of contacts that still won't transfer no matter what I try.
On a side note, I have a Clarion CZ500 rig in my car, and the N1 is incompatible with the microphone boost firmwares they offer on their site. All I hear is crackling when I try to make or receive a call.
What's odd is that the HTC Desire works fine with those firmware. Even Blackberry Pearl.
I ordered the N1 dock on eBay. I guess I'll see if the dock can handle the firmware.
i have a n1 and im still running cm 5.0.8 with android 2.1
my phone pairs with my car without any problems and i am able to talk to people and whatnot. Now as far as music, i use a blackberry music gateway bluetooth device that i plug into my car's 3.5mm jack and then i pair that device with my phones bluetooth. It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!! I paired the blackberry gateway device with my gf's mytouch and there was no such problem, which leads me to believe that the problem is in my n1 :/
My $02: I cannot use a2dp and hands free at the same time. If both are connected the the a2dp drops out all the time.
This is not an issue with my HD7.
A workaround would be awesome.
Sent from my Nexus One using XDA App
I suspect the main difference, hardware combinations aside, between Stock/CM and Sense roms is that they use different bluetooth stacks.
Differences in the bluetooth stack that have caused issue for the FM radio on stock roms, an issues for bluetooth file transfer on Sense roms as far as I know.
Like iphone fanboys would say: fragmentation
On a related note the behavior of my N1 with the Parrot handsfree has vastly improved in GB.
i have the kensington liquidaux bt adapter in the car and cm7 rc4 with stock kernel skipped constantly. rc2 was better, but still unbearable.
i am currently on intersectraven's 4/3/2011 kernel and from limited use, has not skipped on me yet.
have people tried bt music streaming with other kernels with cm7 rc4? wildmonk? pershoot? etc.. thanks.
Try CM7 Issue 3233 fix
d1mitrov said:
It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!!
Click to expand...
Click to collapse
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
scotte9999 said:
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
i think thats exactly what my problem is, when the phone is connected to the car and the music gateway is connected as well i get the intermittent connection and it skips every so often but if i disconnect the phone part then the music never skips...however im not on CM7 so i dont know if that fix applies to me and i dont know how to begin changing those settings
My droid would use whatever BT headset (stereo or not) for the phone when my headphone jack was also in use (to use car stereo) for audiobook player.
I have new Fascinate and I swear it did the same until I rooted it. Regardless, it will be close to a deal breaker if I cannot find a solution to this.
Even if the headset indicator is ON, the sound still goes to the headphone jack, RIDICULOUS
In my opinion, plugging into headphone jack should only take over media type output (music, audiobook player, video) and LEAVE PHONE ON BLUETOOTH. We should at least be able to chose this behavior in a setting.
So is this a Samsung screwup? do other Samsung devices behave this.
How hard would it be for a dev to build an app to FIX this on Fascinate.
I thought I was the only one with that situation... I would love to know the answer/fix, however I have a feeling someone will be by soon to move this to the general forum...
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Click to expand...
Click to collapse
I believe that my Droid 1 behaved my desired way on 2.1 and 2.2, can't remember if I used this way on 2.0...
I was assuming this was a 'problem' on Fascinate or Samsung, not android OS in general.
I thinj its a problem with fascinate. I was driving for 5 hours last week and I had bluetooth connected to my garmin and used one of those cassette thingies to play music from my fascinate. Sometimes I were able to talk without unplugging the headset.
Another reason I suspect its fascinate is cuz when I use my old blackberry headphones I have unplug and replug to use it for conversations.
Btw whats good stereo heaphones with mic that works with the fascinate?
Sent from my SCH-I500 using XDA App
I have a friend with a Vibrant and his apparently does NOT have this problem, so I am wondering if a Bluetooth file from his system might work on my phone.
There are 3 BT files in system dump:
BT OPP
BT services
BT test mode
so is one of these the file that would determine what path audio would take in any given situation? (e.g. headphone jack occupied while BT headset connected, desired paths media>headphone phone>BT)
I REALLY need to fix this before my 30 days are up or phone probably going back.
I got my hopes up when I discovered the 'secret menu', but I don't see any setting in there that seems appropriate.
I've tested with the superclean 0.7 DL30 rom and this same problem still exists
Please let me know if anyone finds a solution.
[email protected] said:
i've tested with the superclean 0.7 dl30 rom and this same problem still exists
please let me know if anyone finds a solution.
Click to expand...
Click to collapse
stupid ass samsung friggin morons!
It looks like this is a problem on other Samsung Galaxy S phones as well, see a thread and app someone made in the Epic forums.
http://forum.xda-developers.com/showthread.php?t=842571
it is just the phone app
this problem is extremely frustrating. if i have headphones plugged in the mic works just fine. the mic is only turned off when i use an AUX cable. It would be nice to be able to drive and not have to worry about unplugging the AUX cable everytime I wanted to use my phone.
I downloaded the Epic app they made over there but all it did was hard lock my phone with my first test. I dug into the code but I'm a wee bit over my head so I'll hit up the books and see if I can't work with the guy who made the Epic one to see about getting it working with our phone.
This was with the .7 superclean DL30 rom, I'd love for someone else to try one of the other DL30 roms and see if they have any better success.
I contacted the author of the app and he replied back stating he had a buddy with a fascinate test it and it worked fine and that it might be an issue with the busybox version included with the .7 superclean 2.2 rom I was running and that it relied on busybox having the pidof command. Later tonight I'll dig into this a bit more and post back hopefully a fix and instructions on hwo to ensure this is working
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
thande said:
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
Click to expand...
Click to collapse
I am on original DL30 leak and did NOT work for me... at least with Ambling Book Player. Not sure if it matters what app we are using to play media file. It shouldn't, but this whole problem should not exist. SAMSUNG morons!
Ok so i tried with my Rubiks DL30 ROM installed. The app opens up, no FCs or bricks or anything, but it doesn't work. I had my wife call me when i was driving, I picked up and she said she could hear me but I still couldn't hear her. I'm assuming that the car's mic is functioning but it still doesn't fix the issue. Is there a bluetooth adapter out there i can stick in the aux jack? Well i guess the first question should be, can the phone handle having two BT devices connected at the same time? i.e. hands-free calling and BT audio adapter
I'd say maybe try another full wipe and re-flash. I've switched over to the superclean EB01 roms, currently on 2.3 and hasn't had any issues with this working on 2.1, 2.2 or 2.3. I did have 2.2 initially not function with this tool, similar to what you reported above with it looking like it was working but not actually doing anything but a full wipe and reflash did the trick.
ok... thanks, at least you've run into that problem so i'm willing to give it another go. I'm currently on SC 2.4 so i guess i can be your guinea pig
I'm on SC 2.4 currently and had it stop working on me again. At work now but I'm going to try setting the app off and then back on, I have had to do that sometimes when flashing as the files get overwritten. This was working properly in SC 2.3
Hey man, thanks for the updates and info... you're really like the ONLY person that's giving me any hope on this. I thought the compatibility issues were busybox related? So I don't see why it wouldn't work on SC2.4
Would someone please fix this on Fascinate... ? pleeeeezzzzzz
my wife just updated her moto DX to a new TB. She used to sync her bodymedia fit device to her DX - its basically a bluetooth pedometer.
Now she can't sync with her TB. Also no go with a small bluetooth keyboard from deal extreme.
I knew about the wiimote issue but this is kind of sad. can the TB sync with anything other than headsets?
I remember when I first got my iphone i ended up jailbreaking and modding the BT stack.
Will this be fixed in the update? Can rooting allow a new bt stack? I'd really not want to install a whole new rom.
thanks!
CM7 has a completely different bluetooth stack than stock and every other currently available ROM. I've been trying and failing to try to get someone to write and update package to replace the stock bt stack with the one from CM7, but no one really seems to care.
For me it's about BT Audio quality. The stock setup sounds horrible because the bitpool setting of the stock stack is too low. If someone could figure out how to increase this or change the stack completely I'd be a happy camper. I did test CM7 out last night and the audio quality was superbe as I expected, but there's just too many things that are broken or don't work to use that ROM daily right now.
I was hoping that there would be a way to simply replace the bt stack without flashing a new rom. Seeing how the HTC phones don't work with so many bt devices you would think there would be more demand for this hack.