[SOLVED] Random shutdowns with Sailfish X [answered]

Question

4

[SOLVED] Random shutdowns with Sailfish X [answered]

bug

asked 2017-11-09 12:32:09 +0200

Piece_Maker
231 ●5 ●7 ●10

updated 2017-12-07 02:51:59 +0200

Hi everyone,

I snagged an Xperia X a couple of weeks ago and flashed SailfishOS onto it. Since then I've noticed a frequent problem where the phone will completely shut down without warning, and sometimes it'll refuse to switch back on until I plug it in.

It doesn't seem to matter what apps are open at the time, except that it only seems to do it when the screen is blanked (It's never actually happened when I'm holding the phone and fiddling with it).

My usage isn't ridiculously heavy - I usually have IRC and music player open, and occasionally a web browser tab or two.

I did have LPM enabled by mcetool but I've disabled that (just in case!)

[EDIT - SOLVED] This issue was solved by returning the device and getting it repaired. Doesn't seem to be a Sailfish issue!

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-12-07 16:05:05.885369

Comments

1

i experience random shutdowns/lipstick restarts when in use, with Android/SFOS apps running, often when using Flipboard, the Browser or graphics heavy sites, probably due to running out of memory or CPU is my guess.

DarkTuring ( 2017-11-09 23:16:08 +0200 )edit

I do have Alien Dalvik set to start on boot, and don't disable it, but I rarely leave Android apps running for any length of time.

Piece_Maker ( 2017-11-10 01:48:36 +0200 )edit

i experience random shutdowns/lipstick restarts when in use, with Android/SFOS apps running, often when using Flipboard, the Browser or graphics heavy sites, probably due to running out of memory or CPU is my guess.
DarkTuring ( 2017-11-09 23:16:08 +0200 )edit
I do have Alien Dalvik set to start on boot, and don't disable it, but I rarely leave Android apps running for any length of time.
Piece_Maker ( 2017-11-10 01:48:36 +0200 )edit

Answer 1

11

answered 2017-11-09 12:55:06 +0200

spiiroin
13237 ●151 ●224 ●199

moderator

Check /var/log/systemboot.log file.

Every bootup and (orderly) shutdown is logged in there.

Look for abnormal shutdown reasons (like battery empty etc) and/or sequences where startup follows startup (which might indicate hw reset / total power loss without going through normal shutdown sequence).

edit flag offensive delete publish link

Comments

Hey that's a handy file, thanks!

I'm not sure what to make of the errors in here to be honest. I've dumped some of it into a pastebin, the rest are all basically the same as this, in various orders.

https://pastebin.com/QY8R3zQx

I'll keep my eye on it a bit more and see if I can narrow it down to a time when it happens - weirdly all day today it's behaved so I'm not sure what to think at the moment.

Piece_Maker ( 2017-11-10 01:48:05 +0200 )edit

@Piece_Maker: For example this slice from the paste:

20171107_220957 Startup:  Reason Unknown
20171107_220957 Received: dsme internal state USER
^ (assumed) normal bootup
20171107_233904 Received: reboot request from dsme
20171107_233904 Received: dsme internal state REBOOT
20171107_233908 Shutdown: SW reboot request
^ normal reboot, should be initiated by the used (journal would have more info)
20171107_233932 Startup:  Reason Unknown
20171107_233932 Received: dsme internal state USER
^ normal bootup as expected after a reboot
20171108_013905 Startup:  Reason Unknown
20171108_013905 Received: dsme internal state USER
^ startup "out of the blue" without going through shutdown/reboot

Couple of things that might cause something like this:

Voltage over battery terminals drops under some hw specific level (low battery + sudden usage spike)
System does not manage to sufficiently "feed" watchdog hw(s) (cpu time starvation, memory pressure)

How the system reacts (power off / reboot), how the situation is reported / detected, etc. varies from one device to another (but usually at least power up due to charger connect is reported so that it can be distinguished from other boot reasons).

spiiroin ( 2017-11-10 09:40:32 +0200 )edit

Here's one from today:

20171109_041137 Received: dsme internal state USER
20171110_151920 Received: battery  empty
20171110_151928 Received: dsme internal state SHUTDOWN
20171110_151932 Shutdown: Battery empty
20171110_151948 Startup:  androidboot.mode=charger  

20171110_151948 Received: dsme internal state ACTDEAD
20171110_172636 Received: dsme internal state SHUTDOWN
x-no-time-stamp Startup:  preinit ignored androidboot.mode=charger
20171110_151932 Startup:  androidboot.mode=charger  

20171110_151932 Received: dsme internal state USER

Seems to imply my battery died - this happened with the thing plugged in!

Edited for formatting

Piece_Maker ( 2017-11-10 20:50:49 +0200 )edit

[SOLVED] Random shutdowns with Sailfish X [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-12-07 16:05:05.885369

Comments

1 Answer

Comments

Question tools

Stats

Related questions

[SOLVED] Random shutdowns with Sailfish X [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel close date 2017-12-07 16:05:05.885369

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2017-12-07 16:05:05.885369