I'm having this issue where the phone doesn't react properly to an incoming call (stock ROM, unrooted).
The phone rings, but the dialer screen with the controls to answer the call does not come up. It doesn't help if the screen is already on, I'm just staring at my home screen while it rings. There's also no call icon in the notification bar. When the caller hangs up, I immediately get a missed call notification.
Rebooting the phone solves the problem for a while, but then it comes back. I tried reverting to the stock dialer with no luck. I'm thinking of reverting to the stock launcher as well, but I'm not sure it has anything to do with it. Other than that I'm running out of ideas.
I've searched the web and it looks like people are experiencing all sorts of variations on this problem, but not the exact same thing, and in any case I haven't seen anyone post a tested workaround.
Has anyone encountered something like this and maybe knows of a solution?
Did you try clearing the data of the phone app in settings > apps?
If not, try that
Sent from my Nexus 5 using Tapatalk
Related
About half the time, when I try to answer an incoming call, my Verizon TP2 will only mute the ring without answering the call. It responds the same whether I use the touch screen to answer or press the send key, and whether or not the phone is locked or unlocked when the call arrives. Has anyone had a similar problem or know of a fix? Thanks.
I got this behavior the first time I finished getting the phone set up how I wanted. I eventually had to hard reset to fix it.
I think it was probably s2u2 interfering with the nonstandard dialer / answer bits on the phone. Even uninstalling it didn't help though. I have not bothered to try reinstalling s2u2 after the reset though to see if it causes the problem again.
i have this same problem. as i recall there was some registry tweak you could do to fix it, but i cant remember it to save my life. I have the worst problem with being on the internet and trying to answer a call. anyone know of a fix? whenever i am on opera and try to answer an incoming call it just freezes and i have to exit opera and call the person back. anyone with a fix for this other than a hard reset?
i had the same problem before i flashed to 6.5 on my vzw tp2. I also suspected that it was because of s2u2: I followed to uninstalling and i kept on getting a message about s2u2.exe not being a valid app or something. I also thought it could have been because of the dialer i had. The dusk dialer...for sense2.1 while i had manilla. after the flash i reinstalled s2u2, and will see if this persists to happen again.
It happened to me for the first tiem twice yesterday, my phone awoke and I could see my taskbar icon switch to 1x but I didn't see a call then I got a voicemail, when I called the person back they said it rang 6 times and went to voicemail, and it happened again later where i saw the call box and slide to answer come up but the screen was stuck and I couldn't answer it, not even with the hardware key.
Same thing is happening to me. The first time someone calls it won't answer whether I use the soft key or the hard key and the screen just freezes. However when the person calls back, it answers immediately when I click the answer button. I don't have S2U2 or any other phone/lock apps which interfere with answering a call.
Same here guys, I have been having the same issue, but as I can see for weeks now I haven't been able to nail down a solution either...
I too have had the same issue for several weeks. More prevalent when the screen is locked. Rings once and goes to voicemail.
stupid double post.
I've only run across this issue when I am using too much RAM. Try using cleanram and closing out tasks that you are not using.
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
reddington said:
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
Click to expand...
Click to collapse
have you tried s2u2 and their call answering interface?
When i press the home button, the screen stays black for like 10 sec, and then shows me the lockscreen. Also when i make a call, the screen turns black and i only see my signal strenght, battery and wifi indicators. So i cant hang up after i'm done with the conversation, when people call me, i can answer, but i also cant disconnect. Sometimes the force close popup of the process com.android.phone comes up. This is very annoying, does anyone recognize this problem and know's what i can do?
I reinstalled DarKy's rom, I don't think it's a software problem.
something you might want to try to solve the phone problem is downloading a different phone app from the market and setting it as your default phone app. for example "dialer2" fpund in the market might work just fine for you
So I had a Note previously, WhatsApp worked perfectly fine.
I notice now that there are a lot of weird notification issues now. I ran some tests and this is what I've found.
Screen On - Clear all apps with Task Manager. Exit to home screen. Meaning, WhatsApp is not running in the background, not running at all. I use my girlfriends phone to send me 10 + messages. I get NO pushed messages, no notifications. Nothing happens. I then launch the app and see that I have 10+ unread messages under her name. I click to read the messages, and exit back to the home screen (either back arrow or home button). I send another message from her phone, and NOW I see the notifications.
Screen Off - (sleeping but app is still in the background) - I send a message from her phone, get NO push notification. But... as soon as I hit the power button to light up the screen (wake from sleep), I get the notification in the bar. I read the message, clear the notification bar.. then put the phone back to sleep. Same thing happens. While the screen is off, I get no push notifications until I turn on the screen.
Anyone having weird issues with WhatsApp? It can't be the app because it works perfectly normal on my Samsung Note. I'm thinking ICS broke it some how.
The notifications works fine for me with whatsapp. The only thing is that when I hit clear in the notification bar and haven't read the actual message, the notification will reappear again.
Sent from my HTC One X using Tapatalk 2
Same thing here just happened with me on my HTC ONE S , if screen if off and whatsapp is running i get no notification, however as soon as i press the power button immediately i get notified and the weird thing is the notification sound is the default ringtone while in whatsapp settings i have another tone set. Whatsapp was working fine. I tried reinstalling, force stopping, rebooting.
My phone is stock rom no root any help would be appreciated
EDIT (SOLVED): Disable Fast Boot under power options in settings, disabling it fixed my problem (Read it somewhere online)
I have problems with notifications when wifi is on. No problems w/out wifi
I have exact same issue on my Xperia Arc...with or without Wifi...I have ICS 4.0.3
I think it is phone independent issue...
i think you all should stop closing all apps from the task manager and everything would be fine.
you cant shut down all apps and then expect from them to work.
(at004 solution could help too)
Sorry to revive this thread, but I have a solution to the problem (I think) and I thought I might share it.
Some routers flag push messages as "Anonymous Internet Requests" which the NAT dismisses. This will effectively kill push and you'll only get your messages on the next sync.
To counter this problem you can forward the google push port to your phone.
You'll need a static IP for the phone. The port Google uses for push messages is 5228 on TCP.
Good luck with your problems!
ahh.. i got the notification problem.. there is no sound or vibrate for incoming whatsapp messages..
this happen affter i update the apps.. damn!
Yze said:
So I had a Note previously, WhatsApp worked perfectly fine.
I notice now that there are a lot of weird notification issues now. I ran some tests and this is what I've found.
Screen On - Clear all apps with Task Manager. Exit to home screen. Meaning, WhatsApp is not running in the background, not running at all. I use my girlfriends phone to send me 10 + messages. I get NO pushed messages, no notifications. Nothing happens. I then launch the app and see that I have 10+ unread messages under her name. I click to read the messages, and exit back to the home screen (either back arrow or home button). I send another message from her phone, and NOW I see the notifications.
Screen Off - (sleeping but app is still in the background) - I send a message from her phone, get NO push notification. But... as soon as I hit the power button to light up the screen (wake from sleep), I get the notification in the bar. I read the message, clear the notification bar.. then put the phone back to sleep. Same thing happens. While the screen is off, I get no push notifications until I turn on the screen.
Anyone having weird issues with WhatsApp? It can't be the app because it works perfectly normal on my Samsung Note. I'm thinking ICS broke it some how.
Click to expand...
Click to collapse
This happens on my brand new nexus 4
This used to happen way back when I first got my One X, but it is solved now. I thought it was because I had rooted and gone with a newer build, but I got a replacement One X stock with 2.20 and notifications work fine when screen is off.
Same issue in my nexus 4
I'm facing the same issue in my nexus 4.But this is applicable to the application which having the same properties of WhatsApp.For eg Viber.
When we are in the screen of Whats App and Viber i'm getting the notification otherwise not..
I also noticed one more thing unless we open the application the data notification in the signal bar is idle. I don't why its like that.Usually it should be always active.
dreamweaver9962 said:
I'm facing the same issue in my nexus 4.But this is applicable to the application which having the same properties of WhatsApp.For eg Viber.
When we are in the screen of Whats App and Viber i'm getting the notification otherwise not..
I also noticed one more thing unless we open the application the data notification in the signal bar is idle. I don't why its like that.Usually it should be always active.
Click to expand...
Click to collapse
Facing the same issue with my HTC Desire Z running ICS custom ROM.... Not always.. but 90% of the time. This has made whatsapp a less reliable mode of messaging.. I cant keep on checking my mobile for new messages..
manujosephv said:
Facing the same issue with my HTC Desire Z running ICS custom ROM.... Not always.. but 90% of the time. This has made whatsapp a less reliable mode of messaging.. I cant keep on checking my mobile for new messages..
Click to expand...
Click to collapse
Same here, with the same phone and running CyanogenMod 7.2.0.
Also seeking help on the same issue.
Seems there's no point to use this "instant" messager with this defect.
Go and complain with the makers of it as you have paid for it and using a custom ROM is 100% supported...
This is a users forum guys. If you install custom ROM some things may not work as on stock ROM.
We share experience and knowledge but not complaining about the product or demanding for a solution.
Go to WhatsApp website and tell them about the issue. I doubt they read this post.
Sent from my XPeria Z
So, my mom got the Nexus 5 from T-Mobile, and she's had this issue occur twice...
Basically it's when she tries to make a call, the dialer doesn't come up. If she uses the contacts or recents, it'll pull the call up, but doesn't show the phone screen, like the time, hangup, or anything. Basically she had to rely on other people o hang up to end calls, or turn off the phone.
Rebooting the phone fixes the problem, but it's slightly frustrating...
Has anyone had the same issue and know how to fix it?
I heard some solutions involving removing "YouMail", but she doesn't have it on her phone...
I constantly have my ear pull down the notifications and launch whatever app had a notification while I'm on a call, thus making the phone disappear, but hitting the back key to get out of the new app brings the phone back.
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.