• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Calls muted when not using headset or speaker

cerp

Lurker
Hello there.

For a while now I haven't been able to make or answer a phone call without using speakerphone or a bluetooth headset. When I try to call or answer the phone without these peripherals I can hear nothing: no dial tone, no voice, etc.

The problems started when I flashed AOKP. I accidentally restored the system backups from Titanium backup which it explicitly says not to do in the installation directions for AOKP. I assume this is what caused the problem. For some reason I cannot play sound through play music or the web on the onboard speakers either. It appears that my phone "thinks" that the headphones are always plugged in. The ringer and notification sounds work.

I have tried to flash multiple different ROMs, wiped all the caches multiple times, but no luck. Any ideas?
 
All I can think of is go completely back to stock...unroot and relock. If there is still a problem... exchange for a new one.
 
Hello there.

For a while now I haven't been able to make or answer a phone call without using speakerphone or a bluetooth headset. When I try to call or answer the phone without these peripherals I can hear nothing: no dial tone, no voice, etc.

The problems started when I flashed AOKP. I accidentally restored the system backups from Titanium backup which it explicitly says not to do in the installation directions for AOKP. I assume this is what caused the problem. For some reason I cannot play sound through play music or the web on the onboard speakers either. It appears that my phone "thinks" that the headphones are always plugged in. The ringer and notification sounds work.

I have tried to flash multiple different ROMs, wiped all the caches multiple times, but no luck. Any ideas?

You could try this free app:

https://play.google.com/store/apps/...W5kcm9pZC53aXJlZGhlYWRwaG9uZXJvdXRpbmdmaXgiXQ..
 
Yes! This worked, although of course it's not ideal to have to flip the switch always. Thank you.

According to the page this is a common problem with the GNex although I didn't find any threads anywhere pertaining to it.

Thanks again.

Cool, glad it worked! This will at least get you by until you can do a clean flash of your next ROM :) :thumbup:
 
Cool, glad it worked! This will at least get you by until you can do a clean flash of your next ROM :) :thumbup:

It's actually stayed with me through several ROMs and cache wipes, but all the same, thanks. :driver: this was a cool smiley and I want you to have it.
 
It's actually stayed with me through several ROMs and cache wipes, but all the same, thanks. :driver: this was a cool smiley and I want you to have it.

Were those dirty flashes or did you factor reset/wipe data between ROM flashes? If you weren't wiping data/factory resetting, then that would explain the issue persisting across ROMs (or if you restored system data in TiBu).
 
Were those dirty flashes or did you factor reset/wipe data between ROM flashes? If you weren't wiping data/factory resetting, then that would explain the issue persisting across ROMs (or if you restored system data in TiBu).



I always wiped before flashing but as I said in op I did restore system in titanium
 
I always wiped before flashing but as I said in op I did restore system in titanium

Yeah, so what I mean is, the next time you flash a ROM do a clean flash and don't do a system restore data. ;) Just take a few mins to re-do the system/AOKP/ROM settings, trust me it'll save you time on issues like this one and FC's etc. :)
 
Yeah, so what I mean is, the next time you flash a ROM do a clean flash and don't do a system restore data. ;) Just take a few mins to re-do the system/AOKP/ROM settings, trust me it'll save you time on issues like this one and FC's etc. :)

Yeah, I did the system restore once a while back. Haven't done it since.
 
Back
Top Bottom