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

Spam Hunter ( 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
0

answered 2017-10-26 12:15:40 +0300

Rubio gravatar image

TuringPhone really needs to be updated! The current version 2.0.4.14 is too old! Does Jolla give up updating TuringPhone?

edit flag offensive delete publish link more

Comments

I think the best option is to ask Jolla about that during meeting https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/

atlochowski ( 2017-10-26 13:22:17 +0300 )edit
4

It's not Jolla, but Turing who is responsible for keeping their phone up to date, so you should complain to Turing.

nthn ( 2017-10-26 15:59:18 +0300 )edit
2

answered 2017-10-15 10:57:56 +0300

mister gravatar image

This is the first time I have issues with an update on my Jolla 1, where I don't have any hacks/openrepos stuff applied. It is stuck at 0% for obout 22 hours now. What should I do, wait some more time? Or force reboot by removing battery? Or something else?

edit flag offensive delete publish link more

Comments

@mister i would advise you to post a question for that, not an answer in the release notes. besides this just being the wrong place, only few people will see it here

misc11 ( 2017-10-15 13:14:55 +0300 )edit

It happened to me once, in the end I removed the battery and the device booted normally. Second update attempt worked without issue.

Sthocs ( 2017-10-16 13:37:23 +0300 )edit

Issues with Dual sim aquafish. 1. The Bluetooth gets connected to the car but does not work with Sim2. 2. On Bluetooth when one makes a call out using Sim1 as default the phone used sim2 instead and got billed for the call. 3. Weather display on the home screen does not connect to internet even restarting the phone does not help.

I will raise these as bugs later.

TheOwlEye ( 2017-10-16 20:12:50 +0300 )edit
0

answered 2017-10-13 22:37:48 +0300

nomeata gravatar image

Upgrading to this version (from 2.0, I presume, I missed the discontinued 2.1 release) broke the WPA connections that I had configured for connman. There is now a UI to enter username and password, but it does not actually succeed to connect.

edit flag offensive delete publish link more

Comments

2

Remove the manually created configuration files, disable/enable WLAN, enter the login details for your network and it should work.

nthn ( 2017-10-14 00:47:51 +0300 )edit
4

answered 2017-10-13 11:30:17 +0300

jloup06 gravatar image

updated 2017-10-14 19:39:21 +0300

Hi Jolla, Still no update on my Jolla 1. I currently use SFOS 2.1.1.26. I install 2.1.1.26 during the short public roll out period. Is it normal (phased roll out) ? Need be patient, or a bug exist ? Thanks for your answer.

Edit : update is available for me today (october 14th)

edit flag offensive delete publish link more

Comments

2

Same here, I'd love to know if 2.1.2 rollout is still ongoing, finished (something'w rong on my side) or ceased (update withdrawn)

Xeno_PL ( 2017-10-13 12:29:48 +0300 )edit
1

Me too. It never took so long, I wonder why...

IZ1IVA ( 2017-10-13 18:08:56 +0300 )edit
7

Sorry about this. There was entry for 2.1.1.26 for preventing it from offering downgrade when we halted the 2.1.1 roll out. Unfortunately that was also blocking the update notification now. This has now been fixed and you should be able to get 2.1.2.3.

Keto ( 2017-10-14 11:40:56 +0300 )edit

Thanks @Keto

IZ1IVA ( 2017-10-15 01:20:54 +0300 )edit
0

answered 2017-10-11 20:46:31 +0300

ExTechOp gravatar image

On my JollaC updating initially failed twice after loading it (luckily I'm on a very fast Wifi connection at work) with "Sailfish OS could not be updated. Please try again later. Press [OK] to reboot." I noted that the display had switched off during the update process, and I set it not to switch off while the phone is connected to a charger. This time the update went through.

I also had this same issue with the previous OS update, and solved it the same way. Anyone else see this pretty strange problem?

edit flag offensive delete publish link more

Comments

it is a known problem with installed patches. i guess you have them too. if not, this would be kind of new. i have this issue every update. just search on tjc

misc11 ( 2017-10-11 21:24:12 +0300 )edit

It's always something that was installed via OpenRepos, be it patches, applications, libraries, etc. Sometimes it works on the first try, sometimes after a couple of tries, usually it doesn't and you have to update through the command line.

nthn ( 2017-10-11 21:53:37 +0300 )edit
6

answered 2017-10-11 20:22:31 +0300

olf gravatar image

updated 2017-10-13 22:28:06 +0300

The "release to all" of SailfishOS 2.1.2.3 was a couple of days ago (2017-10-09), but checking manually under Settings > Sailfish OS updates still states "Up to date" on two Jolla 1 phones under 2.1.1.26!?!

While I could update at the command line, I wonder what is wrong here?

edit flag offensive delete publish link more

Comments

Same here.

orol ( 2017-10-11 20:35:45 +0300 )edit

Same here...

abanai ( 2017-10-11 20:45:20 +0300 )edit

Same here...

sunkan ( 2017-10-11 21:31:42 +0300 )edit
1

From the release notes:

 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.
nthn ( 2017-10-11 21:48:59 +0300 )edit
1

@nthn, fair enough. Let me phrase it this way then:

This is taking longer than expected (i.e. more than two days) and has not happened on any release before (as far as I remember).

When is SailfishOS 2.1.2.3 supposed to be available for all users (via the regular GUI way)?

olf ( 2017-10-12 02:45:19 +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.

Spam Hunter ( 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
2

answered 2017-10-06 22:00:29 +0300

florifreeman gravatar image

Except for the missing keyboards, everything went fine! A shame that Alien Dalvik did not get an Update again on JP1!

edit flag offensive delete publish link more

Comments

3

AFAIK (we need confirmation from official from within Jolla Oy) :

  • Because Alien dalvik relies on the bits present in the actual Kernel and libs, and upgraded (Kit-kat based) Alien Dalvik would require an Kit-kat compatible update kernel and drivers than what is currently availble on the Jolla. (On the other hand, there are a couple of other smartphone with similar or identical chipset that got a port of Kitkat, so somewhere Qualcomm must be in possession of an appropriate kernel/driver set).

  • Alien Dalvik is a commercial closed source product. And Jolla 1 is an old device. It might be that the licensing agreement between Jolla Oy and Myriad doesn't cover upgrades to Jolla 1 smartphone.

DrYak ( 2017-10-07 22:41:16 +0300 )edit
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
2

answered 2017-10-04 23:12:41 +0300

hoschi gravatar image

Connecting to mobile data service harmonized

Please elaborate?!

edit flag offensive delete publish link more

Comments

Maybe they sang gumbayaa ... =)

olli ( 2017-10-06 21:47:33 +0300 )edit

Feel like...

hoschi ( 2017-10-06 22:21:47 +0300 )edit

Question tools

Follow
22 followers

Stats

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

Seen: 18,578 times

Last updated: Oct 26 '17