Can't Answer Phone Since Nougat!!

[rafeevans]

After a smooth OTA upgrade, the phone now presents no incoming call screen. When I get a call the phone rings and vibrates but the screen stays dark. Sometimes I can unlock it with a fingerprint, then go to the home screen, then go to the phone icon, then open the on screen keyboard, which shows "Return To Call In Progress" among other options. Tapping that brings up the familiar screen that lets me answer the phone - if I am fast enough. A Google tech told me this is the new protocol but obviously that's bs. What to do?

 

[B. Diddy]

Welcome to Android Central! No, that's clearly not how it's supposed to work. Any system apps disabled? Have you already tried a cache partition wipe?

 

[rafeevans]

Thanks for the reply. Moments ago a system upgrade came in promising to fix bugs etc. Alas, it didn't fix this disaster. I did clear the cache btw. I guess now I will go thru the brain damage of a full wipe but somehow I doubt something this serious will be fixed by it. I mean seriously, no incoming call screen!?

 

[bjrosen]

Do a factory reset

 

[B. Diddy]

Before the factory reset, see if this happens in Safe Mode as well: https://support.google.com/nexus/answer/2852139?hl=en

 

[rafeevans]

Just tried Safe Mode boot - the Google tech suggested it before the latest update. It didn't solve it then and it didn't just now. Any other ideas? This is a very major bug.

 

[B. Diddy]

Ok, then the next step would be a factory reset. If that still doesn't work, then the firmware may have become corrupted, in which case you would have to reinstall the firmware: How to manually update your Nexus | Android Central

 

[rafeevans]

I appreciate your suggestions Diddy. Sadly, I am getting a warranty replacement and will spend a couple of hours reconstructing my set up. I am just grateful it's a Nexus so there was nothing like Samsung blaming Google and visa versa.

 

[GSDer]

Well, since you're going to have to setup a new device from scratch anyway you might as well try a Factory Reset.

And reloading the firmware would be good practice even if it doesn't solve your problem.

 

[rafeevans]

Yes, I did the factory reset and it did not help. Oh well.

 

[renegad3]

do you have a screen protector on the phone?

 

[GSDer]

Yes, I did the factory reset and it did not help.

I'd suggest reloading the firmware if that didn't help.

 

[jhasty]

I am having the same problem. Started after Nougat upgrade. Rebooting the phone makes it go away for a while.

I'm using Fi. I suspect it is related.

 

[Trigati]

I am having the same problem. Started after Nougat upgrade. Rebooting the phone makes it go away for a while.

I'm using Fi. I suspect it is related.

If you're on Fi, do you have Signal Spy or a similar app installed? If not, install something like it so you can keep track of which network your phone is connected to. You can see if it's trouble with a particular network (TMo, Sprint, or US Cellular), or a different issue. It may be (although I have no clue why) that the phone is unanswerable on certain networks. At least it would help troubleshoot if nothing else.

 

[rafeevans]

Reboots didn't help so they sent me a new phone yesterday. Annoyingly, it hadn't been upgraded from 6.0 so it took about 5 install cycles to get it up to Nougat No problems now.

 

[jhasty]

The phone app is not coming up on the screen during the call. That makes me think it is a software problem.

 

[elcustardo]

have you checked the dialer app is allowed notifications?
I had the same issue and it was blocked.

 

[stan23]

The problem is hardware related. It's the proximity sensor. Glad a replacement phone is working for you.

 

[GSDer]

The problem is hardware related. It's the proximity sensor.

Do you have some evidence to support that? If it was hardware, why did the problem suddenly start when the OP updated to 7.0?

 

[Golfdriver97]

It might be the screen protector blocking the proximity sensor, however, I don't think this would have suddenly surfaced.

I had the same issue with my 5X. An updated version of the screen protector fixed it.