Related
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.
I have a Canadian Rogers Galaxy Note 3 (SM-N900W8) running the latest software update (as of last night).
Any time I dial someone's number, there is a full 10 to 15 seconds delay/lag before the phone 'reacts' and starts to actually make the call. This lag/delay happens regardless if I am:
using speed dial (though it is especially obvious then)
manually dialling a number
sliding to the right on a person's contact (quick dial)
pressing and holding on a contact's number to dial
I've tried adjusting the Google Sync settings, turning on/off the "Sync People details" as well as my Samsung account's "Sync contacts". I've disabled Facebook/Linked In "Sync Contacts", based on my theory that there was some sort of hiccup being caused by these apps' attempts to pull data on the contact immediately upon me placing the call.
The other issue is that Contact photos/names are also severely delayed when receiving an incoming call, for example when my phone starts ringing, all that I can see is their phone number at the top of the screen (almost as if it's the 'raw' cellular data), and not their name or picture (as normally would immediately appear on say my Galaxy S 3).
I've searched all over but have yet to see this issue pop up. This seems really strange. Any ideas or solutions?? Thanks!
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
If it's any consolation, it's not just your Rogers Note 3. I'm having the same issue with the Note 3 made for T-Mobile USA. I'm going to try the battery pull like you suggested and see if that resolves the issue, as well as some alternate dialers. I'll post my luck once I've tried this.
kamandor said:
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
Click to expand...
Click to collapse
I have found this problem (delay dialing) for 2 weeks.
When I connect to internet, by wifi or mobile data, it is corrected. But whenever the internet connection is disconnected , it apears.
I'm disappointed from Note 3 because of lots of bugs that has got especially after update to kitkat
-delay dialing
-not working any auto call recording app.
-not working properly it's sensors.
And etc
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Shaunuss said:
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Click to expand...
Click to collapse
At least 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone is running smooth..
StaticBlaze said:
Atleast 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone.is running smooth.
Click to expand...
Click to collapse
Thanks for your reply! I have 1.1gb RAM free pretty much all the time, 1.18GB ROM free, and 20.99GB internal SD free.
Not sure this is the problem.
I got the same problem and i realized after i read this post that it doesnt happen if im connected with wifi. There should be a way to fix this, its a 500euro phone there shouldnt be such problems...
Had the same problem with a Samsung Relay, after a few updates. Had a chat with Samsung, after a hard cache clearing left me with the option to factory reset. Which I'm not very interested in. Uninstalled a lot of applications, then by chance connected to the wifi and sent an email. After that, it seems to be working now.
Didn't fix the problem for more than a few hours. Actually I believe hooking on wi-fi did it, because I connecting again this morning solved the problem again.
I installed a firewall and denied permission for all apps, let's see if this works...
No, the firewall doesn't work.
After connecting on wireless it works for about 3-4 hours. Then again bull**** happens. Don't know why, but this relation is interesting. There is no actual traffic sent form the device, since the firewall blocks a lot of the system bull**** apps from communicating, but after enabling it it works.
I see that enabling wireless even for a short while (3sec) is enough to get it back on track. Why might this be so?...
Prey
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Cross-referencing this thread on Prey:
https :// help.preyproject.com/topics/ android-call-delay-caused-by-prey
(sorry, as a new user I can't post outside links, so you must correct the URL above)
Seems I'm having the same issue on two of my Prey-enabled devices (HTC One X+ and HTC One X) after upgrading to latest version. Happens with Data-off.
norenendur said:
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Click to expand...
Click to collapse
Is there a fix for this mess?
I've disabled Google+ and still have this problem.
Please help........
I got that message after debranding my n910f. I simply went into the bootloader, cleared the cache and I've not seen it since.
Unrooted 4.4.4 btu n910f
My phone is just a stock Verizon Note 4 and I get this message several times a day. :crying:
I get it too, clearing data did nothing. Seems like a bug lots of people are reporting. Just a minor annoyance if you ask me.
Sent from my Note 4
I n calendar, activate the phone calendar.... That will solve the contact problem
I've been having this same issue since I updated to the ota lollipop from Sprint. I tried the fixes in this thread but nothing helped, mine does when I use the dialer.
I'm still sucking butts with this problem. Is there any clear cut fix for this?
My phone unlocked still get the problem
Dear LG G6 users,
For the last 4 weeks I have a problem with my Phone.
Whatsapp keeps crashing immediately after I try to open it, but if someone send me a message then I can open the notifaction and answer. Via the contacts I can also open Whatsapp en send someone a message.
See the video: I cant copy the link.
Type on YouTube: LG G6 Whatsapp problem from the Channel Petysqua!
I hope someone has a solution.
Everything is up to date!
Mathuse
Same here. I actually can't send anything more than text through this app. Sometimes I can share photos from the phone's own gallery but it crashes a little bit after that. I tried opting out of the beta and factory resetting the phone for no avail. I think it's the app's fault for not having a proper compatibility with Android N because it happened sometimes with my last phone, a Nexus 5X
It is so strange. I have no issues with every social app, just a heavy battery drain not fixed, for me, also with the last v10t update.
I have no issues with any apps. Try resetting your device.
No issues here with Whatsapp
I have issues with whatsapp under wifi, it doesn't seem to be able to connect properly, it takes a lot to send and receive.. If I switch to 4G, it sends and receives messages normally.
iam betatester and i have no problem with whatsapp, so i hope it helps
I use whatsapp to send and receive text along with with voice calls, haven't video call yet. everything works, I get some "reconnecting" with voice calls other than that works great. factory reset your phone and go from there..
Hi there,
since the beginning of December I am unable to playback the WhatsApp voice messages I send, not only I cannot play them but the receivers cannot play my messages either.
It was working perfectly before, but suddenly it stopped. I could not find a reason, so I factory reset my phone, reinstalled WhatsApp from scratch, but no go.
When I hit the Play button, it just stays there, the cursor does no move anywhere. I am pretty sure the phone records the messages, but nobody is able to listen to them. The audio settings are correct as well as permissions.
Am I the only one experiencing this issue?
I can only think this is due to an update from WhatsApp that has generated a software conflict with this phone, which is why I would like to know if anybody else is experiencing this problem.
Thank you!
Alex
Anybody?
kwajongen said:
Hi there,
since the beginning of December I am unable to playback the WhatsApp voice messages I send, not only I cannot play them but the receivers cannot play my messages either.
It was working perfectly before, but suddenly it stopped. I could not find a reason, so I factory reset my phone, reinstalled WhatsApp from scratch, but no go.
When I hit the Play button, it just stays there, the cursor does no move anywhere. I am pretty sure the phone records the messages, but nobody is able to listen to them. The audio settings are correct as well as permissions.
Am I the only one experiencing this issue?
I can only think this is due to an update from WhatsApp that has generated a software conflict with this phone, which is why I would like to know if anybody else is experiencing this problem.
Thank you!
Alex
Click to expand...
Click to collapse
My uncle is facing the same issue you mentioned. Tried resetting the phone but no solution so far. Looking for solution.
I spoke to the 'so called' WhatsApp customer support, they are aware of the issue and they said it will be fixed in the future. Mind, this was 6 weeks ago.
I asked for an ETA, they said they have none.
Obviously they do not care about the few Nokia phones around, therefore they will never fix this.
Very disappointing, but there is nothing we can do if their app sucks.
I am facing the same issue. tried clearing the cache, resetting the app, changing to a new phone number, and at the end resetting the whole phone. It just refused. I think it might have something to do with the version of Android. it has Android 9 so I might try to see if there is a good rom with android 11 or 12 and see if that helps.
Any solution? I have this problem fow months. Is possible change the android to another version to fix?