Ask / Submit
116

[release notes] 1.1.7 / Björnträsket [released]

asked 2015-07-15 13:43:48 +0300

Aard gravatar image

updated 2017-10-02 22:22:00 +0300

olf gravatar image

Update on 31.8.2015: 1.1.7.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.

In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.

If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.

As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.

Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly.

As usual,

  • If you use phonehook from OpenRepos, uninstall it before upgrading
  • If you use patchmanager, revert all applied patches before upgrading
  • Do not reboot the device while the update is in progress.
  • The device screen may blank out during the update process, you may waken the display by a short press on the power key to monitor the progress.

For detailed instructions on updating software, visit Zendesk

Upgrade version history

  • 1.1.7.24 (15.7.2015): Initial early access release
  • 1.1.7.25 (27.7.2015): Fix an issue in package management middleware
  • 1.1.7.27 (13.8.2015): Fix a reboot issue when using hotspot with GPS and an icon scaling issue for favourite settings
  • 1.1.7.28 (27.8.2015): Fixes issues youtube video playback in native browser, adds a feature to enable persistent logging during the upgrade process and fixes MER #1208.
  • 1.1.7.28 (31.8.2015): Roll-out to all users

Highlights

  • New gcc 4.8 based tool chain is used on SailfishOS platform from this release onwards, bringing C++11, among other things
  • Alien Dalvik (Android support)
    • Added 'Android Support' settings to Settings > System > in the 'Info' section
      • Option to prevent Android apps from accessing your contacts
      • Option to Stop/Start Android support
    • Added a settings page for Android applications in Settings > App from where you can control how the installed application works on your Jolla device (Force stop, Clear cache, Clear data, and running the app on background)
    • Having the option to run Android applications on background enables receiving notifications for Android messaging apps even when the app is closed.
    • Better WLAN connection handling for Android apps
  • Introduce certificate handling middleware (p11-kit). All crypto libraries now share one CA store.
  • Update to PulseAudio 6.0, improving Bluetooth audio
  • Possibility to choose different keyboard layouts for Bluetooth keyboards if paired with one for different languages via Settings > System > Text input > Active layout

Security fixes

CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153

Known issues

OS update process

  • OS update may remain at about 95% for a long time. If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade went through.
  • If you have phonehook from OpenRepos installed uninstall it before upgrading.
  • Currently, checks on available disk space happens very late during the OS upgrade process and will fail in the installation phase if the disk space is low. Normally there should be an error note asking you to free some disk space and try again, but in some marginal cases it might not be shown. Should this happen, free some disk space and try to install the OS update again.
  • OS update may fail due to some other reasons too, for example it may have installed some packages from the new release and still have something left from the old. If the device can boot up, you can try to recover by doing the following. If not, you can attempt to recover the device using the recovery mode.
    • Delete the file /home/nemo/.cache/store-client/os-info
    • Stop the store-client process (for e.g. pkill store-client)
    • Reopen Settings app, check for updates again and attempt to install the OS update again
  • We have also noted that if the OS update is attempted while there is long queue of installation of apps from the Store, the system may end up in mixed state (for e.g. select all the apps from startup wizard, and start the system update already while the apps are being installed).
    • In such cases, the OS update appears to be stalled, however it is just waiting for the installations to complete before attempting to upgrade the OS. Just wait patiently, the worst thing to do here is to reboot the device!

Other issues

  • calDAV and cardDAV services are in experimental stage. We have made some improvements with this update, however you may still face issues with certain service providers. Do report it in t.j.c. We'll take a look and try to sort it out.
  • Deleting photo from Camera roll may also delete the previous photo. If camera reel's pulley menu has "Show details" greyed out - means the photo hasn't been indexed yet. Deleting photo in such state will result in previous photo deleted too. If you wait long enough (~10-15seconds) for 'Show details' to become active, only that photo will get deleted when you choose to.

Changelog

The full changelog is available in a separate post

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2017-10-02 22:22:15.505162

Comments

1

Downloading!!

nick75 ( 2015-07-15 14:01:44 +0300 )edit

First release named after a Swedish lake!

Stefanix ( 2015-07-15 14:08:33 +0300 )edit
3

@Stefanix, or the Swedish name for the 30 Finnish lakes named Karhujärvi. I doubt there are any Finnish lakes starting with B, as that letter is seldomly used in the Finnish language.

nick75 ( 2015-07-15 14:14:33 +0300 )edit
4

It's a lake between Porvoo and Loviisa so I'd say it is very much a Finnish lake. Finland has a long history of Swedish rule though, so Swedish names are not that uncommon. See Järviwiki)

Yaniel ( 2015-07-15 14:16:18 +0300 )edit

Update failed after the progress bar was over 90 %. However, after reboot the phone claims that it's running version 1.1.7.24 but at the same time it offers an update notification but checking for updates doesn't work...

