Ask / Submit
7

[bug] Long wait before accepting input at pin code screen

asked 2015-01-14 10:04:07 +0300

When I reboot my phone, and it comes to the pin code screen, it takes an abnormal amount of time before it starts accepting input. This started to happen after the previous upgrade (from December). I haven't timed it, but I'm not talking about a couple of seconds here, more like a minute. It's extremely frustrating, and the first time it happened I thought I wasn't going to get in at all. This happens every time now, but it never happened before the upgrade. Has anyone else seen this behaviour? I couldn't find a related issue.

edit retag flag offensive close delete

Comments

Maybe the SIM is not correctly connected in the phone´s Slot? Never recognized this.

florifreeman ( 2015-01-14 10:07:23 +0300 )edit

No, it just takes a long time before the phone accepts input. Once I get to type in the pin code, the phone starts up fine and connects to the network. It's just that I see the input screen for the pin code for very long without being allowed to type anything.

Cecilie ( 2015-01-14 10:08:55 +0300 )edit

Yes, I have exactly the same problem since I upgraded to Vaarainjärvi (1.1.1.27). In my case the delay is more like 10 minutes which is quite bad. The phone boots quite normally and quickly to the pin code query screen, then nothing happens, it accepts no input until I wait ~10 minutes or so. After that, it connects normally to the network. This happens every time I boot it. Definitely a bug in Vaarainjärvi.

jussivuorisalmi ( 2015-01-14 20:37:20 +0300 )edit

Yep, I have the same problem too.

Alex Huusko ( 2015-01-21 21:42:14 +0300 )edit

I have this problem too. As I boot, myJolla returns to the pin code screen and stops there. Does not accept any entries. But if I plug my Jolla to recharger and recharge it it will immediately accept pincode to be entered. Now when I boot I need to have the recharger available.

Hakanakki ( 2015-01-22 14:23:03 +0300 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2015-01-19 11:26:33 +0300

spiiroin gravatar image

What changed in update10 is that the touch input is not enabled until proximity sensor reports that it is not covered. This is done to prevent pocket calls from happening if the device/ui restarts or power button is pressed while the device is in a pocket.

The caveat is that if proximity sensor for some reason incorrectly reports that it is covered (might be more likely to happen during bootup), the touch stays blocked even though it should not be.

We have plans to give visual feedback in case this happens, but even now you could try to:

  • Cover the sensor area briefly (top right corner of the display, closest to the power button) -> might get the sensor back to sync with reality
  • Do triple power key press -> forces the sensor to be temporarily regarded to be in "not covered" state
edit flag offensive delete publish link more

Comments

Covering the sensor area briefly does the trick for me, thanks. Pin code query accepts input as soon as I have touched the top-right corner.

jussivuorisalmi ( 2015-01-28 22:49:42 +0300 )edit

This worked for me too, thanks for the answer. But I hope the issue will be resolved in an update. If it was just something that happened every now and then, visual feedback would be good, but since it happens every time for certain people (like me), I suspect there may be a bug in the code to check this proximity sensor on startup.

Cecilie ( 2015-01-29 16:44:14 +0300 )edit
Login/Signup to Answer

Question tools

Follow
5 followers

Stats

Asked: 2015-01-14 10:04:07 +0300

Seen: 168 times

Last updated: Jan 19 '15