We have moved to a new Sailfish OS Forum. Please start new discussions there.
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
0

answered 2015-07-29 15:16:02 +0300

fasza2mobile gravatar image

updated 2015-07-31 00:22:12 +0300

After the new update my Camera seems to not work properly either. Flash can't be turned on even thought it works with flashlight app(not the same time) Also, I can't change the focus to auto or tap to focus, only infinity focus is available.

Update: the factory reset and updating again to 1.1.7 this issue is also fixed.

edit flag offensive delete publish link more
0

answered 2015-08-06 21:31:50 +0300

Mohjive gravatar image

After updating my google e-mail account stops syncing after a couple of days of uptime. I have set it to "always up to date" and that does work until it stops completely. Neither automatic update nor manual fetching works until the device is rebooted. Haven't seen this behavior with previous versions. Is there something I can do to provide a better report/log of the issue?

edit flag offensive delete publish link more

Comments

2

yes, there is! You can create question with bug report

virgi26 ( 2015-08-07 03:37:15 +0300 )edit

Search if there's another topic about sync issues (I know for certain that for CalDAV and CardDAV there are). If you can't find a suitable topic to edit, open a new one.

To get proper logs, you need to enable developer mode. I'm sure after you've opened an issue, someone can give you instructions how to get the logs. (I know there's instructions for CalDAV but I can't test how it works for Google as my Jolla is in repair). Hope you get it resolved.

raketti ( 2015-08-07 08:36:12 +0300 )edit
0

answered 2015-08-08 11:47:28 +0300

Groucho gravatar image

What is actually the latest official release of Sailfish?

To me it seems 1.1.7 is still early release and my Jolla shows no updates from 1.1.6 available. I'm just wondering, as 1.1.7 has been early release for weeks and just now some rumors are starting about 1.1.9.......

So, do I have issues with my update process or do I just need to wait?

edit flag offensive delete publish link more

Comments

It's still an early release, I am wondering when they will release it to everyone.< So the current Sailfish OS version is still 1.1.6.

Dylan Van Assche ( 2015-08-08 11:59:41 +0300 )edit

Thanks, so I'll sit and wait.

Groucho ( 2015-08-08 12:04:13 +0300 )edit

Wonder what's holding it up?

Aashish ( 2015-08-09 14:48:33 +0300 )edit
0

answered 2015-08-08 17:25:16 +0300

t-lo gravatar image

updated 2015-08-08 17:26:05 +0300

BUG: Android notifications do not work. They can be configured per application, but no respective notifications do appear. Tested with Google calendar, Google Plus, Hangouts, amongst others.

See https://together.jolla.com/question/101370/11724-android-notifications-dont-work/ for a detailed report.

edit flag offensive delete publish link more

Comments

for me they started to work with android notification app from coderus. then make sure you have volume set to some level on phone.

FOMBE ( 2015-08-13 09:18:28 +0300 )edit

I understand that when I install unsupported 3rd party software that may break my phone on the next update I'll get notifications and a ton of other useful stuff. This bug report is for the dysfunctional official Jolla feature, not for Coderus' good work.

t-lo ( 2015-08-13 09:40:50 +0300 )edit

Everything works perfect.

N9Sailfish ( 2015-08-13 12:38:35 +0300 )edit

@N9Sailfish Google Calendar reminders pop up as configured? Google+ Notifications pop up timely, too? And most importantly, when you get an incoming call to Hangouts, you are notified? I'm asking because none of those work for me.

t-lo ( 2015-08-13 13:51:17 +0300 )edit
0

answered 2015-08-13 08:54:49 +0300

FOMBE gravatar image

#bugreports bluetooth keeps making nosound and shows "phone active" for ~1-2mins after connecting to car bluetooth handsfree. so for example you cannot listen to radio. Also *no sound noise still exists when typing and keyboard sounds are off.

android app numkeypad "," button doesnt work. atleast on fuelio app.

edit flag offensive delete publish link more

Comments

5

oh come on, really?! please, stop posting bugs as answers!!!

virgi26 ( 2015-08-13 11:09:00 +0300 )edit
2

@FOMBE: #HashtagsDontWorkHere 😉

wanderer ( 2015-08-15 10:10:35 +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
0

answered 2015-08-14 04:52:20 +0300

vishal gravatar image

At this version i can feel much difference regarding android apps, before the version not able to use some of the apps but in this i am able to use android apps without any issue. And sometime when i click on folder icon it stucks and screen goes black and lock screen appears, i think it may have been fixed in yesterdays(13/8/2015) update. waiting for v2.0 as you promised it will be released on the month of august.

edit flag offensive delete publish link more

Comments

I guess 1.1.7 will be skipped for the public and 2.0 will be rolled out ? What do you think?

ozzi ( 2015-08-28 13:40:31 +0300 )edit
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-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
4

answered 2015-08-23 21:28:20 +0300

CLR64 gravatar image

updated 2015-08-25 14:42:23 +0300

Hi guys / jolla team,

don't get me wrong on this post, I'll just post some thoughts (really everything coming in my mind) to the annoying bug which is that hard to debug. I guess most of them were surely already considered of your team. At the moment I also signed to early access and install the update. I'll give another note if I hit the bug. Because the hardware is the same for everyone the only reason of this bug can be one of those:

  1. A driver / app / whatever just installed by ppl affected by the bug
  2. An event appearing just for ppl affected by this bug in the period of updating
  3. A combination of one of the first two points including a critical (special) moment of the update

A key question also is: What changed in update process / installed update between this and last updates??

Being more specific I got following ideas. Most of them are surely completely random because previous updates went well - this includes question from above.

One of the following events occurred on update. Maybe including key update progress step on occurrence:

  • Charging cancelled / reconnected (maybe also connected to computer and asking for kind of connection)
  • Some provider events like time update / other provider services (no advanced knowledge than their pure existence)
  • Bluetooth / wlan /gps
  • Unix / jolla services
  • New android emulation- / whatever service booting up issue
  • Active application closing / updating issue

All for now. I'll convert this to a comment later if this doesn't seem to be of any help.

UPDATE #1: - btrs 3.17 Chaneglog: fix for the infamous deadlock

https://btrfs.wiki.kernel.org/index.php/Changelog#v3.17_.28Oct_2014.29

You seem to use an old version of the btrfs file system (for a good reason ?) If we look at the changelog there is one version later a bugfix for the so called "infamous deadlock". I looked into this a bit deeper and if or if not this is the source of this problem. Shouldn't it be merged?

edit flag offensive delete publish link more

Comments

1

Added possible problem in btrfs

CLR64 ( 2015-08-25 14:11:56 +0300 )edit

Question tools

Follow
21 followers

Stats

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

Seen: 44,644 times

Last updated: Sep 02 '15