We have moved to a new Sailfish OS Forum. Please start new discussions there.
0

Sailfish update 1.0.4.20 is not going to be downloaded [answered]

asked 2014-03-18 11:31:57 +0200

majuss gravatar image

updated 2014-07-25 14:03:41 +0200

jiit gravatar image

First of all I have to say, that I'm running my jolla device on sailfish 1.0.3.8 currently. I have experienced also this issue: https://together.jolla.com/question/5184/system-update-notifications-keep-re-appearing-although-update-already-installed/ First the workaround using the 'check for updates' function in the settings app has solved this, but recently it was no longer working, meaning: The update notification was always visible and in the setting app I was only able to 'start update'.

One time I have accidental chosen this, and so the jolla store has been opened. But the update itself was not going to be downloaded. The progress-bar in the store was simply stuck in the beginning for hours. So I rebooted the phone in order to 'free' the store from this unnecessary task.

Now 1.0.4.20 update is out. As I have had only the 1.0.3.8 notification visible, I rebooted again in order to have a correct notification about 1.0.4.20. This has worked. But when I try to update now, I have the same issue with the 'false' 1.3.0.8 update: The store is loading, it tries to download, but there is simply no progress for hours. No message or any notification either...

I have seen also that one has the opportunity to execute some helpful tasks manually via command-line. But therefore I have to enable the developer-mode - if I'm correct? Well, I tried it before, but it was also not working: There is a progress bar of bright lines which is moving from left to right. The lines are getting smaller, until they disappear one after another.. No further message or notification comes up. after waiting 30 minutes or so, I quit the settings app.

So, I'm quite confused what options do I have now to update to 1.0.4.20. Any useful hint for me?

Thanks in advance!

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by majuss
close date 2014-04-29 10:52:55.156603

2 Answers

Sort by » oldest newest most voted
0

answered 2014-03-18 12:00:28 +0200

rainisto gravatar image

https://together.jolla.com/question/14909/jolla-store-stubborn-update-notifications/ most likely your domain is not in sales or your jolla account is having problems. So most likely changing domain to sales and disabling possible openrepos should do the trick. (And the clock needs to be in correct time too). Worst case you need to factory reset and start updates from scratch.

edit flag offensive delete publish link more

Comments

Thanks for your answer. Can you specify what you mean with 'domain not in sales' or how can I check if something is wrong with my jolla account? As I never have activated the developer mode and only have installed basic jolla-apps (mail, docs, calendar etc...) + 4 android apps (one via manually downloaded apk and 3 via yandex store) I don't think I have enabled any openrepos, do I? I just checked the clock and saw, that automatic synchronization was disabled, so it was approximately 1 minute behind. Could this cause such issues?

majuss ( 2014-03-18 12:15:16 +0200 )edit
1

domain changes if you accidentally press SSU enabler button under developer menu (even if you cancel and uncheck it). If that has happened then you need to change domain back to sales. This forum has multiple posts howto do that.

Account checking, check that you remember your login/pass in https://account.jolla.com/ and delete & re-create jolla-account in device settings and see if that helps.

rainisto ( 2014-03-18 13:01:48 +0200 )edit
1

And other things to test is to use 3G vs WLAN (some AP's can give you bad nameservers which can prevent updates beeing downloaded).

rainisto ( 2014-03-18 13:03:48 +0200 )edit

Thanks! Will check all that in the evening and give some feedback here...

majuss ( 2014-03-18 13:07:06 +0200 )edit

My summary of yesterdays tests: I really didn't know what the term 'openrepos' would mean regarding the jolla device. I read a little bit about it: I never had any warehouse-app installed, nor I did activate the dev-mode (this didn't work, as I said in my original question). So I can't imagine how to activate any other repositories... The same is for the domain, which can only be changed via dev-mode. There was no chance I could have changed it.

majuss ( 2014-03-19 11:18:55 +0200 )edit
0

answered 2014-04-24 17:55:28 +0200

majuss gravatar image

Finally this has been individually solved via jolla zendesk case# 8740 (https://jolla.zendesk.com/hc/en-us/requests/8740). For all non-servicedesk-agents find the solution as follows:

  • A remote telnet connection to access the recovery console has been opened while the jolla device was in recovery mode and connected via USB to a PC as 'Remote NDIS Compatible Device' (Windows OS). One can retrieve a manual from jolla support how to establish such connection.
  • The rpm database has been be cleard first via the following commands:
cd /var/lib/rpm 
rm -f __db.00* 
rpm --rebuilddb
  • After that the device has been rebooted via recovery console
  • jolla now booted as usual and after checking for new updates the most recent update (Paarlampi) has been detected.
  • It has been switched to the store app successfully and the download of the update has been started...

  • The download has been interrupted again, after the progress-bar initially processed two pixels or similar

  • Afterwards it was realized that a device-lock code has been setup. Via settings-app the lock-code has been disabled.

  • After switching back to the store-app, the download was proceeding as originally expected. So the current assumption is a coincidence between a corrupt rpm-database and the usage of a device-lock code preventing the update from being downloaded.

Jolla support confirmed to me that they try to reproduce the issue and will implement a so called 'rpm-healing-automation' in the future. They will also look for possible bugs regarding the usage of device lock codes in that area.

edit flag offensive delete publish link more

Stats

Asked: 2014-03-18 11:31:57 +0200

Seen: 662 times

Last updated: Apr 24 '14