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

[release notes] 2.1.4 / Lapuanjoki [released]

asked 2018-02-15 13:59:39 +0300

jovirkku gravatar image

updated 2018-06-05 15:50:44 +0300

Update version history

  • 2018-02-20: 2.1.4.13 was released to Early Access subscribers. Japanese and Korean removed from the list of new languages (not yet quite ready).
  • 2018-02-28: 2.1.4.14 was released to Early Access subscribers. BT audio issue on Jolla1 fixed.
  • 2018-03-06: 2.1.4.14 was released to all Jolla users (Jolla1, Jolla Tablet, Xperia X). Aqua Fish and Inoi R7 are pending customer acceptance.
  • 2018-03-13: 2.1.4.14 was released to all Aqua Fish and to all Jolla C users.

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 C from 2.1.3.7 to 2.1.4.13: 380 MB
- Jolla 1 from 2.1.3.7 to 2.1.4.13: 340 MB
- Xperia X from 2.1.3.7 to 2.1.4.13: 390 MB

Release Highlights

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

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

Accounts

  • CalDav syncing getting stuck fixed
  • CalDav reminders no longer trigger twice after sync
  • Dropbox account creation failure fixed (recent regression)
  • Active Sync settings UI polished
  • Weather service in Events View now tracks network connectivity status, and automatically refreshes when connectivity is regained.

Aliendalvik

  • Updated Android Support of Xperia X from version 1.0.79-1 to 1.0.85-1 (no update for Jolla devices), fixing:
  • Add support for camera HAL introduced in Android 7.
  • Prepare for notification improvements.
  • Update device configurations.
  • Improve camera startup speed on Android 7 based devices.
  • Solved an issue where certain apps (i.e. Wechat) were unable to record voice messages.

Bluetooth

  • SyncML support dropped.

Browser

  • Browser cover no longer flickers during device orientation change.

Camera

  • Camera app is launched if shutter key is long-pressed (does not work on lock screen yet)
  • Photo details fixed for Camera photos stored in SD card.

Connectivity

  • WLAN: support for IEEE802.11r enabled. This brings the Fast Transition feature. It is meant to allow faster handoffs for a mobile station between two or more Access Points, a sort of handover for WLAN.
  • Homescreen crash fixed that sometimes happened when connecting to WLAN.

Device management (MDM)

  • Activation displays a disclaimer to user
  • Date and time API extended to support all time zones.

Email

  • Fix a crash when an attachment is opened second time
  • Fix search losing focus after backstepping from Email viewer
  • Downloaded attachments can now be picked as attachments for new emails.

Facebook

HW adaptation

  • Xperia: support of BTRFS filesystem for SD cards added
  • Xperia: low memory killer enabled.

Keyboard

  • Hungarian and Slovenian layouts added.

Languages

  • New system languages: Chinese (Taiwan), Czech, Dutch, Estonian, Greek, Hungarian, Portuguese (Brazil), Slovenian, Spanish (Bolivia), Turkish.
    Many thanks to you our valued community people for the translations!

Media

  • Show the correct playback state when the playlist playback stops
  • Order music albums by date released, instead of alphabetically.

Messages

  • Send button in Messages app touch area enlarged for easier use.

Middleware

  • Qt framework updated 5.6.3, including hundreds of bug fixes
  • Tracker updated to the latest V1 version to possibly fix some metadata extraction failures.

Notes

  • Search is now supported.

Notifications

  • Notification banners can now be swiped away with horizontal flick.

OS updates

  • PackageKit framework upgraded to newer version
  • OS updates are now a privileged operation run as proper system-side service
  • OS update process rewritten to reduce dependencies and thus potential causes of failures
  • OS update descriptions now support links.

SDK

  • Enable (hint) showing apps in fullscreen on emulator
  • Resize mode set for created views to resize root object conveniently.
  • App icon size variant 172x172px introduced for Full HD displays
  • 3rd party app icons finally scale properly to different display resolutions.

