Random shutdown on Jolla running 1.0.8.21

Question

15

Random shutdown on Jolla running 1.0.8.21

asked 2014-10-13 20:13:15 +0300

copyninja
220 ●7 ●9 ●13

updated 2014-11-03 14:19:05 +0300

Hi,

I installed skype today from aptoide store but I was unable to login I'm not sure if the crash is related to this, but after installing using any android apps phone suddenly goes blank then charging symbol appears even though no charger is attached after a while screen shows some light and tapping on it brings up lock screen. This happened twice when I tried to use skype and once I was playing a game after installing skype.

Is there a way to know what is going wrong?. I'm using Sailfish OS 1.0.8.21 I recently brought this phone and don't want to screw it up :-). So any help appreciated.

Edit 1: Ok it doesn't seem to be related to android app it happened again when I'm using sailfish-browser, suddenly charging symbol appeared as appears in powered off jolla and the screen lighted up and lock screen appears after a while! I'm not even sure if its a crash or something else.

Edit 2: Ok further checking of journalctl I found some kernel trace with cut here instruction after this phone rebooted and possible register dumps. Not sure if this will be helpful but I'm just pasting it here.

Oct 14 09:09:49 Jolla kernel: ------------[ cut here ]------------
Oct 14 09:09:49 Jolla kernel: WARNING: at arch/arm/mach-msm/subsystem_restart.c:799 subsys_restart_init+0xec/0x14c()
Oct 14 09:09:49 Jolla kernel: Modules linked in:
Oct 14 09:09:49 Jolla kernel: [<c010cabc>] (unwind_backtrace+0x0/0x11c) from [<c01762b0>] (warn_slowpath_common+0x4c/0x64
)
Oct 14 09:09:49 Jolla kernel: [<c01762b0>] (warn_slowpath_common+0x4c/0x64) from [<c01762e0>] (warn_slowpath_null+0x18/0x
1c)
Oct 14 09:09:49 Jolla kernel: [<c01762e0>] (warn_slowpath_null+0x18/0x1c) from [<c0d0cb2c>] (subsys_restart_init+0xec/0x1
4c)
Oct 14 09:09:49 Jolla kernel: [<c0d0cb2c>] (subsys_restart_init+0xec/0x14c) from [<c01005ac>] (do_one_initcall+0x90/0x160
)
Oct 14 09:09:49 Jolla kernel: [<c01005ac>] (do_one_initcall+0x90/0x160) from [<c0d00a2c>] (kernel_init+0xf4/0x1b8)
Oct 14 09:09:49 Jolla kernel: [<c0d00a2c>] (kernel_init+0xf4/0x1b8) from [<c0106f2c>] (kernel_thread_exit+0x0/0x8)
Oct 14 09:09:49 Jolla kernel: ---[ end trace da227214a82491b7 ]---

And going down in the log I found some register dump again not sure if its helpful

                                  [I]<6><><bmm_wakeup><183>waking up the chip...
Oct 14 09:09:49 Jolla kernel: 
                              [I]<6><><bmm_wakeup><199>wake up result: succeed, tried times: 1
Oct 14 09:09:49 Jolla kernel: 
                              [I]<6><><bmm_probe><1076>register dump after waking up
Oct 14 09:09:49 Jolla kernel: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
Oct 14 09:09:49 Jolla kernel: 32 05 01 ff ff ff ff ff ff ff ff ff ff ff ff ff
                              ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                              ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                              ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Oct 14 09:09:49 Jolla kernel: 
                              [I]<6><><bmm_check_chip_id><140>read chip id result: 0x32
Oct 14 09:09:49 Jolla kernel: 
                              [N]<5><><bmm_probe><1081>Bosch Sensortec Device bmm050 detected
Oct 14 09:09:49 Jolla kernel: input: bmm050 as /devices/virtual/input/input8
Oct 14 09:09:49 Jolla kernel: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
Oct 14 09:09:49 Jolla kernel: 32 05 01 00 01 00 01 00 00 00 00 01 06 3f 07 00
                              00 04 0f ff 00 1f b3 42 00 90 56 63 84 00 00 00
                              28 31 00 00 1b 1b 11 00 da 02 ee 59 98 19 00 00
                              fd 1d ff ff ff ff ff ff ff ff ff ff ff ff ff ff