skvark ( 2015-07-15 14:46:47 +0300 )edit

33 Answers

Sort by » oldest newest most voted
2

answered 2015-08-14 22:44:44 +0300

updated 2015-08-28 01:24:38 +0300

* I've also this issue as an comment to the release notes *

I experience 2 issues with release 1.1.7.x (I am running release 1.1.7.27)

Calendar updates: When creating a Calendar entry (in my Jolla Calendar app) that uses my Google calendar, it is not synced with Google calendar and the entry disappears. If an calendar entry is created in my Personal (Jolla Calendar app) calendar, all is fine, the entry does not disappear and shows in the calendar. Now if entries are created in Google calendar via the web, these entries are synced to my Jolla Calendar app and does show in the Calendar.

Clipboard: The clipboard stops working frequently. Restarting it via Utilities (Restart Keyboard) does not restart it. The only solutions is rebooting the phone.

Thank you wanderer for your remark, I'll use your work around until this issue with the Clipboard has been resolved.

@wanderer: I am also experiencing this. Sometimes restarting Keyboard via utilities works after the second or third try. Also restarting the GUI via systemctl --user restart lipstick (in terminal, developer mode required) fixes the clipboard most of the time. It is just another workaround, but a bit faster than a reboot. wanderer


Update : I'm now running release 1.1.7.28, calendar issue still persists.

edit flag offensive delete publish link more

Comments

@WilliePre - you can also restart the non-working clipboard from the Utilities by selecting Restart Home Screen. I'm still running 1.1.6. but for me that works and no reboot is required. However, this is not a solution this bug needs to be addressed since it's been around for some time now.

raketti ( 2015-08-28 08:48:16 +0300 )edit
1

answered 2015-07-15 14:04:49 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2015-07-15 14:05:06 +0300

V10lator gravatar image

One question before doing the update: All previous updates told to disable openrepos repos before updating. Is this still needed and if so: How to do it? If it's not needed: Will the repos be deactivated and reactivated automatically?

edit flag offensive delete publish link more

Comments

1

have a look at the 'zendesk' link, especially the last paragrah

rudi ( 2015-07-15 14:09:41 +0300 )edit

"If your Jolla phone has now a SailfishOS version which is one of 0.99.5.11, 1.0.0.5, 1.0.1.10, 1.0.2.5 or 1.0.3.8" - Mine has 1.1.6.27, so it does deactivate and reactivate automagically?

V10lator ( 2015-07-15 14:11:18 +0300 )edit

https://together.jolla.com/question/33581/how-to-disable-openrepos-repositories/

You can do it with 1 copy/paste. Better safe than sorry.

alcalinebattery ( 2015-07-15 14:12:48 +0300 )edit

@V10lator: As 1.1.6.27 ∉ {0.99.5.11, 1.0.0.5, 1.0.1.10, 1.0.2.5, 1.0.3.8}, you don't have to disable third party repos before updating.

Valker ( 2015-07-15 14:49:53 +0300 )edit
3

Good lord, no, it hasn't been necessary for a long time. Every time there's an upgrade somebody asks this question. During the update procedure, external repositories no longer interfere, fiddling with openrepos is an unnecessary waste of time.

vitaminj ( 2015-07-15 15:00:45 +0300 )edit
1

answered 2015-07-16 09:52:29 +0300

Fellfrosch gravatar image

What does the "Better WLAN connection handling for Android apps" mean?

It's unfortunatly still impossible to connect my Canon DSLR or my Panasonic ActionCam.

Otherwise all works fine so far, despite the fact that the update took 3,5 hours.

edit flag offensive delete publish link more

Comments

Theres already a open question due to that issue, please just vote there. https://together.jolla.com/question/99256/wlan-issue-11724/

heubergen ( 2015-07-16 19:48:42 +0300 )edit
1

answered 2015-08-14 02:28:53 +0300

liqquid gravatar image

Hi