Security

  • kernel: CVE-2014-9785, CVE-2014-9787, CVE-2014-9864, CVE-2014-9865, CVE-2014-9884, CVE-2014-9887, CVE-2014-9894, CVE-2017-9077, CVE-2016-5340, CVE-2017-1000364, CVE-2015-7872, CVE-2013-7446, CVE-2016-6786, CVE-2016-6787, CVE-2017-5970, CVE-2016-8480, CVE-2015-7550, CVE-2017-7618, CVE-2015-8767 (not yet fixed in jolla1 aka sbj)
  • kernel: CVE-2017-8890, CVE-2017-11176. (fixed in all kernels: jolla1 is patched)
  • display driver: CVE-2014-4323 (not yet fixed in jolla1 aka sbj)
  • bluez: CVE-2016-7837
  • libav: CVE-2015-8365, CVE-2017-9992, CVE-2017-7862, CVE-2015-8365.

Startup and shutdown

  • Patch for systemd (provided by our community) integrated to reduce logging.

System

  • Low memory killer enabled on Xperia. This should help preserving an adequate amount of free RAM.

Utilities

  • relocated in development repositories to make the app resistant against API changes.

UX

  • Android device hardware keys mapped to Silica actions of Sailfish OS on Jala Accione devices.

WLAN

  • automatic reconnection to saved hidden WLAN network
  • WLAN hotspot a.k.a. internet sharing fixed (Xperia).

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

Changelog

For detailed changelog, see https://together.jolla.com/question/179224/changelog-214-lapuanjoki/ .

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:

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

PLEASE NOTE:

If you installed 2.1.4.12 update manually from command line you need to do the following fix to get the repositories working:

[nemo@Sailfish ~]$ devel-su 
Password: 
[root@Sailfish nemo]# sed -ie 's/releases-internal.jolla.com/releases.jolla.com/' /usr/share/ssu/repos.ini 
[root@Sailfish nemo]# ssu ur

NOTIFICATIONS CONCERNING APPS FROM OPEN REPOS:

Installing OS update 2.1.4 automatically removes **Warehouse** (versions <= 0.3) and **Storeman** (versions <= 0.0.15) applications.

This is necessary because 2.1.4 brings in the new PackageKit that has changed its API. Warehouse and Storeman are locked against the older version of the library. If they are not removed during the update, they block the upgrade of PackageKit-Qt5, which then breaks all further updates (Settings page would get stuck on 'Preparing update' and version --dup would fail with an InvalidArgs error).

Warehouse and Storeman can only be installed again after they switch to the new PackageKit API.

In addition, take the following advice into account:

  • 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.

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

  • NEW: Jolla1 cannot route audio signal to Bluetooth accessories. => Fixed in 2.1.4.14.
  • Bluetooth pairing and audio connections may still fail in some circumstances
  • Utility "Clear tracker database" ("Refresh media database") is failing - will be fixed in update 2.2.0 (the next one)
  • VPN is still at beta level.

Known issues specific to Xperia X

  • Screenshots are placed to the end of the thumbnails list if Gallery app is open while taking the screenshot.
  • Issues with mobile data persist on some SIM cards
  • Xperia X does not power up due to an alarm
  • 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. (still valid with most SIM cards)
  • VPN does not work.
  • Bluetooth: still problems with car equipment, some audio devices and computers.
  • Waking up the device by double-tap does not work
  • Loudspeaker volume level cannot be adjusted high enough (but echo cancellation was added to the audio path in 2.1.4)
  • Sensors:
    • not working: fingerprint, barometer, step counter.
    • compass (or gyro?) working in Google Maps, not yet natively.
  • 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 close delete

Comments

4

Hmmm... Bluetooth nightmare still not fixed or at least improved for Xperia X? I thought I could read it somewhere that this topic was on the list. Hopefully the X can be used now finally.

Anyway many thanks for this large new update package ;)

vision ( 2018-02-20 11:13:31 +0300 )edit

swap memory not enable?

TMavica ( 2018-02-20 11:40:34 +0300 )edit
4

