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

[release notes] 2.1.1 / Jämsänjoki [released]

asked 2017-07-24 12:40:33 +0300

jovirkku gravatar image

updated 2017-10-02 21:55:27 +0300

olf gravatar image

Jämsänjoki update fixes dozens of bugs reported by our community, adds many improvements and new corporate features, like mobile device management (MDM), new Camera user interface with quick access from Lock Screen, smarter Calendar on Events, WPA2 Enterprise PEAP support, new VPN options (PPTP, L2TP), Bluez version 5 for Jolla C and much more.

Thank you for your contribution in improving Sailfish OS!

PLEASE NOTE: This is a BIG update as some major libraries have been touched. Therefore 1) Keep your device connected to a charger. 2) Wait patiently - the download may take tens of minutes.
-- If you have Call Recorder from Openrepos installed, uninstall it before the upgrade.

Upgrade version history

  • 2017-07-24: 2.1.1.23 Released to Early access subscribers
  • 2017-07-28: 2.1.1.24 Released to Early access subscribers
  • 2017-08-24: 2.1.1.26 Released to Early access subscribers. OpenVPN improved.
  • 2017-08-29: 2.1.1.26 Released to all. [Roll out ceased on Aug 31 for now due to few problem cases with the security code. We are investigating the issue.]
  • 2017-09-20: Decided to discontinue the roll out of 2.1.1. We will focus on finalizing 2.1.2.

Release Highlights

This list contains examples of new features added to SailfishOS since the 2.1.0 release (and some bug fixes).

Aliendalvik [on Jolla C devices: version 1.0.63]

  • Fixed issues in using Facebook Messenger over a mobile data connection
  • Android music apps now publish music artist to Lock Screen.
  • Backspace now deletes the selected URL in browser search bar (Android browsers like Chrome or Opera)
  • Text editor character input behavior aligned with native Sailfish OS, including fixes for word suggestion, autocorrection and line break input cases.
  • Issues related to adding contacts with website item fixed.
  • WhatsApp conversations now show correct timestamps.
  • Alien Dalvik fixed to better respect Sailfish OS location settings
  • Reception of notifications and notification sounds for android apps fixed.
  • Stagefright vulnerability CVE-2015-6602 fixed.
  • An issue of some Android apps getting killed when user taps on their notifications on Events view fixed.
  • Frequent crashes of Alien Dalvik's background processes caused by Qt 5.6 upgrade fixed, causing instabilities with many sub-services like audio, haptic, lights and notifications.
  • Some Android apps not always seeing the new pictures issue fixed.
  • OpenSSL upgraded to 1.0.1j to fix Alien Dalvik's OpenSSL vulnerabilities (CVE-2015-4000, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1791, CVE-2014-8176, CVE-2015-1793).
  • Some missing default Android sounds included fixing notification tone playback issues.
  • Clearing Android app data now shows remorse popup.
  • Android app settings now display how much disk space the app requires, i.e. Android app, data, cache and total sizes.

Audio

  • Routing low quality audio (8 kHz mono) to Bluetooth headsets not meaningful - SCO audio disabled for media use cases (non-call).
  • Dedicated PulseAudio configurations for Bluez4 and Bluez5.
  • PulseAudio extended to support Android 6.
  • Voice calls fixed to work with Bluez5 HSP/HFP.
  • Added support for HSP profile audio with Bluez5.

