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
46

answered 2015-07-28 11:14:41 +0300

pan tau gravatar image

updated 2015-09-01 03:06:14 +0300

well, i have to say i am disapointed, 1.1.7.25

jolla phone with sailfish OS and then some ugly android has higher priority than IMPORTANT THINGS SUCH AS CALDAV , EMAIL, CONNECTION STABILITY for xmpp,icq,imap idle , unable to answer calls sometime, could not send sms sometime until data are restarted or changed 4g/3g mode (it works right after data disconnect) or while travelling - wait for another antennas in another location and then sms works...

instead of improving Phone and Message app, one hour shifted caldav events, just important things for daily use...

there are also localizations ready and still waiting and waiting to be included, instead we reading boring news about updated android....

https://together.jolla.com/question/99580/carddav-contacts-do-not-sync-after-update-to-11724/ https://together.jolla.com/question/96871/11617-xmppicqimap-idle-affected-unstable-network-connection-on-bts-change/ https://together.jolla.com/question/96300/wlan-does-not-check-bssid-ap-mac-address/ https://together.jolla.com/question/60486/all-dates-shifted-by-one-hour-in-calendar-after-updating-to-11038/

edit flag offensive delete publish link more

Comments

17

I agree. While I understand that a better "Android compatibility" makes the device more appealing to new users, we (the people owning a Jolla) need better support for Caldav, emails and XMPP.

ilpianista ( 2015-07-28 11:20:24 +0300 )edit
3

