Jolla randomly shuts down

Question

566

Jolla randomly shuts down

asked 2013-12-30 22:04:14 +0300

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

updated 2015-05-20 01:45:14 +0300

Neo

30712 ●180 ●234 ●229

Numerous users have an issue with the phone rebooting by itself. User testing has revealed that it most likely has something to do with the battery. If this is happening to you, there are two ways you can probably solve the problem. You can either:

take out the phone battery, and rub all contact areas on the battery and the phone with a regular eraser, then just put the battery back in.
take a small piece of paper and put it between the bottom of the battery and the phone, so it makes better contact.
put a bit of paper between the battery and the phone body (as seen here)

If neither of these solutions helps at all, please mention this and edit this post to include that information.

It would be nice to read an official statement on the issue, if this is something related to the manufacturing process or something else.

edit 06.04.2015 (MacManus): i noticed that my jolla reboots on weak network connections (can't reproduce in wlan). If i'm in an area with weak network, my jolla constantly reboots. If i didn't activate my sim, the phone didn't reboot. As soon as i activate sim and get mobile network connection, the jolla reboots.

Edit 20.05.2015: Anyone with this problem please see this answer, it seems that they finally have a clue about how to fix this issue.

edit retag flag offensive close delete

Comments

3

I'm experiencing this same problem starting today. I haven't installed any new updates / apps since the last SW update 2 days ago. Sometimes after the shut down the phone refuses to turn back on. Trying different things with the phone now to track the problem down.

EDIT: After the shut down happens, the phone turns back on on first try if I plug in the charger.

fAzu ( 2013-12-30 22:13:32 +0300 )edit

3

I have my Jolla phone turned on for 24/7 and it's also updated to this recent firmware and haven't ever seen such unintentional shut downs. None. Nothing even close to that. So definitely can't confirm this. There is a change you may have problems with hardware.

Simakuutio ( 2013-12-30 22:14:29 +0300 )edit

1

I've had 2 reboots so far, but both were before 1.0.2.5 update and while I was not actively using the device. I can't really say anything else about the cases, but I think I had nothing special running, just WiFi/3G and Settings or something. What apps and networks are you using when this happens?

Julle ( 2013-12-30 22:16:30 +0300 )edit

Did you try hard reset for solve some issue ?
1. if yes, try to run CSD tool on your phone for discover any abnormal hardware malfunctionality before return your product for hardware repair
2. pully down, select phone, input code (i can't show the code) and follow instructions and we wait feedback you can find the code here http://jollafr.org/un-utilitaire-secret-pour-tester-toutes-les-fonctionnalites-de-votre-jolla/

redge73 ( 2013-12-30 23:03:06 +0300 )edit

7

Ok, so after removing my battery for a longer period (roughly 10 minutes) the problem vanished. Seems like a software glitch. I cannot recreate this behavior for now, but I'll monitor my workflow in case the problem reappears.

fAzu ( 2013-12-31 10:18:51 +0300 )edit

I think it is software ass well. But don't want to reset the device. Still not realy shore what the cause is. I am now back on a default ambiance ass from last reboot I lost my custom ones (different Bug all ready reported) Maybe it is related to that, because right now it is stable

teun ( 2013-12-31 16:29:18 +0300 )edit

Mine shut itself down twice today: once while charging (battery was nowhere near empty) and again while in my pocket (plenty of space, and as far as I can tell, nothing was pressing against the power button). Software version 1.0.2.5.

Also, the CSD tool itself kills audio. A reboot brings it back.

jsiren ( 2014-01-01 03:45:07 +0300 )edit

This problem reappeared again for me. My phone worked fine for a couple of days and now it's shutting down again. This time it shut down randomly when someone tried to call me (2 times) and when I started to work with my phone just to check clock or email (3 times). One time it also flashed the recharging battery logo even though it wasn't plugged in. Maybe this has something to do with the battery status....(?)

fAzu ( 2014-01-04 21:51:37 +0300 )edit

I'm having this same issue!

Jolla has shut down for me with no one pressing the power button, like once while it was waiting in a bookshelf (lots of battery left) --> two hours later I found that it had shut down. This has happened to me since the 1.0.2.5 update like 5-10 times, so basically almost every day since the update. Just can't figure out what could be causing it. It can happen any time of the day, busy time, idle time, inside pocket, outside pocket...

I did a factory reset today, updated to the 1.0.2.5 firmware --> a few hours of some minor use, mostly on idle --> it shut down again. So factory reset didn't solve my issue. I didn't even use any android applications, didn't install the android support so at least it isn't the one to blame.

I tried to remove the battery for an hour, now I put it back in, let's see if that helps, I'll report the results here later...

goldenm ( 2014-01-04 23:30:39 +0300 )edit

I don't know if it's related, but a memory consumption bug has been reported of upowerd - would this be related? Assuming upowerd would run out of memory, crash, and trigger a watchdog of some sort?

jsiren ( 2014-01-09 17:32:05 +0300 )edit

Or then something is leaking memory.

jsiren ( 2014-01-09 17:33:47 +0300 )edit

Since yesterday, I've experienced some accidental shutdowns of the phone when trying to make a call and while being inside a (native) app. I've just experienced a shutdown while the phone was idling on the table. Some of the shutdowns are 'hard', i.e. like pulling the battery, and some are 'soft', i.e. like shutting it down with the power button. The battery has always been far from being low (60-80%). The shutdowns during use happened with only one app open and without data connection, i.e. there was no heavy load on the phone.

SagaciousT ( 2014-01-09 19:30:39 +0300 )edit

I had the problem once, the phone shutdown like 5 times a day. Once when I was ending a conversation. 2 times when I was in the mail app. Other times when I was doing nothing special. All in the same area as where I work daily. Removing the battery for 20 minutes solved the problem.

BonoNL ( 2014-01-09 21:16:24 +0300 )edit

It was 4 days since that happened, I have Mitakuuluu running and the NFC chip is disabled throug systemctl stop tohd.service. The battery was at 65% an dropped during the reboots and startups. At one moment it said it was at 4%. After the cooldown, the battery was at 50 percent and phone felt hot.

BonoNL ( 2014-01-09 21:20:02 +0300 )edit

I think I caught the phone in the act. The screen went all wonky, and then the phone booted by itself.

csd doesn't find any problems, but kills audio. I have saved the initial logs from booting the phone. The phone didn't feel hot to the touch, but battery had risen from 28% to 31% after reboot.

jsiren ( 2014-01-09 23:27:53 +0300 )edit

During the last half hour, with light use of the phone, the one process that seems to grow most in memory footprint is lipstick. Also pulseaudio is growing slightly. It's early to say anything, though. I'll see what happens.

jsiren ( 2014-01-10 00:09:27 +0300 )edit

2

I'm experiencing this problem too. This started about 4 days after i got the phone. There can be a week when the phone works fine, then suddenly 5 shutdowns / day. I enabled logging and managed to see the phone enter a state called "ACT_DEAD" after a crash. But then restarting it works fine.

plipp ( 2014-01-10 09:22:06 +0300 )edit

I also "caught the phone in the act", it suddenly complained about "Low batterycurrant" (or "Låg batterispänning" in swedish). I managed to peek the battery to be at 4 % before it crashed. I then restarted the phone and the battery indicator was back at ~70 %, and it worked the rest of the day. I have now reset the phone, lets see if it helps..

plipp ( 2014-01-10 09:25:20 +0300 )edit

I'm also having the same problem after updating to 1.0.2.5. It mostly happens when battery is below 40%, and never when it's connected to a charger. Have tried Factory reset and pulling the battery out for an hour, but nothing have helped...

Skullb ( 2014-01-10 12:11:12 +0300 )edit

I have now used my Jolla soon one week without this "random shutdown". I fixed it by removing the battery for one hour and removing that nfc bug fixing tinfoil... I'll just wait for an official fix for that.

goldenm ( 2014-01-10 20:56:01 +0300 )edit

3

It seems to be a power problem. I had a shutdown yesrerday when taking a photo. I powred the phone up again and it shut down again when taking the photo. I was able then to take a few photos. The battery showed 4% then; before this, it was around 50% (3 days w/o recharging but covered NFC chip). It seems that the phone draws too high current for the moment and shuts down due to a short-term undersupply. Maybe a techie can brighten this better.

SagaciousT ( 2014-01-12 18:39:01 +0300 )edit

1

An excessive short-term power draw might also explain random shutdowns in poor coverage, i.e. transmitting at a high power to find a base station. (It would also explain why the phone tends to shutdown in my pocket while driving, but not when in the dash stand, not surrounded by 2 tons of Ford.)

jsiren ( 2014-01-13 13:16:48 +0300 )edit

Which TOH are you using? Could it be a problem with the "first ones"?

Pascal Schmid ( 2014-01-16 01:03:25 +0300 )edit

2

Often when i take metro in Paris, or the train, i'm facing an annoying error that make device unresponsive by creating many error network notification message. And i think this is also the cause of some sudden reboot. Until now i wasn't able to catch a reproductible case. But i notice today that this happen more in Paris, so could be something related with network cell.

I use a french operator : Free.fr

Also, i notice that lipstick is eating 25% of cpu, crash-reporter 25% (yes i ve enable it for an other crash), and msyncd an other 25% ... and the 25% other percent, i was able to read it before it s lag too much (ssh connexion to device dropped)

Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:55 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:56 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Operation aborted
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: connect-failed
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Connection failure: Free
Jan 16 08:02:57 localhost lipstick[1138]: ---- errorReported: Operation aborted

:)

A more detailed log :

Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4ddb;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1b6b056;t=4f01103cc0afc;x=64cd15b7e45f2b56;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: connect-failed
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4ddc;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1b7bc1a;t=4f01103cd16c1;x=45f091f9efe3348c;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Connection failure: Free
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4ddd;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1b84f94;t=4f01103cdaa3a;x=64cd15b7e45f2b56;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: connect-failed
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4dde;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1b92c23;t=4f01103ce86c9;x=45f091f9efe3348c;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Connection failure: Free
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4ddf;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1b9c799;t=4f01103cf2240;x=db7c8f4a6c05b002;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Operation aborted
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:55 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4de0;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1bb05cc;t=4f01103d06054;x=64cd15b7e45f2b56;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: connect-failed
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:56 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4de1;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1bc0f2f;t=4f01103d169d5;x=45f091f9efe3348c;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Connection failure: Free
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:56 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4de2;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1bc644e;t=4f01103d1bed6;x=64cd15b7e45f2b56;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: connect-failed
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:56 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4de3;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1bcf340;t=4f01103d24de6;x=45f091f9efe3348c;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Connection failure: Free
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost
Thu, 16 Jan 2014 08:02:56 +0100 [s=c72a1c9ff17e44f4ab356b8dafd41ab4;i=4de4;b=4bc38f3d454444bcb11f2b2ae4e944c4;m=8b1bd73c5;t=4f01103d2ce6b;x=db7c8f4a6c05b002;p=system@c72a1c9ff17e44f4ab356b8dafd41ab4-0000000000004e47-0004f011041655f2.journal]
    _TRANSPORT=stdout
    PRIORITY=6
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=lipstick
    MESSAGE=---- errorReported: Operation aborted
    _PID=1138
    _UID=100000
    _GID=100000
    _COMM=lipstick
    _EXE=/usr/bin/lipstick
    _CMDLINE=[137B blob data]
    _SYSTEMD_CGROUP=/user/nemo/c2/systemd-1068/lipstick.service
    _SYSTEMD_SESSION=c2
    _BOOT_ID=4bc38f3d454444bcb11f2b2ae4e944c4
    _MACHINE_ID=8c18df265cf548b49e0dcbbc930bae3c
    _HOSTNAME=localhost

Khertan ( 2014-01-16 17:07:39 +0300 )edit

@Pascal Schmid: Perhaps, but if I may add that although mine just shut down randomly for the first time a day after receiving the poppy red OH, I was using the standard white OH at the time it shut down.

martti ( 2014-01-16 22:50:59 +0300 )edit

Well I am also having problems. Just noticed that Timed, Lipstick and msyncd are hogging memory and processor power. Five random shutdowns in about a months time. Lagging when and unresponcive when network connection is extablished after device wake up with double tap and power button press.

These processes take the power lately: https://picasaweb.google.com/115946291292582430648/Bugs#5969821714947901810

Anyhow hope you guys can triage these bugs.

miqu ( 2014-01-17 15:07:57 +0300 )edit

(sorry, this is looong)
Unfortunately, I'm having this problem as well. Over the last week (longer?), my Jolla has suddenly decided to shut itself down - not re-boot, as I'll need to press-hold the power button to start it again (including enter SIM PIN).

Note that I have never tampered with/in the Jolla terminal (but I do have a bunch of apps, some are bluetoothed from an Android phone, some are installed from F-Droid, and then installed, or are native apps installed from Jolla Store).
I also have the white Other Half (still waiting for my LE TOH - got the email that it's on its way, but still no sign of it in my mailbox), with aluminium foil covering the NFC chip.
I always have mobile data on, and move to several places in my job so I can't pinpoint these shutdowns to a single place.

First time I realized something weird was up when it had shut itself down (not the first time), was when I tried to re-start it, and it complained about low battery - and that "low battery" in that case meant 25%! Connected it to charger, and then re-start worked. (This happened this week (two days ago? beginning of this week?).)

It has shut-down itself once a day for at least a week, but twice today (yesterday as well? can't remember).
So far, I have always held my Jolla in my hand, doing something with it.
None of the times (since the 25% battery left-thingie), I've had less than 25% battery when it happened, and none of the times it has shut itself down due to low battery (when that has happened, I've always got warnings at 10%, 9%, 8%, ... counting down to 3% or 2%, and then shutting itself down).

As a matter of fact (I found some notes I added end of December) I've had "soft resets" as well, but most of them have been when tinkering with Android apps: I've used Android apps, and the Android layer refuses to work. I close down as many Android thingies as possible, and then - or when I close the last of them - the Jolla re-boots itself, and I'm presented with an empty Home screen (no need to enter SIM PIN, or swipe up from Lock screen).

I've also had a bunch of "double-tap only presents a black screen, but the pulley works (I can hear it); swipe down to turn screen of, and double-tap to re-start screen, and now things are ok". (Can't remember whether they include "soft resets".)

phle ( 2014-01-17 18:48:56 +0300 )edit

(also - but I'm unsure whether this is related, but I figured I should mention it:

1/3 to 1/2 of the times when I do swipe-down-to-turn-off-screen, my Jolla
1) turns screen off
2) waits for less than a second
3) turns screen on again (showing Lock screen)
I then swipe-down-to-turn-off-screen again, and the screen turns off.)

