Why do I have to unlock phone through my pattern to receive call on my Z2 - D6503 on android 5.0.2 ?

[AC Question]

In the past it was not like that, even on the android 5.0.2. My mobile is completely locked with my patter and the screen does not even light up,its still black during the notification of an upcoming call. I must unlock it to receive a call whether by pin lock, patter or whatever security methods.
Any suggestions please ?

 

[B. Diddy]

Welcome to Android Central! Are these regular mobile calls, are you using an app like Hangouts Dialer or Skype to receive calls?

 

[RohanD6503]

Thank you for your prompt reply, Yes they are regular phone calls. I am using the phone dialler to make calls !

 

[B. Diddy]

That's strange. Open the Phone app, tap Menu>Settings, then check all of the Call Settings to see if there are any related options.

 

[RohanD6503]

I did checked, There are no related options on the phone dialler or call settings. However I checked my display options, the phone is on sleep after 2 mins of inactivity ie it locks afer 2 mins of inactivity. Is this the reason why I have to unlocked it to receive calls ?

 

[Kelly Kearns]

I did checked, There are no related options on the phone dialler or call settings. However I checked my display options, the phone is on sleep after 2 mins of inactivity ie it locks afer 2 mins of inactivity. Is this the reason why I have to unlocked it to receive calls ?

It shouldn't cause this issue. I have mine set on secure lock after 10 minutes (I use fingerprint) and I never have to unlock it to answer a call..

Are you using a launcher?

 

[B. Diddy]

No, that shouldn't happen. Even if the phone has a screenlock, you should still be able to swipe to answer it. In order to get to the homescreen from within the call or after the call, that's when you should have to enter your screenlock.

 

[Kelly Kearns]

Just found something..

I just did a quick Google search for, android 5.0.2 have to unlock phone to answer call, and this seems to be a bug of 5.0.2. Now it isn't on every phone, but on various phones. Such as the Nexus 5 seems to do it and the Nexus 6 doesn't. There are several other phones that mention doing this.

It seems like all of them also have to do the same thing to dismiss and alarm. It is supposed to be corrected in 5.1.

 

[B. Diddy]

Good detective work! But it must not have been a bug that showed up universally on those devices, since I never encountered it on my Nexus 5. I wonder if other 3rd party apps might also be involved.

 

[Kelly Kearns]

Good detective work! But it must not have been a bug that showed up universally on those devices, since I never encountered it on my Nexus 5. I wonder if other 3rd party apps might also be involved.

Don't know..I found a guy that he and his girlfriend both have a Nexus 5 and it happens to both of them.

Seems some with the Moto G, 2nd Gen were also having the problem.

It could be similar to the bug I have in the "more settings" of my call settings. It shows a "network or sim error" when I go in there. It seems to be only AT&T branded phones, but it isn't all AT&T branded phones and it was present on KitKat, but wasn't reported as a known issue. It could be something just like that.

 

[RohanD6503]

I found the solution after thorough research on the net, just go to <settings> <apps> <all> <IncallUI> click on Force stop,then enable it again. It did unlock my phone on swipe for incoming calls. By the way, the notification tick should always be on !

 

[B. Diddy]

Thanks for letting us know your solution! Although IncallUI isn't on the app list for all devices (like on my Zenfone 2), so I wonder what would have to be done if this issue crops up on those devices.