We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2013-12-27 14:26:11 +0200 |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them. There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
2 | No.2 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them. There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them. There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
4 | No.4 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them. There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
5 | No.5 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them. There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
6 | No.6 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
8 | No.8 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
9 | No.9 Revision |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
10 | retagged |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
11 | retagged |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.
13 | retagged |
If your Jolla is connected to WLAN network, an OS update notification should pop up shortly. If you just can't wait, you can manually trigger an OS update check as follows:
This version of the release notes includes update information that was not in the original notes. There was a communication failure during the holidays and not all relevant items related to hardware adaptation and user privacy were included. There was no intention to hide anything and the changes are mentioned in the RPM changelogs on device.
It was discovered that it was possible to access the data of a device even when locked with a device lock code. This could be done through the fastboot protocol of the device bootloader without OEM unlocking the device (making it obvious that a breach had been made) or entering device lock code. A change was made that closed this security hole.
The philosophy regarding security which we follow in Jolla is that we'd like to protect a user's data against attacks, be it physical attacks (somebody steals your device), application/malware or security exploits. Our focus is on user privacy.
If a factory reset cannot be performed or if the device has booting issues,
Note: it is still possible to break the Recovery mode in developer mode.
Some of the android apps are still unable to connect to mobile data network if the SIM PIN code is entered after a measurable delay on boot up. This is due to the incorrect 3G connectivity detection API used by them.
There are 2 ways out of this situation:
[nemo@localhost ~]$ devel-su
Password:
[root@localhost nemo]# systemctl stop aliendalvik.service
[root@localhost nemo]# systemctl start aliendalvik.service
Also sometimes Android apps don't play any sound anymore. Here as well restarting Aliendalvik service fixes the issue.
Due to the bug fix to protect user privacy, it is not currently possible to utilize the fastboot protocol to boot other kernels. This is naturally a regression in tinker-ability and a temporary problem that we will fix in an upcoming update when it can be done in a secure manner with respect to device lock and user privacy.
There is no intention to lock down the device and disallow tinkering and we'll seek to remedy this regression when possible.