This started to happen after upgrade to 1.0.8.21, was there fix to kernel in that bug fix update? Any one please help :)

Edit 3: This trace might not be related to crash as I can see it every time I boot the phone so I'm really clueless why the charging symbol appears and jolla restarts. Is there anyway to find out what went wrong? I'm new to journalctl and unsure how to get more information.

Edit 4: I had several restarts within 10 minutes and I was baffled only thing I did was sitting in a car where sunlight was directly falling on me and my phone was inside my pocket started buzzing. I noticed its rebooting and it went for about 5-10 minutes after again digging through log found this

Oct 14 13:59:42 Jolla kernel: [BAT]## USB_ONLINE: 1 (plugin=1)
Oct 14 13:59:42 Jolla kernel: [BAT]battery_warm = 1
Oct 14 13:59:42 Jolla kernel: [BAT]vddmax  = 4250 mV
Oct 14 13:59:42 Jolla kernel: [BAT]r_sense finetune ibatmax = 1225 mA (origin = 1000)
Oct 14 13:59:42 Jolla kernel: [BAT]## SOC= 25( 25, 25),3368(3922),A=0669,T=571,On=1,0,(1),USB 000(100),vd=4250(0,1),ib=1000,0,F03,R02,W3B
Oct 14 13:59:42 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 718 > 68degC, device will be shutdown
Oct 14 13:59:42 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 718
Oct 14 13:59:42 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 491
Oct 14 13:59:42 Jolla kernel: [BAT]## SOC= 25( 25, 25),3489(3922),A=0750,T=491,On=1,0,(1),USB 000(100),vd=4250(0,1),ib=1000,0,F03,R02,W3B

Especially the line

Oct 14 13:59:42 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 718 > 68degC, device will be shutdown

So is battery heat which is causing reboots? I've seen battery heating during android games playing but never after. Also I never faced this issue with 1.0.8.19 this only started after recent security update. Did something broke in this?

Edit 5: So I used the cleaning contacts using pencil rubber and my phone was running for almost 4 weeks now, till yesterday when I reinstalled skype and used it unsuccessfully and guess what I had random 5-6 shutdowns. So this whole process started for me with skype installation and now its recurring again?.

edit retag flag offensive close delete

Comments

I've had the same thing happen to me on a couple of occasions. Never got to the bottom of it - but at least you are not alone.

strongm ( 2014-10-14 10:12:24 +0300 )edit

Ah! Thats bit re-assuring that I'm not alone :-). Hope some Jolla development guys look into this, I tried extracting previous boot log entry and with --since to see what exactly happened but no luck. Looks like journalctl lost those records. Next time it happens I will try journalctl with --since option giving time few minutes before the crash

copyninja ( 2014-10-14 10:21:08 +0300 )edit

1

This possibly is the same probelm which is mentioned here

copyninja ( 2014-10-14 11:53:02 +0300 )edit

I have no android but coming back from airoplane-mode that happened to me also two days ago.

lasse ( 2014-10-14 12:25:40 +0300 )edit

Is there anyway to approach official Jolla devs on this? It really seems to be problem faced by many

copyninja ( 2014-10-14 12:28:37 +0300 )edit

I've had the same thing happen to me on a couple of occasions. Never got to the bottom of it - but at least you are not alone.
strongm ( 2014-10-14 10:12:24 +0300 )edit
Ah! Thats bit re-assuring that I'm not alone :-). Hope some Jolla development guys look into this, I tried extracting previous boot log entry and with --since to see what exactly happened but no luck. Looks like journalctl lost those records. Next time it happens I will try journalctl with --since option giving time few minutes before the crash
copyninja ( 2014-10-14 10:21:08 +0300 )edit
This possibly is the same probelm which is mentioned here
copyninja ( 2014-10-14 11:53:02 +0300 )edit
I have no android but coming back from airoplane-mode that happened to me also two days ago.
lasse ( 2014-10-14 12:25:40 +0300 )edit
Is there anyway to approach official Jolla devs on this? It really seems to be problem faced by many
copyninja ( 2014-10-14 12:28:37 +0300 )edit

Answer 1

6

answered 2014-10-17 12:39:29 +0300

