I've been using my Nexus 4 as a phone by using Groove IP until I got my Straight Talk SIM. Now that I have the SIM, the native phone app won't work right. The first call will allow me to hear the other person, but they can't hear me. Every call after that, I can't hear them, and they still can't hear me, and unless I reboot, every other call is like that. Here is a logcat of the first call, and the second call. Groove IP still works. Any ideas on how I could fix this? Running bootloader locked stock rom.
I had a problem where I couldn't hear other people, and they couldn't hear me, and I could not for the life of me find out how to fix it. I was running rooted stock, it had been working fine, and then just one day this problem popped up. I assumed it was a problem with the phone thinking a headset was still plugged in, but all those fixes didn't work. Then I just reflashed the stock ROM on the phone (no wipes), and it worked again and the problem hasn't come back. Not sure if that will help you, but it might be worth a shot.
OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.
Ok so as of today I have noticed a issue with calls.
The issue I am having is that when I make or get a call, neither of us can hear the other.
Texts/Data both work fine, I don't get a dial tone when calling people either yet it does ring through.
This happened once before but I thought it was a one off and I have no idea what actually happened between when calls worked, and when they didn't.
Stock ROM, Matr1x 5.5
Error that shows in logcat http://pastebin.com/ruSXwD3R
I have not tried a factory reset or reflashing my ROM, I consider those last resorts.
Bump, I can't be the only one who has experienced this
Anyone?
Sent from my Jelly Nexus 4
Hi everyone, i am having a couple issues with my phone. Im no pro, but after rooting my old s3 i got thr s4 and rooted it before even making a call. i installed the pac-rom ROM and its been working great except for the following...
about 3 of 10 calls when answered is dead air, the person on the other end says it rings then stops to dead air..
also about 3 of 10 calls placed are dead air also, the person on the other end gets a ring and answers to dead air.. my call timer starts counting as a normal call would, not as if the phone is unable to gain a network connection to make the call, where the phone just wouldnt connect. i dont hear ringing.
its very annoying. not so much when making the call, but when trying to answer a work call then having to call them right back as they are trying to call you back and leaving a VM or something.. i talked with Telus, and of course they see nothing wrong. but they will only do so much as my phone has a custom rom and they just blame the problem on that regardless of whats actually causing it.
donation coming to whoever can get this fixed for me!
also, when i have google chrome open, or by using the google search bar, i cant google anything or go to my bank website from my phone. it seems that all secure webpages cant be viewed.. im also having a problem where some pages just wont load. wireless or not.. gives me a server error connection refused message.
im more worried about the connection problem than the surfing problem, any help is appreciated though! thanks!
anyone?
What device, what rom, what version of baseband, come on, more info will yield more answers...
If it's a 4.2 AOSP ROM, it's possible that the audio fix from cm hasn't been merged, and even if it has, there are still issues. There is a modified phone.apk you can try as well, just search the forums for it. This issue shouldn't be an issue much longer since it doesn't exist on 4.3
Sent from my SGH-I337 using Tapatalk 2
I have an s4 from rogers (Canadian model) and initially had cyanogen mod as my rom but I realized that I was missing nearly 5 GB of storage on my phone. I read that to fix this I had to go back to stock using Odin. I went back to stock 4.2.2 using Odin, but then my WiFi stopped working. I couldn't turn WiFi on or search for networks. I then rooted my phone and installed a rom and my WiFi problem was fixed, but now I cant make calls. Every time I try to call someone my screen goes black and the recipient cannot hear me and I cannot hear them. Also, the sound on my phone does not work. I have flashed multiple roms and still get the same problem. Does anyone know any possible solution. I have looked around and many people have had the same problem, but no solution. Any help would be appreciated.