I made a mistake. This is not the first time unfortunately. This before I factory reseted my system and installed all of software updates and apps and settings again, but if possible I don't want now. I always use patchmanager and the eventsview controls patch. I forgot again to switch off this patch before I refresh the firmware. The other patches nothing problem, but this one not working now again... I didn't can switch off, and reinstall, and activate again, nothing to this one :( .

Possible somehow to repair this without again factory reset my system? I hope it is somehow possible...

(and just one thing yet: Possible to refresh and overwrite to the newer system version the base factory reset function?)

Thanks!

edit flag offensive delete publish link more

Comments

Same for me with "Upcoming events on lockscreen", during the minor update from 1.1.7.25 to 1.1.7.27. It doesn't work and I can't unapply or remove it (some file under /tmp os blocking it). Any idea?

hoschi ( 2015-08-14 08:36:34 +0300 )edit
1

answered 2015-08-16 04:54:26 +0300

vishal gravatar image

Jolla team before the update v 1.1.7(13/aug/2015) there was no much issue with reboot, but after last update frequently it reboot unnecessarily while using browser, always i get app registry error. please fix it.

edit flag offensive delete publish link more
1

answered 2015-09-01 07:40:34 +0300

quazar gravatar image

Update went smooth and quickly. The Jollas seems to get snappier each update, but is this also because a cleanup is done during the install process? If so, would it be possible to run this command every other week or so? Or is there an actual (noticeable) speed improvement with each update? Nice to see the Jolla/Sailfish OS improve each month!

edit flag offensive delete publish link more

Comments

Since 1.1.6.x file optimization should occur every week tuesday at 3:00am, if charger is plugged in

drummer12 ( 2015-09-02 21:45:39 +0300 )edit
0

answered 2015-07-15 14:04:09 +0300

tortoisedoc gravatar image

I get a " not enough disk space" after download; but I have 8 GB:(

edit flag offensive delete publish link more

Comments

also with 'btrfs fi show'?

rudi ( 2015-07-15 14:06:21 +0300 )edit

Hmhm I get a "ERROR : unable get label Inappropriate ioctl for device"

Label "Sailfish" uuit blahblahblah

Total devices 1 FS bytes used 7.75 BiB

devid 1 Size 13.75 GiB used 13.75 GiB path /dev/mmcblk0p28

tortoisedoc ( 2015-07-15 14:10:57 +0300 )edit

One more thing, "df" highest usage perc is 70% but that on /dev/mmcblk0p18 (firmware)

tortoisedoc ( 2015-07-15 14:12:41 +0300 )edit

'used 13.75 GiB', so no freespace on device.

rudi ( 2015-07-15 14:14:29 +0300 )edit

sounds like you need a balance @tortoisedoc

r0kk3rz ( 2015-07-15 14:15:01 +0300 )edit
0

answered 2015-07-15 16:58:01 +0300

tatico gravatar image

Hello,

upgrade stuck at 99% for 45 minutes. removed the battery, got scared as hell, first boot was really long. now it's in 1.1.7, but still has the notification from available update.

bottom line, wait for the official release.

edit flag offensive delete publish link more

Comments

1

The Update was stuck at 99% for me too. I waitet at least one hour and the update finished successful at last. >1 hour at 99% without any indication of some progress is problematic.

jpa ( 2015-07-15 17:18:57 +0300 )edit
3
0

answered 2015-07-15 17:31:28 +0300

The update did not finish successfully (I have no openrepos nor patches installed).

After 95% there was a screen which informed that the phone couldn't be updated. However, after reboot the phone was reporting that the version is now 1.1.7.24 and gave a "system update available" notification. I tried to check for updates but no update was available.

After that I did as guided in the release notes above:

  1. Delete the file/home/nemo/.cache/store-client/os-info
  2. Stop the store-client process (for e.g. pkill store-client)
  3. Reopen Settings app, check for updates again and attempt to install the OS update again

After step 2 there were no updates available and the current status can be seen below (wrong lake image). Question: did the update process finish succesfully or not?

image description

edit flag offensive delete publish link more

Comments

Easy way to check - under setting do you now have android settings? If so, the update was successful. That is one of the things this update has brought.

Aashish ( 2015-07-15 17:40:12 +0300 )edit

Yes, it's there. But that's just one small part of the update. I'm curious was the update fully installed or not.

skvark ( 2015-07-15 17:44:53 +0300 )edit

At least store-client wasn't updated. I did pkcon install store-client and rebooted but now the updates section in setting seems to hang forever (loading spinner, looking for updates).

skvark ( 2015-07-15 18:18:55 +0300 )edit

My problem is not same as in that stuck udpate. Yes, this could have been a separate bug report.

skvark ( 2015-07-15 18:40:43 +0300 )edit
0

answered 2015-07-16 07:43:22 +0300

Flaury gravatar image

updated 2015-07-17 00:42:37 +0300

Hello,

the phone asked me to prepare the update installation by cleaning up the file system (btrfs balance?). While doing so, the phone hugh up (jolla logo) and does not boot any more! I was able to back up all data via recovery mode using

mkdir -p /mysd
mount /dev/mmcblk1p1 /mysd/
btrfs restore -i -v /dev/mmcblk0p28 /mysd/
umount  /mysd

But even the device factory reset does not work: It complains about failed deleting files because of read-only filesystems.

Any hints?

EDITED 2015-07-16: Solved. File system was full and not able to balance. Removed some snapshots and balanced manually. Then the factory reset worked.

edit flag offensive delete publish link more

Question tools

Follow
21 followers

Stats

Asked: 2015-07-15 13:43:48 +0300

Seen: 43,608 times

Last updated: Sep 02 '15