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

[release notes] 2.1.3 / Kymijoki [released]

asked 2017-10-31 11:47:07 +0300

jovirkku gravatar image

updated 2018-02-15 18:24:52 +0300

olf gravatar image

This update, 2.1.3 alias Kymijoki brings Sailfish X for Sony Xperia X. All Sailfish devices get fixes for some recent well-known security vulnerabilities, including WPA issues and Bluetooth Blueborne. Kymijoki contains connectivity improvements made for Qt and Android apps and fixes dozens of other issues, too. Lastly, go try the new "Flow" ambience! Please check the new product page: https://jolla.com/sailfishx/

Many thanks to you our active contributers for your feedback and proposals!

Update version history

  • 2017-10-31: 2.1.3.7 released to Early Access subscribers.
  • 2017-11-13: 2.1.3.7 released to all (not Aqua Fish).
  • 2017-11-20: 2.1.3.7 downloadable image for Xperia X available for Sailfish X licensees.

Size of update

The download size of the update depends on the device type and on the OS version currently in the device. Some typical values below:
- Jolla Phone from 2.1.2.3 to 2.1.3.7: 170 MB
- Jolla C from 2.1.1.26 to 2.1.3.7: 350 MB
- Jolla C from 2.1.2.3 to 2.1.3.7: 240 MB
- Jolla Tablet 2.1.2.3 to 2.1.3.7: 190 MB
- Xperia X 2.1.3.5 to 2.1.3.7: 80 MB.

Release Highlights

This list contains examples of new features (and some bug fixes) added to SailfishOS since the 2.1.2 release. The release notes of upgrade 2.1.2 can be found here: https://together.jolla.com/question/168137/release-notes-212-kiiminkijoki/

Instructions for installing Sailfish OS to Sony Xperia X devices are here - covering Windows, Linux and Mac computers.

Accounts

Aliendalvik (Xperia X only)

  • Updated Android Support of Xperia X from version 1.0.75-1 to 1.0.82-1 (no update for other devices but Xperia X), fixing:
  • "Waiting for connection" issue fixed in case of Facebook Messenger.
  • Restarting of Android Support fixed.
  • Aptoide app icon should now appear in the app grid after installation of it.
  • Android apps can recover mobile data connection.
  • Camera keeps working now also after using it in some Android apps.
  • Android market place installations again in Startup Wizard.

Ambiences

  • New ambience by the name "Flow" introduced (the default on Sailfish X, available from Top Menu on other devices).

Bluetooth

  • Blueborne fixed (on all Sailfish devices).

Browser

  • Fixed the issue of detecting Jolla Browser as a mobile browser on some Chinese websites (already deployed as an OTA update from browser.sailfishos.org).
  • Browser configuration tuned to be more suitable for FullHD display.

Camera

  • Media Booster added to all Sailfish OS devices equipped with 2GB of memory or more to speed up startup times.
  • Xperia X: hardware shutter button now supported, press half-way to focus.

Connectivity

  • Connectivity breaking on many apps when switching from mobile data to WLAN fixed.
  • Ofono and connman logs protected from unauthorized access.

Device management (MDM)

  • Email provisioning and SSL certificates handling introduced.

Home screen

  • Swiping between lock screen and device lock keypad from both left and right allowed (proposed by a community member).
  • Running app is closed when it is uninstalled.
  • Homescreen layouts polished for higher resolution displays.
  • Device backspace is easier to press now.

HW adaptation (Xperia X only)

  • Flashable images for Xperia are packed to zip now (instead of tar.bz2) to make extracting easier on Windows.
  • Support for Sailfish X installation to Xperia X using Windows PC.
  • Support for Sailfish X installation to Xperia X using Linux PC.
  • Support for Sailfish X installation to Xperia X using Mac.

Mediaplayer

  • Switched OMXCodec for MediaCodecSource for video recording.

Security

  • WPA security issues: CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088.
  • kernel: CVE-2016-4485, CVE-2016-5244.
  • Blueborne: CVE-2017-0781, CVE-2017-0782, CVE-2017-0783, CVE-2017-0785; CVE-2017-1000251, CVE-2017-1000250.
  • connman DNS proxy: CVE-2017-12865.

