Related
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!
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.
Hi chaps,
Wierd issue. Headphones are not detected when plugged into my phone unless I do a reboot. Similarly, when I unplug the headphones they are not 'un-detected' until a reboot.
However, using an app called toggleheadset I can force audio through to my headphones. This is a bit of a pain because 1) I have to remember to do it and 2) I lose Beats functionality.
I have tried using different headphones but this has no effect.
Any ideas as to why the headphone state is only detected at boot?
I have tried different Kernel/ROM combinations but to no avail.
Any help would be greatly appreciated.
also, if anyone can provide me with some pictures of their headphone port so I can compare it to mine that would be great.
Hi,
I have the exact same issue with my HOX since yesterday.
At first I thought the ROM had something to do with the issue, but after flashing several other ROMs, it still wasn't solved. (I haven't flashed back to stock btw)
"toggleheadset" works ok, but I can't use the microphone that way; I can't use my headphones to make calls anymore.
Also when answering phonecalls, sometimes my headphones are still toggled on, so I can't hear the other end. And the worst thing is: when I try to toggle the headphones off during the call, my screen dimms and I struggle to activate the widget. THATS a pain in the ass.
Does anyone know if the issue is software/hardware related? And the best way to solve this?
I'm wondering if this issue affects bluetooth headsets. If it doesn't, I'll consider buying one.
Old thread, but me the same... But my HOX survived waterboarding... I felt into the wather while sailing. Changed battery and screen, but now I see i have one more problem to solve. If any one have solution - please write. But for now I'll try to fix by my own
Cleaning Hole
Try to clean the hole where the Headphones are put in...
If its clean, try to reinstall the rom.
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.
Hey there,
I'm currently running a OP3 with the OmniDragon 8.1 ROM and previously the ResurrectionRemix ROM. However, I do not believe this issue to be a ROM issue so that's why I'm posting here instead.
I've recently been having some issues with bluetooth and was hoping someone could help. I can connect my phone to my cars handsfree system perfectly fine and it works correctly. I can play music via Spotify and any other music player fine.
However, as soon as I make or receive a phone call I'm left where the person can't hear me, and I can't hear them. I can't even hear the ringing tone when phoning someone. However, as soon as I turn it from bluetooth back to the phone or just regular speaker, it works fine.
This previously was not the case when I was running Nougat.
But as soon as I upgraded to 8.1 this issue started happening.
I don't think it has anything to do with the ROM and is actually something to do with perhaps OP3 Firmware/Modem or something similar.
Car hands free works fine with other phones like an iPhone, so that's out of the question.
I've attached a catlog to this post from when this issue was happening in the car, so hopefully someone can narrow it down for me.
Any help is appreciated!
Actually many roms have been having issues with BT calls. It's due to some of the changes in the telephony package.
Hello, did you manage to find any Oreo rom that fixed this issue for you? Would appreciate any tips.
I too have had similar issues with Oreo and OnePlus 3. Using an handsfree Jabra Freeway and the microphone often does not work when I answer or phone someone during a drive. Which is extremely annoying and dangerous.
I had hopes that with the release of some alpha Android Pie roms, these BT issues would be fixed. But the issue seem to persist, at least for my device.
My only fix was to go back to nougat. The most stable rom i've found is the unofficial lineage 14.1 by sultan. This have been my daily driver for awhile now and seems to work fine.