I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Had a similar experience
Headset being detected even when not connected seems to be a common bug on Gnex, have seen several posts and I myself had to go through this. It usually gets fixed by itself in a day or two.. but till then use the "toggleheadset2" from the play store, which would allow you to manually say when the headphone is connected or not.
--Vj
PhreeqQitsikk said:
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Click to expand...
Click to collapse
---------- Post added at 10:27 AM ---------- Previous post was at 10:17 AM ----------
Only permanent solution is to change the socket. Its the switch inside which usually gets jammed.
Same exact problem
I am having this same exact problem. Its fine on stock, once I flash CM10 calls say connected and the time starts ticking but I can't hear a thing and no one on the other end can hear me.
Sometimes when I do connect, the person will hear me for a couple seconds and then it'll drop then connect again then drop...over and over again.
Google now doesn't pick up any voice searches either.
HELP, this is a relatively new issue. (2-3 months old) I've had the nexus since January and had it rooted and rom'd shortly after. Only recently has this issue cropped up.
toggleheadset2 seems to work but it sucks that I even have to use it. Any devs out there have suggestions/input? I've looked all over for a resolution.
Please don't make me go back to stock....Please!
Related
OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
Just bought a nexus from Verizon, on my second device now. First device was exchanged after 1 day, battery ran out in 6 hours, never held signal for more than 2 min. Second device is a refurb, phone worked great and had ZERO issues until updating to 4.0.4. Came with 4.0.2 on it, put off the update for several days to see if it worked ok. Everything ran smooth and fast, great battery life and signal. Immediately after the update, phone now hangs and freeze when unlocking, switching home screens, open app menu etc. Phone also seems to randomly think a headset is plugged in and will not make any sounds except ring, and in a call, neither ear speaker or mic work. Speakerphone works, and if a headset is plugged in, sounds works normally through headset. Found this app:Wired Headset Routing Fix which sometimes fixes mic issue. Sounds and mic work normally after a reboot, but will then randomly stop. Found several pages of threads all over about the mic issue, but with no fixes.
Tried flashing Bugless Beast rom to adress some of these issues, all problems remain. Mic/sound issue seems tom be related to something with the software that controls the headphone jack. Should I continue trying different roms? Try a different kernel? Possible to complete reset phone back to stock 4.0.2? It worked FANTASTICALLY before the update, how could I get it back to the way it was when I unboxed it? My 14 day warranty runs out on the 22nd, so I could exchange the phone again, but my Verizon store has been hounding me to switch to another device.
Any help would be greatly appreciated!
After your first device they gave you a refurb? Only After a day? That's strange.
Sent from my Galaxy Nexus using xda app-developers app
They initially gave me a brand new one, case was cracked completely through when they opened the box to activate it. The only other phone they had on hand was a refurb.
Here's the deal. I have an iBolt car dock (that specific really shouldn't matter) and Tasker profiles to turn on GPS, Bluetooth, etc while my phone is plugged in. Been like that for months. Up until about a week and half to two weeks ago, my phone app would crash when trying to receive a call while in said dock. The message I got was "unfortunately, the process com.android.phone has stopped". When I noticed, I was running Carbon. I clean flashed the nightly I was on and same result. I then tried Deviant, Slim, JellyBeer, PAC-man, etc. All of them gave the same result. Same wipe procedure for all of them. Same apps as I've always had. I then flashed AOKP M1 and everything worked. Then I tried Task's AOKP. Same thing. Everything worked. I don't get it. I posted the issue without a logcat (as pulling one of those while driving is a no no) in those respective dev's threads but it seems they don't know what's going on with everyone else. Hence, this thread. If you are running any of the ROMs I mention and experienced the same problem, post here. If you have logcats (ballsy), even better. I figure this would be the best way for all the devs of those ROMs to see what is happening and so the problem can be nailed down.
I'm also using an iBolt dock. Posted this in Xone Deviant thread: http://forum.xda-developers.com/showthread.php?t=2215840&page=55
itsmikeramsay said:
Not 100% sure bro, haven't been able to test it...
Click to expand...
Click to collapse
CrackerTeg said:
@ itsmikeramsay. Did you see this a few pages back? Thoughts?
Click to expand...
Click to collapse
Same here. Phone ui crashes when call is initiated but call goes through. Catlog attached.
Glad to see someone else feels my frustration with this. I battle this issue all the time. I have 2 iBolt docks(the regular one & the pro dock) & have had this issue with both. If not the not the incoming calls freezing the phone, its the phone rebooting when pluging it in, or the dev will update the rom and the usb audio doesn't work at all. I'll give task's AOKP a try to see how things with it. I was a huge fan his roms in the past up untill an update and the usb audio stopped working. In that situation, I usual just try a couple different roms untill one works. But then, the incoming issue happens or it reboots when docked and I feel like throwing my phone out the window
btw, i got an email today about the prodock cables being shipped. I've been using the one that came with the first iBolt
If my wallet would allow it, I would buy a headunit with bluetooth and use a NFC chip to put the phone in dock mode and not have this issue regardless of what rom i'm running. but my wallet stays empty
---------- Post added at 01:16 PM ---------- Previous post was at 12:41 PM ----------
I'm pretty sure the usb audio out working on some roms/updates vs. not working others is due to something in the kernel. Ex. I flashed the latest deviant xone update(2.0) and the didn't work. So I reflashed the previous version (1.0 stableish) and the audio works.
I hope this gets resolved 'cause I enjoy listening to podcasts & playing ingress during my commute only to have it ruined by a phone call that freezes my phone, rebooting booting and listening to my wife "quit ignoring my phone calls"
Sent from my SGH-I747 using xda premium
Interesting. My complaint has nothing to do with the audio out portion of it as I use my phone for browsing and as a phone. I have my tablet or iPod for the music in my car. So the complaint has nothing really to do with the iBolt but the phone being docked and not being able to use the actual phone function. If the usb audio gets fixed, bonus but I'm much more concerned with the primary function of this device.
After doing a bit of research, it seems that samsung didn't implement call audio through the dock connector. I know this is not your direct complaint BUT if you are using the ibolt cable that has the dock resistor( that tells the phone to go in dock mode) and the Rom/kernel is trying to route the audio via the usb than the phone may be getting confused. I think the solution to your issue, since your not concerned about audio out, is to replace the supplied cable with a standard data/charging cable. I haven't tested this theory, but i'm pretty sure taking the dock resistor out of the equation will fix the phone freezing when receiving a call.
I did have a rom installed at one point that had audio out working AND didn't freeze on incoming BUT had an unrelated bug that drove me nuts, so flashed another rom. It's too bad I can recall which rom and which release it was
Thing is, I have a Parrot bluetooth adapter that my calls go through. They don't go through the dock at all. I have a tasker profile that triggers the phone to go into car mode with Google's no longer supported Car dock app when the device is plugged in. It also turns on bluetooth, GPS, blah blah. Like I said in the OP, everything was just peachy up until two weeks ago where something in those ROMs got borked. Either way, I'm now running Carbon's latest and the issue is gone. Whatever got messed up is now fixed. I wish I knew what it was tbh but I can't read git.
I would like to add my two cents.
I too have an iBolt dock for SGS3, and an after-market radio with bluetooth.
I have tried several ROMs (CM stable, LiquidSmooth, ParanoidAndroid), and all of them exhibit the same behavior:
Going into the docked mode is flakey at best. 90% of the time the phone doesn't recognize it has been docked.
Now comes the "best" part: on disconnect from the dock the phone's bluetooth stack apparently crashes. The bluetooth connection gets immediately lost, and the phone's bluetooth status is stuck in 'ON' position. After that there is no way to turn the phone's bluetooth 'OFF' and back 'ON'. The only way to restore is to reboot the phone.
I haven't tried to pull the logs from the phone yet, but it may be possible if I take the dock home and try to repro the condition.
Not asking for answers, just voicing my frustration hoping to draw dev's attention to the problem.
This problem just started for me and I have experienced nothing like it. I'm running the LG p930 with CM10.1.3 RC2. Yesterday, the phone began restarting whenever it tries playing a sound. This happens in Netflix/ Youtube once a video starts, Pandora when it attempts to start playing a song, even the sound panel when I use the volume rocker to try changing my volume and it attempts to play the little beep. It also happens no matter what speaker it tries using - headphones, speakerphone or earpiece, meaning I can't actually use the telephone functionality of the device either..
As far as fixing- I've tried clearing the cache and dalvik, fixing permissions, and even flashed several other ROMs. Everything seemed to have the same problem. Does anyone know what could be going on?
This exact thing happened to me. I couldn't find any information on it.
I had to completely format and un-brick the phone. I'm not even sure that it worked the first time. But after completely wiping and un-bricking a couple of times, it was back to normal. I think this is the guide that I have always used for that.
http://forum.xda-developers.com/showthread.php?t=1597488
Hope this works for you. I know that problem can really suck.
Thank you so much! I'll try this. I can't believe someone else had this issue, it seems incredibly rare. Can you tell me more about it? What ROM were you running? could you play any sounds at all?
Thanks again
I know what you mean. I was surprised to stumble across this post about it. I feel like I have had a few issues that just seemed very strange with this phone.
Mine was just like you described. I couldn't even change the volume without it crashing. If my phone was on vibrate, I could see the call come through. When I answered the call, the phone crashed.
I was probably on a PAC-ROM or CM10 Nightly. But like you, I probably went through every available ROM, stables and nightlies at that time. I think I even tried to flash a stock ROM.
Thank you so much. Actually, you don't have to follow the whole guide. All you need to do is download the image files, and skip to step 4 in the section "Restoring the original Nitro HD images:" Then get cwm working, and move on from there with whatever ROM you want. I would never have thought to try this. Thanks again.
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk