Unintended reboots release 1.0.4.20 [answered]

bug
reboot

asked 2014-03-18 22:58:56 +0300

Aequanix
2165 ●26 ●36 ●38

updated 2014-03-21 18:47:00 +0300

Just had my first one after 1 day uptime. Phone showed charging screen while in shirt pocket and definetly not being connected to charger. Then white Led flickering and reboot. Far better than with 1.0.3.8 but still unsatisfactory. How can we help finding the root cause?

edit: 2nd reboot after slightly more than on hour uptime.

edit: 3rd reboot ~ 20h uptime

edit: today uncounted reboots in a chain. Sometimes reboot happend just after jolla logo during boot. In other cases I was able to enter PIN and launch firefox before reboot.

edit: reboot loop resulted in phone beeing unable to boot. Green LED flashing. Factory reset. Upgrading to 1.0.4 via 1.0.2. Only installed minimum apps (Jolla apps, Cargo Dock, Firefox, BeyondPod, vlc, K9-Mail and Droid48). No openrepos or such things. Lets see if that helps.

edit: shutdown after 10h uptime. Screen just went black.

edit: within 20 minutes 3 consecutive shutdowns. Battery removal needed 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 Aequanix
close date 2014-05-21 14:57:45.153943

Comments

Mine Jolla got into a reboot loop by opening Mitakuuluu. But at least I am able to use my data connection while traveling now. :)

Alex ( 2014-03-19 02:24:56 +0300 )edit

Mine was on the charger with mobile data and bluetooth enabled (since wlan and bt is a no no). When I woke up it showed the charging icon and I had to boot it myself. The Jolla had troubles with mobile data in my bedroom before 1.0.4.20, so maybe this issue isn't completely fixed. edit: just rebooted again while watching youtube over wlan(mobile data and bt disabled)

staticint ( 2014-03-19 05:35:17 +0300 )edit

I already experienced 2 reboot loops since the update. The first one happened when I was manually switching connexions between wifi and mobile data. It's not clear how the second one happened.

As usual for me, this ended when I lifted the back cover.

Jordi ( 2014-03-19 08:36:29 +0300 )edit

Had my first involuntary spontaneous shut-downs today, since upgrading to 1.0.4.20.

First one was when I swiped down to close an app (Jolla Store). Restarted device.
Second one was a few minutes later. Can't remember what I did then. Restarted device (again), entered PIN-code (again), let it be for a short period, and then shut it down, took off The Other Half, took the battery out, waited 10+ minutes, put battery back, powered it on, entered PIN-code, and then things worked again.

Was on mobile network / data connection. Had (my own, separate) WLAN nearby, but Jolla neither connected nor enabled for WLAN connection. No 3rd party SailfishOS apps, but a few Android apps (.apk bluetooth-transfered from Android device, or installed using F-Droid).

phle ( 2014-03-20 22:27:30 +0300 )edit

The update hasn't really helped at all - my Jolla is doing random shutdowns and reboots equally often as before the update. Taking battery out for 10 minutes (as officially suggested) has helped nothing and the cause of the shutdown/reboot seems to be random. So far experienced reboot/shutdown when:

peeking in poor network conditions (2G, poor wifi)
zooming in on a webpage
swiping away the keyboard
holding shift down while typing
opening email app
opening clock app or editing an alarm
typing in a URL in browser
plus a dozen other cases

ziller ( 2014-03-20 23:56:51 +0300 )edit

ive had the same problem, finally removing my jolla account from the device did it for me. I came to that idea because running the device without my second hand Snow white TOH ( which is registered with account from first owner) did the trick for me too

juwelenjupp ( 2014-03-21 19:26:48 +0300 )edit

Half an hour ago: phone reported an empty battery, after reboot it said 45%. I was traveling and had a weak connection.

Just now: was reading an email (ironically from this together thread) in the middle of my house, until unexpected reboot. Was still on mobile data from traveling. Had to remove battery.

staticint ( 2014-03-21 19:50:32 +0300 )edit

