2.2.0.29 after update annoyances
asked 2018-06-06 13:27:20 +0300
In general the update to my J1 went okay, (I used the ssu re XX && version --dup way) but the following small annoyances still remain:
First Annoyance: perstistant, incorrect upgrade notification
- I am getting a persistant "system update available" message, which wants me to install 2.1.4.14
- In Settings - Sailfish OS updates, I can download an "update" to 2.1.4.14. Trying to install this fails, and the device reboots into 2.2.0.29 again
I have hat this problem earlier as well, while on 2.1.4 it always notified me of a 2.0.x version I could "upgrade" to. No real, permanent solution was found here on TJC.
Second Annoyance: droid-tools package
Looking at the CLI, I see the following:
[root@Sailfish nemo]# ssu s
Device registration status: not registered
Device model: Jolla (SbJ / JP-1301)
Device UID: XXXXXXXXXXXXXXXXXXX
Release: 2.2.0.29
Domain: sales
[root@Sailfish nemo]# cat /etc/os-release
NAME="Sailfish OS"
ID=sailfishos
VERSION="2.2.0.29 (Mouhijoki)"
VERSION_ID=2.2.0.29
PRETTY_NAME="Sailfish OS 2.2.0.29 (Mouhijoki)"
SAILFISH_BUILD=29
SAILFISH_FLAVOUR=release
HOME_URL="https://sailfishos.org/"
[root@Sailfish nemo]# version --verify
+ droid-tools-0.0.4-1.3.7.armv7hl
- droid-tools-0.0.4-10.2.2.jolla.armv7hl
One ore more packages are not at the expected version for Sailfish OS 2.2.0.29 (Mouhijoki)
(+ = expected version, - = installed version)
Okay so apparently the only thing missing it that droid-tools package. Let's try to get it:
[root@Sailfish nemo]# pkcon resolve droid-tools
Resolving
Querying
Installed droid-tools-0.0.4-10.2.2.jolla.armv7hl (installed) Some tools from android
Available droid-tools-0.0.4-1.3.7.armv7hl (adaptation0) Some tools from android
root@Sailfish nemo]# pkcon install droid-tools
[...]
The following packages have to be installed:
droid-tools-0.0.4-10.2.2.jolla.armv7hl Some tools from android
Proceed with changes? [N/y] y
Installing
Starting
Refreshing software list
Querying
Resolving dependencies
Downloading packages
Installing packages
Finished
So it does install the wrong version, also issuing the same pkcon install again results in exactly the same behaviour, as is the package was NOT installed. I have not found an invocation for pkcon which causes it to install the droid-tools-0.0.4-1.3.7.armv7hl package instead...
My repos are these:
[root@Sailfish nemo]# ssu lr
Enabled repositories (global):
- adaptation0 ... https://store-repository.jolla.com/releases/2.2.0.29/jolla-hw/adaptation-qualcomm-sbj/armv7hl/
- aliendalvik ... https://store-repository.jolla.com/releases/2.2.0.29/aliendalvik/SbJ/
- apps ... https://releases.jolla.com/jolla-apps/2.2.0.29/armv7hl/
- customer-jolla ... https://store-repository.jolla.com/features/2.2.0.29/customers/jolla/armv7hl/
- eas ... https://store-repository.jolla.com/features/2.2.0.29/eas/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/2.2.0.29/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/2.2.0.29/jolla/armv7hl/
- xt9 ... https://store-repository.jolla.com/features/2.2.0.29/xt9/armv7hl/
Enabled repositories (user):
- mer-tools ... https://releases.jolla.com/releases/2.2.0.29/mer-tools/builds/armv7hl/packages/
[ ... and a myriad of openrepos repos come here ...]
Any and all hints on how to improve either of the two annoyances are warmly appreciated.
Don't forget pkcon refresh.
nthn ( 2018-06-06 14:42:08 +0300 )Yeah, did that, but it doesn't change the behaviour.
nephros ( 2018-06-06 16:18:01 +0300 )I just checked, and it turns out droid-tools is also on -10.2.2 instead of -1.3.7 on my Jolla 1.
nthn ( 2018-06-06 17:11:03 +0300 )I had these persistent incorrect update notifications with 2.1.4 after normal update, not CLI (J-C), and the update before that, and before that. I tried all sorts of things to get rid of them and none worked. So I turned off EA. I wonder if it'll still happen when I get 2.2?
Edited to add: got the update. After update and reboot the notification persisted, tapping it told me I was up to date but didn't remove it. But this morning - phone off overnight - it's gone. So not perfect, but much better.
DaveRo ( 2018-06-07 09:24:12 +0300 )@nephros and @DaveRo: if it happens again and the notification doesn't want to go away, you can manually remove it by deleting the file
nthn ( 2018-06-10 16:28:54 +0300 )/home/nemo/.cache/store-client, then checking for updates again.