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!
Hi, I have been searching and can't seem to find anything on this. My wife's and my epics pair, and work, great with with our car stereos (clarion). but, when we get out of the car, and the phone unpairs, we have no more system sounds. we miss calls and texts because we never hear them. the sounds now only come out the ear piece. Only a reset corrects it and then we hear sounds from specker again. Of coarse until we get in the car, and it all starts over again.
any ideas? I'm stumped.
thanks!
have you tried turning bluetooth off entirely when u leave the car?
also are you using any applications to send media with bluetooth such as BTmono?
I have the same problem -- as does my wife. I'm using a Motorola BT in the car, but it seems to be a problem with any BT connection as she primarily connects to our BT phone connection in the house. I saw this problem mentioned in a couple other threads, but no real solutions other than things like turning off BT on the phone before disconnecting, etc. Frankly, that's a hassle and I never remember to do it. I was hoping the latest version of Syndicate ROM might fix it, but just had it happen again this morning. So, I can confirm it's a problem on both Froyo stock and Syndicate ROMS. At least it seems like rebooting is a bit faster on Syndicate, so that's my solution for now as soon as I realize sounds aren't coming through. Just gotta remember to check before I miss a call!
Sent using Tapatalk.
thanks for the replies. I am not using anything that starts to stream to the car stereo. Music player use to, but I removed it. I did notice today that the specker sound loss only happens if i make/receive a call. Today I drove to store and while in store away from car sound was fine. got back to car, called wife, and then when I was at home sound was gone. I will try to toggle off BT before phone is unpaired. what a pain.
Wouldn't ya know I found a thread about this after I post this.
http://forum.xda-developers.com/showthread.php?t=1029198
This post has worked for me: thanks mattallica76. I had to be in car paired to do this.
http://forum.xda-developers.com/showpost.php?p=13102385&postcount=31
This problem is a bug that exists while using Bluetooth on a device for both ad2p and phone calls. The only workaround (until Sammy or one of our great devs comes up with a fix) is to use the BT device for one or the other. This will prevent the audio from being routed to the phones earpiece after BT disconnects. To do this, go into the phones BT settings. Then long press the device that you are having trouble with. Next uncheck "Media Audio" or "Phone Audio", depending on which purpose you want for the device.
Been having some problems with making and receiving calls which appeared yesterday, all this without dropping my phone or anything, it was just in my pocket.
Whenever I try to make or receive calls the phone thinks there is a headset attached so I can't hear anything that the other person says, I've never actually connected a headset to my phone either and there is no icon in the status bar for it.
I was using MIUI when the problem occurred so I tried doing a full wipe (data/cache/dalvik) and installing Cyanogen, same problem. So I tried installing a market app called 'headset blocker' still to no avail. Finally I tried going back to MIUI with a full wipe and using 'headset blocker' and it still doesn't work!
I can call fine if I put the phone on loudspeaker and the music plays through the speaker fine as well so I'm just not sure what else to try.
I read somewhere that a switch in the headphone port controlling whether a headset is connected or not could be the problem but didn't really want to have to take it apart unless I had to, anyone got any ideas?
Thanks for any help.
EDIT: Just tried putting my headphones in and wiggling it around and at one position (about half in) the phone thought there was a headset attached (an icon appeared in the status bar, before no icon was there) and wiggling it some more made the phone start a song briefly. So it's looking like it's a hardware fault..
Just in case anyone comes here with a similar problem, I took it to a local repair shop to be fixed and in the end it had nothing to do with the headphone port or the actual ear speaker. It turned out to be the ribbon connecting the two halves of the phone, no idea how it happened but it's fixed now!
So my problem starts with the motorola finiti headset. Pairs and connects fine. after being connected for a while and going about my day the phone rings but not through my headset. The bt symbol up in the notification bar shows its connected but when I go into bt setting it just says paired. Sprint replaced my phone, motorola replaced my headset still same problem. I call samsung they tell me to try a samsung headset I do same damn thing happens. I send my phone in to samsung (thinking they have headsets to try) they send my phone back saying it passed all functional testing. I get it back it still does the same damn thing. I call them back they say this time send your phone in with the headsets. we dont have any to test with??? So y the hell didnt u tell me to send the headsets the first time? So 1 week without phone got it back for 2 days now Im without again. Phone was stock no root when started. Rooted it still same thing.
TLTR: anyone else have prob with bluetooth saying connected in notification bar but in settings it just says paired? I have a screen shot I will show when I get home.
I just got my S3 last night. I am running Stock 4.1.1 UVDLJC (it updated after I turned it on). Today I was talking on a call via Bluetooth through my car and the voice starting fading out, like an old AM radio. I thought maybe I was in a bad spot, but it happened again later on when I had full bars. It sounds like the person on the other end is talking though a tin can. I'm not sure if they can hear me. Anyone else have this? I've used 4 different phones in my car and this is the only one that did it. Thanks.