edit: Slightly over an hour ago, my Jolla stated 4% left on battery. I shut it down, took out the battery + SIM + microSD, thought I should wait 10', and then forgot it.
Just assembled it (sans microSD, as it's empty) and turned it on, and it now shows 49%. Strange.

phle ( 2014-01-17 18:53:14 +0300 )edit

Yesterday my Jolla shut itself at least 4 times even though battery was supposed to be at over 60%. It often displayed the "connect usb cable to device" indicator, that you get when you connect it to charger when the device is powered down. Also, it didn't boot up (or stay up) without a charger.

Julle ( 2014-01-18 12:05:50 +0300 )edit

This has happened for me for few times too. I also suspect some problems with power. Jolla turned off, when I tried to take a photo. I booted it, tried to take a photo again and it turned off again. The battery charge seems to be around 80%.

Maybe some spikes in power consumption makes Jolla believe, it's out op power and it turns off?

Pesasa ( 2014-01-18 12:37:48 +0300 )edit

Ok ... i got many shutdown, sometime 15 or more in a row !!!

So ... this happen randomly, sometime when it idle in pocket, sometime when trying to take photos, sometime during a call, sometime during internet session, while on wifi, or 3g, or just scrolling apps in launcher ... or doing nothing !

I ve reset the device, that didn't improve things ... giving log to stskeeps.

I clearly believe that s faulty hardware ...

Khertan ( 2014-01-20 18:39:06 +0300 )edit

This is happening to me too. Sometimes I take jolla out of my pocket and it is turned off. Today I was sending sms in a low 2G signal enviroment and phone shut down. I turned it back on, opened conversation app and it shut down again. I took the battery out and put it back in than I turned phone back on, opened conversation app and status of sms was sending. Sms was send but status of it remains sending. For now phone has not randomly shut down.

PG ( 2014-01-22 02:27:56 +0300 )edit

it happen to me too now, from 21.01.2014 version 1025 phone setting language=french + Warehouse app phone setting language=english, don't remember crash but without warehouse app

redge73 ( 2014-01-22 03:45:00 +0300 )edit

I've started experiencing this issue today 22 Jan 2014 starting from 16.00 (GMT+1) . In the last 1 hour and half my Jolla has shutdown 4 times without a specific interval, both on 2G and on 3G, full netwrok signal or weak signal, both during intense usage and when in standby after a double-tap. I turned on my Jolla Sunday 19 Jan and never shutdown since then; i put it in airplane mode and in silent mode every night; I put in silent mode every day from 9.00 to 18.00. I disabled tohd service almost 3 weeks ago, auto time update is on since first configuration. After last shutdown (17.36 GMT+1) I removed the battery for very few seconds and restarted it, not shudowns in the last 7 minutes.

SailfishOS Version 1.0.2.5

Patrizio Bruno ( 2014-01-22 18:46:10 +0300 )edit

3 shutdowns in the last 4 minutes:

1) while entering home, in a zone where cellular signal goes down 2) few seconds after I switched it on and it was connecting to the wifi 3 and 4) few seconds after I switched it on

