Ask / Submit
65

[release notes] 2.1.2 / Kiiminkijoki [released]

asked 2017-10-02 11:59:11 +0300

jovirkku gravatar image

updated 2017-10-10 22:56:22 +0300

olf gravatar image

This update, 2.1.2 alias Kiiminkijoki, fixes dozens of bugs reported by our community and adds many improvements. It makes the new Dropbox service interface available and improves some security features. 2.1.2 also contains the basic support for Sony Xperia X devices for development purposes (available for a limited user group only).

Thank you for your contribution in improving Sailfish OS!

PLEASE NOTE: This is a BIG update (hundreds of megabytes) for those upgrading from 2.1.0 or earlier versions. Therefore: 1. Keep your device connected to a charger. 2. Wait patiently - the download may take tens of minutes.

Upgrade version history

  • 2017-10-02: Update 2.1.2.3 (RC3) was released to Early access subscribers (*).
  • 2017-10-09: Update 2.1.2.3 Released to all (*).

(*) This is a phased roll out, i.e. the update is not available for all users at the same time. Please be patient.

Release Highlights

This list contains examples of new features (and some bug fixes) added to SailfishOS since the 2.1.1 release. The release notes of upgrade 2.1.1 (which did not roll out for all users) can be found here: https://together.jolla.com/question/164349/release-notes-211-jamsanjoki/

Accounts

  • Dropbox support migrated from deprecated to newer V2 API.

Aliendalvik

  • Updated Android Support of Jolla Tablet and Jolla C to version 1.0.69-1 (no update for Jolla1).
  • Fixed the issue of autocaps stop working after typing ca. 100 characters.
  • Fixed the issue of installing apps with apkd-install immediately after device boot up.
  • Fixed the issue of installing apps with apkd-install immediately after installing Android Support.
  • Video files sorted under correct date now, making it easier to find them for sharing.
  • Two issues with QQ aopp fixed.
  • Some inprovements to show document files (.pdf, .doc, etc.) in Android apps. This may still require using an Android file manager app.
  • GPS service for Android apps is more robust now.
  • Vibration fixed on Android messaging apps.
  • Co-operation of Tracker and Android Support at boot up improved.
  • TJC: Spotify music stream is now paused on unplugging headphones.
  • TJC: Android applications on Tablet follow the system language now.

Browser

  • Support for webM/VP8 playback in Browser/Gallery (has been there for sometime).

Connectivity

  • Network related notifications cleaned up.

Device management (MDM)

Events view

  • Weather widget can save open/close state (in events view).

Input and Keyboard

  • Allow configuring which keyboard layouts get into a customer variant.

Notifications

  • Network related notifications cleared up.

SDK

  • Warnings given by SSU when doing registration in SDK improved (when D-Bus is unavailable).

Security

  • Gstreamer vulnerabilities fixed: CVE-2017-5838, CVE-2016-9811, CVE-2017-5837, CVE-2017-5839, CVE-2017-5842, CVE-2017-5844, CVE-2016-10198, CVE-2016-10199, CVE-2017-5840, CVE-2017-5841, CVE-2017-5845, CVE-2016-9809, CVE-2016-9812, CVE-2016-9813, CVE-2017-5843, CVE-2017-5848.
  • Random generated passwords must be type twice before accepting.
  • Disabled the services of systemd that are not needed.
  • usb-moded made to supervise if something else tries to change USB control files.
  • ofono and connman logs have been protected from unauthorized access - they will not serve non-privileged processes.
  • Prevent unprivileged processes from toggling flight mode.

Settings

  • Folder creation inside sub-folders fixed.

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

Changelog

For detailed changelog, see: https://together.jolla.com/question/168138/changelog-212kiiminkijoki/

Updating your device

Your device must be connected to the Internet and signed in to 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:

  • If you use Phonehook from OpenRepos, uninstall it before upgrading.
  • If you use oFono from OpenRepos, revert to the official oFono before upgrading (or else you may face problems with LTE etc.).
  • If you have Call Recorder from Openrepos installed, uninstall it before the upgrade.
  • 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

