What would be the best update practice/method to next SF version (i.e. March update)? [answered]

asked 2014-03-01 15:30:42 +0300

Kari

3106 ●83 ●115 ●122

updated 2014-07-31 14:10:33 +0300

jiit

2678 ●32 ●58 ●59

admin

As the next SF update for our Jollas is so called first official/commercial what would the best way to make the update?

Make the update normally by updating over SF 1.0.3.8?
Make the factory reset and start from scratch?

if one would make the factory reset what would the advisable actions to do before making the factory reset e.g. taking backup etc.?

Will there be new issues with lost 3rd party apps data like we had when updated to SF 1.0.3.8 like desribed in here => https://together.jolla.com/question/21842/howto-restore-lost-3rd-party-apps-settings-after-update-1038/

Is it still needed to do the actions indicated in the above mentioned post?

Edit: 18.03.2014/Kari March update SF 1.0.4.20 has arrived and on my Jolla it installed quite nicely on top of the SF1.0.3.8 without factory reset.

However I have experienced big problems after the update related to both Mobiledata and Wlan connection, but for those issues there will be new dedicated questions and this post will be now closed as outdated

Due to the additional update to the answer by @zlatko the closing tag will be also updated from Not relevant to Answered - Thanks for the update on the answer related to the Update best practise of the SF OS.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kari
close date 2014-03-19 11:43:31.015573

Comments

It's my fair belief that the guys at Jolla take into account that people can update from different versions. In any case, if you do a factory reset, you will lose the app data with it, so I'm not quite sure how that would be better?

Acce ( 2014-03-01 15:48:36 +0300 )edit

@Acce I remember to see posts complaining that removing applications during the beta phase had not been 100% perfect.

Idea of starting from really clean slate was coming from these small things we have all experienced.

I am not a developer nor linux user, but many of you have already done your own tweeks to your jollas and some of them has caused problems as well.

The last update was not 100% perfect from Jolla as many users lost their app data until the issue was found. However many users aren't skilled enough to make to changes under the hood and thus starting from scratch could one solution.

Kari ( 2014-03-01 16:20:15 +0300 )edit

I wouldn't recommend resetting your phone "just in case". Do it only if you're having serious problems with it. Just install the new update when it comes.

If you perform a factory reset, you'll have to download and install all system updates released this far, one by one. I mean if you have 1.0.1.10, you have to update to 1.0.2.5 before you can update to 1.0.3.8 – at least that's how the updates have worked this far.

In case you at some point need to do a factory reset, there's some info in this question on how you can backup your data and restore it to the resetted phone. But I'm hoping there will be an easier way to do that when the next update comes.

ssahla ( 2014-03-01 23:18:58 +0300 )edit

Until the update is available, users can only read tea leaves. If you want to be sure, just wait until sufficient users have updated and shared their experiences here on Together.

jgr ( 2014-03-02 00:45:45 +0300 )edit

Why would this update be any different than other OTAs that have arrived to the phone? There is never a need to factory reset a phone cause of update (unless explicitly asked for). This question should be closed for being too subjective or localized (or for not being really a question).

foss4ever ( 2014-03-02 05:17:35 +0300 )edit

answered 2014-03-01 17:45:51 +0300

zlatko

16489 ●109 ●150 ●142

updated 2014-03-19 08:03:49 +0300

@Kari The "data" loss you commenting is not an actual loss - all data is still there, just some paths are changed. So resetting or backing up will not change the situation. My humble opinion is that if reset is needed(or advisable) Jolla would communicate that with its users.

EDIT 18.03.2014:I would like to add some more info, quoting a notable sailor's(Robin Burchell) post from TMO: (http://talk.maemo.org/showpost.php?p=1417090&postcount=405)

*Q(bockersjv): Given that this is the first full release is anyone else planning to do a full reste before the release? I know that on both my N900 and N9 the device always seemed to run better after this. Question is do I do a full device reset before or after the update, or just not bother?

A(w00t): At least part of the reason for this was likely that standard development practices, at least while I was working on Harmattan, involved a lot of reflashing. Daily, or more often, depending on how often you were multitasking in some cases. I was pretty resistant to this, but especially earlier on, it was hard to avoid. Jolla on the other hand has been much more focused on getting upgrade paths working from the start. I reflashed my N950 a sum total of, I think 3 times, from when I started hacking on Sailfish in 2012 to when I retired it mid 2013. My Jolla devices have been a similar experience: I haven't often managed to get into a situation where I need a reflash, and when I have, it's generally been thanks to me doing something stupid not that I'd ever screw up my homescreen without USB rescue mode enabled, or anything..* This isn't to say that we're perfect, I'm sure we've made mistakes, but just that at least for a number of us, updating is a core part of how we work - not reflashing - and if the upgrade experience isn't smooth, we'd like to know why.* "*

Comments

@zlatko yes you are right as the last update created new folder path for app data and the old data was and still is in the old folder.

As said for really rookie on linux creating script and moving old data to new location would have been too diffucult as you are not able to find hidden folders with apps like file browser or cargo dock.

With my question I was hoping to get comment/answer from Jolla staff member, but will see...

Kari ( 2014-03-01 19:14:10 +0300 )edit

Resetting the device because of an update is just not an option. I can't believe anybody would even mention such an alternative. Unless that person has nothing else to do in his life but play around with his phone ;)

tapio.oling ( 2014-03-01 19:14:24 +0300 )edit

@tapio.oling I haven't used linux and thus don't know how well Linux updates works. But unfortunately many windows programs are mandatory to uninstall before installing the official release. Even the Windows OS RC versions are recommended to be removed before applying the released OS version.

I also would not like to update the Jolla phone starting from scratch, unless it is recommended by Jolla.

However as Jolla phone and SailfishOS have been build quite open for user isn't also one fundamental idea that Jolla phone users are playing with they Jolla phones. Otherwise one could buy e.g. an iPhone, which you can't play around too much - right?

Kari ( 2014-03-01 23:41:59 +0300 )edit

@Kari updates are less of an issue on Linux, when it is not a kernel related update you usually don't even need to reboot. And soon kernel patches will be possible to apply on-line as well thanks to SUSE and others. Regarding your other point just because Sailfish is somewhat open for hacking, users shouldn't be required to hacking it just to get it working, Sailfish devices are expected to work just as good or even better then closed systems.

fasza2mobile ( 2014-03-02 02:52:16 +0300 )edit

What would be the best update practice/method to next SF version (i.e. March update)? [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kari
close date 2014-03-19 11:43:31.015573

Comments

1 Answer

Comments

Question tools

Stats

Related questions

What would be the best update practice/method to next SF version (i.e. March update)? [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kari close date 2014-03-19 11:43:31.015573

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 Kari
close date 2014-03-19 11:43:31.015573