ICS Bluetooth Discussion - Verizon Droid Incredible 2

I'm branching off from aeroevans CM9 thread to talk about bluetooth.
Notable: I'm connecting to bluetooth in my car.
I have been using Bluetooth for a couple years on CM7 with no problems. I flashed the 4-20 build the other night and had trouble with both calls and music streaming. In outgoing calls, the recipient couldn't hear me, though I could hear them. With music, it would go silent every couple seconds for a few seconds. These problems weren't unexpected as the ROM is still in development. (and HTC can't get their **** together and give us ics vivow drivers...)
I use bluetooth a lot, so I proceeded to restore CM7 that I had backed up before flashing ICS. Now, I'm not able to stream my music as I had in the past. It's doing the same silent thing as it was in the ICS build. I was able to make an outgoing call, but it cut in and out more than normal.
So my questions are: What controls the bluetooth? The kernal? the rom? HTC drivers? something else? Why would I still have issues even after restoring to CM7 that has worked find in the past?

Similar problem with both cm9 and AOKP ICS for me.
Just to clarify I am talking about BT in my car.
When I dial out I can't hear them and they can't hear me. When I receive a call I can sometimes hear them but they can never hear me. Audio BT for music transmits fine though.

I think I fixed this just by clearing the cache... The must have been something lingering from ICS.
To get bluetooth working on ICS, do we need drivers from HTC?

Related

[Q] BlueAnt V1 Headset + Evo

Trying to find some feedback from anyone using the BlueAnt V1 bluetooth headset with the EVO.
I'm having problems with the headset not answering calls maybe 85-90% of the time. It announces there is a call, but will not answer via voice command or hitting the button. I can answer via the phone but when I do it doesn't transfer voice to the headset. The headset thinks it is connected because when the call is ended it tells me.
Have done two factory resets on the phone and resets on the headset with no change. Also spoken to Blueant tech support and they weren't much help. All they said is they haven't heard of it having problems with the EVO and should be compatible with all Android devices. Their suggestion was to try it with another EVO and see if the problem still exists. Well, I don't have another to test it on so that does me no good. This headset worked great on both my Blackberry phones before I got the EVO and has the latest updates installed.
BTW...I'm running Myn's RLS4 w/ #17.
Thanks.
Well I don't think it is the Bluetooth , it is the Rom. I have problems with myns #4 with the sync in my email. I have a blue ant also and it does the same thing . I have tried other roms including virus and it works on them , try that .
sent from the phone that is EVO
Pretty sure I tried this headset when the phone was stock and with some other Sense and non-Sense roms. It has never worked properly.
Not sure if it has something to do with the lockscreen or not. The first time it is connected to the phone it works fine. But every time after that, it doesn't connect the call.
I haven't had any problems running anything on Myn's. But just to make sure, when I switch a rom again I will reset and try the headset.
yeah mine does the same thing, it works if i answer w/ voice command but if i press answer button most of the time the audio is route to phone speaker......Lame!
has anybody with a blueant tried it with cyanogenmod? i wonder if the different bluetooth stack yields different results. I'd like to see an app update for the blueant software too (had a cheaper headset that stayed connected way better)
When I pair the headset, it connects and works great the first call I get whether using voice command or button to answer. Then every time after that, it won't connect the call.
Maybe it has something to do with the lockscreen or the phone going to sleep. I will have to do some trial and error.
Currently I am trying out the headset with MikFroyo 4.2 (Sense rom) to see if it makes any difference. This rom is really close to stock so maybe it will work?
I will post back with my conclusion.
My headset works fine now. I have found there is a coding issue that exists in certain roms such as Myn's and CM that prevent proper operation. CM seems to have put together a fix for it. Myn's still does not work at this time. It has been requested as a fix for RLS5 final.
Running eVoKINGS Black Titanium with Mik's 4.2 base and my headset works good.
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
jbrazee said:
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
Click to expand...
Click to collapse
Sorry...it's been a while and can't remember where I read about the fix. If I run across again will let you know. Might try downloading "BT mono" from the Market to see if that helps. Not sure if it is effective on AOSP or not but worth a look.

[Q] Sound stuck in earpiece after disconnecting bluetooth headset?

I've used many ROMs (Viper, Bonsai, Nebula, currently ACS Syndicate) and I've had this problem on all of them. I've even ODIN'd back to stock before and it still didn't fix my problem.
After disconnecting my Epic from my Jawbone Icon headset, the sound often gets stuck inside the earpiece. Music, movies, games, ringtones will all play from the earpiece instead of the speaker behind the phone.
Is there some software fix to correct this? Can any of the devs point me in the right direction as to how I might troubleshoot this (maybe at the kernel level)?
Thanks in advance!
This doesn't really go in Development, and I suspect it will be moved soon.
I can tell you, though, that I've experienced similar problems, intermittantly, and here's what I've observed.
If I'm listening to music through bluetooth, before I disconnect, I'll stop the music. Then I'll turn the bluetooth device off. Then I'll turn bluetooth off on the phone. If I do it in that order, I don't seem to get the bug.
If you do still get the bug, rebooting fixes it.
Hope that helps!
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
daddymikey1975 said:
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
Click to expand...
Click to collapse
This stuff has been going on since DK28 and before. I believe Rodderick was looking into fixing it from the kernel side, but I'm not sure how much progress has been made. I know it's not as bad as it was on DK28, but still very annoying. It used to happen to me all the time (audio going through earpiece instead of speaker after disconnecting Bluetooth) when I would turn my car off and it would disconnect the Bluetooth to my car stereo. Now that I have the Samsung Car Dock, I just connect Bluetooth for phone only, and use the audio out on the Car Dock for Navigation and Media.
Moved to Q&A.
i am having a simular issue but mine is that when i connect to bluetooth headset i have to have media playing before i get a call or i will not hear the other person in the call.
it seems to me that ANY bluetooth headset with A2DP is doing this and i have tried 3 diffrent headsets. Jabra Stone, Jawbone Icon, and the Blueant T1.
all 3 of these headsets do this. does anyone have any solution yet?
Even if there isn't a fix, I wish there was an app to reset the sound settings post facto. Anyone know of one?
I just want to add my name to the list of those who are affected by this. Glad it's not just me, though. Hopefully it can be debugged easily.
For the record, a Quickboot Hot Reboot (reboot of Android only, not phone) does NOT solve the issue. Only a full reboot works for me. Seems like it may not be a software issue but something hardware-related.
Sent from my SPH-D700 using Tapatalk
Just want to add this happened to me the first time just now. I'm on rooted EC05. I was scared for a bit that the speaker had blown. Then when I discovered it all coming from the earpiece, I remembered this thread. A reboot did make it go away.
I wonder if it has any relation to the issue I see once in a while since the upgrade where my BT devices need re-pairing and ask for a passcode, when they really shouldn't.
I Also Have This Issue
I have had this exact issue since DI18.
After I hang up a Bluetooth call, I have popping sounds coming out of the earpiece. Turning off Bluetooth doesn't fix it. Turning Bluetooth back on after turning off doesn't fix it. In addition, after this happens, all devices sounds (phone ranging, notifications) all come through the earpiece and *not* the main speaker.
I've had all of the stock ROMs up until EC05 loaded on this Epic and have had the same issue throughout. I am now running midNIGHT ROM, which has cured most problems I’ve had with my device, except this issue.
I was just poking around trying to find some sort of tool or the name of the service(s) that I need to restart to fix this issue.
Same issue for me. Quite annoying as I listen to audible over bluetooth quite a bit, and then pretty much know I have to reboot when I turn bluetooth off.
SRF users have reported Bluetooth issues being cleared vs. stock builds. I can't say exactly why, but it does seem to work.
What are SRF users?
Nope...
Syndicate Rom Frozen...
Well, I'm on SRF 1.1.1 and I've got the same incredebly annoying audio issue.
Please, someone, come up with a fix!

[Q] Music and bluetooth headset problem

Hello folks
I have tested these roms Leedroid 3.1.1 and Revolution hd 5.1.8
Sound lag when listening to music(Bluetooth Headset) Can anyone fix this problem.
Can you describe the lag better? What kind of headset?
I have this problem too...i have SE MW600 bluetooth headset....problem is signal noise in hight frequenties.with wired headset is no lag.i have this problem only with sense's ROM. cyanogen mod is without this problem.
Sent from my Desire HD using XDA Premium App
Hi,
I don't know if my problem is the same.... perhaps due to language.
My problem is that every 3-4 minutes listening to music, sound pauses for 1-2 seconds, and then it resumes music for 3-4 minutes to next pause and so on...
I have the problem with a Cardo / Schuberth SRC System bluetooth handsfree.
I tried several Sense ROMs and I found always this problem, but with CM7 it works correctly.
I tried to compile the kernel by using CM7 bluetooth options, but no succeed.
I tried by compiling the kernel by overwritting all bluetooth source code related (using CM7 kernel code). I get an error, and once solved by merging code, the problem is still there.
I tried by overwritting all bluetooth related libraries, but the ROM is not starting.
If anyone has any idea on how follow...
THANKS!
This is a known issue with Gingerbread. I actually am surprised there's not more chatter in the XDA DHD forums about it. Google updated the Bluetooth stack in Gingerbread, which breaks compatibility with many Bluetooth audio devices, like headsets and car stereos. While some people claim that updating the Bluetooth stack on your headset/stereo should fix the problem, it's not always possible. In fact, it's rarely possible, as most of the manufacturers aren't going to bother with firmware upgrades for those of us with Gingerbread devices yet.
I haven't tried CM7 myself, as I'd much rather keep Sense, but I think Jorgitosms's on the right track. Not being much of a developer, I'm not at all sure how to go about doing this, but what about pulling the Bluetooth stack out of a Froyo Sense ROM and putting it into a Gingerbread one? I love everything about Gingerbread, except the broken A2DP audio, so I've gone back to Froyo. If we could get this done, I think a lot of people would be relieved.
Jorgitosms said:
Hi,
I don't know if my problem is the same.... perhaps due to language.
My problem is that every 3-4 minutes listening to music, sound pauses for 1-2 seconds, and then it resumes music for 3-4 minutes to next pause and so on...
I have the problem with a Cardo / Schuberth SRC System bluetooth handsfree.
I tried several Sense ROMs and I found always this problem, but with CM7 it works correctly.
I tried to compile the kernel by using CM7 bluetooth options, but no succeed.
I tried by compiling the kernel by overwritting all bluetooth source code related (using CM7 kernel code). I get an error, and once solved by merging code, the problem is still there.
I tried by overwritting all bluetooth related libraries, but the ROM is not starting.
If anyone has any idea on how follow...
THANKS!
Click to expand...
Click to collapse
I initially thought it was my bt headphones (nokia 905i) creating this skipping but today i exhumed my old htc hd and the music played skip free via bluetooth.
@craig0r, Ive had this skipping on Froyo as well so Im not sure, maybe I have a dud Desire HD. Mind you Im still on stock gingerbread rom. downgrading and rooting seems just too complicated, not too mention which rom to choose!

[Q] Bluetooth on el29 vs fc07 question

When I connect my phone on el29 via Bluetooth with my car stereo I have no issues swapping back and forth from music to phone calls. An issue that I have encountered with fc07 is that I can only choose one or the other and there is a lag between connecting to radio and phone calls. For example on fc07 I am listening to Pandora and my phone rings and I answer no problem with Bluetooth. Once I hang up the call Pandora begins to play through my phone before it reconnects back to the car stereo. On el29 I don’t have this issue so when the call ends Pandora will start back up on Bluetooth right away. I am not sure if this is a bug or if ICS just separates the Bluetooth connections unlike GB which seems to migrate the two functions. I know in pervious build of ICS Bluetooth has some issues but I have not been able to pinpoint this as an issue. I am running Phantom Hacker 4.0 el29 and ran Calkulin’s 1.1 ICS. Any ideas on this?

BT echo with ICS ROMs

Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
chadillac3 said:
Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
Click to expand...
Click to collapse
My girlfriend complained about the same issue with my phone, and my "fix" was to lower the BT volume on the device, and max out the volume in the car, and she said the echo was gone.
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Ok, going to ask what's most likely a stupid conceptual question:
For both my Calk's ICS 1.4 and the AOKP Milestone 5 installs I followed qbking's video's to the letter.
Now, to the best of my understanding, this ROMs come packed with a kernel such as FD26. However, you can load different kernel's such as the new FE07 which could very well affect my BT and potentially fix it (or not...)
So, to flash a new kernel, I'd have to use ODIN to install the EL26+CWM to get back to a GB recovery. From there I flash the new kernel, then reflash the ICS ROM.
Here's what I don't get...if the ROM comes packed with say the FD26 kernel, won't that overwrite the FE07 (or whatever) kernel I just flashed? What am I missing here?
Thanks!!! Really trying to see if my BT issue is something I can fix. Want AOKP back again, bad!!
chadillac3 said:
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Click to expand...
Click to collapse
Lol...it won't be so loud, at least, not for me it isn't.
I'm an over the road truck driver and the only time I experience this is if I, or the person I'm talking to is in a really poor service area, i.e. South Carolina anywhere on I-95. Other than that I never have echo, & I'm on the phone for hours & hundreds of miles at a time spanning multiple states.
So it's not a ROM problem, kernel or modem related maybe, but I'm usually running the latest modem & kernel & have been on Team Nocturnal's ICS Blend "The Goodness" since about version 1.5, we're on version 8.0 right now. That would lead me to believe it's also not kernel or modem related
Fwiw, I use a Blue Parrot BT250-XT+, or Planatronics BB903, or a Blue Parrot VXi2 Expressway.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
I have not noticed this with any ics leak and my car built in bluetooth. My only complaint about bluetooth is that the volume is too low when streaming audio.
I know of three people from my searching who did...one person said they went to the latest version of CM9 and that fixed it...going to try this weekend.
chadillac3 said:
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
Click to expand...
Click to collapse
I was using a vehicle one, that I installed myself.
http://www.crutchfield.com/p_113BT300/Kenwood-KCA-BT300.html paired with http://www.crutchfield.com/p_113DDX512/Kenwood-DDX512.html?search=ddx512&tp=20217
I reduced the echo by lowering the BT volume during the call on the handset, and raising the volume on the car receiver.
I know, I know the thread title is BT echo with ICS ROMs...I am not running ICS, but for what it's worth, same issue here often, though NOT every call... I am running completely stock (still GB 2.3.6). Phone BT is paired with Motorola T215 that's clipped to the visor in my truck. ...and for me also, turning down the volume down a notch or two helps...In my case, I was actually thinking it is a feedback issue, where the other person hears their voice picked back up through the mic...that's why turning down the mic helps (or why they don't hear it when the mic is on mute)...
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
Really? That's weird. In my car, adjusting the handset volume affects the system volume coming out of the speakers.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
When I press the volume on the BT module, the phone will display "Bluetooth In-Call Volume" and adjust accordingly. Conversely, the phone will display the same when pressing the volume on the phone during a call. It could be relative to your BT module - if I understand correctly the BT module needs the Audio/Video Remote Control Profile (AVRCP) - as what allows for volume control via BT (as well as the play,pause,etc. on music over BT). Does your device support it?
I also found that if I slightly lower the visor, the sound doesn't "bounce" off the roof of the truck and helps not create echo as often, so I can turn the BT module volume up higher, if need be.
Just an FYI - when I used to plug a line from the headphone out from my HTC Hero to the truck stereo aux in , I would use the truck's speakers and the phone's mic...but there would definitely be echo issues if I cranked up the volume on the stereo...which of course let me to believe the similar issue occurs with my BT device and the phone itself because the mic is close to the speakers on the BT device.
Yep, module is AVRCP 1.3 compatible...which is part of the reason I like AOKP. Bitpool on the BT is set much higher than stock, and the metadata is transferred correctly. Everything is wonderful except for the damn echo.
What's weird is stock works totally fine; AOKP M5 had the echo, and Calk's 1.4 had an echo and static per my parents on their ground line and their ET4Gs. Wife's iPhone didn't seem to have the issue, so I wonder if it had processing built in to cut out the echo.
Going to try the latest versions of the ROMs to see if it magically fixes it.

Categories

Resources