yes, but if new user will get jolla, with perfect android support and buggy important things for what is phone made today what he will think about? that he should buy new android phone instead :(

i see no point for bringing 'sheeps' who loving androinds to unstable system, it could do more mess and bad reputation. (i selling and supporting jolla devices to companies arround me, so i know what 'normal' users needs and says)

pan tau ( 2015-07-28 11:29:20 +0300 )edit
3

its a minor upgrade before the big kahuna of 2.0, which may very well address some of these issues.

r0kk3rz ( 2015-07-28 19:28:10 +0300 )edit
5

well personaly i think there will be many guys and many arguments why not to upgrade to v2, im not in actual picture about v2 os, but if there is missing swipe from top to close/lock i will be one of them who will never upgrade to v2 whatever it will offer. before 1.6 most of things was functional (phone, messages, caldav ... )

so will be nice to get functional v1 . not just say that in v2 everything will be fixed

pan tau ( 2015-07-28 21:02:16 +0300 )edit

if the blog is anything to go by, this is it for v1 releases, there won't be any more.

I highly doubt 'everything' will be fixed in the first v2 release, but the usual monthly upgrade cycle will continue to march on.

r0kk3rz ( 2015-07-28 21:14:14 +0300 )edit
7

answered 2015-07-15 14:40:57 +0300

hamlatzis gravatar image

Still no fix for SDL2 library regarding portrait/landscape orientation

Too bad

:-(

edit flag offensive delete publish link more

Comments

10

we are still waiting for upstream to accept our patch:

https://bugzilla.libsdl.org/show_bug.cgi?id=2943

Kontio ( 2015-07-15 15:57:49 +0300 )edit

@Kontio So there's a patch available? Then don't wait but apply it downstream till it's accepted upstream.

V10lator ( 2015-07-16 07:31:21 +0300 )edit
11

@V10lator we don't apply patches until they are accepted by upstream into their master, to avoid problems in case upstream fixes the problem different. Once upstream takes them into master branch, we normally apply them also and don't wait until upstream made a new release.

Kontio ( 2015-07-16 12:18:19 +0300 )edit
5

answered 2015-07-15 14:08:55 +0300

kaulian gravatar image

Does this upgrade include the patch for ofono and Orange French Provider for MMS correct by Slava Monich last week ?

Thanks

edit flag offensive delete publish link more

Comments

I think this will be revealed once they publish the full changelog.

nick75 ( 2015-07-15 14:11:22 +0300 )edit

doesn't look like regarding detailed changelog, but rpm is available for download and fully working if you need it, I can share :)

clovis86 ( 2015-07-15 15:47:20 +0300 )edit

After update no MMS @clovis86 : Now we need for this release

kaulian ( 2015-07-15 15:49:41 +0300 )edit

WARNING Use it at your own risk, blabalbalbalbal can kill your cat and family, etc... WARNING reboot after installing this RPM http://we.tl/F7vPsrkJIv ofono-1.16+git9+ports.ge11f7a1.armv7hl.rpm

clovis86 ( 2015-07-15 16:28:33 +0300 )edit
5

answered 2015-07-15 15:34:17 +0300

Milhouse gravatar image

Still no reliable, dependable email notification for every new email received?

https://together.jolla.com/question/4068/email-add-option-to-sound-alert-for-every-newly-received-email

Sorry to say guys, but if you can't/won't address the basics that every other platform already has covered and does well, then I think it's time to jump overboard (and I say this with a very heavy heart, having invested waaay too much time, money, effort and misplaced hope in the Maemo/MeeGo/Sailfish project since falling in love with the Nokia 770 in 2005).

edit flag offensive delete publish link more

Comments

3

Well, I'm really happy to see notifications for Android apps even if they're not running.

They can't fix everything at once, unfortunately...

bilgy_no1 ( 2015-07-15 23:29:18 +0300 )edit
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
2

answered 2015-07-16 02:43:25 +0300

pan tau gravatar image

updated 2015-07-16 03:15:33 +0300

CALDAV events are gone, some black shadow items are present, after account recreation, still no events, no calendars visible in Manage Calendars, tried, enable, disable, calendars or whole account, reboot, no change.

while syncing and quickly openning calendar i can see for second all dates with my events underlined (almost everyday), but only until sync is complete, it just flash all days with events for moment , while i am on day with event, name and time of events will flash too then disapear :( ... then again, no events, no calendars

https://together.jolla.com/question/99029/calddav-calendars-not-found-in-calendar-app-after-update-to-117/

shadow events from nonexisting cal

edit flag offensive delete publish link more

Comments

1

CalDAV works for me (with Owncloud as backend server)

tortoisedoc ( 2015-07-16 07:41:49 +0300 )edit

caldav-client[12035]: [C] CalDavClient::syncFinished:372 - CalDAV sync failed: 403 "unable to save calendar storage"

pan tau ( 2015-07-22 23:49:13 +0300 )edit

What does your owncloud publishing configuration look like? IIRC i just copied the default config from the owncloud website.

tortoisedoc ( 2015-07-23 09:11:16 +0300 )edit

fixed by removing all 'shadow' items from jolla then created caldav account, works: https://together.jolla.com/question/99472/how-to-wipeout-caldav-related-tables/?answer=103326#post-id-103326

we use ZENTYAL 4 not OwnCloud

pan tau ( 2015-08-02 17:23:10 +0300 )edit
2

answered 2015-07-16 07:17:24 +0300

Shadow gravatar image

Warning!

I think I messed up the upgrade by downloading the upgrade and then installing an application with Warehouse before the OS upgrade. I think trying to install that program made the OS upgrade begin without rebooting the phone as it started installing many things that are unrelated to the program I was installing.

Now my phone is partially upgraded. And my phone shows a notification that there is an update available while it shows as 1.1.7.24 installed in the settings.

edit flag offensive delete publish link more

Comments

I have experienced this behaviour also with the 1.1.6.27 update!!

Stefan P ( 2015-07-16 18:53:43 +0300 )edit
2

answered 2015-07-16 17:25:38 +0300

Rikudou_Sennin gravatar image

Is it possible to get the .ts files somewhere, so I can translate them? I'd love to have my phone full in Czech :)

edit flag offensive delete publish link more

Comments

I would suggest to look here. There you find a other language pack so you can find out how you can do that.

heubergen ( 2015-07-16 19:50:09 +0300 )edit
2

answered 2015-07-21 11:15:35 +0300

updated 2015-07-21 11:40:17 +0300

This bug is still arround (1.1.7.24) I experienced it a few minutes ago.

[bug] Trying to answer a call: Pulley menu cannot be pulled down.

edit flag offensive delete publish link more

Comments

4

Thanks, will keep this in mind with future posts.

WilliePre ( 2015-07-21 12:20:22 +0300 )edit
2

answered 2015-07-22 00:20:01 +0300

Nokius gravatar image

Thanks Sailors, Wifi networks with Capture page are now much better detected with 1.1.7!!!! <3 <3

edit flag offensive delete publish link more

Question tools

Follow
21 followers

Stats

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

Seen: 44,639 times

Last updated: Sep 02 '15