We have moved to a new Sailfish OS Forum. Please start new discussions there.

Unable to unlock lock screen [answered]

asked 2017-11-30 01:47:11 +0300

juhaj gravatar image

updated 2017-11-30 15:06:48 +0300

jiit gravatar image

After removing the meecast lockscreen widget and rebooting,I can no longer access the phone: at reboot (and all subsequent reboots) only a plain ambience-screen appears. The phone does not ask for lock-code, nor either of the PINs, it just looks like a lockscreen with no way to trigger the unlock-sequence. The only things working are swipe-from-bottom (gives me camera, as it should) and swipe-from-top (which gives me ambience pulley menu). Volume keys also work, but nothing else dose, so I am unable to use the phone for anything. I've tried https://together.jolla.com/question/171477/missing-number-pad-on-lock-screen-unable-to-unlock/ but that does not help. Any ideas how to recover?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by ced117
close date 2017-11-30 22:58:09.087922


Do you have ssh access to the device?

juiceme ( 2017-11-30 07:57:08 +0300 )edit

The last resort (if you know the security code) would be factory reset in recovery mode:

jovirkku ( 2017-11-30 10:09:02 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2017-11-30 15:38:33 +0300

anig gravatar image

I guess this was using lockscreen widget manager. if you can access the device via ssh then you need to manually change two files in /home/nemo/widgetManager. In both PortraitWidgets.qml and LandscapeWidgets.qml you need to remove references to meecast widget including:

import "file:///usr/share/widgetManager/widgets/meecast-widget"


MeecastWidget{ id: meecastwidget anchors{ top:parent.top topMargin: 491.0 left:showcalevents.left leftMargin: 0.0 } }

It should work after that.

edit flag offensive delete publish link more

answered 2017-11-30 22:54:19 +0300

juhaj gravatar image

Thanks for a proposed solution anig, but don't know if it works because I got around fixing it myself. I do think your solution would have worked though because the problem was indeed an interplay between widget manager and meecast daemon. Your solution, if it works, is better than mine, because it would work in recovery mode, mine needs ssh access (or I suppose recovery mode with enough mount points active to make rpm work).

My solution: 1. Reboot 2. Check if wifi comes up (it has never been 100% reliable on Sailfish), if not, go back to 1, otherwise go to 3. 3. ssh in the phone 4. uninstall (rpm, zypper, pkcon, you name it) all meecast packages. 5. reboot.

In the step number 4 I am pretty sure removing just meecast daemon would be enough but in the middle of the night I just wanted a working phone and go to bed so I removed them all.

edit flag offensive delete publish link more

Question tools

1 follower


Asked: 2017-11-30 01:47:11 +0300

Seen: 286 times

Last updated: Nov 30 '17