We have moved to a new Sailfish OS Forum. Please start new discussions there.
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
2 | No.2 Revision |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
3 | retagged |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
4 | No.4 Revision |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem
MGConfItem.
gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
5 | No.5 Revision |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
6 | retagged |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
7 | No.7 Revision |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
8 | retagged |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
9 | retagged |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.
11 | retagged |
Release date : 9.6.2014
Download size : ~173MB
Saapunki is the combined software update (update6 + update7) for SailfishOS (refer to the post Next OS update in early June). It brings in many new and requested features for our dear users along with other improvements and bugfixes.
The software update will be first available to our dear users owning "The First one" covers. The rest of our user base will be able to update their devices on the same day, but a few hours later.
If you are unable to successfully configure the account, please visit account.jolla.com and try to reset your password.
If your device is running software version lower than 1.0.4.20 and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device. Else, you risk breaking the device. Read important-steps-to-do-before-updating and how-to-disable-openrepos-repositories posts for more information.
If your Jolla is connected to internet, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
Do not reboot the device while the OS update installation is in progress. The process takes up to 10 minutes. During the update, the device screen might blank out. You can awaken the display by a short press on the power key to monitor the progress. When the upgrade has completed successfully, you will see the LED light up red before the device restarts.
In rare circumstances, you may have to try a second time to get through the update successfully.
View detailed instructions at Zendesk.
We've been working for a while on updating connman ( the connection manager in SailfishOS) to a newer version. While it fixes connectivity issues in some environments, it comes at a regression risk in some networks. If you are interested in helping us out with testing, you can find more details in the hotfix-opt-in-hotfix-for-connectivity-in-upcoming-update-7 post.
GConf has now been replaced with DConf. If you are using MGConfItem from mlite or the declarative plugin (declarative plugin is not harbour-whitelisted) then no action is required. mlite MGConfItem has been patched to use DConf as the storage backend. The class MGConfItem name though misleading, has been retained in order to prevent API and ABI breakage.
All GConf data will be migrated from GConf to DConf during the first boot after the update. Schemas however will not be converted to anything.
If you use gconf directly then please consider moving to MGConfItem instead. If you cannot then please realize that DConf API is not stable at all and it can change and break your application. Please consider moving to MGConfItem. gconftool-2 is now gone also and /usr/bin/dconf is the replacement. However care should be taken not to run dconf as root.