Bluetooth

  • Bluez5 taken into use on Jolla C devices. Bluez4 remains the default on Jolla 1 and Jolla Tablet. ( http://www.bluez.org/about/ )
  • Support for voice calls with Bluez 5 HSP/HFP.
  • Enabled FTP profile in Obex / BlueZ 5.

Browser

  • Text selection markers are now cleared when opening a new tab
  • Password saving works again
  • Smaller bug fixes.

Camera

  • New Camera interface introduced with easier access to camera/video and front/back camera toggles.
  • Taking pictures without unlocking device. Camera can be brought up by a swipe up from the lockscreen. The new shortcut is optional and can be disabled in Settings > Gestures.
  • Viewfinder's focus lock duration shortened from 10 to 5 seconds, and the general focus handling improved.

Connectivity

Customization and configurability

  • Improved configurability for different vendors. Now vendors can drop more easily things like Developer Mode, Sideloading, Store and Sailfish OS updates.
  • Device security lock can be configured according the vendor security requirements: maximum and minimum code length, locking timeout, expiration, maximum attempts
  • Vendor can enforce OpenSSL-based secure code generation
  • Startup wizard made configurable to allow customer modifications.

Device management (MDM)

  • https://en.wikipedia.org/wiki/Mobile_device_management
  • Remote device management APIs introduced for Device Lock, Location, Connectivity, Notifications, SIM and System, OS Upgrades and SW Management
  • Policies added for Camera, Location Settings, OS Updates, Side Loading, Developer Mode Settings, WLAN, Internet Sharing and Device Reset
  • Device management is not enabled or even installed on vanilla Sailfish OS devices.

Email

  • Email app now starts faster.

Events view

  • Upcoming calendar events from the following days also shown.

Flashing

  • Ability to enable/disable fastboot flashing in Settings > Developer mode on developer devices (e.g. Jolla C).
  • Issue with Gallery hanging if screenshot is taken while certain Gallery app views are open fixed.

Input and Keyboard

  • Tatar language added.

Localisation

  • Tatar language added.
  • Russian time zones updated.
  • Date picker now handles Sydney timezone correctly.

Messages

  • Google Talk support removed due to Google dropping support for Google Talk XMPP
  • Draft message recipients can now be modified.

Notes

  • Notes cover layouts polished for different display sizes.

Office

  • Performance enhancements on PDF files: PDF table of contents is now loaded in the background as it can take time. PDF search was changed to process document incrementally, making it faster to start showing matches.

Phone

  • Repeatedly tapping Call Again button in call ending view no longer breaks the telephony.
  • Close icon shown on call ending state you can tap to dismiss the call dialog (you could already tap the dialog to dismiss but people didn't realise this).

SDK

  • Becomes public as soon as 2.1.1 SDK has rolled out.
  • Sqlite3 C++ API allowed in addition to the already allowed Qt SQL API in Harbour.
  • New 3rd party API for Content Pickers provided.
  • Thumbnailer API is also published.
  • Public Nemo middleware APIs changed to use CamelCase QML import path naming (Nemo.Domain vs. old org.nemomobile.domain).

Security

  • Vulnerabilities fixed: CVE-2015-8842, CVE-2016-7911, CVE-2016-8655, CVE-2015-8966, CVE-2015-5364, CVE-2016-10229, CVE-2015-6602, 2015-3288, CVE-2016-6761, CVE-2016-9793, CVE-2016-7910, CVE-2016-3134, CVE-2016-6758, CVE-2016-7117, 2017-6074, CVE-2017-7184, CVE-2015-2686, CVE-2017-6074, CVE-2015-3288, CVE-2017-1000366, CVE-2013-2207, CVE-2014-8121, CVE-2015-1781, CVE-2015-5277, CVE-2015-8776, CVE-2015-8777, CVE-2015-8778, CVE-2015-8779, CVE-2015-8982, CVE-2015-8983, CVE-2015-8984, CVE-2016-1234, CVE-2016-2856, CVE-2016-3075, CVE-2016-3706, CVE-2016-4429, CVE-2016-6323.
  • Vulnerabilities in Alien Dalvik fixed (Jolla C only): CVE-2015-4000, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1792, CVE-2015-1791, CVE-2014-8176, CVE-2015-1793.
  • New users are prompted to add a security code during the first start up to prevent others from using the device if it gets stolen or lost. Can be skipped.

Settings

  • Tapping disk space low notification opens up Disk Usage settings page.
  • OS Upgrade settings page available disk space calculations didn't refresh properly, now fixed
  • Update option for disk space added to pulley menu for Settings > Storage.
  • Show IMEI software version on About Settings page by long-pressing IMEI detail.

UX

  • Reliability of system gestures improved
    • Dismissing of calls and alarms
    • Performing edge gestures used to return from app to Home or slide in system panels like App Grid or Top Menu.

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

Changelog

For detailed changelog, see https://together.jolla.com/question/164350/changelog-211jamsanjoki/.

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

  • OpenVPN works now. However, the device must be restarted one time after adding any new VPN configuration to it (we are investigating what is causing this). After that one reboot the configuration(s) existing in the device do work and can be switched without rebooting. Apologies for this limitation. VPN on Sailfish OS is still in beta phase.
  • If you have Call Recorder from Openrepos installed, uninstall it before the upgrade. Otherwise the upgrade will fail and most likely put the device in unbootable state.
  • 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.
  • 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. Sometimes synchronizing the phonebook may fail, too, and some problems with audio playback appear. Especially on Jolla C. To be investigated and fixed.
  • Two of the Utlities do not work currently. Will be fixed.
  • Not all Jolla C devices can be updated directly from an early OS version (e.g. 2.0.0) to 2.1.1. An intermediate step is needed. This can be done on the command line (Terminal app, developer mode enabled):

Step 1:

devel-su
ssu re 2.0.5.6
version --dup
reboot

Step 2:

devel-su
ssu re 2.1.1.26
version --dup
reboot
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 21:56:02.864262

Comments

4

Jolla utilities need update, some option not working

TMavica ( 2017-07-24 14:11:19 +0300 )edit
1

TMavica: which options do not work? Any error messages if you try use them?

jovirkku ( 2017-07-24 14:22:06 +0300 )edit

@jovirkku Restart keyboard or Refresh media database

atlochowski ( 2017-07-24 15:00:18 +0300 )edit
5

Great to see another big update :) Just one question: if I understood correctly all the listed AlienDalvik updates and fixes are exclusive to Jolla C? Checking my Jolla 1, it seems it's on 0.17.35. No bump there, then?

walker ( 2017-07-24 15:12:44 +0300 )edit

restart keyboard I found

TMavica ( 2017-07-24 15:59:36 +0300 )edit

31 Answers

Sort by » oldest newest most voted
2

answered 2017-08-19 14:01:00 +0300

louisbob gravatar image

Hi Jolla team! First thank you very much for this update. The number of fixes you have done is just awesome!

I would like to know if this issue has been added into this release: https://together.jolla.com/question/40725/call-ended-but-phone-is-still-processing-the-ending/. I didn't found any traces of it in the changelog, albeit a fix has been published by your team.

Thanks!

edit flag offensive delete publish link more

Comments

2

Hi, we have unfortunately not found the culprit for this long-lasting issue. It must be located somewhere in the modem binary for which we do not have the source code. Some debugging aids have been written but the real fix is missing. Sorry.

jovirkku ( 2017-08-24 16:08:52 +0300 )edit
1

answered 2017-07-25 09:56:02 +0300

Quenti gravatar image

updated 2017-07-25 09:56:27 +0300

If the mistakes in the French version are still there after 2 updates since my message here, I will not translate any SailfishOS app. any more. I'm really tired of seeing the timestamps badly written, some 10 year old child mistakes else where.

edit flag offensive delete publish link more

Comments

2

You should check the translation here: https://translate.sailfishos.org/fr/

Do you see the wrong translations? Probably you could fix them, couldn't you?

magullo ( 2017-07-25 13:44:43 +0300 )edit
1

Rightly said @mangullo and @Quenti isn't your annoyance a little too exagerated? I know we owe it to Moliere to be a bit more respectful with that beautiful language

DameCENO ( 2017-07-25 14:42:38 +0300 )edit
3

I don't know if it's too exaggerated, but it's been time since several people pointed out mistakes : https://together.jolla.com/question/158790/french-mistakes-in-translations/?sort=votes&page=1

And French is official, it's not community driven, in addition we can only make suggestions on translate.sailfishos.org =/

Quenti ( 2017-07-25 20:03:36 +0300 )edit
1

answered 2017-07-28 09:50:33 +0300

amandalam gravatar image

Great stuffs as always.

Found these issues so far. Not sure if they are specific to this release or are they just specific to my devices...

Jolla 1

  • TOHKBD failed to work after the upgrade. NFC does detect the TOH as it shows me the Install button when I attach the TOH; but pressing the Install button gives me no response. Attaching the keyboard does not show up "Keyboard Connected", and it's not working after all. Rebooting doesn't help. FYI, the pins on the keyboard are intact.

Jolla Tablet

  • Looks like the screenshot functionality is broken. When I take a screenshot by pressing Vol Up and Vol Down buttons together, the screenshot taken is a total black image.
  • [Could be my hardware problem] Battery charges up to 50% and cannot be further charged. When I disconnect the cable and reconnect again, it may charge for additional 1-2%, but then it stopped charging again.
edit flag offensive delete publish link more

Comments

2

Screenshots are a problem since the last release: https://together.jolla.com/question/157070/bug-screenshots-dont-work-in-jolla-tablet/

nthn ( 2017-07-28 11:06:23 +0300 )edit

I wonder if any of the guys who reported issues while booting when TOHKBD was attached did try to reattach it after the device had started...

zagrimsan ( 2017-07-28 15:06:42 +0300 )edit

Attaching the TOHKBD after booting works without problem.

jpa ( 2017-07-28 16:12:22 +0300 )edit
1

answered 2017-08-19 15:02:26 +0300

lupastro gravatar image

What is this release version/date...

2017-08-dd. 2.1.1.25 Released to ...

...supposed to mean?

edit flag offensive delete publish link more

Comments

This means that in the coming days there will be another release candidate, but the ETA is not known yet.

Alex ( 2017-08-19 15:25:34 +0300 )edit
1

We are expecting 2.1.1.25 n 2.1.1.xx to all and please give us directly update with fixes for buds in 2.1.1.24...

Twinklestar1792 ( 2017-08-19 15:27:06 +0300 )edit

I had a wild dream about the 2.1.1.25 being the first public release for the Xperia X :-) :-) :-)