plipp

211 ●4 ●6 ●13

Just out of curiosity i made a graph of my battery temperature reading from the last couple of days. Shutdown means the log showed: get_prop_batt_temp: BATT_TEMP= * > 68degC, device will be shutdown. Warm means the log showed: [BAT]battery_warm = 1.

I also had a shutdown today around where the warm indicators are, but the log does not show the "device will be shutdown" entry for that one.

image description

edit flag offensive delete publish link

Comments

Interesting graph. Btw after using the rubber to clean the contacts on my phone and battery I didn't get the shutdown issue for about 2 weeks now!

copyninja ( 2014-10-24 20:46:47 +0300 )edit

1

I am having the very same problem, phone is shutting down all the time, several times per day.

I am seeing some clearly bogus temperature readings in the logs:

Dec 29 12:32:36 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 688 > 68degC, device will be shutdown
Dec 29 12:32:36 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 688
Dec 29 12:32:36 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 688 > 68degC, device will be shutdown
Dec 29 12:32:36 Jolla kernel: [BAT]## SOC= 61( 61, 61),3446(3612),A=0918,T=688,On=0,0,(0),Unknown 000(100),vd=4250(0,1),ib=1000,0,F03,R01,W00
Dec 29 12:32:36 Jolla kernel: [BAT] Internal R 1322 mOhm, I1:699240uA I2:918304uA V1:3649704uV V2:3360000uV
Dec 29 12:32:36 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 760 > 68degC, device will be shutdown
Dec 29 12:32:36 Jolla kernel: [TSL277X_P][Before] raw=113, status=0, far=500, near=847
Dec 29 12:32:36 Jolla kernel: [TSL277X_P][After] far=363, near=847, from=112, to=847
Dec 29 12:32:36 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 587

Also this kind of lines are present:

Dec 29 12:32:34 Jolla DSME[588]: thermal: Suspicious battery temperature change from 35 to 63 in 60s

Jukka L ( 2014-12-29 13:14:58 +0300 )edit

Using the paper trick for a long time now. Had only seldom crashes than. So it helps but is not the full solution. Last crash occurred some days after upgrade 10 in low network conditions in our office. As others noted it is maybe also related to low temperature on the way to my office. After a crash I normaly take out the battery and clean the contacts.

Next time i will also check the kernel log for this kind of problematic battery log lines.

axaq ( 2014-12-31 16:01:31 +0300 )edit

Just had my first crash half a day after New Year when pressing the Call button to call a contact ;-(

The phone was in LTE network with good signal level. For the call it needed to switch to 3G. The phone/battery was not cold or hot beeing home for a while.

Nothing in journal log because I didn't know that the journal log starts fresh after reboot. Now I switched it to persitent as found in this link and this link.

axaq ( 2015-01-01 16:08:03 +0300 )edit

Run again into several crashes/reboots some days later. Nothing special found in journal. But seems also to depend on

Network mode: Prefer 4G

and WiFi enabled without an available known WiFi network in my office. There is only low mobile 2G signal available and it gets instable.

axaq ( 2015-01-09 03:34:02 +0300 )edit

Answer 2

1

answered 2014-10-14 18:21:38 +0300

sada11
161 ●3 ●6 ●12

updated 2014-10-14 18:29:40 +0300

like @copyninja say: here is situation ... https://together.jolla.com/question/7144/jolla-randomly-shuts-down-10819/ that was just beginning for you :( sorry for say this, but many people had it before. I have 2 solutions for you and for others with same problem. 1st what I done is clean contact on the battery and on the device you can do it on many way (with WD40...etc). 2nd I stop to carry my phone inside pocket because Jolla hardware is so weak, so carry Jolla in pocket with all the bending and movement, to me may cause a reboots, because Jolla hardware is so unstable! :( After this no more reboots for me so far. I hope this will help !?

edit flag offensive delete publish link

Comments

Its sad that device design has flaws but I also suspect software bugs because when I saw 62 deg C battery temp phone was not at all heated but I don't know why software thought its that high amount of heat. Atleast I should feel the heat and it was fine as long as I was using 1.0.8.19 started with 21 but again as many people had similar problem before. For now I'm applying 1st using an eraser after that device didn't reboot for some 8 hrs now let me see how far this goes

copyninja ( 2014-10-14 19:40:52 +0300 )edit

Answer 3

1

answered 2014-10-15 09:25:04 +0300

plipp

211 ●4 ●6 ●13

I just had a reboot this morning, and i can confirm the above invalid battery reading bug:

okt 15 09:03:58 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 578
okt 15 09:03:58 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 777
okt 15 09:03:58 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 777 > 68degC, device will be shutdown
okt 15 09:03:58 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 616
okt 15 09:03:58 Jolla kernel: [BAT]get_prop_batt_temp, Temp = 710
okt 15 09:03:58 Jolla kernel: get_prop_batt_temp: BATT_TEMP= 710 > 68degC, device will be shutdown

Seems like a totally bogus reading that should be disregarded. Phone was not hot when this happened. I was looking through e-mail. If the reading is in celsius, then perhaps readings above the melting point of plastic should be disregarded, or something :).

