I'm having a problem with my phone thinking and acting like a corded headset is plugged in. I started having the problem using ZenEXP-0.9.6OC and thought maybe it was a ROM problem then flashed over to fresh 2.1 to no avail. A reboot doesn't fix the problem and neither do the two other fixes on here. It does go away briefly when I plug in my USB cord but comes back shortly afterwards. Has anyone else had this problem? It's become annoying having to run out to my car to talk through the stereo.
Sounds like it is indeed a hardware issue. Sounds like perhaps some sort of short in the headphone circuit. I would suggest reflashing the 1.5 recovery image and bringing it to a store or trying to fix it yourself. I would try using a bright light to see if you can see whats causing it.
So I RUU'ed back to 1.5 and took it into Best Buy (Where I bought the phone.) The lady told me to jam a 3.5mm headphone plug into it and pull it out repeatedly. She said that that was all anyone could do. I attempted that and it fixed for about 45 seconds (Long enough to make a phone call) and then it cut back out again. I tried taking my phone apart to see if I could see anything and there were no obstructions. What I'm wondering now is if I could customize a ROM to allow me to disable the headphone port all together. I never use headphones with the phone anyways and it would allow me to keep this phone without running the risk of having to switch to 2.1 RUU.
i've got the same problem for long ,i solve it temply with toggleheadset.apk ,,but it doesn't work in android 2.2..
Related
So, the microphone on my headset stopped working. I can't really tell if it's going in all the way, it seems like it's almost making it in all the way but that could just be me. I tested another headset on my N1 and it didn't work, and I tested my headset on another phone and it did work, so that tells me something is wrong with either my headphone jack or my phone. I am running CM 6.1 RC1, so that may be the problem, too. It stopped all of the sudden and hasn't worked after several reboots. So I guess my pre-emptive question is: Does anyone else with the same ROM as me have this bug (I've checked the CM experimental forums)?
First question: is the 3rd ring on the headset the one responsible for audio in? If that's the case, I think there might be some gunk stuck in the hole.
If it's the 3rd ring that isn't making contact, how am I supposed to clean it out?!? I've tried air-duster, but I'm afraid whatever is in there is compacted from the first few times I've tried to get it to work. Should I get super super thin tweezers or something like that and try and break up whatever's in there?
Or, I could try and take it apart, which I've done with other phones, but just wondering if anyone has had this problem or tried taking it apart to clean it. Wondering how far in the disassembly process will I have access to this area.
Or, I could get a new phone. Not quite worth the $130 deductible to replace this small problem, but it is super annoying as I use the headset most of the time.
Ideas?
I'm really hoping someone can help with this, because it is driving me insane! I will try to keep this as brief as possible, but feel free to hit me with questions.
So 2nd hand Samsung Galaxy S I9000. I have had issues. At first the home button didn't work so I had to get the screen replaced. After this I installed DarkyRom v10.2.2 Extreme Edition TouchWiz4.
After I installed the Rom the sound went (can't remember if it was instantly after the install, it may have been, but I suspect not. It may have been after a day or 2. No longer). The sound worked through the headphone socket, but would not come out of the speakers. I figured that it thought that the headset was plugged in. I installed Cyanogen Mod (as it has the headphone indicator) and lo, there it was. Headset indicator was on, despite not being plugged in. Tried some fixes (compressed air into the headset socket, plugging in and removing headphones). No dice.
Took it to a repair centre, and they fixed it. BUT, when it came back, the LEDs lit up whenever the screenlock was engaged. They looked at it again and said that it was a problem with the mainboard and wasn't fixable. Got into quite an argument with them as the LED problem did not exist prior to taking the phone in, so they agreed the headset repair for free. I am not convinced of their honesty nor that they actually replaced anything.
Obviously quite annoyed at this point, as I basically now have a battery drain. Anyhow, decide to reflash it again, see if it fixes it, so I flash DarkRom 10.2 Resurrection Edition. OMG The LED problem is fixed. Sound still works at this stage.
I then flash DarkyRom v10.2.2 Extreme Edition TouchWiz4 again. Boots up. THE DAMN SOUND HAS STOPPED WORKING AGAIN! I have not plugged headphones into it, so it cannot be the jack socket. I have only just brought the phone home again.
I have reflashed back to DarkRom 10.2 Resurrection Edition and I still have no sound. I am now thinking this may be a problem with the TouchWiz4 Rom, as I am at a complete loss why the sound would have gone between the Resurrection to the Extreme edition. I haven't put Cyanogen back on, but I am pretty certain that it will tell me that the headset is plugged in.
Does anyone have any idea what I can do to get sound back on my phone, because I am basically back to having a useless brick? I have tried searching but cannot find anyone asking a similar question.
Many thanks, and apologies in advance if I have broken any n00b rules! If any further information is required, fire away.
Cheers
torz77
Ok. I have done nothing since posting this message and now the sound just works again. I'm not going to risk reflashing again, but if anyone has any ideas why I am having this issue then I would like to hear it, because I am not convinced that the problem is going to go away for good!
Hello again!
As I suspected, this problem has not gone away.
I still have not plugged anything into the headphone socket, so I think that can be ruled out as an issue.
The sound has gone on it twice now, since my post. The first time I took it out of vibrate mode and enabled sound. I noticed that the keypad wasn't clicking. Tested it, yep. Stuck in headset mode again.
I went to power down the phone, and noticed that when I hit reboot the keyboard click had returned. When it rebooted sound was back on.
The second time, I was playing the ultra-lame App ARShooter. Sound went off midway through playing it. Again, I heard the keyboard click comeback when I hit the reboot option when powering down.
Sound came back again.
There is clearly something wrong with this phone, and I would love to know how to fix it, or if it's even possible, or where I should even start looking. If anyone has any ideas of what is causing this problem, then please let me know.
Thanks again!
Flashing back to stock?
Hi there.After one and a half month i noticed that the one speaker of the headphone provided inside the i9000 package was not working.Also the i could barely hear what was the other person was saying.I tried a normal headphone with the simple 3.5 audio jack(no mic) and it worked fine.Also i used it in the car and stereo works fine,but if i put a 3way 3.5jack then it doesnt really worked.I flashed a 2.3.4 simple honey rom but it didnt work .I tried to go to the secret codes menu using *#*#197328640#*#* but the AUDIO directory is not opening!I tried pressing on it and typing {5} (it the number of the directory) but it doesnt open whatever i do.I tried voodoo and although it works wonderfull at playing music i still cant use the mic+headphones that came with samsung or another one i bought to check if the first is faulty.Now i want to revert back to stock so i can take it to the samsung shop for repair;What drivers do i need and what do i do to take it bac kto stock? stock rom that came with my phone was xwjvi 2.3.3
Thank you!
I have a new Razri and I notice that seemingly randomly the sound will just stop working.
To fix, I either have to reboot or plug something into the headphone jack and then pull it out, it then starts playing sounds normally again
Anyone else had this issue? My last phone (Defy+ running GB never had this issue)
It's running ICS, I'm unsure if I should send it back or wait for the imminent JB update, anyone have any ideas?
techguyone said:
I have a new Razri and I notice that seemingly randomly the sound will just stop working.
To fix, I either have to reboot or plug something into the headphone jack and then pull it out, it then starts playing sounds normally again
Anyone else had this issue? My last phone (Defy+ running GB never had this issue)
It's running ICS, I'm unsure if I should send it back or wait for the imminent JB update, anyone have any ideas?
Click to expand...
Click to collapse
Sounds like a hardware problem. Could something get into your 3,5 mm port like pocket lint? Use a toothpick and try to gently explore the port.
I flashed a cyan build delta using the app cyandelta the other day and after that, the phone refused to charge unless it was turned off. I figured the build had broken something but discovered that the phone would hang when trying to boot into twrp. So i did a full reset using the 1.29 ruu to see if that would help and it did not except now i get a warning on screen saying the usb host is unplugged and unable to change in the notification area.
the stock build also suffers from other random quirks like during phone call it repeatedly turns on and off the speaker phone and the gyro sensor will randomly turn my screen sideways.
took it into the sprint store and said there was corrosion on the charging port but i know it has not gotten wet at all the past few days and that the problem occurred right after the flash.. They refuse to touch the phone and say i have to pay 150 to replace it. I have tried cleaning the port with a dry toothbrush to no avail
Is there anything else i can try and re flash that might fix some messed up software or was flashing the ruu the best bet.
Thanks for your time and help
-shadow
Had the EXACT same issue on mine, never unlocked or rooted. Sometimes the volume would just disappear as well (even when using headphones) but the Beats icon would still show. Everything would go into permanent landscape mode at times. Calls answered in speaker automatically. If I plugged it in while it was on I got the usb host notification. The car mode app thingamajig launched for no flippin' reason, had to turn it off to charge it, all that jazz.
Definitely a hardware issue with the usb port. I took mine to Sprint hoping for a replacement but it has a barely visible crack horizontally across the screen so that was denied unless I agreed to pay the $150 deductible. It flew out of a car with me about a month prior so that did some damage to the phone. Then I dropped it the day these issues started happening. The port felt loose, I figured all of the wear and tear messed it up.
I didn't actually fix the phone though. It just randomly started working smoothly again and I haven't had a problem with it since - it has been a couple of months now. From all of the research I did, I saw that most people had the problem just fix itself for no reason and never come back. I tried cleaning the port and poking and prodding but nothing fixed it. Just one day, BOOM, all better.
Hope it decides to behave soon
Sent from my HTCONE using Tapatalk 2
If you dont want to read my boring story of breaking my phone, skip to the two dotted lines your expertise is appreciated
-
Ok, so i have a problem. Today i was screwing around with a project of mine (a portable boombox thing) for this project i needed a subwoofer. I hit up the local thrift store and BAM. New subwoofer. I plugged my phone into it just to see if the speaker driver worked. Plug into headphone jack=immediate reboot. Once it booted back up, i tried again to get it to play, but to no avail. It seemed to not recognise that the speaker (or headphones) were plugged in at all and proceded to play through the phone speaker. I unplug and plug the 3.5mm jack back in. And thats where the s**t hit the fan. The display flashed a pure blue screen (no words, just a pure blue screen) for around a second, and then my beloved G2 met its shocking end from an electrified audio jack. So sad,so sad.
-----------------------------------------------------------
-----------------------------------------------------------
Long story short, i killed my phone with a short in the audio jack (i guess), and im sending it in to verizon for warranty replacement. Normally this wouldnt be a problem and everything would be fixed by big red and everyone lives happily ever after but its never that simple for us tweakers..
/\The device will NOT power on whatsoever
/\Cant access download mode
/\Cant get into recovery
/\Cant get it to do a dang thing, not even vibrate
Tried vol- and power for up to a minute
Tried the three finger salute vol-,vol+,power
Even tried vol+,power but i dont think thats supposed to do anything anyways..
Tried vol+ while plugging in the usb (original cable)
---
---
So is there anything that i am missing?
Obviously i was not able to flash back to stock before returning it, and i want to make sure im not slapped in the face with that $299 (software tampering) charge from the ever wonderful big red -_-
It seems to be a complete brick but i wanted to consult people of greater knowlege than myself.
If there is no power coming from the device, I think you should be ok. I think you might of fried the motherboard. If so there should be no problem with them replacing it since they themselves cannot power up the phone and see that it's rooted.
Sent from my VS980 4G using XDA Premium 4 mobile app