It seems it can't stay on

Patrizio Bruno ( 2014-01-22 19:48:33 +0300 )edit

Looks like disabling automatic time updates helps to prolong the period with no shutdowns after last pulling the battery. My shortest interval from pulling the battery to the next shutdown was approx. 32 hours with time updates disabled, and about 1 hour with time updates enabled.

pycage ( 2014-01-23 20:00:21 +0300 )edit

I'm experiencing this as well. I've used my Jolla for about a month without an issue, then it began to shut down about like a week ago. It happened several times when I was underground without network coverage, and once when using Android Firefox, and yet once when I tried to make a backup.

paul7 ( 2014-01-25 11:27:51 +0300 )edit

1) I never used automatic time updates; 2) TOH service have beed disabled all the time; 3) I've had 1.0.2.5 since the end of December and everything was OK for several weeks. 4) In fact pretty much nothing had changed in software when my Jolla began to shut down.

paul7 ( 2014-01-25 11:31:16 +0300 )edit

I experienced those shutdowns. The only way to solve the issue is to remove the battery. I had the feeling the issue is linked to losses of mobile signal but I'm not sure of that. I'm also using automatic clock updates because accuracy of internal clock is bad.

ron282 ( 2014-01-28 09:08:23 +0300 )edit

How can I create logfiles of these crashes? AFAIK SailfishOS uses journald for logging, but it looks like the logs are not persistent, i.e. empty after each reboot or crash. Am I right? How can I persist these logs?

schmittlauch ( 2014-01-29 17:56:35 +0300 )edit

I am experiencing this as well. For extended periods of time and when the phone is plugged into the charger, it doesn't seem to restart. At home, where I have poor cell reception, it restarts sometimes - even during a phone call.

