rm /home/nemo/.local/share/system/privileged/Notifications/notifications.db To fix notifications.
If still persist the issues on update the OS, uninstall thirdparty master package if has.

new feature on camera a fake 1600 iso

So, while removing all those unneeded account-extensions packages for sociald and jolla-settings, I stumbled upon this interesting package:

Edit: Just found out, this package exists since 2.0. Oh well.

I ran in the same problem as cy8aer (http://talk.maemo.org/showpost.php?p...90&postcount=8). I downloaded only a few minutes after the first problem with the download was solved and tried to install before the second problem was solved.
The installation started fine and the Xperia X got to the Progressbar of the update. There it stayed for >2 hours with no progress at all.
I then rebooted and the old system came up without a problem.
I then decided to try the "version --dup" way for the update.
This worked without problems and I rebooted in 2.2.0.29. The system seems to work without a problem.

My probem is that I still have the update notification.
When I check if there is an update I says my system is Up to date with 2.2.0.29 but the last time the check ran has the shows as bevore the update. Checking again runs in a timeout.
The journal shows the following:

May 31 21:47:41 Sailfish invoker[6103]: invoker: Invoking execution: '/usr/bin/store-client'

May 31 21:47:41 Sailfish [6101]: [D] unknown:0 - System update already in progress. Check request ignored.

...and later...

May 31 21:49:41 Sailfish [6101]: [D] unknown:0 - -- quiting, inactivity timer expired

May 31 21:49:41 Sailfish [6101]: [D] unknown:0 - telling PackageKit daemon to quit

May 31 21:49:41 Sailfish PackageKit[6115]: daemon quit

May 31 21:50:41 Sailfish estart[4296]: [D] unknown:0 - Update check timed out!

rebooting the device over a dozen time by now hasn't changed anything.
To me it looks as if some of the preperations for the update weren't cleaned up after the first update failed and the updater doesn't check anything because he believes to be in the middle of an update.

Does anybody know how to fix this?

Best Regards

Edit:

found a solution for my Problem here:
https://together.jolla.com/question/...#post-id-99219

I think I found a use case Jolla had not considered. Or maybe they had but don't care. Or don't know how to fix it.

In short, the "use WiFi only" setting for dowloading updates is honoured only at the start of the download. A download already in progress is not paused or interrupted when you leave the WiFi area and the network switches to expensive mobile data.

[tl;dr]
I started downloading the update at work, about 30 minutes before going home. Risky but I thought, what the hell. By home time, only about 200 out of 400 MB had been downloaded. I had to leave sharp to collect the kids and cannot dilly-dally, so I closed the Settings app, assuming that the download would be interrupted and I would either resume or start all over again at home. So you can imagine my surprise when I checked it at upon arriving home and found that the download had finished and my credit reduced by amount roughly equivalent to downloading 200 MB through mobile data.

As far as I know, I don't have thirdparty master packages...
I still can't update...
Tried via terminal:
pkcon refresh (same error about dalvik repo)
zypper ref (same error about dalvik repo)
ssu ur (show nothing)
pkcon repo-set-data jolla refresh-now true (no errors)

Don't know what to try else...

I have 3GB included in my data plan so for me it wouldn't have been a problem...but I always switch off mobile data if I don't need it, especially if I have to pay for it! Never trust what's running in background...
On my brother's Nokia 5800, one of the first days the A-Gps used mobile Internet without asking, stealing more than 10€...
Aaah, Symbian was a pain, with whatsapp I had to kill it several times with another app, since it was not possible to turn off mobile data, except of putting it to offline.

My First impressions, Xperia X:

• Update through command line went through beautifully, no stuck notification, no problems with previously updated webkit package.
• I like the gallery layout – the previous layout wasn't my cup of tea. Have not spend more than a few seconds there, though. Did not try camera.
• Boy, does the keyboard sound get on my nerves. Such a small thing, yet so irritating for me. EDIT: as has been pointed out: This is a OKBoard bug.
• Fingerprint unlock does not work great for me, though it could have something to do with my huge protective case. Also I was negatively suprised that you have to swipe from the lock screen before using it. I had hoped you wouldn't even have to press the power button – that would have been a nice substitute for double-tap-to-wake. Well. EDIT: You don't have to swipe, It was just not registering well for me! Still have to press Power, though.

In finland everybody has unlimited flat rate plans so it really does not matter whether one uses wlan or 4g.

I guess that's the reason for such slips in SFOS design

What did they do to the gallery? This is so bad. No longer touch friendly, several ways to achieve the same thing, ugly, ... Who on earth is responsible for this?

Also, what is this so called "Emoji-Keyboard" supposed to be? I would have expected something that's at least on par with the keyboard from Openrepos... but those are just a few smiling faces, nothing more. No dogs, no pizza, no beer... Who is going to use this instead of the existing Emoji Keyboard?