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.

Events view

Flashing

Gallery

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.

Changelog

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.

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

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?

Comments

5

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.

I think removing the half assed broken NON-Federation stuff is better than trapping people in the mess of Google. Moreover, the integrated support of XMPP will not be improved it should be removed. It is super convenient, but it is a mess:
No OMEMO, NO SEND and RECEIVE notifications, no ERROR-Messages on not delivered messages (switch to SMS-Mode to see them), no FILE-Transfer and so on, no Audio/Video-Chat and a lot of more stuff. I'm using now Conversations (Android) and Chatsecure (iPhone) and even encryption is convenient, everything works reliable and all the awesome features are available. Sorry, either Telepathy or Jollas support for Telepathy are rotten.

Exact same thing with TOHOLED. Although upgrading sailfish was not interrupted on a clean - factory settings - jolla (and toholed attached with the service installed) at first boot networking was not working thus wifi couldn't be turned on. Rebooting with no other half attached fixes the problem and didn't see any issues after attaching toholed. Still this is a bummer...

Yhm, yeah, my symptoms seem to be long boot time & no mobile network at all when booting with the tohkbd attached, and when it's unattached while booting, I do get mobile network, but still withoug mobile data. ): Not much use for my Jolla now, without being able to use irssi... A fix would be much appreciated!

@olf yeah, jolla C got 1.0.63, tablet even though also 4.4 is stuck on ancient 1.0.29 as jolla never updated the x86 alien dalvik that is on tablet (and seeing the amount of security fixes it really sucks for the youyota buyers, not to mention the amount of apps that just won't start)

We have found an issue in the OS update repositories such that installing updates from 2.0.5 (or earlier) to 2.1.1.23 tend to fail. This is being fixed in the update servers. Updates 2.1.0.11 => 2.1.1.23 should work ok. Note that 2.1.1 is a big update due to some vulnerability fixes in the libraries. Because of this the download phase can take tens of minutes. Apologies for the inconvenience caused.
-There will be another release candidate 2.1.1.24 for early access subscribers one of these days.

Great to see this upgrade, maybe it fixes some issues. But finally my Jolla started to fail seriously, it didn't reconnect to the carrier-network after a connection lost. Which could not only happen from time to time, in my case two times a day, in the underground garage. I couldn't fix it with a network-restart, just full reboot of the device. Maybe my GSM-Modul was damaged, but I think a lot of Qt-Stuff has problems which Jolla couldn't fix themselfes (e.g. WiFi/Cell-Network-Switching).

Comments

2

I experienced the same today on my Jolla1 - my device was unable to connect to mobile network after leaving home and the WIFI network. Restarting the network via Sailfish Utilities did not solve this issue and I had to reboot my device.

@Alex and @lispy: Did you experienced that on the 2.1.1.23 or the old release?

It was serious for me and I switched to an iPhone SE for this only reason. Not only the undergroudn garage was an (planable) issue twice a day, it could happen any time in a building or during sports in the woods. A lot of stuff sucks hard on the iPhone (especially SCP/SSH e.g. file moving from/to device) but other things just work right (the pull all emails initally! Like any normal Email-Client!).

previously (manually defined) existing WPA2 PEAP entries are ignored when the related network is available (but perhaps it's "normal" because of official support added in this release)
-> Workaround 1: change something in the file will force Connman to read it again.
-> Workaround 2 (not really a workaround, thanks to Jolla Team ;)): delete the file then register the wlan from UI, like it always should be.

In addition I have some questions:

Since at least one year now, Jolla 1 haven't receive any Alien Dalvik update (understand migration from 4.1 to 4.4 like Jolla C/Tablet). Why? Have you any (good) reason to keep this old version for all Jolla 1 users?
-> backport Alien Dalvik 4.4 on Jolla 1 seems need a lot of work because of kernel/driver update and it's not free because of Myriad licensing (thanks yuri). Otherwise, an official answer would be great since it's a question that interests many people.

I'm waiting for Bluez5 since month because I experience many many issues all days of my life with Bluetooth when connected to my car radio (JVC) and again and again Jolla 1 keep the old Bluez4 version. Again, why? Have you any (good) reason to keep this old version for all Jolla 1 users? Can you please give me a way to switch right now from developer options like with Jolla C on previous release?

I'm not an expert in development but I think that maintain an unique Bluez software version is simpler than two isn't it? So I don't understand the manner you deal with that... :( Can you please explain? Please notice that European users have only Jolla 1 as an official public device at this time (Jolla C for dev, Intex Aquafish not officially for European country) so I think you should either give us another official device or offer the same quality (in term of release number) for all supported devices (especially Jolla 1).

Why AD 4.1? Because Android 4.4 comes with A LOT of changes, that the specs of the JP1 propably wont handle. This can cause that the phone feels a lot slower (it is already pretty slow).
I think they wont risk any problems with that.

Mobile data and MMS access point
settings now allow you to change the
authentication method (no, PAP, CHAP,
automatic).

FYI, on Jolla 1, my mobile data connection didn't work after the update to 2.1.1.24 with the error "problem with connection".

I am with O2 network in the UK, so I checked the APN settings in Settings >> Mobile network >> Data access point and MMS access point.

The problem was the (newly added feature) 'Authentication' setting was set to the incorrect authentication type 'CHAP' for the O2 UK network (O2 UK requires 'PAP' authentication). Once I had set this correctly and restarted the phone, my mobile data connection worked correctly.

Comments

Nice to have a quick way to get to the camera but you really should be able to get to the photos by swiping right from there. Currently it does not seem to be possible. Of course this feature could be disabled if the device is locked via code but otherwise you really should be able to look at the photos you take.

Comments

3

Oh indeed, it doesn't open the normal camera app, a bit useless then :/

Also, in the normal Camera app, when I view the last photos taken in portrait, they are rotated in landscape... And I can't see those new photos in the Galery (I've rebooted and run the indexation but no success)

I noticed the same, the vertical photos rotates weirdly in gallery. The ones you take in horizontal are good, though! The photos are there, but now the newest are the last on the gallery. Any way of changing this?