lupastro ( 2017-08-19 21:03:44 +0300 )edit
1

answered 2017-08-30 07:47:27 +0300

tapanit gravatar image

Update left Jolla C unbootable (probably because of Call Recorder - yeah, failed to read this before upgrading). :-(

Any way to recover short of reset to factory state? (Recovery shell works.)

edit flag offensive delete publish link more

Comments

Me too, should we just use the recovery shell or is there any alternative? It doesn't seem to be possible other things, i guess...

antoniovr ( 2017-08-30 10:47:49 +0300 )edit
0

answered 2017-07-25 10:15:01 +0300

arcadia gravatar image

updated 2017-07-25 10:15:17 +0300

With this update on Jolla 1 my account google doesn't receive the messages of hangout in the Messages App. in the setting the voice "Presence" is "Unavailable".. I try to delete and Add the account but nothing

edit flag offensive delete publish link more

Comments

10

Did you read release notes?

Messages

  • Google Talk support removed due to Google dropping support for Google Talk XMPP
tom.i ( 2017-07-25 10:19:00 +0300 )edit

Sorry, I didn't read it all

arcadia ( 2017-07-25 20:44:22 +0300 )edit
1

There is an easy workaround: just add an XMPP account manually, using your e-mail address as user name, the server is talk.google.com, the port is 5223. If you use 2-factor auth, you'll have to set up an app-specific password though.

JMairboeck ( 2017-07-29 11:03:20 +0300 )edit
1

@JMairboeck do you get it in the Presence menu after setup? Tried with just username/pass and with the server/port you mentioned (google asked me to enable low security apps, did that too), still presence menu in settings says no accounts with presence configured, not sure how to get that working, used to work fine with just the default google account setup, now can't get it to work with any of those

szopin ( 2017-08-29 21:30:28 +0300 )edit
0

answered 2017-07-25 17:08:21 +0300

remove this account gravatar image

updated 2017-08-13 10:47:32 +0300

Upgrading my Jolla C to his early access version caused the device to loop on boot. systemupdate.log showed a single error due to callrecorder:

Jul 25 09:55:35 Sailfish store-client[547]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotTransactionError(PackageKit::Transaction::Error, const QString&) 20 "Subprocess failed. Error: RPM failed: Stopping service...\nFailed to get D-Bus connection: No such file or directory\nerror: 0xb28e11d8reun(harbour-callrecorder-0.6.2-1.armv7hl) scriptlet failed, exit status 1\nerror: harbour-callrecorder-0.6.2-1.armv7hl: erase failed\n\n" Jul 25 09:55:35 Sailfish store-client[547]: [D] unknown:0 - void PackageHandler::slotUpgradeFailure(const QString&) "Subprocess failed. Error: RPM failed: Stopping service...\nFailed to get D-Bus connection: No such file or directory\nerror: 0xb28e11d8reun(harbour-callrecorder-0.6.2-1.armv7hl) scriptlet failed, exit status 1\nerror: harbour-callrecorder-0.6.2-1.armv7hl: erase failed\n\n" Jul 25 09:55:35 Sailfish store-client[547]: [D] unknown:0 - Wrapped transaction failed: "Subprocess failed. Error: RPM failed: Stopping service...\nFailed to get D-Bus connection: No such file or directory\nerror: 0xb28e11d8reun(harbour-callrecorder-0.6.2-1.armv7hl) scriptlet failed, exit status 1\nerror: harbour-callrecorder-0.6.2-1.armv7hl: erase failed\n\n"

Factory wipe worked, and the device is indeed ok.

I will open a new ticket to handle this issue.

edit flag offensive delete publish link more

Comments

1

There is a dedicated help article for Jolla C:
https://jolla.zendesk.com/hc/en-us/articles/115000663928-Jolla-C-How-to-use-Recovery-Mode

jovirkku ( 2017-07-26 15:40:44 +0300 )edit

Today tried to update to the latest version. Three times I downloaded the update but update failed while booting. On third time my JollaC went to boot loop. Now trying recovery mode.

Qwerty ( 2017-08-04 22:47:19 +0300 )edit
0

answered 2017-07-31 13:50:46 +0300

walkingzen gravatar image

Good to see that there is an update on the way. I afraid this update also won't solve my problem with proxy as I could see in release notes. It would be great if you could suggest something to make it work. I am not sure how difficult it would be to implement this feature, but most of the other GNU/Linux on laptops and desktop work fine. As per the comments on proxy related questions, it require some effort to be put on. I have seen that some of the apps work fine and uses proxy if I run it from terminal. Please advise.

edit flag offensive delete publish link more
0

answered 2017-08-16 14:20:24 +0300

Finland dna mobilenetwork does not work (network error) wifi works normal.

edit flag offensive delete publish link more
0

answered 2017-08-26 09:23:02 +0300

pawel gravatar image

update to .46 ob aquafish as C successfull on second attempt. first said again not pissible to update yiur device

edit flag offensive delete publish link more

Comments

`$ dwdiff a.txt b.txt

update to [-.46 ob-] {+.26 on+} aquafish as C successfull on second attempt. first said again not [-pissible-] {+possible+} to update [-yiur-] {+your+} device`

I had to read your answer 4 times to get what you mean.

fl0rp ( 2017-08-27 16:40:19 +0300 )edit

Question tools

Follow
25 followers

Stats

Asked: 2017-07-24 12:40:33 +0300

Seen: 36,196 times

Last updated: Oct 02 '17