Anybody else's update(s) get interrupted due to sloooow connection?

asked 2018-09-27 18:50:50 +0200

ossi1967 gravatar image

updated 2018-09-28 12:04:29 +0200

I updated my Xperia when 2.2.1 became available for early access. Download was slow as always but acceptable. (A little over 30 mins)

Now I have a few more devices to update, some of them need to go to 2.2.0 before. All of these updates - the download, that is - go incredibly slow. In fact, they fail after about 50%. It takes several hours to get there and then it stops completely. I need to re-start the device, re-start the OS update, wait another few hours... sometimes the download finishes on the second attempt, sometimes it freezes again and I need to try a third time.

As I said, the OS downloads have always been slow for me (much too slow for the size of it), but it was never that bad. It would be acceptable if I could just leave it overnight and wait patiently, but there's this damned timeout that causes the download to stop entirely.

What's going on here? Anyone else experiences this? Can't Jolla afford faster connections? Why do they have this timeout? There's a tablet in front of me that I started to update 2 days ago and it's currently still downloading. They can't be serious about this.

Edit: Seems I'm not all alone, see first sentence here:

edit retag flag offensive close delete



Are you referring to update via UI or Terminal as haven't experienced such delays with the latter?

aspergerguy ( 2018-09-27 21:56:33 +0200 )edit

For me, the updates take usually less than two hours on my Aqua Fish. I use 4G connection to update the phone and I can tell you we do not have the best speeds here in India. On my other SIM, connections drops sometimes and I have to restart update (version --dup) again and again. So, I suggest trying a different internet connection as your ISP might be having network congestion or it might not have good connectivity with Jolla servers.

addydon ( 2018-09-28 02:34:00 +0200 )edit

@aspergerguy I always update via GUI. That's the one official way to update that I expect to work, that I expect to be tested by Jolla, that end users are supposed to use.

There was one single exception recently (also with 2.2.1) when for the first time in my life as a Jolla user, an updated failed completely and the device wouldn't boot properly afterwards. I used the update via terminal then because the GUI wasnt available... but that was before those download problems started, so I cannot compare the results in terms of download speed. :(

ossi1967 ( 2018-09-28 11:16:18 +0200 )edit

@addydon It's hard to simply switch from wifi to mobile internet on the tablet. :) Also, my mobile provider is also my landline provider. Same backbone infrastructure. I'll try to switch next time I experience such a problem just to see if it makes any difference...

Still, you tell me that a download of a relatively small OS update that shoul finish in no longer than 5-10mins took two hours for you on LTE and was interrupted (like mine) several times on a different network/SIM. And, while I use the GUI to update, you use the terminal, so that doesn't seem to make much of a difference.

Maybe there is a problem with either the Jolla servers or with the routing to them. (I'm only a bit surprised that these issues surface quite a while after the release of a new OS. I'd have expected network issues on the first day when everybody updates...)

ossi1967 ( 2018-09-28 11:22:31 +0200 )edit

@ossi1967 I can confirm, same happened to me with the 2.2.1 update, bricked my Jolla1. After the recovery, I noticed that all previous updates came in quickly, only the 2.2.1 was always stuck in download forever. Personally, I think it is better that way; Jolla should pull the update; seeing too many failures with this update. Jolla please focus on SFOS 3, this is your future, please don't mess with with a working OS!

tomorrow ( 2018-09-29 11:24:41 +0200 )edit