guaq ( 2014-02-02 10:45:24 +0300 )edit

Having much more random reboots sind 1.0.3.8. Some days 2 or more times. Last one just after pressing Send in Messaging app.

Happily after reboot the written message wasn't lost. Copied it and Send this time worked:-)

axaq ( 2014-02-12 15:18:01 +0300 )edit

I started experiencing these random reboots after upgrade to 1.0.3.8. They come in series of 5-10 in row. I enter PIN and lock codes and just start to open some applications and device reboots again. Sometimes it reboots right after entering the codes, without anything open. It is very annoying and looks to become epidemic in Jolla population. So far no statement from Jolla team, but I hope they are working on a hot fox for that.

zlatko ( 2014-02-12 20:14:42 +0300 )edit

I am noticing a cycle behaviour of the reboots of my Jolla - every 24 hours, at nearly the same time(18:15 EEST) I get a chain of 10-20 reboots. This is happening past 3 days. Today I stopped it by pulling out the battery. After reinserting it so far(30min) all looks OK.

zlatko ( 2014-02-13 18:56:14 +0300 )edit

Same problem here. Started to happen after the 1.0.3.8 update. Before that, my Jolla was rock-solid. After the update, it's become unusable. It just constantly reboots and rarely goes for more than a couple of minutes without rebooting.

It's definitely related to the network connection. In offline mode, no reboots. As soon as the network connection is enabled, the reboot cycle begins.

It's not wifi or 3G-specific. It reboots when either or both are enabled.

I can't reproduce the problem reliably. Most of the time, the phone will reboot 30 seconds or a minute after having booted and gone past the lock screen, either on its own or whenever I try to use the data connection in some way (e.g. loading a page in the built-in Web browser or launching the native Whatsapp app).

Occasionally however, it will run for a good 10 or even 15 minutes (whoo hoo!) before rebooting and it will even let me stream music with the Rdio Android app for a little while. But that's very rare - I manage to get it going for that long maybe once a day at most.

Overall, completely unusable :(

MehdiMe ( 2014-02-14 13:44:59 +0300 )edit

I'm not sure whether it's related, but for what it's worth: when I rebooted my Jolla after it had turned off for the second time in an hour this morning, the first thing I saw was a message at the top of the screen saying "Device is getting hot. Close all apps now." (or something like that, not sure what it said exactly). I had no apps running (just switched it on) and it didn't feel particularly hot, though.

martti ( 2014-02-19 21:48:35 +0300 )edit

For me device sometimes shuts itself down(you have use power key to turn it ON), sometimes it gets into reboot loop(turns OFF=>turns ON=>asks for PIN=>starts UI=>and after small period turns OFF again) and sometimes I got a random mixture of the other 2 cases. For me these symptoms have common root/cause(I might be wrong!). Shall the original question be re-worded or the community thinks we need 2 separate threads about "random shutdowns" and "random reboots"?

zlatko ( 2014-02-25 14:48:52 +0300 )edit

(just adding "for reference")

Lately, I'm experiencing "shutdown - reboot - enter PIN" for no apparent reason - the only common factor seems to be "uptime at least 2-3 days" (which I noticed when it happened when my uptime was 5-days-and-some-hours; and it occurs more often if I don't take out the battery, wait 10 minutes, and then put back the battery and boot-up).

This morning, I - for the first time - had a "shutdown, won't auto-reboot". That was odd, as I "expected" it to reboot by itself, and ... it didn't.

For now, I'm just "living with it", hoping it will be fixed with the 1.0.4.(something) update mentioned in Ygriega's "answer" below (also mentioned in the question-edit "Update (2014-02-14)" above).

phle ( 2014-02-27 18:52:04 +0300 )edit

I had some not so random reboots recently. Phone did stay on while waiting for SIM PIN to be entered but after entering the pin phone rebooted almost instantly. If I didn't activate the sim then the phone didn't crash.

So I took the sim out and brushed it against a table. After that the phone didn't crash anymore and has been working since, four days now. So can't tell if massaging the sim helped or just taking the battery out while doing that.

This palace where I was had quite poor reception.

hetas ( 2014-03-03 20:52:34 +0300 )edit

1

Another observation that might help - when my device enters a reboot loop, in most cases(like 9 out of 10) just prying open the TOH slightly makes the phone boot and work afterwards. I am starting to wonder if part of the problem is not HW related?

zlatko ( 2014-03-05 08:38:11 +0300 )edit

Adding that while my Jolla seems to be randomly shut down, it gets worse while roaming. I had it crash at least twice on me as I was trying to send SMS while roaming (sending SMS in home network didnt cause the same thing). There are other occasions when it shut down during roaming as well but for there were no clear pattern with what I may have done to cause the shutdown.

Henkka ( 2014-03-05 23:00:39 +0300 )edit

I haven't experienced the random shutdown issue but on three separate occasions the phone has acted weird, up to the point of having to remove the battery in order to fix it and each time the phone has completely scrambled my app order. Now I'm not even trying to organize them to my liking until the underlying issue (whatever it may be) is fixed. Also, when that has happened, apps have typically thought they are being launched for the first time despite e.g. saved games still being there.

typo ( 2014-03-07 18:51:10 +0300 )edit

my Jolla shuts down as well, today it gone loop jolla-logo => black screen => jolla-logo

plugging to charger started phone normally, battery level was about 60%.

my Jolla shut down couple times of week, hope that next update helps with that problem.

Sami ( 2014-03-09 00:39:18 +0300 )edit

Since 3 days I'm facing this problem as well. Phone has latest update. The problem started using the phone app, but later occurred as well using the msg app. My battery level was about 50% and up to 90% while it happened. Using the phone without radio's enabled (like I do now with the Jolla and using my beloved N9 as main mobile) hasn't produced any random shutdown till now.

Hope the update will address this problem.

Vieno ( 2014-03-14 13:57:51 +0300 )edit

I did happen to me a few times before, but after the update yesterday (1.0.4.20) it happened twice. The first time I described it here https://together.jolla.com/question/33919/battery-level-bug/. Today after the shutdown I wasn't able to restart the phone at all. I pulled out the battery for a while and after that the phone could be restarted.

Neo ( 2014-03-18 22:47:57 +0300 )edit