For me on Xperia X, great update. Thanks for fixing internet sharing.

lispy ( 2018-02-20 16:09:02 +0300 )edit
1

Hungarian keyboard! Finally - thank you!

zlutor ( 2018-02-20 17:04:28 +0300 )edit
2

I have been waiting to see Sailfish in my own language for 4 years and 2 months! Thank you, Jolla! Too bad, my The First One does not live to see it.

Anyways, thank you! Köszönöm, LVPVS

LVPVS ( 2018-02-20 19:08:02 +0300 )edit

30 Answers

Sort by » oldest newest most voted
0

answered 2018-02-20 18:09:51 +0300

p1rat gravatar image

hello,

tried to update, but the "Preparing Update" runs endless.

How long does it normaly take?

then I tried to force the update via terminal as root:

"# version --verify

"# ssu release 2.1.4.13

Changing release from 2.1.4.13 to 2.1.4.13

Your device is now in release mode!

"# version --dup

REFRESHING CACHE AND DOWNLOADING PACKAGES [W] PackageKit::Transaction::parseError:803 - Transaction::parseError: unknown error "org.freedesktop.DBus.Error.InvalidArgs"

and my phone came to following error.

Does anyone know what this error mean and how to fix it?

regards christian

edit flag offensive delete publish link more

Comments

Usually invalidArgs is mismatch between old and new packagekit vs packagekit-qt packages. For example system otherwise updated but something like those warehouse and storeman openrepos things forcing old packagekit-qt version. Can also be system updated with version --dup and not being rebooted so old packagekitd is still running.

Pekka Vuorela ( 2018-02-20 19:21:44 +0300 )edit

I think you have to remove Warehouse and Storeman. It's in the release notes actually.

Direc ( 2018-02-21 23:35:16 +0300 )edit

@Direc: they're automatically removed if they're incompatible.

nthn ( 2018-02-22 13:43:13 +0300 )edit
0

answered 2018-02-20 18:17:38 +0300

Lutwolf gravatar image

Dammit, updating bricked my Jolla 1.

I couldn't update via GUI ("Please try again later"), so I did that in Terminal (everything as Jolla itself suggests, and I didn't have any typos). The phone tried to update 10 times before it aborted - there was a brief message that a certain rpm couldn't be found. There was a "restart on your own risk" message, and after restarting there's only a slowly flickering white screen. The /var/log folder was empty, and there was no /home/ folder in Recovery Putty Telnet mode (maybe relevant, maybe not). What can I do? Is factory reset my only option?

edit flag offensive delete publish link more

Comments

recovery mode does not mount home or system as far as I know

idnovic ( 2018-02-20 18:27:27 +0300 )edit

Is there a way to mount /home/ to either a) fix the system or b) recover and save user data not saved on SD?

Lutwolf ( 2018-02-20 20:36:41 +0300 )edit
2

yes but I do not remember top of my head. How familiar are you with linux? home and system are one lvm device. Here is what I did (as far as I remember); mount lvm (home + system); chroot into system; reroute network to have internet over usb; at this stage you can even install/uninstall apps over terminal;

here is a partly useable guide: https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode and https://together.jolla.com/question/114716/what-is-the-tablets-fs-and-partition-scheme/?answer=114743#post-id-114743

idnovic ( 2018-02-20 20:57:34 +0300 )edit

Thank you, I already did that short while after writing above text ^^ Next time I'll read before I write, resp. torture the internet more purposefully :)

Lutwolf ( 2018-02-20 21:29:41 +0300 )edit
0

answered 2018-02-21 23:52:19 +0300

RodSeq gravatar image

updated 2018-02-21 23:58:23 +0300

Thanks for this update ! For next 2.1.4.x, please remove the touchscreen Kalman filter by default on Jolla C / Aqua Fish !!!

edit flag offensive delete publish link more

Comments

I haved filed a task about this for the UI experts. Let's see what can be done.

jovirkku ( 2018-03-06 09:33:34 +0300 )edit
0