edit flag offensive delete publish link

Comments

Yes it seems to be bogus reading because when that happened I was using browser and I didn't feel any heat. Other time also only sunlight was falling on my lap and phone was in pocket but phone was not at all heated. and when it says 68 deg C atleast we should feel the heat right :)

copyninja ( 2014-10-15 09:30:10 +0300 )edit

1

You would think so :). Just a guess, but the reading might be *10, so 777/10 = 77.7 degrees C. Looking through the log a bit more:

okt 15 09:03:00 Jolla kernel: [BAT]## SOC= 92( 92, 92),3987(4020),A=0000,T=250,On=0,0,(0),Unknown 000(000),vd=4350(0,0),ib=1000,0,F03,R00,W00
okt 15 09:03:00 Jolla kernel: [BAT]## SOC= 92( 92, 92),3844(4020),A=0367,T=353,On=0,0,(0),Unknown 000(000),vd=4350(0,0),ib=1000,0,F03,R00,W10
okt 15 09:03:48 Jolla kernel: [BAT]## SOC= 91( 91, 91),3647(3634),A=0831,T=466,On=0,0,(0),Unknown 000(000),vd=4250(0,1),ib=1000,0,F03,R00,W10
okt 15 09:03:58 Jolla kernel: [BAT]## SOC= 91( 91, 91),3129(3214),A=0749,T=616,On=0,0,(0),Unknown 000(000),vd=4250(0,1),ib=1000,0,F03,R00,W00
okt 15 09:03:58 Jolla kernel: [BAT]## SOC= 91( 91, 91),3148(3214),A=0865,T=777,On=0,0,(0),Unknown 000(000),vd=4250(0,1),ib=1000,0,F03,R00,W00
okt 15 09:03:58 Jolla kernel: [BAT]## SOC= 91( 91, 91),3467(3214),A=0905,T=578,On=0,0,(0),Unknown 000(000),vd=4250(0,1),ib=1000,0,F03,R00,W00

the T= seems to indicate the battery temperature reading.

plipp ( 2014-10-15 09:45:32 +0300 )edit

@plipp. Makes sense as the values in

cat /sys/class/power_supply/battery/temp
cat /sys/class/power_supply/battery/uevent | grep TEMP

have the same range (degrees * 10).

axaq ( 2014-12-31 16:03:40 +0300 )edit

Answer 4

0

answered 2014-10-23 04:51:55 +0300

alexduf
98 ●3 ●4 ●9

I have the same problem, it reboots around once a day, which makes the user experience terrible. I noticed it happens more often since I'm using Xabber from F-Droid. (Because, yes, native xmpp is also broken but that's another issue) My journalctl is full of reboots as well, I can dump it if necessary

I wonder if it is related to the android runtime.

edit flag offensive delete publish link

Comments

I don't think its related to android runtime, I first faced this when I installed skype and was playing Shadow Fight 2 android Game but later noticed this was unrelated it happened again couple of time without any warning or doing anything in the phone. Then I followed the cleaning the contacts using a pencil rubber and reboots have stopped for about 2 weeks now!. I would suggest you try the same

copyninja ( 2014-10-24 20:48:50 +0300 )edit

Random shutdown on Jolla running 1.0.8.21

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Random shutdown on Jolla running 1.0.8.21

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions