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

Bug: Screen turns off after a few seconds [released]

asked 2013-12-30 21:42:58 +0300

Julle gravatar image

updated 2014-01-21 11:14:58 +0300

zlatko gravatar image

For some reason, my Jolla started to turn off the screen after a few seconds (~5) if I didn't touch the screen. Screen just went black after a couple of seconds. For instance, while opening a web page or if I just left the app launcher visible. Changing "Sleep after" for Display had no effect. The device was not locked: double-tap after screen power down powered the screen and showed the app that I had been using.

Reboot fixed the issue, so it's not a big problem. However, I noticed 2 things:

1) (probably completely unrelated and worthy of an another bug report) I was typing something to terminal (actually Irssi via SSH) when I received a phone call and answered. When the call ended, terminal was writing the letter 'e' repeatedly. Pressing 'e' resolved the issue, but 'e' had been repeated for at least 20 lines.

2) Somehow I put a calendar alarm to the background. I don't recall snoozing it (could have happened though), or doing anything else. Yet I lost the alarm, until I pressed the power button after the screen had powered off. Then the alarm came back normally. Unfortunately, dismissing it didn't fix the screen issue.

My gut feeling is that the calendar alarm had something to do with the problem, but I could be wrong. Now the device seems to be working fine. Also, closing all open apps had no effect on the problem.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by eric
close date 2014-05-20 15:16:09.373668


I can alreadyI tell you that it is neither of these things that should be the cause, as I experienced the same screen problem yesterfay without doing such things :) Just a regular day with no developer mode. Nevertheless the problem remains and was really annoying :/

DaTa ( 2013-12-31 00:50:17 +0300 )edit

I've had this happen as well. Not much help as I can't reproduce it, but thought I'd chime in anyhoo.

ZZB ( 2013-12-31 08:29:47 +0300 )edit

Same here. Reboot solved it. Perhaps related, after a reboit I get a notification that thete is a sydtem update. But that one is already installed when I view the update via the norification.

Could it be the update wasn't correctky/completely

Jarno ( 2013-12-31 10:20:41 +0300 )edit

And same problems here. Reboot solves it. Bug was there too before latest update.

Nitro ( 2014-01-02 12:32:13 +0300 )edit

I've had this bug a several times, first I thought that it was something to do with android support, but the problem still exists after a factory reset & using my Jolla without android support. Very anoying, must reboot to fix it temporary.

goldenm ( 2014-01-08 01:47:07 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-01-21 10:43:02 +0300

droll gravatar image

updated 2014-01-21 12:04:07 +0300

i have this problem too. toggling phone between silent and audible mode fixed it for me. didnt have to reboot.

edit flag offensive delete publish link more


I did this too and the problem fixed...for a while. When you reboot the device the problem starts again...

akira1980 ( 2014-01-21 12:09:40 +0300 )edit

Happened to me again today - tried going to silent and back - issue was fixed.

zlatko ( 2014-01-24 23:59:12 +0300 )edit

Question tools



Asked: 2013-12-30 21:42:58 +0300

Seen: 1,531 times

Last updated: Jan 21 '14