I'm experiencing this same problem starting today. I haven't installed any new updates / apps since the last SW update 2 days ago. Sometimes after the shut down the phone refuses to turn back on. Trying different things with the phone now to track the problem down.
EDIT: After the shut down happens, the phone turns back on on first try if I plug in the charger.
fAzu ( 2013-12-30 22:13:32 +0300 )edit
I have my Jolla phone turned on for 24/7 and it's also updated to this recent firmware and haven't ever seen such unintentional shut downs. None. Nothing even close to that. So definitely can't confirm this. There is a change you may have problems with hardware.
Simakuutio ( 2013-12-30 22:14:29 +0300 )edit
I've had 2 reboots so far, but both were before 1.0.2.5 update and while I was not actively using the device. I can't really say anything else about the cases, but I think I had nothing special running, just WiFi/3G and Settings or something. What apps and networks are you using when this happens?
Julle ( 2013-12-30 22:16:30 +0300 )edit
Did you try hard reset for solve some issue ?
if yes, try to run CSD tool on your phone for discover any abnormal hardware malfunctionality before return your product for hardware repair
pully down, select phone, input code (i can't show the code) and follow instructions and we wait feedback you can find the code here http://jollafr.org/un-utilitaire-secret-pour-tester-toutes-les-fonctionnalites-de-votre-jolla/
redge73 ( 2013-12-30 23:03:06 +0300 )edit
Ok, so after removing my battery for a longer period (roughly 10 minutes) the problem vanished. Seems like a software glitch. I cannot recreate this behavior for now, but I'll monitor my workflow in case the problem reappears.
fAzu ( 2013-12-31 10:18:51 +0300 )edit
I think it is software ass well. But don't want to reset the device. Still not realy shore what the cause is. I am now back on a default ambiance ass from last reboot I lost my custom ones (different Bug all ready reported) Maybe it is related to that, because right now it is stable
teun ( 2013-12-31 16:29:18 +0300 )edit
Mine shut itself down twice today: once while charging (battery was nowhere near empty) and again while in my pocket (plenty of space, and as far as I can tell, nothing was pressing against the power button). Software version 1.0.2.5.
Also, the CSD tool itself kills audio. A reboot brings it back.
jsiren ( 2014-01-01 03:45:07 +0300 )edit
This problem reappeared again for me. My phone worked fine for a couple of days and now it's shutting down again. This time it shut down randomly when someone tried to call me (2 times) and when I started to work with my phone just to check clock or email (3 times). One time it also flashed the recharging battery logo even though it wasn't plugged in. Maybe this has something to do with the battery status....(?)
fAzu ( 2014-01-04 21:51:37 +0300 )edit
I'm having this same issue!
Jolla has shut down for me with no one pressing the power button, like once while it was waiting in a bookshelf (lots of battery left) --> two hours later I found that it had shut down. This has happened to me since the 1.0.2.5 update like 5-10 times, so basically almost every day since the update. Just can't figure out what could be causing it. It can happen any time of the day, busy time, idle time, inside pocket, outside pocket...
I did a factory reset today, updated to the 1.0.2.5 firmware --> a few hours of some minor use, mostly on idle --> it shut down again. So factory reset didn't solve my issue. I didn't even use any android applications, didn't install the android support so at least it isn't the one to blame.
I tried to remove the battery for an hour, now I put it back in, let's see if that helps, I'll report the results here later...
goldenm ( 2014-01-04 23:30:39 +0300 )edit
I don't know if it's related, but a memory consumption bug has been reported of upowerd - would this be related? Assuming upowerd would run out of memory, crash, and trigger a watchdog of some sort?
jsiren ( 2014-01-09 17:32:05 +0300 )edit
Or then something is leaking memory.
jsiren ( 2014-01-09 17:33:47 +0300 )edit
Since yesterday, I've experienced some accidental shutdowns of the phone when trying to make a call and while being inside a (native) app. I've just experienced a shutdown while the phone was idling on the table. Some of the shutdowns are 'hard', i.e. like pulling the battery, and some are 'soft', i.e. like shutting it down with the power button. The battery has always been far from being low (60-80%). The shutdowns during use happened with only one app open and without data connection, i.e. there was no heavy load on the phone.
SagaciousT ( 2014-01-09 19:30:39 +0300 )edit
I had the problem once, the phone shutdown like 5 times a day. Once when I was ending a conversation. 2 times when I was in the mail app. Other times when I was doing nothing special. All in the same area as where I work daily. Removing the battery for 20 minutes solved the problem.
BonoNL ( 2014-01-09 21:16:24 +0300 )edit
It was 4 days since that happened, I have Mitakuuluu running and the NFC chip is disabled throug systemctl stop tohd.service. The battery was at 65% an dropped during the reboots and startups. At one moment it said it was at 4%. After the cooldown, the battery was at 50 percent and phone felt hot.
BonoNL ( 2014-01-09 21:20:02 +0300 )edit
I think I caught the phone in the act. The screen went all wonky, and then the phone booted by itself.
csd doesn't find any problems, but kills audio. I have saved the initial logs from booting the phone. The phone didn't feel hot to the touch, but battery had risen from 28% to 31% after reboot.
jsiren ( 2014-01-09 23:27:53 +0300 )edit
During the last half hour, with light use of the phone, the one process that seems to grow most in memory footprint is lipstick. Also pulseaudio is growing slightly. It's early to say anything, though. I'll see what happens.
jsiren ( 2014-01-10 00:09:27 +0300 )edit
I'm experiencing this problem too. This started about 4 days after i got the phone. There can be a week when the phone works fine, then suddenly 5 shutdowns / day. I enabled logging and managed to see the phone enter a state called "ACT_DEAD" after a crash. But then restarting it works fine.
plipp ( 2014-01-10 09:22:06 +0300 )edit
I also "caught the phone in the act", it suddenly complained about "Low batterycurrant" (or "Låg batterispänning" in swedish). I managed to peek the battery to be at 4 % before it crashed. I then restarted the phone and the battery indicator was back at ~70 %, and it worked the rest of the day. I have now reset the phone, lets see if it helps..
plipp ( 2014-01-10 09:25:20 +0300 )edit
I'm also having the same problem after updating to 1.0.2.5. It mostly happens when battery is below 40%, and never when it's connected to a charger. Have tried Factory reset and pulling the battery out for an hour, but nothing have helped...
Skullb ( 2014-01-10 12:11:12 +0300 )edit
I have now used my Jolla soon one week without this "random shutdown". I fixed it by removing the battery for one hour and removing that nfc bug fixing tinfoil... I'll just wait for an official fix for that.
goldenm ( 2014-01-10 20:56:01 +0300 )edit
It seems to be a power problem. I had a shutdown yesrerday when taking a photo. I powred the phone up again and it shut down again when taking the photo. I was able then to take a few photos. The battery showed 4% then; before this, it was around 50% (3 days w/o recharging but covered NFC chip). It seems that the phone draws too high current for the moment and shuts down due to a short-term undersupply. Maybe a techie can brighten this better.
SagaciousT ( 2014-01-12 18:39:01 +0300 )edit
An excessive short-term power draw might also explain random shutdowns in poor coverage, i.e. transmitting at a high power to find a base station. (It would also explain why the phone tends to shutdown in my pocket while driving, but not when in the dash stand, not surrounded by 2 tons of Ford.)
jsiren ( 2014-01-13 13:16:48 +0300 )edit
Which TOH are you using? Could it be a problem with the "first ones"?
Pascal Schmid ( 2014-01-16 01:03:25 +0300 )edit
@Pascal Schmid: Perhaps, but if I may add that although mine just shut down randomly for the first time a day after receiving the poppy red OH, I was using the standard white OH at the time it shut down.
martti ( 2014-01-16 22:50:59 +0300 )edit
Well I am also having problems. Just noticed that Timed, Lipstick and msyncd are hogging memory and processor power. Five random shutdowns in about a months time. Lagging when and unresponcive when network connection is extablished after device wake up with double tap and power button press.
These processes take the power lately: https://picasaweb.google.com/115946291292582430648/Bugs#5969821714947901810
Anyhow hope you guys can triage these bugs.
miqu ( 2014-01-17 15:07:57 +0300 )edit
(also - but I'm unsure whether this is related, but I figured I should mention it:
1/3 to 1/2 of the times when I do swipe-down-to-turn-off-screen, my Jolla
1) turns screen off
2) waits for less than a second
3) turns screen on again (showing Lock screen)
I then swipe-down-to-turn-off-screen again, and the screen turns off.)
edit: Slightly over an hour ago, my Jolla stated 4% left on battery. I shut it down, took out the battery + SIM + microSD, thought I should wait 10', and then forgot it.
Just assembled it (sans microSD, as it's empty) and turned it on, and it now shows 49%. Strange.
phle ( 2014-01-17 18:53:14 +0300 )edit
Yesterday my Jolla shut itself at least 4 times even though battery was supposed to be at over 60%. It often displayed the "connect usb cable to device" indicator, that you get when you connect it to charger when the device is powered down. Also, it didn't boot up (or stay up) without a charger.
Julle ( 2014-01-18 12:05:50 +0300 )edit
This has happened for me for few times too. I also suspect some problems with power. Jolla turned off, when I tried to take a photo. I booted it, tried to take a photo again and it turned off again. The battery charge seems to be around 80%.
Maybe some spikes in power consumption makes Jolla believe, it's out op power and it turns off?
Pesasa ( 2014-01-18 12:37:48 +0300 )edit
Ok ... i got many shutdown, sometime 15 or more in a row !!!
So ... this happen randomly, sometime when it idle in pocket, sometime when trying to take photos, sometime during a call, sometime during internet session, while on wifi, or 3g, or just scrolling apps in launcher ... or doing nothing !
I ve reset the device, that didn't improve things ... giving log to stskeeps.
I clearly believe that s faulty hardware ...
Khertan ( 2014-01-20 18:39:06 +0300 )edit
This is happening to me too. Sometimes I take jolla out of my pocket and it is turned off. Today I was sending sms in a low 2G signal enviroment and phone shut down. I turned it back on, opened conversation app and it shut down again. I took the battery out and put it back in than I turned phone back on, opened conversation app and status of sms was sending. Sms was send but status of it remains sending. For now phone has not randomly shut down.
PG ( 2014-01-22 02:27:56 +0300 )edit
it happen to me too now, from 21.01.2014 version 1025 phone setting language=french + Warehouse app phone setting language=english, don't remember crash but without warehouse app
redge73 ( 2014-01-22 03:45:00 +0300 )edit
I've started experiencing this issue today 22 Jan 2014 starting from 16.00 (GMT+1) . In the last 1 hour and half my Jolla has shutdown 4 times without a specific interval, both on 2G and on 3G, full netwrok signal or weak signal, both during intense usage and when in standby after a double-tap. I turned on my Jolla Sunday 19 Jan and never shutdown since then; i put it in airplane mode and in silent mode every night; I put in silent mode every day from 9.00 to 18.00. I disabled tohd service almost 3 weeks ago, auto time update is on since first configuration. After last shutdown (17.36 GMT+1) I removed the battery for very few seconds and restarted it, not shudowns in the last 7 minutes.
SailfishOS Version 1.0.2.5
Patrizio Bruno ( 2014-01-22 18:46:10 +0300 )edit
3 shutdowns in the last 4 minutes:
1) while entering home, in a zone where cellular signal goes down 2) few seconds after I switched it on and it was connecting to the wifi 3 and 4) few seconds after I switched it on
It seems it can't stay on
Patrizio Bruno ( 2014-01-22 19:48:33 +0300 )edit
Looks like disabling automatic time updates helps to prolong the period with no shutdowns after last pulling the battery. My shortest interval from pulling the battery to the next shutdown was approx. 32 hours with time updates disabled, and about 1 hour with time updates enabled.
pycage ( 2014-01-23 20:00:21 +0300 )edit
I'm experiencing this as well. I've used my Jolla for about a month without an issue, then it began to shut down about like a week ago. It happened several times when I was underground without network coverage, and once when using Android Firefox, and yet once when I tried to make a backup.
paul7 ( 2014-01-25 11:27:51 +0300 )edit
1) I never used automatic time updates; 2) TOH service have beed disabled all the time; 3) I've had 1.0.2.5 since the end of December and everything was OK for several weeks. 4) In fact pretty much nothing had changed in software when my Jolla began to shut down.
paul7 ( 2014-01-25 11:31:16 +0300 )edit
I experienced those shutdowns. The only way to solve the issue is to remove the battery. I had the feeling the issue is linked to losses of mobile signal but I'm not sure of that. I'm also using automatic clock updates because accuracy of internal clock is bad.
ron282 ( 2014-01-28 09:08:23 +0300 )edit
How can I create logfiles of these crashes? AFAIK SailfishOS uses journald for logging, but it looks like the logs are not persistent, i.e. empty after each reboot or crash. Am I right? How can I persist these logs?
schmittlauch ( 2014-01-29 17:56:35 +0300 )edit
I am experiencing this as well. For extended periods of time and when the phone is plugged into the charger, it doesn't seem to restart. At home, where I have poor cell reception, it restarts sometimes - even during a phone call.
guaq ( 2014-02-02 10:45:24 +0300 )edit
Having much more random reboots sind 1.0.3.8. Some days 2 or more times. Last one just after pressing Send in Messaging app.
Happily after reboot the written message wasn't lost. Copied it and Send this time worked:-)
axaq ( 2014-02-12 15:18:01 +0300 )edit
I started experiencing these random reboots after upgrade to 1.0.3.8. They come in series of 5-10 in row. I enter PIN and lock codes and just start to open some applications and device reboots again. Sometimes it reboots right after entering the codes, without anything open. It is very annoying and looks to become epidemic in Jolla population. So far no statement from Jolla team, but I hope they are working on a hot fox for that.
zlatko ( 2014-02-12 20:14:42 +0300 )edit
I am noticing a cycle behaviour of the reboots of my Jolla - every 24 hours, at nearly the same time(18:15 EEST) I get a chain of 10-20 reboots. This is happening past 3 days. Today I stopped it by pulling out the battery. After reinserting it so far(30min) all looks OK.
zlatko ( 2014-02-13 18:56:14 +0300 )edit
Same problem here. Started to happen after the 1.0.3.8 update. Before that, my Jolla was rock-solid. After the update, it's become unusable. It just constantly reboots and rarely goes for more than a couple of minutes without rebooting.
It's definitely related to the network connection. In offline mode, no reboots. As soon as the network connection is enabled, the reboot cycle begins.
It's not wifi or 3G-specific. It reboots when either or both are enabled.
I can't reproduce the problem reliably. Most of the time, the phone will reboot 30 seconds or a minute after having booted and gone past the lock screen, either on its own or whenever I try to use the data connection in some way (e.g. loading a page in the built-in Web browser or launching the native Whatsapp app).
Occasionally however, it will run for a good 10 or even 15 minutes (whoo hoo!) before rebooting and it will even let me stream music with the Rdio Android app for a little while. But that's very rare - I manage to get it going for that long maybe once a day at most.
Overall, completely unusable :(
MehdiMe ( 2014-02-14 13:44:59 +0300 )edit
I'm not sure whether it's related, but for what it's worth: when I rebooted my Jolla after it had turned off for the second time in an hour this morning, the first thing I saw was a message at the top of the screen saying "Device is getting hot. Close all apps now." (or something like that, not sure what it said exactly). I had no apps running (just switched it on) and it didn't feel particularly hot, though.
martti ( 2014-02-19 21:48:35 +0300 )edit
For me device sometimes shuts itself down(you have use power key to turn it ON), sometimes it gets into reboot loop(turns OFF=>turns ON=>asks for PIN=>starts UI=>and after small period turns OFF again) and sometimes I got a random mixture of the other 2 cases. For me these symptoms have common root/cause(I might be wrong!). Shall the original question be re-worded or the community thinks we need 2 separate threads about "random shutdowns" and "random reboots"?
zlatko ( 2014-02-25 14:48:52 +0300 )edit
(just adding "for reference")
Lately, I'm experiencing "shutdown - reboot - enter PIN" for no apparent reason - the only common factor seems to be "uptime at least 2-3 days" (which I noticed when it happened when my uptime was 5-days-and-some-hours; and it occurs more often if I don't take out the battery, wait 10 minutes, and then put back the battery and boot-up).
This morning, I - for the first time - had a "shutdown, won't auto-reboot". That was odd, as I "expected" it to reboot by itself, and ... it didn't.
For now, I'm just "living with it", hoping it will be fixed with the 1.0.4.(something) update mentioned in Ygriega's "answer" below (also mentioned in the question-edit "Update (2014-02-14)" above).
phle ( 2014-02-27 18:52:04 +0300 )edit
I had some not so random reboots recently. Phone did stay on while waiting for SIM PIN to be entered but after entering the pin phone rebooted almost instantly. If I didn't activate the sim then the phone didn't crash.
So I took the sim out and brushed it against a table. After that the phone didn't crash anymore and has been working since, four days now. So can't tell if massaging the sim helped or just taking the battery out while doing that.
This palace where I was had quite poor reception.
hetas ( 2014-03-03 20:52:34 +0300 )edit
Another observation that might help - when my device enters a reboot loop, in most cases(like 9 out of 10) just prying open the TOH slightly makes the phone boot and work afterwards. I am starting to wonder if part of the problem is not HW related?
zlatko ( 2014-03-05 08:38:11 +0300 )edit
Adding that while my Jolla seems to be randomly shut down, it gets worse while roaming. I had it crash at least twice on me as I was trying to send SMS while roaming (sending SMS in home network didnt cause the same thing). There are other occasions when it shut down during roaming as well but for there were no clear pattern with what I may have done to cause the shutdown.
Henkka ( 2014-03-05 23:00:39 +0300 )edit
I haven't experienced the random shutdown issue but on three separate occasions the phone has acted weird, up to the point of having to remove the battery in order to fix it and each time the phone has completely scrambled my app order. Now I'm not even trying to organize them to my liking until the underlying issue (whatever it may be) is fixed. Also, when that has happened, apps have typically thought they are being launched for the first time despite e.g. saved games still being there.
typo ( 2014-03-07 18:51:10 +0300 )edit
my Jolla shuts down as well, today it gone loop jolla-logo => black screen => jolla-logo
plugging to charger started phone normally, battery level was about 60%.
my Jolla shut down couple times of week, hope that next update helps with that problem.
Sami ( 2014-03-09 00:39:18 +0300 )edit
Since 3 days I'm facing this problem as well. Phone has latest update. The problem started using the phone app, but later occurred as well using the msg app. My battery level was about 50% and up to 90% while it happened. Using the phone without radio's enabled (like I do now with the Jolla and using my beloved N9 as main mobile) hasn't produced any random shutdown till now.
Hope the update will address this problem.
Vieno ( 2014-03-14 13:57:51 +0300 )edit
I did happen to me a few times before, but after the update yesterday (1.0.4.20) it happened twice. The first time I described it here https://together.jolla.com/question/33919/battery-level-bug/. Today after the shutdown I wasn't able to restart the phone at all. I pulled out the battery for a while and after that the phone could be restarted.
Neo ( 2014-03-18 22:47:57 +0300 )edit