Settings

  • Regression with low disk notification not opening Storage settings fixed.
  • Internet calling tone until the VOIP feature is officially supported in the OS.

Start-up wizard

  • Installing Android app stores possible.

Issues reported by the community at together.jolla.com and fixed in this update

Changelog

For detailed changelog, see https://together.jolla.com/question/172248/changelog-213-kymijoki/

Updating your device

Your device must be connected to the Internet and signed into your Jolla account. If your Jolla account is registered for Early Access releases you should receive an OS update notification when an update is available. If you have decided not to take the Early Access registration then you will get the OS update typically one week later.

We warmly recommend making some 3-4 GB of free space to the internal storage of your device before starting the update. Move your pictures and videos to the SD card (or to your PC or cloud service). After the upgrade turn on the option to save pictures and videos directly from the camera to the memory card (Settings > Apps > Camera). This is important particularly in case of "Jolla 1" devices (product name "Jolla" in Settings > About product).

This is the usual drill before attempting to update your devices:

PLEASE NOTE:

- If you use Phonehook or Callrecorder from OpenRepos, uninstall it before upgrading.
- If you use oFono from OpenRepos, revert to the official oFono before upgrading.
- If you use Patchmanager, revert all applied patches before upgrading.

Take a backup of your data before attempting to update your device and save the backup to an SD card or to some other off-device location (PC, your cloud service). Note that videos and images are not included in cloud-based backups. Do not reboot the device while the update is in progress. Do keep the phone connected to a battery charger during the whole process. 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: https://jolla.zendesk.com/hc/en-us/articles/201836347

About SD cards

Please read our help article on SD cards supported by Sailfish OS: https://jolla.zendesk.com/hc/en-us/articles/201997993

Known issues

  • Volume keys on tablet do not seem to work during playback.
  • After entering an incorrect WLAN (WPA) password the device may not present a new password dialog but keeps searching and using the incorrect password. In this case stop the search, turn WLAN off and on, and search again: the password dialog appears.
  • Bluetooth pairing may fail with some car models. Sometimes synchronizing the phonebook may fail, too.
  • VPN is still at beta level.
  • Two of the Utilities do not work currently.
  • New pictures sometimes appear at the bottom of Gallery.
  • Reliance Jio SIM cards (India) work in SIM slot #2 only according to some reports. We are not aware of similar issues in other networks.

Known issues specific to Xperia X

  • Manual network/carrier search lists all networks by the same name (the name of the SIM provider). Use automatic search. If not possible, you need to try several items in the manual search results, unfortunately. The top most item is not necessarily the one that can serve you.
  • Mobile data connectivity: In some cases using "Prefer 2G" for a while, then reverting to "Prefer 4G", may help.
  • VPN does not work.
  • Bluetooth: problems with car equiment, some audio devices and computers.
  • Waking up the device by double-tap does not work
  • New pictures may appear at the end of the Gallery (the fix is being prepared)
  • Sensors:
    • not working: fingerprint, barometer, step counter.
    • compass (or gyro?) working in Google Maps, not yet natively.
  • Internet sharing (WLAN hotspot, tethering) does not work but the hotspot can be controlled at the command line, see this Zendesk help article.
  • Issues with video playback and video recording (less than before).
  • FM radio missing.
  • Even though all CPU cores get eventually enabled, foreground apps do not always run on the big cores.
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2018-03-06 20:52:40.613070

Comments

3

Updating went without any problems for me (Xperia X). The only thing that irritated me was that the red led is shining while the phone shuts down. Didn't noticed that behaviour previously and got a bit nervous when updating ended with just the red led and ablack screen for some seconds :)

Also, I had to disable and re-enable the "Show reboot option in top menu" option in the Developer Tools to get the reboot option back, but that's no big deal.

ghling ( 2017-10-31 12:35:53 +0300 )edit

new flow ambience introduced - what does that mean?, anyone care to enlighten?