Known issues

  • VPN implementation is still at beta level.
  • Bluetooth pairing may occasionally fail (on Jolla Tablet, in particular), or turning Bluetooth ON may fail. In such cases it is best to restart the Jolla device and try again.
  • Bluetooth pairing may fail with some car models especially in case of Jolla C devices. Sometimes synchronizing the phonebook may fail, too.
  • 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.
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-11-13 21:56:38.423213

Comments

5

@jovirkku - could you please add the size of the download, now and for future release announcements?, I may be in a minority, but I do not have WiFi at home and have limited data plans, so it would useful to know the size of the update, thanks.

Edz ( 2017-10-02 16:59:32 +0300 )edit

not visible here yet :(

tortoisedoc ( 2017-10-02 17:08:03 +0300 )edit
5

I upgraded my Jolla 1 without any trouble. I noticed that the default font is lighter, it's on purpose?

jfebrer ( 2017-10-02 18:45:42 +0300 )edit
7

Thanks for the update!

There seems to be no fix for blueborne yet though.

William ( 2017-10-02 20:06:24 +0300 )edit
3

@Edz, the size show 230 mb on my jolla 1.

Dam ( 2017-10-03 00:14:26 +0300 )edit

23 Answers

Sort by » oldest newest most voted
1

answered 2017-10-03 07:30:28 +0300

francisbbelisle gravatar image

For the first time, this released have brick my Jolla C. After fews hours, i've backup all my data and do a factory reset. Needed to update to 2.0.5.6 before update to 2.1.1.26.

Maybe it's time for Sailfish OS to update the factory reset build?

edit flag offensive delete publish link more

Comments

4

Did you uninstall the call recorder app before the update as mentioned in the release notes?

Alex ( 2017-10-03 12:15:19 +0300 )edit
1

answered 2017-10-03 13:19:20 +0300

vp gravatar image

My first attempt to download the update failed by getting stuck at about 5 %.

I shut down the phone and restarted the update. Now proceeding well at about 25 %.

While starting the first attempt, I saw no preparation phase. Now with the second attempt I saw a message about preparation. Is there some unreliability in the download process?

edit flag offensive delete publish link more

Comments

Same for me, but a restart didn't help :-/ Jolla C, after complete Factory Reset.

MoritzJT ( 2017-10-03 14:22:03 +0300 )edit
1

answered 2017-10-04 01:43:32 +0300

schmittlauch gravatar image

One minor glitch I encountered: After the automatic reboot after a successful installation, the homescreen didn't load successfully: The spinner animation which is usually shown before even the lock screen is loaded remained there for over 10min. But as both the power menu & the top-edge pull-down menu were already working, a simple reboot fixed this.

edit flag offensive delete publish link more
1

answered 2017-10-05 05:43:10 +0300

lancelin2k7 gravatar image

Has anyone been able to successfully upgrade a Turing phone?

edit flag offensive delete publish link more

Comments

Jolla has given up to update turing phone, isn't it?

Rubio ( 2017-10-11 10:20:41 +0300 )edit
0

answered 2017-10-03 10:16:43 +0300

I have updated a JP1 and a JollaCified AF from 2.1.1 recently without any problems. Thank you for the update guys!

edit flag offensive delete publish link more
0

answered 2017-10-03 11:21:28 +0300

lkraav gravatar image

updated 2017-10-03 21:04:06 +0300

My Jolla 1 is sitting at 40% SAILFISH OS progress bar overnight. It looks like it's stuck for good. What now?

EDIT After 18h, I removed battery. Fortunately, the phone managed to boot itself back to the OS, About product says 2.1 Jämsänjoki so clearly the update did not complete.

EDIT2 Cleared as much disk space as I could, Storage settings said 5,0GB free. Then re-launched update process and now it completed successfully. Phew!

edit flag offensive delete publish link more
0

answered 2017-10-03 12:35:52 +0300

mono gravatar image

Strange, i upgraded Jolla1 to 2.1.2.3 and i have no network connection except of rndis0 (USB) anymore. After i logged in shell and started connmand manually, WIFI was enabled and i could connect, but it stop immediately again:

Oct 03 11:17:22 Sailfish wpa_supplicant[2313]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
Oct 03 11:17:22 Sailfish wpa_supplicant[2313]: wlan0: WPA: Key negotiation completed with 34:31:c4:f7:ff:f5 [PTK=CCMP GTK=CCMP]
Oct 03 11:17:22 Sailfish wpa_supplicant[2313]: wlan0: CTRL-EVENT-CONNECTED - Connection to 34:31:c4:f7:ff:f5 completed [id=0 id_str=]
Oct 03 11:17:22 Sailfish kernel: wlan: [2313:E :SME] sme_FTUpdateKey: Unhandled state=0
Oct 03 11:17:22 Sailfish kernel: wlan: [2313:E :SME] sme_FTUpdateKey: Unhandled state=0
Oct 03 11:17:22 Sailfish connmand[2299]: Can not request DHCP lease
Oct 03 11:17:22 Sailfish kernel: wlan: [2313:E :SME] csrRoamIssueDisassociateCmd: 6197:   reason = 0
Oct 03 11:17:22 Sailfish kernel: wlan: [2313:E :SME] csrNeighborRoamIndicateDisconnect: 3033: Disconnect indication on session 0 in state 2 (sub-state 12)
Oct 03 11:17:22 Sailfish kernel: wlan: [2313:E :TL ]  ----> CRegion 0, hRSSI 0, Alpha 5
Oct 03 11:17:22 Sailfish kernel: wlan: [575:E :PE ] limSendDisassocCnf: 3798: FT Preauth Session (eebe8000,0) Cleanup
Oct 03 11:17:22 Sailfish wpa_supplicant[2313]: wlan0: CTRL-EVENT-DISCONNECTED bssid=34:31:c4:f7:ff:f5 reason=3 locally_generated=1
Oct 03 11:17:23 Sailfish kernel: wlan: disconnected
Oct 03 11:17:23 Sailfish kernel: wlan: [575:E :SME] csrNeighborRoamIndicateDisconnect: 3033: Disconnect indication on session 0 in state 1 (sub-state 0)
Oct 03 11:17:23 Sailfish kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 03 11:17:23 Sailfish wpa_supplicant[2313]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 03 11:17:23 Sailfish kernel: ieee80211 phy0: info: cfg80211 reg_notifier callback for country 00
Oct 03 11:17:23 Sailfish kernel: cfg80211: World regulatory domain updated:
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
Oct 03 11:17:23 Sailfish kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
Oct 03 11:17:33 Sailfish kernel: wlan0: no IPv6 routers present

and ofono does not find any modem:

Oct 03 11:12:24 Sailfish ofonod[3256]: oFono version 1.19
Oct 03 11:12:24 Sailfish systemd[1]: Started Telephony service.
-- Subject: Unit ofono.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit ofono.service has finished starting up.
-- 
-- The start-up result is done.
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Novatel modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Sierra modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding ZTE modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Icera modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Huawei modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Calypso modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding MBM modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Telit modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding HSO modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Infineon modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding STE modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Dialup modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Hands-Free Profile Driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding SpeedUp modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Phone Simulator driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding CDMA AT modem driver
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding External Hands-Free Profile Plugin
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Dial-up Networking Profile Plugins
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding BlueZ 5 Utils Plugin
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding Hands-Free Audio Gateway Profile Plugins
Oct 03 11:12:24 Sailfish ofonod[3256]: Excluding CDMA provisioning Plugin
Oct 03 11:12:24 Sailfish statefs[565]: There is(are)  0  modems
Oct 03 11:12:24 Sailfish simkit[1361]: [D] unknown:0 - updating .desktop 0
Oct 03 11:12:30 Sailfish dbus[573]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.96" (uid=0 pid=3256 comm="/usr/sbin/ofonod -n --nobacktrace --noplugin=he910") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownObject" requested_reply="0" destination=":1.13" (uid=0 pid=652 comm="/usr/bin/fastdormancyd ")
edit flag offensive delete publish link more

Comments

Are you using any special TOH?

nthn ( 2017-10-03 12:55:55 +0300 )edit

Jep, TOHKBD., Edit: I downgraded to 2.1.1.26 and that worked fine with all network connectivity back.

mono ( 2017-10-03 13:04:49 +0300 )edit
4

It was known issue in 2.1.1 that you needed to detach your TOH before rebooting your device, otherwise network would not work. Sounds like it isn't fixed yet.

nthn ( 2017-10-03 17:14:57 +0300 )edit

@nthn you're correct. Without, updating working.

mono ( 2017-10-03 20:41:32 +0300 )edit
0

answered 2017-10-03 19:00:44 +0300

polarphone gravatar image

updated 2017-10-03 19:01:31 +0300

Maps fails for J1. J1 is denied installation or fails maps. Could it be a bug that J1 is treated as a device without licence for 'maps;. Much greateful if fix could found soon. Otherwise thank you jolla for an improved release.

edit flag offensive delete publish link more

Comments

1

My J1 also lost maps during update, and re-installing it failed. After a restart it installed fine!

MystIsland ( 2017-10-03 19:23:24 +0300 )edit

@MystIsland likewise a reboot resolved it for me.

GD ( 2017-10-03 23:57:44 +0300 )edit

@MystikIsland Thank you reboot fixed it

polarphone ( 2017-10-04 00:08:41 +0300 )edit

It's not the reboot that solved it (I had already tried that), it's the fact that Jolla fixed the repos ;)