Answer 1

0

answered 2015-10-03 22:51:15 +0300

NuklearFart

1556 ●27 ●48 ●49

I had 4 restarts today, had several restarts a few days ago, did all erasing /pin tricks listed here but after today i'm really depressed. it rebooted 2 times when i got a call ans once during a call. the firsr reboot was this mornig and i had 6 apps running during night but flight mode enabled. i need a working phone!

all problems started after some update, think around 1.1.4 and never went well again

edit flag offensive delete publish link

Comments

Clean the battery contacts properly.

Go to an electronics shop and buy a contact cleaner. Spray on a q tip and clean both the battery pins and contact pins. Wait a few minutes and put the battery back in the phone.

ApB ( 2015-10-03 23:34:43 +0300 )edit

Answer 2

0

answered 2016-05-10 14:07:30 +0300

patjolla
15 ●3 ●3 ●8

I had a same problem and i fixed by putting the paper next to battery. Hopefully works! :)

edit flag offensive delete publish link

Answer 3

0

answered 2018-09-12 09:49:58 +0300

thesix
470 ●21 ●26 ●36

Good day to all,

Just two days ago one of our Jolla 1 devices started showing random reboots out of the blue. Mostly it happens while typing longer text messages (by longer I mean 80+ characters), but sometimes also while making a call. Up to then it has been in constant use without any problems at all.

