I’m new to SFOS (using an old OnePlus6 until August – batch 3), this might be a dumb question…
Is the Browser based on a more modern code base in SFOS 5.1?
(see e.g. Browser soon incompatible with SailfishOS forum)
1 Like
Same for me on a 10iii. Pressing Vol Up (or down?) and the power button simultaneously was required to reboot the phone.
First impression: it’s quick! Good job, y’all!
4 Likes
Doesn’t holding a power button for 5-10 seconds help? It should work as a HW poweroff AFAIK.
1 Like
Don’t worry. You’ll know when it’ll happen.
1 Like
No, but vol up and Power for 5 sec worked!
Cool thank you for your quick help!!!
6 Likes
Worked, thank you!!!
1 Like
Curiously enough it didn’t. Held it down for more than half a minute without anything happening. Same story with the other Vol-button pressed.
I’m glad I could help.
1 Like
P.s. Thanks. The Weather App works also… 
5 Likes
Yes, we would do that if we had the fix. But this is a bit difficult problem to fix properly.
How it currently works is that the package management layer reports how much more (or less) disk space will be used after the installation. That is calculated from installed packages - removed packages sizes (updated package is also an install of new version and removal of old version). For this update that number is a bit over 100MB, depending on what you have installed.
On top of that the update UI adds 500MB of safety buffer, which is currently a hard coded number. So currently the update UI would say that you need at least 600something MB of free disk space, and would not allow the installation if you have less.
But, in this case that is not enough, as some big packages require more during the installation. And that space requirement is not readily available from the package management system.
Just increasing the hard coded safety buffer number does not work, as the older devices like XA2 do not have enough disk space to accommodate the requirements of the newer devices like C2. And it would mean that installing even minor updates would ask for huge amounts of disk space.
Better option would be to pass the extra space requirement along with OS version and other update info from the server, that way we could set it per device and release. Currently looking into this as it is the relatively easy solution. Though it has also it’s drawbacks.
Best option probably would be to somehow calculate the size required during the installation from the to-be-installed packages, but it does not seem to be something as simple as just taking the size of the biggest package and calling it done. So this would require considerable amount of investigation.
Ultimate option would be to have read-only root and atomic updates so that we wouldn’t have to deal with any of this, but that’s completely out of scope for this issue 
21 Likes
Same issues on my upgrade, I guess even reading the upgrade notes and checking space did nothing.. still fell for this issue
Is this Update also available and meant to be “goog to go” for the Jolla Mind2? It does seem not to appear there.
@siucdude Which device and how much free space did you have?
excellent. this is what i want to see.
5 Likes
Good place to hint to “power + vol up”.
I needed this on an XA2.
PS: unplugged from charger (before reboot) and the notification led stayed white: does this hint for a crash?
2 Likes
It is now also available for Mind 2, there was a slight misconfiguration on the server side for that.
2 Likes
It showed I had 1.4 on Sony IV, I’m now trying on my older Sony II but first I have to update to 5.0.0.77 and now I have 1.3 on the II..
1.4GB should be more than enough on that device. In my testing Xperia 10 IV, with all the Jolla apps, AppSupport, and some other random things from store, updated fine with a bit over 900MB free space.
Can you describe what kind of things you had installed?
@Keto what is a right approach to get the 800MB free on an XA2. I have 699.7 available and based upon settings > storage I should delete all sailfish apps (164MB). Sailfish itself consumes 1.5G and deleting all my applications barely meets the requirement.
Perhaps one way around this would be to make the update download to /home/defaultuser/updates/ or /opt/updates/
During the update, files could then be extracted there too before being moved to their correct locations.
1 Like