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-16 08:19:26 +0300

Trizt gravatar image

Balance issues

btrfs fi show tells me that I have 11GiB used of 13.75GiB, but the btrfs balance hangs on

0 out of about 1 chunks balanced (18 considered, 100% left

As the updater do not check if there is enough space (would say 2.5+GiB should be enough for a 1.5G requirement), I can't get past the space check. Also it seems like the updater runs multiple balance request at once, which makes that a reboot will just "get past" one chunk and another balance is started.

Needing more than 14 hours for one balance run is just ridiculous, please backport all the btrfs fixes if you can't upgrade to 4.1 kernel, as we would get auto balance which is a bit more sane than the balance script.

Also seems Jolla has ruined my sdcard which nowadays just mounts as read only, no never change partition layout nor formatted it, guess Jolla writes a lot to it for keeping the index file up to date on static content.

edit flag offensive delete publish link more

Comments

2

The btrfs-balancing before OS update becomes active if the ratio of size and used space exceed 75%. 11 GB of 13.75 GB exceeds it. The balancing consists of multiple runs (7 in total), getting more elaborate with each.

There is a (totally NOT recommended) way to get past the btrfs-balancer guard of the OS update by pretending that you recently balanced successfully already.

As root:

touch /var/cache/btrfs-balancer/last-success

However, this is not recommended at all, because this OS update is quite enourmous in size, and if the filesystem is not well balanced, you risk bricking the device.

pycage ( 2015-07-16 21:29:38 +0300 )edit

Thanks for the suggestion, I'm still waiting for the current balance to get to a point where it ends or that a reboot will cancel it, as it's not possible with the command line to cancel a balance (they should have fix that). I really need a phone that can work, just wish Nokia would deliver phones sooner than end of 2016.

NOTE: Managed to get out of the balance hell Friday morning and did the 350MB download before I had to leave and let the update run all the way downtown, phone getting hot as usually when it does something a bit more heavy work.

Trizt ( 2015-07-16 22:36:05 +0300 )edit

@Trizt Nokia will deliver nothing, they'll just give away licenses to use the brand name. So your 2016 Nokia smartphone will just be some Android thing:

"We will look for suitable partners," Rajeev Suri said in an interview published on Thursday. "Microsoft makes mobile phones. We would simply design them and then make the brand name available to license."

(Source: http://www.reuters.com/article/2015/06/18/us-nokia-phones-idUSKBN0OY21320150618 )

V10lator ( 2015-07-19 17:23:21 +0300 )edit
0

answered 2015-07-17 18:02:18 +0300

vishal gravatar image

i too got problem while updating it updated till 90% and asked to update again when i started to.update.i think it updated remaining 10% within that finished and upgraded without problem. Till now there is no issues in new update working as it was before with new android settings.

edit flag offensive delete publish link more
0

answered 2015-07-19 15:04:33 +0300

aatu gravatar image

Okay,

Didn't work for me. Got this pop-up during install saying "Sailfish-käyttöjärjestelmää ei voinut päivittää. Yritä uudelleen myöhemmin. (Salfish progress bar) Laite käynnistyy nyt uuelleen (OK)."

Also, I now have zero android functionality, that is, not one android app is working, they all fail to launch.

Yes, it sucks,

Adam

edit flag offensive delete publish link more

Comments

Got the .25 update alert, loaded, but at install I got the same message. To free space I removed all downloaded apk's from 1mobile download directory thinking they're abundant once installed ... big mistake? Is this why my android apps aren't working? Also I noticed I now have a Bluetooth icon beside the clock on the left, which however doesn't reflect wether bt is on or not.

aatu ( 2015-07-27 20:11:56 +0300 )edit

Try using Dalvik clean-up from Warehouse/Openrepos then re-installing Android support from the Jolla store, this worked for me when I had a similar issue

sugaryenigma ( 2015-07-29 16:32:00 +0300 )edit

Thanks,

Tried, but Dalvik clean-up wouldn't install (or any other software from Warehouse), because of some error with writing to /tmp/somethingsomething. So I tried deinstalling and reinstalling the Android support from Jolla store, and that possibly made things work, since now everything works again, and even the .25 install went through, thou I have no clue as to why these two things would be connected.

Cheers.

aatu ( 2015-07-30 10:42:08 +0300 )edit
0

answered 2015-07-19 23:45:21 +0300

Nokius gravatar image

The new Store takes ages to load the content :( As I read it is a know issue and there is a fix for it great hope it will be available with the final 1.1.7 :) (Source:https://together.jolla.com/question/101310/what-happend-to-jolla-store/)

edit flag offensive delete publish link more

Comments

This is not my experience, the new Store loads reasonably fast for me.

WilliePre ( 2015-07-21 11:43:06 +0300 )edit

for me it takes a few more than it should it feels like the store is unavailable or overloaded I did check the round trip but a 'precaching' or similar solution to speed it up is needed.

Nokius ( 2015-07-22 00:23:10 +0300 )edit
0

answered 2015-07-29 15:10:40 +0300

fasza2mobile gravatar image

updated 2015-07-31 00:20:05 +0300

Anyone else having problems with dynamic orientation? My device senses it's upside down (both axis). I have to use manual orientation since I updated.

Note: I haven't used the device for a while due to broken screen, I wanted to send for repair, but haven't got around to doing it before my holiday. I just turned the phone back on, to extract a phone number and thought I try out the update. I don't want to send the device twice if it's a hw issue, but rather book both jobs together. However if it's a software issue I don't want to waste money and customer care's time on it.

Update: after a factory reset and reapplying updates again dynamic orientation works correctly again. Something must've gone wrong applying the update the first time.

edit flag offensive delete publish link more
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

Question tools

Follow
21 followers

Stats

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

Seen: 44,639 times

Last updated: Sep 02 '15