Ask / Submit

[Bug] freezes phone, touch function does not work

asked 2014-12-29 21:14:17 +0200

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2014-12-30 08:02:55 +0200

chinauser gravatar image

soon after I installed the touch function failed and the phone became useless. Turning the phone off and on got me stuck at the code lock screen, still no response to touches. During a factory reset the phone worked with the intermediate releases but the problem reoccurred with the last step of installing ver Please advize.

edit retag flag offensive close delete

4 Answers

Sort by » oldest newest most voted

answered 2014-12-29 21:44:05 +0200

Sailor gravatar image

I would say you should contact Jolla Care. They will help you out of this situation.

edit flag offensive delete publish link more


We need the answer here too, so that other affected users can find a workaround solution.

chinauser ( 2014-12-30 08:03:43 +0200 )edit

answered 2014-12-30 08:02:26 +0200

chinauser gravatar image

I re-open this question because I've got the same problem with one of the Jolla phone I own. After the udpate, my phone UI is frozen after the boot. I can see the lock keypad but there's no response when I press the keys. I cannot swipe in any direction. Then, after several power button short presses and after waiting for 30 seconds, by magic, the lock keypad becomes responsive again and I can enter my lock code. Then everything is normal after I'm "in".

Every time I reboot this phone, I need to go through this process and I'm always scared that I won't be able to actually enter my lock code into the phone.

This is a serious bug, and I hope there is a proper answer/bug fix.

edit flag offensive delete publish link more


I've had this problem twice with Vaarainjärvi after reboots. Both times I had to wait for 30 seconds to one minute and it was ok then.

It could have been that I was playing with swap settings and sdcards, but I really don't know what caused it. Thought I should mention that anyway.

Manatus ( 2014-12-30 09:46:02 +0200 )edit

@Manatus Does it happen to you every time you boot the phone? For me, it's happening at every boot.

chinauser ( 2014-12-30 09:51:23 +0200 )edit

No, it just happened twice in a row when I was tweaking stuff restarting the phone in between the changes. [The actual changes were first trying to disable zram through 'systemctl disable', and later by editing the zram.service file. Latter worked, but after both changes I got that longish stuck period.]

I'd say that it has happened two times out of eight, no more. I tested it just now, and the numpad was responsive instantly when it came visible. The zram tweak is still active so the original problem most probably wasn't just because of that.

The issue could be some kind of hair triggered race condition between devices or services.

Just for the reference starting the powered off phone to the lock code on screen takes 30 seconds for me. (From the "nudge" you feel when pressing the power button, to be exact.)

Manatus ( 2014-12-30 11:32:05 +0200 )edit

answered 2014-12-30 09:33:32 +0200

NuklearFart gravatar image

it might be that the first time after upgrading the phone stucks because it also upgrades dalvik for android apps. depending on your installations this might take some time. i did not have that problem because i only use one android thing but i read this somewhere else.

edit flag offensive delete publish link more


It's happening every time I boot the phone. It can't be that my Dalvik is running Android app upgrade every time.

chinauser ( 2014-12-30 09:52:27 +0200 )edit

answered 2014-12-30 15:20:38 +0200

spelle gravatar image

I've had the same issue… It appears that it is related to the proximity sensor :

Check out these threads :

Hope this helps.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-12-29 21:14:17 +0200

Seen: 353 times

Last updated: Dec 30 '14