@Aequanix - Hm. Just to be clear, in your last question-edit, you mention taking the battery out, which you have not mentioned earlier. Is this the first time you've taken the battery out after any unintended-reboot-with-1.0.4.20? I mean, considering it's mentioned under "Known issues" in the "[Release Notes] Software version 1.0.4.20, Ohijärvi"

If you experience continued shutdown or full device reboot issues with the device after this update, turn off the device, take out the battery for 10 minutes and put it back in. If the problems persist, please contact Jolla Care at care@jolla.com.

What I mean is, that I'm impressed that your Jolla doesn't reboot/shutdown more often, if you haven't taken the battery +10minutes out inbetween.

phle ( 2014-03-22 09:25:29 +0300 )edit

Of course I tried to remove battery before resetting the device to factory default. I've experienced a lot of reboots from version 1.0.3.8 onwards. Removing the battery helped whenever there were multiple reboots in a row. However if the device survived more than let say two minutes use after the reboot there was no difference in mean time before failure if you removed the battery or not.

Aequanix ( 2014-03-24 21:32:49 +0300 )edit

First I thougt, the accu was empty. Phone did not reboot and it is not possible to turn it on. I had to remove accu to get it on again. Maybe it is the already described problem with accu connection problem due to tolerance of TOH. But that it appears in same day as 1.0.4.20, has to be a very strange hazard.

SaimenSays ( 2014-03-24 23:10:18 +0300 )edit

I had no reboots whatsoever. None. Everything is pretty stable. What am I doing wrong? :-)

k79 ( 2014-03-25 08:55:34 +0300 )edit

answered 2014-04-20 17:59:02 +0300

Aequanix
2165 ●26 ●36 ●38

updated 2014-05-20 10:13:11 +0300

Had device sent in. Returend after about 1 1/2 weeks. Reciept says: Battery changed, software update. So let's wait and see.

edit: no improvement. Will reopen ticket @care.

edit: device exchanged. Problem gone. Seems it was a hardware issue. Was hard to believe for me.

edit flag offensive delete publish link

Comments

I am no expert on circuitry, but this comment on the PiPhone (raspberry pi DIY mobile phone) caught my eye: "power consumption from the modem is generally low, but it can spike for a short time to even around 2A, for instance when connecting to BTS with very weak signal." (by "dos") http://www.davidhunt.ie/piphone-a-raspberry-pi-based-smartphone/#comment-98706

I have noticed that the lockup/reboot sometimes occurs when the vibrator runs (haptic feedback). Coincidence?

martinrusler ( 2014-04-28 22:29:27 +0300 )edit

Phone gets pretty hot in bad network situations too. Already had some overtemp warnings. There is one situation where I will get this reboot problem for sure: In the communter train during the ride through an underground section. There network connetion is very unstable - and the phone will crash for sure.

Aequanix ( 2014-04-28 23:39:09 +0300 )edit

My reboot/shutdown problem was solved by puttin a piece of paper between the battery and the case+toh. I had tried everything else people suggested except full reset.

Rouxinol ( 2014-03-19 08:38:53 +0300 )edit

I am pretty sure that this is not a contact problem. My major suspect is wwan wlan switching. Removing batteries for 5, 10, 15 minutes sounds more like black magic than information technology. But will give it a try.

Aequanix ( 2014-03-19 08:54:29 +0300 )edit

Don't know what magic (or software/hardware problem) it is, but that piece of paper fixed my phone =)

Rouxinol ( 2014-03-19 09:02:33 +0300 )edit

sounds like you had a loose battery then @Rouxinol :)

droll ( 2014-03-20 08:53:57 +0300 )edit

From my experience that solves nothing and the problem will surface again after sometime has gone. I had 4 reboots yesterday so I decided to do a factory reset and since then I have had only one reboot, but that was with an older version when updating the phone so can't be sure wheter it is related to this or not. I also left the Android support uninstalled this time.

Painkiller ( 2014-03-20 09:37:54 +0300 )edit

Unintended reboots release 1.0.4.20 [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Aequanix
close date 2014-05-21 14:57:45.153943

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Unintended reboots release 1.0.4.20 [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Aequanix close date 2014-05-21 14:57:45.153943

Comments

2 Answers

Comments

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 Aequanix
close date 2014-05-21 14:57:45.153943