I'm not a noob by any means. I've done all the normal troubleshooting. I've looked for other similar topics and none exist for this phone. I've tried everything that I can think. Having said that, please excuse me if i missed anything.
Basically, my issue is that I can't accept 95% of my incoming calls. I try to.... And the call hangs up when I press answer. I have the regular stock google dialer. I'm stock but rooted and unencrypted. I realize this may have to do with LTE still being on and not H+ but it's really annoying. It does switch to H+ but still hangs up.
I tried a few custom ROMs and the issue still exists. I've ensured that notifications are checked in the dialer app.
Someone please help me. Maybe I'm missing something simple. It's really annoying not being able to accept a call and having to call people back for every call received.
Please and thanks
And now I've officially tried EVERY ROM for this phone and still.... Can't answer incoming calls. Ugh. Someone please help
Have you tried updating your radio? Have you tried setting your phone in non-LTE so at most it only utilizes H+/H/3G?
Have you cleared cache and tried it in safe mode?
@zephiK thank you for the ideas. Flashed the new radio from your thread... Issue still persists. I haven't gone to just 3g yet because I use my phone a lot for work (law enforcement) and need the LTE speed when identifying people
Edit: tried using 3g and 2g anyways.... Still hangs up whenever I answer incoming calls. Ugh
PDP///M said:
Have you cleared cache and tried it in safe mode?
Click to expand...
Click to collapse
I have cleared both cache and dalvik cache. I can't get safe mode to work..... I'm using liquid smooth at the moment and when holding power off it doesn't show the option for safe mode
Well I figured out holding reboot gives the safe boot option. My phone bootlooped. I'm going to have to totally undo everything on my phone. Lock and unroot my phone. Then I'll start over using only stock without unlocking or rooting first then continue this trouble shoot.
If anyone can think of anything else please let me know thank you and merry Christmas
I had the same issue with mine. I thought I was going crazy. Hope you get it worked out. I sent mine back to Motorola yesterday for a refund.
Sent from my iPhone 6 Plus using Tapatalk
Update : Solved....
I wiped everything and started over. I flashed stock and went into safe mode. Calls worked. So it was easy to figure out... It was a downloaded app. A call blocker that was blocking everything instead of just the calls it was supposed to.
Thank you to those who offered opinions, suggestions, and comments
I had the same issue with the N5 on att. Was rooted and used a tool that opened a Sprint "only" service menu. Played with a setting and boom, i had voice. Data worked no problem throughout this ordeal.
Have the same problem with a Nexus 6, suddenly the phone did not show up any incoming call screen/window or way to slide out to answer an incoming call. It rings but there is not way to answer the call, even trying to go to the task bar and see if there is a window up there to answer it, no notification or window to press and answer.
This phone is not rooted nor have an application to block calls. it is with lollipop 5.01.
Any ways to solve this horrible bug? This bug is driving me nuts.
Related
I'm not sure what the problem could be.
When I first wipe the phone everything is fine but as soon as I put a ROM on there I lose the ability to receive phone calls. Every call goes straight to voicemail. At first I thought it was an app causing the problem (YouMail, Timeriffic...). I uninstalled those but still no calls. I did a wipe, phone rings. Put a ROM (no apps yet), straight to voicemail. Right now I'm using Damage 1.5 but that doesn't make a difference because it happens with Fresh & Darch too.
Is there a common setting somewhere that changes and could be interrupting my ability to get calls?
edit.....
Now that I think about it, this all started yesterday when I changed that CDMA auto thing. But that setting doesn't keep after restarts right? And wiping the phone should have cleared that anyway right?
trindy said:
I'm not sure what the problem could be.
When I first wipe the phone everything is fine but as soon as I put a ROM on there I lose the ability to receive phone calls. Every call goes straight to voicemail. At first I thought it was an app causing the problem (YouMail, Timeriffic...). I uninstalled those but still no calls. I did a wipe, phone rings. Put a ROM (no apps yet), straight to voicemail. Right now I'm using Damage 1.5 but that doesn't make a difference because it happens with Fresh & Darch too.
Is there a common setting somewhere that changes and could be interrupting my ability to get calls?
edit.....
Now that I think about it, this all started yesterday when I changed that CDMA auto thing. But that setting doesn't keep after restarts right? And wiping the phone should have cleared that anyway right?
Click to expand...
Click to collapse
One word:
nandroid
That was the first thing I did
I've nandroided (is that a word?) all the way back to January. That's all I've done since this started yesterday. Wipe... New image. Wipe... old backup. Wipe, older backup.
I'm about to smash this thing lol
go back into the test menu and make sure your phone isn't set to evdo only tht will keep calls from, coming in
You only get to ask one question per thread, so I'll answer the one in your title.
Yes.
bcnice20 said:
go back into the test menu and make sure your phone isn't set to evdo only tht will keep calls from, coming in
Click to expand...
Click to collapse
It says I'm on GSM auto (PRL). I'm afraid to change it again. I think thats how I got into this mess in the first place
gthing said:
You only get to ask one question per thread, so I'll answer the one in your title.
Yes.
Click to expand...
Click to collapse
Gee thanks! lol
After living like this for 2 days I'm thinking it's not so bad. I changed my voicemail message to say I'm having a problem, send me a text and I'll call them back. I dont have angry ex's calling, no kids needing money, no mother complaining. They text me! And if I want to listen to it I'll call them back. It's kinda quiet. I think I like it
I'll put it back to stock and take it to Sprint tomorrow. Let them deal with it.
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840
I am not sure how this happened but,I am unable to answer incoming phone calls. No matter what button I press, and I have answering mode enabled, also having answering key enabled or not I still can't answer. I don't know if this other glitch will help as a clue to figure this out or not but, the ringertone is stuck on default and rings as one long continuous ring with no break. If I go to settings and try to change the ringtones or notification tones, I'm unable to do that either. When I am selecting from the incoming calls section of sound in settings, in either phone or notification ringtones, when I choose between android or zedge the phone just freezes or sends me back to main settings screen. When it freezes, it really freezes. I have to pull the battery because the power button does nothing.
I'm about to flash a new ROM (not sure which yet), and was wondering if this problem will go away, or will it be persistent and plague me in the new ROM? Thanks in advance to anyone who wants to help me with this one. I'm trying to do things without having to ask for help, but sometimes being a noob has its limitations.
Anytime any of you need answers about your electrical in your house or business, I'll be glad to answer your questions. 17 years as a union journeyman electrician has taught me a few things. LOL
Full Wipe Rom should do away with the problem. Just watch as u restore apps and see if u got a bad app causing the prob.
Sent from my SAMSUNG-SGH-I897 using xda premium
The mic on my son's D4 was cutting out during calls, he could press any button to get it to stop for a second but it would keep doing it. He could hear the caller but they could not hear him. He did numerous factory resets (always being sure not to have stuff backed up to Google) and got a new SIM, tried safe mode. No change, still had trouble. For what it's worth, calls on Skype worked with no trouble so it's not the phone.
I got a new phone so sent him my old D4, it had never done this to me so again, nothing wrong with the phone. He fired it up and it started muting right away. It's not the phone, it's not the SIM...it has to be Google somehow. He's done more numerous factory resets and safe modes and making sure it's not backing up to Google but the new-to-him phone is still muting calls. He says that stuff IS being backed up because it pulls his wallpaper over every time he resets.
Any ideas on what he can try or why it may be happening?
Clementine_3 said:
The mic on my son's D4 was cutting out during calls, he could press any button to get it to stop for a second but it would keep doing it. He could hear the caller but they could not hear him. He did numerous factory resets (always being sure not to have stuff backed up to Google) and got a new SIM, tried safe mode. No change, still had trouble. For what it's worth, calls on Skype worked with no trouble so it's not the phone.
I got a new phone so sent him my old D4, it had never done this to me so again, nothing wrong with the phone. He fired it up and it started muting right away. It's not the phone, it's not the SIM...it has to be Google somehow. He's done more numerous factory resets and safe modes and making sure it's not backing up to Google but the new-to-him phone is still muting calls. He says that stuff IS being backed up because it pulls his wallpaper over every time he resets.
Any ideas on what he can try or why it may be happening?
Click to expand...
Click to collapse
Root safestrap and install cm10.2 on stock romslot? Or fastboot stock image. If neither works its gonna be a h/w issue
Sent from my XT894 using xda app-developers app
It's not rooted and he won't root. It's not a hardware issue, the phone he's using now was mine and never had any issues. It's the same problem on two different phones with different/new SIMs. As I said, Skype works without cutting out.
Something very strange is going on.
Clementine_3 said:
It's not rooted and he won't root. It's not a hardware issue, the phone he's using now was mine and never had any issues. It's the same problem on two different phones with different/new SIMs. As I said, Skype works without cutting out.
Something very strange is going on.
Click to expand...
Click to collapse
I'd say to fastboot or rsd to latest image and try then. Could also be a signal problem also
Sent from my XT894 using xda app-developers app
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Added info
Blown240sx said:
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Click to expand...
Click to collapse
I forgot to add
The phone dialing abilities worked perfectly fine before even with the new google apps installed and on 4.4 KitKat. This problem only came after my friend soft bricked the phone by erasing the old roms.
try disabling "non-intrusive call" in Phone settings
Sent from my One using Tapatalk
Same problem GS4 Sprint
Blown240sx said:
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Click to expand...
Click to collapse
I have the same problem, but I'm not able to finish the call even enabling the "end call with power button". I have to activate airplane mode.
I'm on a Galaxy S4 Sprint. If you found a solution I'll appreciate if you share it.
I still havnt found a solution. Im currently downloading a stock rom hoping that it might have some system file I may be missing.
The Intrusive calling feature isn't on the HTC One
Anyone with programming or some knowledge on whats going on can you please help. Im stumped
Blown240sx said:
Anyone with programming or some knowledge on whats going on can you please help. Im stumped
Click to expand...
Click to collapse
So this is a really old thread, but I'm betting the IMEI got wiped. Phone can't call without an identity.