Spam Hunter ( 2017-10-31 12:49:24 +0300 )edit
2

Probably just a new ambience named "Flow"..?

TomC ( 2017-10-31 13:05:18 +0300 )edit

good point @TomC, I didn't interpret it that way at all.

Spam Hunter ( 2017-10-31 13:09:36 +0300 )edit
2

@TomC: that is correct. @Edz: sorry for the Finglish expression....

jovirkku ( 2017-10-31 13:50:59 +0300 )edit

25 Answers

Sort by » oldest newest most voted
0

answered 2017-11-21 16:42:15 +0300

neter gravatar image

There's some change in the handling of notifications from Android chat applications in this or the previous update (I'm not sure because I was with the previous only few minutes) that causes every new message to trigger sound/vibration even when the previous messages from the same application are not marked as read. I tested it with Facebook Messenger, Slack, Skype and Weechat Android. This is very uncomfortable especially in chats where the people types very often. The right way is only the first message from some application to trigger the sound/vibration and the next messages from the same application only to update the notification text in the Events View without triggering of sound/vibration until marking the messages as read. This was good in the previous versions of the system (Iijoki and before). Is this a bug that can be fixed in some of the next updates, or is there some setting that I can change now?

edit flag offensive delete publish link more

Comments

1

Please search before asking, as (for this specific issue) there already is https://together.jolla.com/question/168474/bug-endless-loop-of-notification-message/

olf ( 2017-11-22 20:27:51 +0300 )edit
1

Sorry, I search before asking and I saw this issue, which is about another behavior (spamming notifications for the same message), so I closed the tab and I missed your comment below, which is about the same as my question. But unfortunately there's no fix in this link for either of the issues, and I don't think this is a bug fix - nobody wants to be notified thousand times per day when using chats with many people, sometimes with several notifications in seconds, and this is not the behavior of the apps when running on Android phone.

neter ( 2017-11-23 09:09:38 +0300 )edit
0

answered 2018-02-03 06:16:40 +0300

walkingzen gravatar image

Hello:

I think there are some changes made in this release and release note says that it is not available for Aquafish. Why Aquafish users like me from India, did not get this update? Is it a problem with Intex company?

edit flag offensive delete publish link more

Comments

It's not a problem. Look this topic

Asmir ( 2018-02-03 07:00:00 +0300 )edit

Thank you for your comment. Interestingly I got an update notification today. Hopefully it works. Thanks again.

walkingzen ( 2018-02-03 08:43:44 +0300 )edit
0

answered 2018-02-03 11:26:01 +0300

kid_satan gravatar image

its now available . my update notification is gone now.

edit flag offensive delete publish link more
0

answered 2018-02-04 13:27:02 +0300

JoHe gravatar image

My elderly friend's Aqua Fish stopped to accept the Device Lock code today. The device was upgraded to Kymijoki on Thursday evening and had been shutdown on the last three nights. Today morning it booted but in the Events Screen the indicator bar for telephone was not on at all. Flight mode was activated. After some fiddling the SIM1 activated and started to provide internet, although the SIM2 was earlier for mobile broadband usage.

Recovery mode does not accept the device lock code. Next we will contact Zendesk.

edit flag offensive delete publish link more

Comments

In Recovery Mode after five attemps to unlock the device there were outputs like

[ERROR] Code check failed. Exiting...
[ERROR] Device access denied!

Though, the Reset device to factory state was succesful! Now installing the device again to production state.

JoHe ( 2018-02-04 14:47:02 +0300 )edit
0

answered 2018-02-06 13:08:10 +0300

Mayank gravatar image

updated 2018-02-06 13:08:52 +0300

can any one please solve GOOGLE PLAY STORE 'download pending' problem and COC game is not logging in with GOOGLE PLAY GAMES.

edit flag offensive delete publish link more

Comments

2

use Yalp-Store

mettska ( 2018-02-06 13:14:51 +0300 )edit

Question tools

Follow
17 followers

Stats

Asked: 2017-10-31 11:47:07 +0300

Seen: 23,470 times

Last updated: Feb 15 '18