Ask / Submit

how to be sure that update to will be smooth? [answered]

asked 2015-05-06 10:22:08 +0300 gravatar image

updated 2015-05-06 13:46:53 +0300

eric gravatar image

Hi, I use the phone as daily phone and I can't afford to have a bricked device. I read many reports of bricked phones or phones with a blank screen (basically bricked unless one has to work out the magic using ssh), or phones running brtfs balance for more than 24 hours.

How can I be sure that the update will be smooth?

Here there are some threads for reference:

and also minor bugs:

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2015-05-07 17:14:47.760434


Mine failed (twice)...

Haven't had any others fail, and believe I had plenty of space and don't think (although didn't explicitly check) I had any fs balance issues...


ie, I'd wait a bit, or until you have some time to potentially fix things...

bruce_one ( 2015-05-06 11:06:19 +0300 )edit

How to be sure that tomorrow will come ! If you are afraid to live, just wonder why you have purchased a Jolla phone ?!?!

tvicol ( 2015-05-06 11:17:05 +0300 )edit

Have a backup, carefully check upgrade requirements, don't do in when you're in a hurry or have something important to do afterwards. But that's a general rule for non-trivial updates.

Blizzz ( 2015-05-06 11:26:32 +0300 )edit

I never had a problem with updates, however I try to keep the phone setup simple,

  • I do not have installed any android app, or
  • optimised the system with third party tools
  • media files are moved frequently to sd card so main storage use remains low <4GB
  • enabled development mode
  • I do install apps from openrepos
pmelas ( 2015-05-06 12:32:28 +0300 )edit

@tvicol I'm not afraid to live, thank you :) and risking bricking the only phone I currently have is a very different matter: it would be serious issue to me because I can't get in touch at all with people I need to communicate with. ( 2015-05-08 14:53:45 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2015-05-06 11:35:03 +0300

juiceme gravatar image

There's no way to be sure of anything, remember that Apple released an update to iOS that bricked half the devices attempting OTA update before they realised it and pulled the update...

The Jolla update problems really have just one root cause; unbalanced BTRFS filesystem.

To be sure that your update goes smoothly you need to manually balance the FS before attemptinting to start the update. This thread gives info on how to do it-

edit flag offensive delete publish link more



+1 check the btrfs situation, make backups and after that trust Jolla to have tested the update process. Or, with some sarcasm: Go buy Samsung.

Jolly-Jo ( 2015-05-06 13:05:00 +0300 )edit

Yep, I haven't had problems with any updates following just two simple rules/steps: 1) disable any openrepos and 2) shut off and restart the phone before updating to ensure there's not any "harmful build-up" (BTRFS problems?) from having the phone running for several days, which causes sudden lock-ups and reboots...

ultraboy ( 2015-05-06 14:05:32 +0300 )edit

Agree with juiceme. My btrfs was full 13.75GB raw space used/ unbalanced, but filesystem only had 6gb used. I had to balance up to 40% to relocate 2 chunks, enough to have 2gb free, following instructions in the thread juiceme linked. I was already aware of btrfs issue from Christmas and had already balanced btrfs once before. Once I did it again this week to free up raw space, the update worked fine first time.

richie ( 2015-05-06 14:18:01 +0300 )edit

I do not think it is enough just to disable openrepos. There is known problem with Phonehook app (it's mentioned in official release notes) so if you have it installed uninstall it first! It bricked my update also (early access) but fortunately I was able manage it through devel mode. And probably other applications which patching original SailFish OS files are also dangerous. Jolla have really good reason for they strict submit rules to official Store...

czdosi ( 2015-05-06 14:29:02 +0300 )edit

Agreed, disabling openrepos is probably not enough for those living on the edge - on a daily driver phone I just wouldn't install any potentially problematic experimental app so I don't worry too much. But for the adventurous who have installed software with clearly marked "danger/death/biohazard"-signs on them, of course there's more to do: enable developer mode, take backups before every update, maybe uninstall dangerous software, learn SSH, buy a spare phone...

ultraboy ( 2015-05-06 14:41:21 +0300 )edit

Question tools

1 follower


Asked: 2015-05-06 10:22:08 +0300

Seen: 443 times

Last updated: May 06 '15