Sthocs ( 2017-10-04 11:47:30 +0300 )edit
0

answered 2017-10-03 22:15:55 +0300

polarphone gravatar image

@MystIsland Thank you reboot and reinstalled worked. Funny thing is that I rebooted after installation :)

edit flag offensive delete publish link more

Comments

1

Actually what fixed it is Jolla, which updated the repos :)

Sthocs ( 2017-10-04 11:51:00 +0300 )edit
0

answered 2017-10-10 15:07:54 +0300

eatdirt gravatar image

Dear Jolla,

thank you for this update and to have bricked my Jolla 1 phone :(((((((

I have followed exactly the recommendations, unapply all patches, uninstalled CallRecorder. I had plenty of free space on the device and I updated from 2.0.1.11.

The update failed after a while saying that I should try later on, press the only displayed button, "OK", and my phone rebooted without reaching any usable state.

You're are really doing good these days, last update disappeared after a while and now the supposedly big update fixing many bugs is a big bug itself!

Thanks, most promising for Sailfish X.

All the best, Chris.

edit flag offensive delete publish link more

Comments

1

have you tried unbricking with recovery?, it may not be completely dead.

Edz ( 2017-10-10 17:38:49 +0300 )edit
1
2

'without reaching any usable state' is vague enough to mean nothing at all. If you're looking for help, you could try to describe at which point it stops doing what it's supposed to do.

nthn ( 2017-10-10 23:29:07 +0300 )edit
1

Update also failed for my JP1, I am dumping parts to sd before factory reset

rzr ( 2017-10-11 02:36:49 +0300 )edit

At rzr, exactly what I had to do, factory reset and all the way up to latest release.

Scandalous!

eatdirt ( 2017-10-12 00:11:20 +0300 )edit

Question tools

Follow
23 followers

Stats

Asked: 2017-10-02 11:59:11 +0300

Seen: 18,033 times

Last updated: Oct 26 '17