answered 2018-02-22 09:51:37 +0300

Geert gravatar image

I have installed the Dutchlanguage pack from Open Repos. So as i well read : this will cause no problems because the update will automatically remove this, and install the new option. Or am I wrong and do i have to perform another action?

edit flag offensive delete publish link more

Comments

It isn't automatically removed, but it causes no problems, and you can safely remove it manually.

nthn ( 2018-02-22 13:40:18 +0300 )edit

thnkx , because is causes noproblems i will leave it as it is

Geert ( 2018-02-23 09:38:16 +0300 )edit
1

@Geert: Dutch (Nederlands) language is included in Sailfish 2.1.4.

jovirkku ( 2018-02-27 13:09:49 +0300 )edit
0

answered 2018-02-22 17:05:06 +0300

ds1979 gravatar image

How can I get rid of the announcement on the screen? I cannot make a long tap and then tap on X to delete it. If BT is not working on my J1, it doesn't make sense to me to make an upgrade, right?

edit flag offensive delete publish link more

Comments

Announcements (notifications) can be swiped away sideways.
The only thing (we are aware of) that got broken with BT on J1 while developing 2.1.4, was audio routing. It has been fixed to 2.1.4.14 (going to be published in near future).

jovirkku ( 2018-02-27 13:15:38 +0300 )edit

@jovirkku - I think the OP is referring to the OS upgrade notification, which to my knowledge cannot be removed/swiped away.....or is that now removable as well? (I don't know as I have already upgraded to 2.1.4).

Spam Hunter ( 2018-02-27 13:53:53 +0300 )edit

@Edz: yes you are right.
Well, there was no change here: the OS update notification remains in the Events view until the update has been installed. The notification cannot be wiped away. It stays as a reminder to use the latest OS version.

jovirkku ( 2018-03-06 09:54:39 +0300 )edit

I found - yet again - that the upgrade notification returned even after the upgrade (early access on J-C). I tapped it and re-upgraded today and it still came back again. I know there are lots of threads about this - it's been 'fixed' several times - and several suggestions of how to remove it. But I can't be bothered - I'll just ignore it - until the next update.

DaveRo ( 2018-03-09 19:22:42 +0300 )edit
0

answered 2018-02-27 12:19:49 +0300

arcadia gravatar image

Hi, I have some problems with new sailfish. My Jolla 1 restart much time if read immediately the sim after the pin code, and camera video when I recorder or answer a call the phone automatically shutdown. I try to restore my phone and update again but I still have this error.

edit flag offensive delete publish link more

Comments

0

answered 2018-03-09 16:38:17 +0300

Malkavian gravatar image

Cannot update. It always say to try later. Last lines of /var/log/systemupdate.log:

Mar 09 15:32:56 Sailfish packagekitd[4921]: Before commit: 873 downloads, 873 installs, 1 removals Mar 09 15:32:56 Sailfish packagekitd[4921]: Byte sizes: 488671224 download, 1140409737 install, 1132796152 remove, 0 cached Mar 09 15:32:56 Sailfish packagekitd[4921]: Download space required 488671224 bytes, available 4769579008 bytes Mar 09 15:32:56 Sailfish packagekitd[4921]: Installation space required 7613585 bytes, available 4769579008 bytes Mar 09 15:33:05 Sailfish store-client[5023]: [D] unknown:0 - void PackageHandler::slotUpgradeProgress(int) 10 Mar 09 15:33:05 Sailfish store-client[5023]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotPackage(PackageKit::Transaction::Info, const QString&, const QString&) 10 "harbour-meecast;1.1.15-4;armv7hl;store" "Weather forecast application for SailfishOS" Mar 09 15:33:05 Sailfish store-client[5023]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&) Mar 09 15:33:06 Sailfish kernel: PK-Backend(4921) send signal 9 to ssu(5233) Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotTransactionError(PackageKit::Transaction::Error, const QString&) 4 "Installation aborted by user\n" Mar 09 15:33:06 Sailfish mce[653]: modules/display.c: mdy_datapipe_packagekit_locked_cb(): packagekit_locked = 0 Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotTransactionFinished(PackageKit::Transaction::Exit, uint) 2 11796 Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - void PackageHandler::slotUpgradeFailure(const QString&) "Installation aborted by user\n" Mar 09 15:33:06 Sailfish store-client[5023]: [D] expression for onOsUpdateResult:55 - System upgrade failed! Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - Wrapped transaction failed: "Installation aborted by user\n" Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - Resetting ssu version Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - void Package::RepositoryTransactionPkgKit::setSsuVersion(const QString&) new version "2.1.3.7" current version "2.1.4.14" Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - changing SSU release: "2.1.3.7" Mar 09 15:33:06 Sailfish store-client[5023]: [D] unknown:0 - virtual Package::DistUpgradeTransactionPkgKit::~DistUpgradeTransactionPkgKit()

