I apologize if this issue has already been addressed, but I could not find anything on this issue.
A few days ago I decided to finally switch from Froyo to the CM7 stable release from CyanogenMod and absolutely loved it. While listening to music on my bluetooth headphones at work, I ended up stepping away from my desk, leaving my headphones, and losing connection between the headphones and the phone.
When I got back, I noticed the headset icon was still in the status bar, and when I reconnected my headphones, I could not hear through them. I disconnected my bluetooth, and the icon was still on. I then tried connecting wired headphones, and then disconnecting to see if the icon would go away, and it would not. I tried resetting with them plugged in, then tried disconnecting, and it would still not go away.
During this time, I could make calls, however, I could not hear the person through the phone's speaker. After this, I rebooted straight into recovery, did the three wipes, rebooted, and STILL the icon would not ago away, and I could not hear anything. I then tried hiding the icon through ADW settings, but that only hid it and didn't deactivate it.
After this, I finally gave up and decided to re-partition, and odin back to the EB01 froyo package. While in Froyo, everything worked fine like it did before, I could make calls and hear perfectly. I then decided to switch back to CM7, because I thought, since it worked in Froyo again, it would work for CM7. Well, I was wrong.
The headset icon is still showing up, after a brand new flash of CM7 (nightly build 104, followed JT's directions on the OP).
I am not sure what to do at this point. I don't think it is hardware related, because it still worked with Froyo. Any help would be greatly appreciated.
My wifes phone did this, but she might have gotten it wet (in her pocket while doing dishes, so it wasn't submerged or anything). After letting it sit without the battery in a sealed bag with some silicate gel the problem went away.
dpercoco said:
I apologize if this issue has already been addressed, but I could not find anything on this issue.
A few days ago I decided to finally switch from Froyo to the CM7 stable release from CyanogenMod and absolutely loved it. While listening to music on my bluetooth headphones at work, I ended up stepping away from my desk, leaving my headphones, and losing connection between the headphones and the phone.
When I got back, I noticed the headset icon was still in the status bar, and when I reconnected my headphones, I could not hear through them. I disconnected my bluetooth, and the icon was still on. I then tried connecting wired headphones, and then disconnecting to see if the icon would go away, and it would not. I tried resetting with them plugged in, then tried disconnecting, and it would still not go away.
During this time, I could make calls, however, I could not hear the person through the phone's speaker. After this, I rebooted straight into recovery, did the three wipes, rebooted, and STILL the icon would not ago away, and I could not hear anything. I then tried hiding the icon through ADW settings, but that only hid it and didn't deactivate it.
After this, I finally gave up and decided to re-partition, and odin back to the EB01 froyo package. While in Froyo, everything worked fine like it did before, I could make calls and hear perfectly. I then decided to switch back to CM7, because I thought, since it worked in Froyo again, it would work for CM7. Well, I was wrong.
The headset icon is still showing up, after a brand new flash of CM7 (nightly build 104, followed JT's directions on the OP).
I am not sure what to do at this point. I don't think it is hardware related, because it still worked with Froyo. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Thanks for the suggestion. I didn't spill any liquid on it. It also seems to work fine when I'm on Froyo. It's just weird because I re-partitioned back to stock, followed the exact instructions in the OP to get back on CM7, and it automatically recognized it has having a headset plugged in when I booted into it for the first time.
Same thing here
Used the stable build and got the same results. Just tried nightly 112 and same thing. Headphones in the top bar (yet I've never connected any) - no sound when dialing unless I turn on speakerphone. I was trying to bring my wife over to the dark side by letting me get rid of her stock OS, but it looks like I'll have to go back :/.
I had this same exact problem with my droid x after I accidentally dropped it in water. I tried everything (Reflashing ROMS, going back to stock, etc). The I found an app called Headset Blocker. All I had to do was enable and disable the app and my problem went away.
See if it does the same magic for you! Hope this helps!
Related
Hello XDA!
First, some background: A few weeks ago, my phone went for a swim. I let it dry for a few days and turned it back on, but the phone wasn't very reliable (time would run slow, half the time I couldn't make calls, and the 3G wouldn't work at all). The touchscreen however was perfectly fine. So I found an eBay auction where it seemed like everything worked except the touchscreen. I bought it, and transplanted my touchscreen onto it.
Unfortunately, while most things work, I don't have any audio coming out of the front speaker, meaning I can't hear people when I call them or they call me, and if I call them, I can't hear the ringing that goes on before the person picks up. I read on some forums this was potentially a software issue, so I reflashed the latest RUU, and got nothing. I flashed KaosFroyo v24 and still have nothing.
My current work around is to wear my headphones all the time with it (which isn't TOO inconvenient, since I listen to Pandora a lot). The microphone works. The speakerphone works (since it goes through the speaker in the back).
Does anyone know if it's possible to transplant that speaker as well? It seems unlikely since I'm pretty sure it is attached to the motherboard...
Thanks!
Okay... so I have to vent a little bit. I am on my 5th Vibrant replacement from T-Mobile. Every one has had the same problem. I am on the phone with Bluetooth for 20 - 30 minutes or more. Everything is great. Eventually turn off BT and the phone ceases to make any noise when an alert comes in. no MMS, email, phone ringing, nothing. I have to restart the phone to get it to work again. I am on Stock KB5 right now but have tried Bionix and Trigger... both do the same thing... which makes me think it is much deeper in the kernel or the hand off between the BT and sound devices. I have an open case with Samsung but they want me to send the phone to them. I'm like... go get one... I've had 5 and statistically it can't be me! I am using a Rocketfish Stereo headset and a Motorola H117. Both do the same thing.
Am I alone? Am I the only one who uses Bluetooth and the Vibrant as a phone?
The rest of my config is...
Gmail (Obviously)
Rooted or un rooted... does not seem to matter.
Exchange Email
Straight MMS (Tried Handcent as well...)
Bionix V, Bionix 1.3.x, Trigger 3.0.1, Eugene's ROMS.... all the same thing. BT eventually goes to hell in a handbasket.
Any advice? Any help?
Hi all,
I am having the weirdest problem here and need some advice. Tried the search function but came up empty, although it seems by googling that other people have faced it. Problem is that none of the following helped.
Out of the blue my phone thinks that the handsfree jack is used at all times.
So, when i actually use the handsfree all is ok.
When i unplug it i still get the headphones icon on the notification bar and every sound except ringtones is routed to the headphones jack so i have no sound at all.
Tried:
Flashed stock rom, other developers roms, and every piece of kernel i could get my hands on. Of course in the process i did the proper wipes from the cwm menu.
Factory reset.
Sound test through the *#*#0673# menu.
Plugged - unplugged the headphones like 100 times.
Cleaned the headphones hole with cotton bud.
Applied force to the walls of the headphones hole with the jack plugged in.
Took it to a tech friend of mine who took the whole thing apart and tested almost every piece of hardware to his personal handset..everything works as it should.
For now the plan is to keep pluging unplugging the handsfree till it works. I will do that because one time it actually played music from the speaker for a couple of seconds... Unfortunately it then started using the headphones again.
I could really use some help here from the gurus PLEASE.
Thanks in advance
Alex
Nothing guys? Comon there must be something i forgot to try...
TAlx said:
Hi all,
I am having the weirdest problem here and need some advice. Tried the search function but came up empty, although it seems by googling that other people have faced it. Problem is that none of the following helped.
Out of the blue my phone thinks that the handsfree jack is used at all times.
So, when i actually use the handsfree all is ok.
When i unplug it i still get the headphones icon on the notification bar and every sound except ringtones is routed to the headphones jack so i have no sound at all.
Tried:
Flashed stock rom, other developers roms, and every piece of kernel i could get my hands on. Of course in the process i did the proper wipes from the cwm menu.
Factory reset.
Sound test through the *#*#0673# menu.
Plugged - unplugged the headphones like 100 times.
Cleaned the headphones hole with cotton bud.
Applied force to the walls of the headphones hole with the jack plugged in.
Took it to a tech friend of mine who took the whole thing apart and tested almost every piece of hardware to his personal handset..everything works as it should.
For now the plan is to keep pluging unplugging the handsfree till it works. I will do that because one time it actually played music from the speaker for a couple of seconds... Unfortunately it then started using the headphones again.
I could really use some help here from the gurus PLEASE.
Thanks in advance
Alex
Nothing guys? Comon there must be something i forgot to try...
Click to expand...
Click to collapse
I would have to guess it's a hardware problem... although you have tested everything, still, I'd have to vote for sending it in for service
cdzo72 said:
I would have to guess it's a hardware problem... although you have tested everything, still, I'd have to vote for sending it in for service
Click to expand...
Click to collapse
Well, thats my next conclution. It has to be the main board which is the only one we couldnt test...i just dont want to go there yet as it means that i have to sell it for spare parts.
As for sammys service i cant really go anywhere near them after what i have put my phone through
I have a 2 year old Motorola Atrix which I have had in an otterbox since day 1. The phone is in more or less mint condition. A couple days ago I noticed that I couldn't hear the phone ring when I called people. So figuring the phone wasn't dialing I would hang up and try again. Still no luck.
I called my phone via GoogleTalk and could not hear anything through the phone. I put it in speakphone mode and could hear no problem. The mic was picking up correctly in both speaker and normal mode. I can hear notification sounds and ringer sounds through the speaker.
If I plug in headphones I can hear sound through them on a call. However if I unplug them I once again hear nothing.
If power off and power back on (or reboot) it continues to behave the same (no sound through phone when calling). However 9/10 times if I do a full power-off and battery pull when I turn it back on it will work for a short period of time. This leads me to believe the speaker itself is still working.
I have tried downloading an app that disables headset pass through, I have tried rebooting, battery pulling, and full factory, cache, and dalvik wipes. I have tried cleaning the headphone jack, putting headphones in and out multiple times, as well as ensured the mic was clean.
I have been running epinters CM10 November 2012 release and have only just started having this issue, so I am confident it is not a ROM issue, as nothing has changed.
Anyone have any ideas outside of me contacting bell, on what might be going on?
I did a full wipe and flashed lastest CM10. It worked for the first couple of calls I made however it is back to not working. I have a feeling now it is not a ROM issue and that it must be hardware.
So I flashed to Carbon a while ago, everything was working perfectly, but I decided I wanted to flash back, so I used TWRP to restore my phone to its previous state. Now even with GPS on, and an application like Maps trying to use it to get a location, the GPS icon doesn't show up in the notification bar and nothing is able to get location. Furthermore, if I attempt to use headphones with my S3, I'll get a series of popping, glitchy noises, followed by audio only working out of one side. I thought this might be due to a bad solder connection in the jack itself, so I replaced the entire audio jack assembly, but the problem persists, telling me it isn't a hardware problem (with the audio jack, anyhow). Does anyone have an idea on how I could go about fixing this, or at least finding out what the issue is? I flashed back to a completely stock ROM (though I'm not sure I formatted everything entirely, I'm a little bit new to this) and I still have those two problems. Everything else works perfectly on it. I've taken good care of it, never really dropped it, nothing. Any help would be greatly appreciated. Thank you
I should also note that I'm not 100% sure it stopped working after I flashed for the first time. It might have been having this problem before I ever flashed it.
Follow the guide in sticky thread, general forum on how to return to factory state. If still the same then you've damaged the motherboard.