Revision history [back]

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 search droid-tools
[...]
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...

Any and all hints on how to improve either of the two annoyances are warmly appreciated.

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 search droid-tools
[...]
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.

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 search 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.

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.