edit flag offensive delete publish link more

Comments

Uninstall meecast and try to update again.

atlochowski ( 2018-03-09 18:10:54 +0300 )edit

Thanks for your reply. I had already tried removing Situations. Then said that, so I tried to remove and reinstall harbour-meecast and did nothing. I tried to remove it as you said and now it say the same about file-browser. No time now for continue trying this way, but I will do. If you had another idea or want me to send some data which could help, tell me please. Log about file-browser:

Mar 09 17:31:24 Sailfish store-client[5096]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotPackage(PackageKit::Transaction::Info, const QString&, const QString&) 10 "harbour-file-browser;1.7-0;armv7hl;store" "File Browser for Sailfish OS"

Malkavian ( 2018-03-09 18:36:30 +0300 )edit

I got the update going by installing the latest update for File Browser and by executing a "pkcon refresh" in the Terminal.

MeegoUser ( 2018-03-09 19:52:54 +0300 )edit

Uninstalled harbour-file-browser, downloaded update again ¬¬, updating.... error, now it talks about harbour-sailseries. Uninstalled, downaload AGAIN ¬¬, updating... It worked finally! Thank you

Malkavian ( 2018-03-10 18:38:19 +0300 )edit
0

answered 2018-03-12 22:03:22 +0300

DarkTuring gravatar image

Ambiences lost (no patches installed) through normal use and when switching between ambiences.
Email webview and browser loads sometimes lagging or where UI actions seem stuck/frozen.

edit flag offensive delete publish link more
0

answered 2018-03-13 10:44:28 +0300

Raymaen gravatar image

https://together.jolla.com/question/177397/xperia-x-roaming-does-not-show-local-operator-and-does-not-show-connection/

https://together.jolla.com/question/175003/bug-fixed-mobile-network-gets-lost-crossing-borders/?sort=votes&page=1

https://together.jolla.com/question/168570/connection-problems-while-roaming-with-automatic-network-selection/

The above mentioned Problems are stil not fixed! It is not like it is mentioned in the update info.

edit flag offensive delete publish link more
0

answered 2018-03-15 01:37:52 +0300

ing gravatar image

My Xperia X frequently hangs with this update. Before 2.1.4 it was rock solid. Now it hangs so much the phone is essentially useless. I have had it hang in both Browser and Email (with only that app running) as well as other apps. Both 2.1.4.13 and 2.1.4.14 have this issue.

Sometimes if I leave the phone long enough (on the order of 10+ minutes) it will come back. Sometimes it just gets really hot and runs down the battery.

edit flag offensive delete publish link more

Comments

I started to get randomly closing applications, so I created and enabled a 2GB swap file on my memory card. Zero issues since. Your internal memory may be full, too. Do you have a lot of Android apps installed? Some (namely Facebook) tend to suck up a lot of RAM.

Direc ( 2018-05-13 21:17:18 +0300 )edit
Login/Signup to Answer

Question tools

Follow
20 followers

Stats

Asked: 2018-02-15 13:59:39 +0300

Seen: 31,107 times

Last updated: Jun 05 '18