The above mentioned method (take out battery, push pins etc.) did not fix it! That's why I am reopening this issue.

The device runs the current version of Sailfish OS (2.2.0.29). Battery Log shows the battery at ~200mA, 3990 mWh, 3815 mV and asserts a status of good.

I don't know how many people out there are still using the Jolla 1, but since the device was made to last it would be really nice to know why this is happening and even nicer to have a fix for the problem.

Cheers, j.

edit flag offensive delete publish link

Comments

@thesix: Consider contacting Jolla customer support at https://jolla.zendesk.com/hc/en-us/requests/new .

jovirkku ( 2018-09-13 11:56:53 +0300 )edit

Helpdesk is working on it. The suggested upgrade to 2.2.1 did not help :(

thesix ( 2018-09-15 18:13:28 +0300 )edit

1

Now we know the cause of the problem. After exchanging some messages with help desk (sending logs) I got the final answer:

Thanks for the message and log file. It seems that the device is rebooting because of btrfs. Unfortunately we don't fix btrfs related issues. Re-flashing or factory reset might help in this case.

Indeed the following can be found in last_kmesg

kernel BUG at fs/btrfs/extent-tree.c:5155!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
(...)
Kernel panic - not syncing: Fatal exception
FCPU1: stopping

I'll open a new question for this one.

Cheers, j.

thesix ( 2018-10-10 10:47:05 +0300 )edit

Answer 4

-2

answered 2014-01-21 22:50:50 +0300

ThomasF
1 ●3 ●4 ●5

Not a real solution, but it works for me.. reset the phone and do not update to the latest Software, i have not seen a singe shutdown for 4 days now.

edit flag offensive delete publish link

Comments

This could be evidence for being a bug introduced with 1.0.2.5.

pycage ( 2014-01-23 12:27:59 +0300 )edit

I also had shut downs only with 1.0.2.5, but I did not reset the phone and had no shutdowns for more than a week now with 1.0.2.5. It seems to be VERY random. I still think, it's a problem of excessive power drain.

SagaciousT ( 2014-01-23 12:50:02 +0300 )edit

2

I found a post on a Finish forum where someone tried resetting the phone, and keeping version 1.0.0.5. According to him, the phone shuts down regardless of the os version installed. Source: http://foorumi.jollasuomi.fi/index.php/topic,240.msg2345.html#msg2345

plipp ( 2014-01-23 12:55:09 +0300 )edit

I haven't found any evidence yet for a power drain relation. In this case I'd expect the Jolla at least to flash a short low battery warning before dying. It dies with >90% of battery, too.

pycage ( 2014-01-23 20:02:43 +0300 )edit

2

I had a low battery warning one or two times while the battery was still at 60+%. Another day, I had a few shutdowns with about 50% battery and 4% directly after the shutdowns. I was trying to make a photo and the phone shut down twice before I was able to make the photos. I had a longer talk on the phone 20 minutes before this.

SagaciousT ( 2014-01-23 20:27:19 +0300 )edit

Answer 5

-3

answered 2014-01-21 21:47:52 +0300

fAzu
1 ●1 ●2

updated 2014-01-22 01:04:50 +0300

So I'm collecting here suggested answers/fixes so that we can start commenting on these and see whether or not they actually work. There are currently a lot of plausible causes for this kind of behavior and there for probably a lot of different possibilities to fix it.

Symptoms: Phone shuts down randomly (without accidentally pressing power key) while virtually in any situation.

Plausible fixes (Not in any order):

Turn off automatic time updates
After shutting down, remove battery temporarely for a significant time period (>10 seconds) and restart
Remove the factory installed protective cover for touch screen (No, I'm not kidding. Has worked for somebody)
Change the back cover you are currently using (mostly Jolla preorder customers)
Try working without the back cover (Not recommended because the phone is left unprotected) OR disable the NFC reader using terminal
Do a complete factory reset (NOT GUARANTEED TO WORK)

As said these are suggested answers/fixes. It might well be that none of these will work for you. In any case, post a comment if they do/don't work or to suggest yet another fix for the symptom described in this post.

edit flag offensive delete publish link

Comments

3

I don't think one of the suggested answers helps. If you do one of these "solutions" and your phone doesn't shut down for a while, it's only a coincidence without a dependence. I haven't changed anything and had no shut downs for more than a week. But they might come back one time. I still think it's a power drain problem.

SagaciousT ( 2014-01-23 11:40:02 +0300 )edit

1

Well doing mostly the battery removal and removing the protective plastic sheet last week my random shutdowns completely vanished. I don't want to try any of the other possible solutions yet, because I want to see if it's truly working now.

fAzu ( 2014-01-23 23:02:51 +0300 )edit

4

I put a piece of paper between the battery and the case+toh, made the batteryconnection firmer or something...not a single reboot or shuydown after that

Rouxinol ( 2014-03-19 08:44:27 +0300 )edit

I've tried the paper trick, the battery trick and now it's two weeks until my vacation :( Planning to buy a cheap Android phone as a vacation phone until this is fixed.

Wizah ( 2014-07-21 16:08:57 +0300 )edit

2

I'm starting to believe that this jolla phone, for 399 euros is not a developer device but an hardware in pre-alfa release... and WE are testers instead of customers... very very disapponted...

I can undestrand the OS bugs o improvement.. but EVERY CHINESE ANDROID DEVICE does not have these problems... ant its cost is 60 euros...

pizzulicchio ( 2014-08-22 00:46:43 +0300 )edit

Jolla randomly shuts down

Comments

75 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Jolla randomly shuts down

Comments

75 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions