We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2015-04-17 05:46:50 +0200

[update-bug] Jolla believes the update has been downloaded

Jolla believes the update package has been downloaded fully & successfully, but it does not.

When went to settings -> Sailfish OS updates -> download updates, Jolla began to download the update package

The process image indicated that it's downloading. But after a while(the process hasn't reach 20% yet), It said download finished.

If choose update in the menu, Jolla will go to the black sailfish OS updating page with a process bar. And immediately, the update fails. Jolla reboots.

  1. This bug does not always happen.
  2. Maybe because the Internet connecting is not so smooth. (I connect Wifi at my home.)
  3. Reboot phone, the "Downloaded" status will go back to "pull down to download" status, then I can download it again
  4. Sometimes re-open the settings can download it again

Happened when Update10->11 and Update11->Early Release 1.1.4

Not a serious bug. Just try several times and there is a high chance that it will work as expected

[update-bug] Jolla believes the update has been downloaded

Jolla believes the update package has been downloaded fully & successfully, but it does not.

When went to settings -> Sailfish OS updates -> download updates, Jolla began to download the update package

The process image indicated that it's downloading. But after a while(the process hasn't reach 20% yet), It said download finished.

If choose update in the menu, Jolla will go to the black sailfish OS updating page with a process bar. And immediately, the update fails. Jolla reboots.

  1. This bug does not always happen.
  2. Maybe because the Internet connecting is not so smooth. (I connect Wifi at my home.)
  3. Reboot phone, the "Downloaded" status will go back to "pull down to download" status, then I can download it again
  4. Sometimes re-open the settings can download it again

Happened when Update10->11 and Update11->Early Release 1.1.4

Not a serious bug. Just try several times and there is a high chance that it will work as expected