We have moved to a new Sailfish OS Forum. Please start new discussions there.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015 - 1.1.9.28 - Early access release
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
For detailed changelog, visit [insert link].
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
2 | No.2 Revision |
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015 - 1.1.9.28 - Early access release
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
For detailed changelog, visit [insert link].
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
3 | No.3 Revision |
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015 - 1.1.9.28 - Early access release
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
For detailed changelog, visit [insert link].
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
4 | No.4 Revision |
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015 - 1.1.9.28 - Early access release
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
For detailed changelog, visit [insert link].
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
5 | No.5 Revision |
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015 - 1.1.9.28 - Early access release
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
6 | No.6 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the early access of 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
09.09.2015
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging. debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28 for our early access users.1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
7 | No.7 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should be enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.8 | No.8 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.9 | No.9 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.10 | No.10 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.11 | No.11 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.12 | retagged |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.13 | retagged |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.14 | No.14 Revision |
Update on 2015-09-24: 1.1.9.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
During this year, we've been working non-stop on iterating prototypes of UI concepts and testing out different possibilities to uplift the Sailfish OS user experience. We are finally ready to introduce the new UI and share the joy of using the reborn Sailfish OS 2.0 user experience with you. This release is especially dear to us as we have also reached the milestone of platform scalability to support multiple devices.
We are happy to announce the 1.1.9 release to our dear users. Thank you for your continued support and patience all through these months where the introduction of new features have taken a back seat.
The next OS upgrade will include further improvements to the Sailfish user experience, thus completing the transition to Sailfish OS 2.0. Here is a glimpse of the changes expected:
The main driver for the new UI changes has been to improve the existing functionality while easing the learning curve for new users. We hope this list of changes gives you an insight on the usability changes compared to the old UI framework.
Click here to view the detailed changelog.
As the issue update to 1.1.7 hang at 95 - 99% remains open, we've enabled persistent logs during software upgrade process in 1.1.7.28. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from the affected devices to assist the debugging (they are in /var/log/systemupdate.log
). To make this possible, we have forced the upgrade path to 1.1.9 through 1.1.7.28. Therefore, if your current OS version is 1.1.6 or earlier then your device will first get 1.1.7.28, and once installed it will get 1.1.9.28.
And now to the usual drill before attempting to upgrade your devices,
For detailed instructions on updating software, visit our support pages at Zendesk.
If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.
We have harmonized the system default tones and ambience tones to be global tone settings.
For example: Consider that you have two ambiences A and B. A has an action for replacing default chat tone and B doesn't.
SSLv3
is not supported anymore by default by Sailfish OS as it is insecure. Those customers having problems with the Exchange 2003-servers should enable TLSv1-protocol
support on their frontend Exchange-servers. More information in https://tools.ietf.org/html/rfc7568. Please contact your Exchange server admin.