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!
Title says it all folks lol. I almost fully submerged my poor Eris, and to my suprise, almost all was well. My only problem is that my Eris thinks that there are headphones plugged into it when there isn't thus rendering my phone silent in everything the speaker would play. Now fortunately for me, under the cyanogenmod settings there was an option in the sound section to always play certain things on the speaker, an override if you will. This fixes my problem for notifications, calls and alarms. Still, I was wondering if there was a way to permanently overide the fooled headphone jack completely so I didn't have to use speaker phone on calls to hear anything and so I can play music and videos again. Any help would be terrific. Thanks in advance!
Sent from my nonsensikal froyo using XDA App
Pull the battery and bury the phone in a bowl of rice (uncooked) for a couple of days. It should help remove any moisture left.
Sent from my CELB ERIS using XDA App
The rice probably won't do anything at this point. You're screwed. The one thing you don't do when you drop your phone in the water is turn it on. If you ever get your phone that wet you immediately pull the battery and let it dry.
Basically your warranty/ everything is voided so I suggest you try opening the phone out and using compressed air to blow out anything that may be trapped inside.
I didn't use rice although I know you can. I actually did what you said Hungry Man. Pulled the battery and let it sit out in the sun for a couple hours. When I first turned it on after that, I noticed the headphone symbol popping up and disappearing a few times, and then it just stuck. Do either of you know more about what cyanogenmod does to overide the headphones? My guess is that if It can be done with a few sounds, it can be done with all of them.
I do know my warranty is voided. That's fine tho. I have the monthly insurance that covers water damage, but the phone is fine, so I might as well open it up. Ill need to fond a tiny star key though lol.
Sent from my nonsensikal froyo using XDA App
Simular Issue
I can relate, I recently rooted my Eris and have been toying around with some roms. Somewhere along the way my phone started to think that headphones are constantly plugged in. Extremly frustrating! Have tried new roms, re-flashing, etc. but nothing helps. May need to try that rom you've been using to compensate. Any suggestions would be great!
JayWalley said:
I can relate, I recently rooted my Eris and have been toying around with some roms. Somewhere along the way my phone started to think that headphones are constantly plugged in. Extremly frustrating! Have tried new roms, re-flashing, etc. but nothing helps. May need to try that rom you've been using to compensate. Any suggestions would be great!
Click to expand...
Click to collapse
Did your phone get wet?
No it didn't get wet. Doesn't matter now anways. Just flashed the 2.1 stock rom and exchanged it for a new one.
I love the Vibrant. Most things work fabulously, however, I'm on my 3rd one (for completely different and unrelated reasons), and this issue just won't go away. It's ironic, all of the whiz-bang functions work flawlessly, but the issues with the basic functioning as a PHONE are getting old. When I'm on the road, more times than not I will be in the middle of a call, and it will plain drop. I NEVER had a call drop with the trusty dusty G1 for almost 2 years. I may have narrowed it down to one of 3 things, but they are not consistent: 1) If I have rebooted and forget to turn off the "auto update of time" function, and it does it's thing, it drops then. If I get another call while I'm on a call, it will do it then. If I'm using Google Voice, it seems to happen even more frequently. The other annoying thing is that every day, at least several times a day, I will try to make or answer a call and the Bluetooth will have plain disconnected randomly. I have Jabra JX10's for both home & the car. Is there anyone else who has had these issues, and have any insight as to what may be causing them? It did both when I had just gotten each, so I can't see that it's the ROM, kernel or lagfix. I've asked this before, and I hate to use the "F" (Froyo) word, but if it comes, will it include a new/stronger radio that maybe the issues will be solved? Oh yeah, one final thing, and this may be solely Google Voice related, but often when a call drops or fails to connect, if I try to make another, I hear an ear piercing ridiculous static sound until I reboot. Someone please tell me that I am not the only one who has ever had these issues and that my phone is possessed by aliens. TIA...
So, lovin' most everything about this phone, but, one annoying thing that keeps happening; I get random bt disconnects with my Jawbone era and my plantronics voyager pro plus.
It happens anywhere, in the car, in the house, outside, so Its not interference from another BT source...
Anyone else getting this or figured out how to stop it?
I've done all the OTA stuff, and I am not temp rooted, no ever tried to be..
thanks!
The only bluetooth device that I use is a bluetooth full face helmet on my bike. I will get random disconnects, but I had thought that this was due to the bluetooth radio in my helmet being of only so so quality.
well, this never happened with my evo4g, so I am suspicious that the BT radio isnt as good as the one in the e4g was
wase4711 said:
So, lovin' most everything about this phone, but, one annoying thing that keeps happening; I get random bt disconnects with my Jawbone era and my plantronics voyager pro plus.
It happens anywhere, in the car, in the house, outside, so Its not interference from another BT source...
Anyone else getting this or figured out how to stop it?
I've done all the OTA stuff, and I am not temp rooted, no ever tried to be..
thanks!
Click to expand...
Click to collapse
I paired it with my Camry's hands free system yesterday and haven't seen any BT disconnects so far. You may have a defective phone.
I have connected to my Handfree in my '09 Lancer and didn't experience any disconnects for 12 hours straight. I also have a Nokia BH-503 and it never disconnects either. Maybe get a replacement phone?
Others are having bluetooth issues as well, mine takes the form of music skipping.
http://forum.xda-developers.com/showthread.php?p=16008951
You are not alone.
For me it runs better than the EVO 4G. But it does occasionally disconnect. But never in the middle of a call. I'm using an old Sony HeadSet.
One trick I used to use on marginal connections over bluetooth was to try pairing it at the maximum distance you can. It *MAY* choose a better channel. Sometimes you have to clear out the history of the old channel or it may reuse that. Only way I know to clear it is factory reset.
Has anyone tried the phone with one of those high priced Bose Bluetooth headsets?
The random disconnects with the Jawbone Era are really annoying to me, but, if its the phone, and not the headset, thats a different issue.
I've already replaced one evo3d due to random rebooting, so I don't want to have to try to replace it again..
thanks
I have a blu ant. And music and call quality are great. No disconnects at all. Have you tried Bluetooth with a different model??? Might just be the unit itself.
Locked & Loaded
Just bought a Q2 Blueant, so here's hoping I can get it to work right!
You should have no probs at all. They make quality Bluetooths.
Locked & Loaded
I had this exact same problem on my EVO 4G. Still happens on the 3d. I have used many different Bluetooth handsets to no avail. Doesn't happen as often with the 3d but it is maddening, because it seems like once it starts it does it all day, and many times right when I am answering a call.
Sent from my PG86100 using XDA Premium App
so far, the Blueant q2 has been perfect; we'll see how it is today, after a full day of phone calls..
I am having the exact same problem. My bluetooth goes into headset mode when I answer the phone or make a phone call, which pisses off me and the person I'm calling because we can't hear each other and I have to hang up and call them back... Really frustrating
Sent from my PG86100 using XDA Premium App
wase4711 said:
so far, the Blueant q2 has been perfect; we'll see how it is today, after a full day of phone calls..
Click to expand...
Click to collapse
Yup. My wife and I own them. Imo you really can't get to much better.
Locked & Loaded
I didnt have hardly any bluetooth problems with mine, my girlfriends, or my best friends og evo's. I upgraded to the 3vo and was having the disconecting issues and my phone would randomly reboot and then freeze while bluetooth streaming (Thats really the only bluetooth I use) so I took it back and ended up buying a 3vo out right. Still have the same issues. Its probably a software bug and will hopefully be fixed in a later update or custom rom
ive been having problems with my lg headset and disconects.. re connects.. took it in to the sprint store, they ran tests on it and it failed both radio tests that they did.. getting a new one tomorrow.. for those that are getting random disconects.. and a lot of droped calls.. have your radios checked out at the sprint service centers... it could be a bad phone.. (sadly.. im getting a refer 3vo back.. **sighs**)
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!