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

[release notes] 3.3.0 Rokua

asked 2020-02-04 14:21:28 +0200

jovirkku gravatar image

updated 2020-08-21 01:11:51 +0200

olf gravatar image

Many thanks to you our active contributors for your feedback and proposals.

Table of content

Update version history

  • 2020-04-02: was released to Early Access subscribers
  • 2020-04-23: was released to Early Access subscribers, fixing the fingerprint sensor on all XA2 devices, audio playback with browser and the plain-text passwords of NextCloud. Some GUI texts were added.
  • 2020-04-28 at 14:20 EET: was released to all users. Installable image files for Xperia and Gemini devices uploaded to Jolla Shop.

The encryption of user data has been added to all Xperia devices. Please read what is said under Security. In addition, it is crucial to follow our advice on apps from Open Repos.

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 Phone from 3.2.1 to 3.3.0: about 260 MB
  • Jolla C from 3.2.1 to 3.3.0: about 270 MB
  • Jolla Tablet from 3.2.0 to 3.3.0: about 320 MB
  • Xperia X from 3.2.1 to 3.3.0: about 320 MB
  • Xperia XA2 from 3.2.1 to 3.3.0: about 500 MB

Device models supported by Sailfish X

The instructions for installing Sailfish OS to Sony Xperia X, Xperia XA2 and Xperia 10 devices are here - covering Windows, Linux, and macOS computers. Read this, please, to learn about the Sailfish X licence.

The supported Sony Xperia 10 models are:

  • 10 single-SIM: I3113 and I3123
  • 10 dual-SIM: I4113 and I4193
  • 10 Plus single-SIM: I3213 and I3223
  • 10 Plus dual-SIM: I4213 and I4293

The supported Sony Xperia XA2 models are:

  • XA2 single SIM H3113 (also H3123, H3133)
  • XA2 dual SIM H4113 (also H4133)
  • XA2 Ultra single SIM H3213 (also H3223)
  • XA2 Ultra dual SIM H4213 (also H4233)
  • XA2 Plus single SIM H3413
  • XA2 Plus dual SIM H4413 (also H4493)

The supported Sony Xperia X models are X single SIM F5121 and X dual SIM F5122

The supported Gemini PDA models are x25 and x27.

Contributions from Aurora OS

Several of the key improvements in this release were developed in collaboration with Open Mobile Platform for Aurora OS. Here are some of the key features contributed by Open Mobile Platform to the Sailfish OS:

  • New toolchain: GCC 8.3
  • Nextcloud service introduction
  • EAS account authentication improvement
  • Backup buttons "Mount" and "unlock" for handling memory cards
  • Calendar app fixes: CalDAV synchronization, repeating events
  • Camera app fixes
  • EAP-TLS authentication support introduced for WLAN connections
  • Connectivity bug fixing
  • MDM and Corporate API for ActiveSync and accounts
  • Documents app fixes for CSV and RTF
  • Email app GAL support, Folder sync settings
  • Events view improvements
  • Gallery app support for Nextcloud, use of ffmpeg, and other fixes
  • Location cold start fixes, enabled use of other location providers, fixes
  • Messages UI fixes
  • People app contact search and autofill
  • Phone app call history improvements, UI and bugs fixes
  • CVE (17) fixes for middleware
  • Custom factory reset animation
  • VPN connections API improved

Jolla appreciates collaborative efforts of its partners and community to make Sailfish OS even better.

Release Highlights

This list below contains examples of new features (and some bug fixes) added to Sailfish OS, compared to the previous public release 3.2.1. The release notes of 3.2.1 can be found here.


  • Nextcloud cloud service introduced. Sharing pictures, documents and notes to the cloud. Syncing of contacts and calendar appointments.
  • Google account icons updated to show the latest Google icons
  • Give a warning when a user tries to set up Gmail and Yahoo emails as generic email accounts, and guide user what service security settings need to be turned off to get them working
  • Exchange (EAS) account can be authenticated on a server using a personal SSL certificate
  • Use PasswordField for XMPP and Email fields

Android™ App Support 8.1

  • Updated to the latest android-8.1.0_r73 branch
  • Display orientation lock fixed for Android apps
  • WhatsApp: "add to contacts" and video playback fixed
  • "Android™ support" renamed to "Android™ App Support" also in Jolla Store (previously in Settings)
  • Many Android apps can access the SD card, now. For instance, OsmAnd and HERE WeGo map apps can save the offline map tiles to the card. Likewise, Spotify can save music to the card. Apps like WhatsApp can attach pictures from the SD card to messages now. The card name (the nickname given when formating the card) must not contain spaces.
  • Nemo storage mounted as an AlienVolume(PublicVolume) and named 'sailfishos_storage'; unneeded bindfs dependency removed

Backup & Restore

  • Buttons "Mount" or "Unlock" added to "Settings > Backup" and shown if the memory card is unmounted or locked, i.e. not available for the apps


  • CalDAV synchronisation fixed
  • A meeting invitation can be declined after first accepting it
  • Prevented the Calendar from setting up accounts that don't support sharing events
  • Ensured that Calendar invitation response is sent to and displayed in the Google calendar of the organiser
  • Sharing calendar event via e-mail now use .ics attachment (replaced .vcs format)
  • Repeating events having a wrong time zone fixed
  • Last week of calendar month grid got clipped on landscape orientation with Xperia 10, now fixed
  • ICS WebCal calendar support introduced, community contribution from Damien Caliste


  • Ensured that all pictures taken with Camera are saved so that they get the correct access rights and hence are available for different apps (JB#45124)
  • An issue with taken photo not visible when visiting right away fixed
  • Contrast improved on lock screen camera roll labels


  • EAP-TLS authentication support introduced for WLAN connections
  • Fixed the connection dialog when connecting to mobile data if WLAN on
  • Do not save WLAN before the connection has succeeded
  • NFC support added to Xperia X
  • NFC setting keeps its value over device restart
  • USB tethering (enabled from command line) fixed (help article)
  • Don't show MDM disclaimer if network mode is disabled due to other reasons

Device Management (MDM) [Corporate API]

  • Active Sync provisioning support added


  • Open documents: performance improvements
  • Documents app opens faster to loading view instead of waiting for the document to fully load
  • Document preview on active cover rendering and scaling improved; no longer shows UI chrome
  • Avoid background flicker when unlocking device to an open document
  • Fixes to CSV and RTF file formats


  • Support for online address book added to Exchange email. When selecting email recipients, type at least 4 characters to the To field to make item "Online address book" appear with a search button. Tap this button. Continue typing if necessary to narrow down the search.
  • Folder sync settings introduced to allow extending automatic sync to other folders than just inbox, IMAP support from community member Damien Caliste
  • Message with an attachment in the Draft folder can now be sent with the attachment
  • Attachment button no longer looks disabled
  • Opening files with filenames having certain characters failed, now fixed


  • Notifications and announcements published on Nextcloud appear on Events
  • Events lacked blur background when accessed from landscape app fixed
  • Background made brighter on light ambiences for better legibility
  • Nextcloud photo albums appear now on Gallery app
  • Pictures from an encrypted SD card unlocked for use are shown in Gallery
  • Video playback is no longer blocked if thumbnail creation fails
  • Fix background flicker when unlocking to an image or video views
  • Show author on image and video details (if available in the metadata)
  • An error notification is shown now if a suitable decoder is missing
  • Support for AMR and AMR-WB decoders added
  • Use of SW codecs simplified: libav swapped out for ffmpeg and gst-libav added; gst-droid limited to HW codecs only
  • Video recording fixed on some community devices by adding audiopolicy service


  • App Grid flicking speed improved
  • Show Bluetooth and location icons in lock screen
  • Only round cover action press effect around cover background corners
  • Operator name is shown at the bottom of the lock screen, again

HW adaptation

  • Some upstream kernel fixes merged to Xperia 10 and XA2


  • Better support introduced for custom input methods with own prediction
  • Edge swipe detection area is now smaller on keyboard edges to ease typing keys close to the edges


  • Temporarily disable Mozilla Location Service online queries if API key fails
  • Better support introduced for pluggable location service providers
  • Hide extra location settings if there are no providers
  • Location fix can be obtained faster than before. For the best results, select "High-accuracy positioning" in Settings > Location.


  • Songs from an encrypted SD card unlocked for use are shown in Media app


  • Fix message bubble corners sometimes rendering incorrectly
  • Add delete button to recipients list in Messages app
  • MMS and error case layouts fixed

Middleware & Sailfish Core

  • Most of the core components upgraded
  • Many hardcoded paths eliminated


  • Contact search results are now sorted to prioritise common details and beginning of the word matches
  • Fix contact cover layout for 1-2 favorites
  • When editing or creating new contact autofill suggests contact details from existing contacts


  • Fixed the routing of call audio in the case of calls started with a wired headset connected
  • Phone number matching improved to avoid false matches
  • Messages app sometimes not opening when tapping "Send message" button fixed
  • Hide SIM information on call history if the device only has one SIM
  • Show company name below name detail in the call history
  • UI tuned up


  • User data encryption added to Xperia XA2 and Xperia X. PLEASE READ this help article. Pay attention to chapter #3.

  • Access from adaptation drivers to the rest of the filesystem limited

  • Vulnerabilities fixed (17):
  • augeas 1.12.0 - CVE-2017-7555
  • e2fsprogs 1.45.4 - CVE-2019-5094
  • file 5.37 - CVE-2019-18218
  • glib2 2.62.4 - CVE-2019-12450
  • libarchive 3.4.0 - CVE-2019-18408
  • libgcrypt 1.8.5 - CVE-2019-13627, CVE-2018-0495, CVE-2017-0378, CVE-2017-7526, CVE-2016-6313
  • libsoup 2.68.2 - CVE-2017-2885, CVE-2018-12910
  • nss 3.49, nss-pem 1.0.5, nspr 4.24.0 - CVE-2019-11745, CVE-2019-17007
  • poppler 0.74.0 - CVE-2019-9631
  • wpa-supplicant 2.9 - CVE-2019-16275, CVE-2019-13377
  • some other vulnerabilities fixes.


  • Support for the Industrial I/O subsystem (IIO) proximity sensor added


  • Continued the development of the support for multiple users, however, not yet ready to be launched
  • Clarifying label to Settings > Display > Adjust automatically added
  • Don't show return to home hint if hints are disabled in Gesture settings


  • New Tutorial style polished for various device form factors


  • App layouts polished for larger smartphones
  • Info label and busy indicator layouts aligned between the apps
  • Vertical page margins increased to improve one-handed use of buttons on devices like Xperia 10
  • Re-designed remorse timer (when deleting items)
    • Tap performs undo, swipe dismisses
    • Remorse now looks like a banner to clearly differentiate style from normal items
    • Further simplify texts to avoid new user confusion
    • Pressing remorse shows swipe gesture hint
  • Zooming in/out with the pinch gesture fixed

UI components

  • Minimized apps don't update orientation (performance improvement)
  • Silica GridItem remorse action now also works with smaller grid items
  • Don't block acceptance of a dialogue if 'canAccept' is set in 'onAccepted'


  • Change management VPN properties improved


  • New colourful weather icons introduced

Device specific notes

Xperia X

  • NFC support added

Xperia XA2

  • Fingerprint recognition fixed ( fixes it also on devices with "ET" sensor and Android 9 baseband)
  • Voice-missing issues during calls fixed

Xperia 10

  • F2FS security enabled for SELinux. Hence, SD cards formatted with F2FS can be mounted on the Xperia 10
  • Magnetic cover sensor enabled
  • Playback of some web videos fixed
  • Fingerprint recognition fixed
  • Xperia 10 kernel upgraded to 4.9.213 version

T.J.C: Issues reported by the community and fixed in this update

All of the links below may not open up for everyone, sorry.

Technical changes

  • Link to technical blog: (add the link here once available)
  • Changes to public APIs concerning application developers:
    • gcc compiler updated 4.9 -> 8.3
    • glibc updated 2.28 -> 2.30
    • glib2 updated 2.56 -> 2.62
    • python3 updated 3.7 -> 3.8
    • qml contextkit backend changed. libstatefs-qt5 to be deprecated.
    • silica: BusyLabel introduced for full screen busy indication
    • screenshot d-bus access is now restricted
  • See also Sailfishos.org.


The detailed changelog is kept here

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 the case of "Jolla Phone" 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, read our help article in Zendesk.

NOTE 1: Sailfish OS does not support downgrading. Never try to downgrade the OS as this would break your device.

NOTE 2: After downloading an update and selecting "Install" in the pulley menu, the device runs a restart first. In case of a device with the user-space encrypted, please note that you will need to type the security code before the actual installation can start.

Notification concerning apps from Open Repos

  • If you use SystemDataScope or collectd (see here), remove them. Having them installed will lead into update failure where Internet connections may be broken. See TJC-226291. Upgrading collectd to the latest version from 2020-05-05 may help (no guarantees)
  • If you use Defender, remove it as it will probably prevent your Xperia 10 (at least) from booting up or causes a conflict with the encryption. See this, please.
  • If you use Aliendalvik Control from OpenRepos, first upgrade it to version 9.2
  • 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. Patchmanager 3 is claimed to be "OS update friendly" but we have no more information on this.

About SD cards

  • Encrypted cards must be unlocked by the user to make them available for Sailfish applications.
  • Non-encrypted cards are mounted automatically when the device is turned on.
  • Encrypted cards can be formatted only when they are locked. Formatting removes the encryption in this case (the card becomes unencrypted and unmounted). You can then format it again with the option to encrypt if needed.

Known issues - generic

  • The Sailfish implementation of NextCloud cloud service has still a number of problems in it.
  • Assisted location services of Mozilla stop working from March 1st. On the positive side, we have been able to speed up getting the location fix.
  • VPN does not work in case of Android apps
  • Sailfish can connect Bluetooth Low Energy devices now. However, Android apps cannot use peripheral devices via Bluetooth - other than for playback of the sound. Therefore smartwatches, for instance, cannot be controlled from Android apps
  • Bluetooth pairing and audio connections may fail in some circumstances
  • In the case of many recent device models, clock alarms (RTC alarms) may not be functional after turning the device off. Please test this feature before using for a real need.

Known issues to Android App Support 8.1 - Xperia 10 & Xperia XA2

  • The alert of incoming WhatsApp calls does not work as intended if the display is locked and black. Then only the ringing tone is played but there is no visual indication.
  • Android apps cannot use peripheral devices via Bluetooth - other than for playback of the sound. Therefore smartwatches, for instance, cannot be controlled from Android apps.
  • The voice of an incoming call is not automatically routed to a wired headset. However, if the user directs the voice to the HF speaker first and then back to the headset, the voice can be heard at the headset.
  • VPN does not work in case of Android apps

Known issues specific to Xperia X

  • Not implemented features: FM radio, double-tap wakeup, step counter, RTC Alarms
  • Issues with mobile data persist on some SIM cards. Turn the Flight mode on and off to reset the network setup. Reverting the device to Android and re-installing Sailfish X has often helped. See our support article.
  • Manual network/carrier search lists all networks by the same name (the name of the SIM provider). Use an automatic search. If not possible, you need to try several items in the manual search results, unfortunately. The topmost item is not necessarily the one that can serve you (still valid with most SIM cards)
  • [camera] Force autofocus mode for photos, and continuous for video. After this, camera focus is still not ideal - as the camera stays out of focus when it starts until you either tap or you try to take a shot - but the pictures seem to be better focused now
  • Bluetooth: problems with some car equipment, some audio devices and computers may appear
  • The loudspeaker volume level cannot be adjusted very high
  • Not all SD cards are recognized and mounted.

Known issues specific to Xperia XA2

  • Not implemented features: FM radio, double-tap wakeup, RTC Alarms
  • Bluetooth: there are problems in connecting to some peripheral devices
  • XA2 does not power up when alarm time has elapsed
  • Flashing Sailfish X to XA2 might still fail (so far seen to happen on Ubuntu 18.04 when using USB3 port). Please read this article.
  • With v17B Sony vendor image we observed a decrease in the perceived signal strength of the 5GHz WLAN access points (investigations ongoing). Version v16 may work better in this respect. Therefore we would not recommend flashing v17B for the time being if you use WLAN networks in the 5GHz band. You can reflash the vendor image of your choice by following the instructions in here.

Known issues specific to Xperia 10

  • Features not yet implemented: FM radio, double-tap wakeup, support for dual-lens camera, RTC Alarms.
  • Rarely, audio playback and sensors (display rotation) may stop working. If this happens, please restart the device
  • In some cases, the acceptance of the PIN code of a SIM card may take up to 5...20 seconds
  • During the decryption of user data in device start-up, there is a period of 10-20 seconds such that the display is black
  • White balance and HDR (of the camera) do not work.

Known issues specific to Jolla Tablet

  • There is no progress bar during the installation phase of OS upgrades. This makes it difficult to follow if it makes progress or not. However, if there are no problems the device will restart itself in the end - please wait patiently. If you feel that you have waited enough, wait for yet another 20 minutes before you turn off the device to allow some more time for it to complete the job. Interrupting too early may break the tablet.

Known issues specific to Gemini PDA

  • Features not yet implemented: double-tap wakeup, RTC Alarms
  • Gemini Screenshot Button Fn + X does not work
  • Not possible to answer calls when Gemini is closed with side button
  • Some 3rd party apps have issues in Landscape mode.
edit retag flag offensive close delete



Downolading.. :) Thank you!

cquence ( 2020-04-02 17:54:45 +0200 )edit

Thanks, just installed.

Peter S. ( 2020-04-02 18:29:47 +0200 )edit

Update went smoothly

Blizzz ( 2020-04-02 18:38:54 +0200 )edit

Same with mine, too. Thank you for the naming - occording to landscapes of my childhood. <3

N9Sailfish ( 2020-04-02 18:48:56 +0200 )edit

From a first glance update went smoothly. Already added my Nextcloud account, it takes ages however 'Setting up Nexctloud accout' after you accept die dialogue.

One question comes into my mind: Since Nextcloud account now synchronises Calendars and Contacts should I remove the existing Accounts for CalDav/CardDav accounts?

jollajo ( 2020-04-02 19:31:32 +0200 )edit

41 Answers

Sort by » oldest newest most voted

answered 2020-04-03 13:39:40 +0200

jkt gravatar image

updated 2020-05-22 11:07:57 +0200

jovirkku gravatar image

How to solve "No network connectivity"

On my XA2 H4113, update via GUI showed an error message that the update failed at this time, and that I should retry later. After a reset, I had no network connectivity. Here's how I recovered.

Recovery via Developer mode

  1. Connect via USB to a Linux notebook and enable Developer mode
  2. Check your IP address(es), and SSH into the device from the Linux machine
  3. Share network access via the Linux machine, over the USB cable, from Sailfish:

    • As root on the Linux machine
      • iptables -t nat -A POSTROUTING -o enp0s31f6 -s -j MASQUERADE (check your device name and substitute enp0s31f6 for the network link you use),
      • sysctl -w net.ipv4.ip_forward=1
    • As root on the phone:

      • rm /etc/resolv.conf
      • echo 'nameserver' >> /etc/resolv.conf
      • route to check if you have default gateway configured

        Destination  Gateway      Genmask        Flags Metric Ref  Use Iface
        default        UG    0      0    0 rndis0  *    U     0      0    0 rndis0

        make sure you have line with default in Destination column. Gateway IP there is the IP of your computer (in this case is

        If line is missing use route add default gw LINUX_MACHINE_IP to add it. If needed, you may figure out LINUX_MACHINE_IP from output of netstat -an | grep ':22.*ESTABLISHED'

  4. The handset has network again, update from CLI (SSH worked for me):
    • ssu re
    • version --dup
    • reboot via the phone's GUI
  5. Wow, green text in e-mails, yay! :)

Extra info

After a failed update, connman was broken:

[root@Sailfish ~]# systemctl status connman
● connman.service - Connection service
   Loaded: loaded (/lib/systemd/system/connman.service; disabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/connman.service.d
   Active: activating (auto-restart) (Result: exit-code) since Fri 2020-04-03 12:15:36 CEST; 375ms ago
  Process: 18490 ExecStart=/usr/sbin/connmand -n -W nl80211 --nobacktrace --systemd --noplugin=wifi $SYSCONF_ARGS $CONNMAN_ARGS (code=exited, status=127)
 Main PID: 18490 (code=exited, status=127)

Apr 03 12:15:36 Sailfish systemd[1]: connman.service: Main process exited, code=exited, status=127/n/a
Apr 03 12:15:36 Sailfish systemd[1]: Failed to start Connection service.
Apr 03 12:15:36 Sailfish systemd[1]: connman.service: Unit entered failed state.
Apr 03 12:15:36 Sailfish systemd[1]: connman.service: Failed with result 'exit-code'.

No extra details were available in the journal, sorry.


I see that the release notes now point to the collectd package from OpenRepos being the culprit. I can confirm that I had it installed.

edit flag offensive delete publish link more


@jkt Can you elaborate more on the commands? I am not getting my connection through to the phone. The "enp0s31fe" is the network adapter on the linux machine. with "ifconfig" I found my adapter name and replaced it. My Xperia 10 has the IP "", so I replaced your "192.168.10/24".

In your echo command there seems to be a ' too much or one missing. Can you correct that? How can I check for working connection, because the download after "version --dup" fails.

Spark ( 2020-04-03 16:08:43 +0200 )edit

I think it's supposed to be echo 'nameserver' >> /etc/resolv.conf but I didn't test that.

Direc ( 2020-04-03 19:36:27 +0200 )edit

Also, serious kudos to posting the repair steps so quickly! I was in such a hurry that I reflashed my phone instead of bothering to actually notice your answer! Oh well, now I get to enjoy a fresh device experience at least :)

Direc ( 2020-04-03 19:39:53 +0200 )edit

Good job !
Worked with my Xperia H4493, just two things:
Need to forward:
echo 1 >/proc/sys/net/ipv4/ip_forward

iptables -t nat -A POSTROUTING -s -o wlp2s0 -j MASQUERADE
Where: is the network of the phone
wlp2s0 is the network where is the connection to Internet (WIFI for my side)

On the phone:
Avoid the graphic message to connect to internet from SIM1, SIM2 or WLAN (do nothing), you will see an increment of % in upgrade.

Thank's, you saved my phone.... ;-)

manu007 ( 2020-04-03 19:45:09 +0200 )edit

@manu007 yep, that works. Here is also a source if anyone needs more help: https://together.jolla.com/question/58975/network-sharing-from-pc-to-phone-answered/

My network works again :)

Spark ( 2020-04-03 20:04:01 +0200 )edit

answered 2020-04-03 00:13:04 +0200

g7 gravatar image

updated 2020-04-03 00:14:19 +0200

* If the Sailfish OS upgrade fails mid-way, and on reboot connectivity is broken *

You can try these steps:

If you don't have zypper installed, you should install it now to be able to recover. If you are upgrading from you can download these rpms:



and then moving them into your phone via SD-Card, USB OTG or whatever. Then you can install them via a file manager. Install first augeas-libs then zypper.

Once they are installed, you should lock them since those packages weren't present before and thus the updated versions from 3.3.0.x weren't downloaded previously:

devel-su zypper addlock augeas-libs
devel-su zypper addlock zypper

Now, to actually recover you should follow these steps:

mv /var/cache/zypp /var/cache/zypp-old
ln -s /home/.pk-zypp-dist-upgrade-cache /var/cache/zypp
zypper dup

If there are repositories which are failing due to missing connectivity, you can safely ignore them (by pressing 'i'). Let the update continue, if there are file conflicts let it continue too. The important thing here is to restore connectivity to finish the upgrade later.

Once it finished, restore the real zypp cache

rm /var/cache/zypp
rm -f /etc/zypp/locks
mv /var/cache/zypp-old /var/cache/zypp

...and reboot:


You should have most of the upgrade installed, connman should now work and connectivity should be restored.

Finish the upgrade with the following commands:

ssu re
version --dup
edit flag offensive delete publish link more



Thanks a lot, worked like a charm!

ziellos ( 2020-04-03 10:32:16 +0200 )edit

I tried to simplify this a bit; I did not have zypperinstalled before, and I was too lazy to yank out the SD card. Developer mode access via SSH over the IP-over-USB-gadget cable worked, and in the end I did not have to install anything manually -- just triggering the update via CLI did the trick: https://together.jolla.com/question/222221/release-notes-330-rokua/?answer=224345#post-id-224345

jkt ( 2020-04-03 13:41:23 +0200 )edit

@g7 Installing zypper gives me an error ("Problem installing Zypper"). I am stuck. Any idea? Other dependencies I am missing? Phone is a Xperia 10

Spark ( 2020-04-03 16:43:56 +0200 )edit

@Spark: have you installed augeas-libs first ? From which release are you upgrading? 3.2.1?

g7 ( 2020-04-03 17:13:33 +0200 )edit

@g7 yes and yes.

Spark ( 2020-04-03 17:27:46 +0200 )edit

answered 2020-04-02 22:09:51 +0200

ds1979 gravatar image

updated 2020-04-02 22:10:19 +0200

Troublemaker: AlienDalvik Control from Openrepos. After removing it, I could start AlienDalvik again.

Device: Xperia 10 Dual-SIM (Non-Plus!)

edit flag offensive delete publish link more



Same here with XA2 dual sim.

pjr ( 2020-04-02 23:28:43 +0200 )edit

Can't confirm. I wanted to test this, so I left mine installed, and Everything Just Worked (TM). XA2 Ultra here, 3.2.1 > 3.3.0

Direc ( 2020-04-03 09:17:17 +0200 )edit

I had AlienDalvik Control installed over the update to 3.3.0. After update I couldn't start AlienDalvik at all. I removed AlienDalvik Control, tried re-installing Android support from store, no help starting. Then I manually run (as root) systemctl restart aliendalvik and got android support back working. Using Xperia XA2 dual sim.

Rulli ( 2020-04-03 09:30:14 +0200 )edit

There's a fix from @coderus for AD control. Update AD control before updating SailfishOS.


Spark ( 2020-04-03 11:31:59 +0200 )edit

You can also update the "Aliendalvik Control" app from OpenRepos after the system upgrade to fix this.

dumol ( 2020-04-04 12:43:03 +0200 )edit

answered 2020-04-03 13:38:39 +0200

xneo gravatar image

Thank you a lot for that amazing Update !!! All works fine for me...

My personal highlights: - Map Download in HereWeGo to SD-Card!!! - SD-Card Downloads in Spotify!!! - Videos playing in WhatsApp

Thank you a lot dear Jolla and highly appreciated your work during these special times !!!!

edit flag offensive delete publish link more

answered 2020-04-04 13:11:41 +0200

Sebix gravatar image

The release removes the possibility to open the Android settings via Settings > Apps > [Any Android App] > Open Android settings > Back button > Open the settings app from Home Screen.

Please re-add the possibility to open these settings, for example by adding a new button in Settings > Android App Support.

edit flag offensive delete publish link more


+1 for noticing. Another hack to reach the Android settings is installing "simple app manager" from fdroid as Leszek Lesner pointed out in this video: https://youtu.be/6Amrr766crc (at 4:10 min).

Open the app, press "+" and add "settings" to the app menu. Now you have access to the android settings through this app.

Spark ( 2020-04-04 14:31:43 +0200 )edit

Yes indeed. That has changed. Don't know yet if this was intentional or not. To be checked.

jovirkku ( 2020-04-06 12:14:12 +0200 )edit

@Spark The app mentioned in the video is Simple App Launcher, not Simple App Manager.

celeron55 ( 2020-04-30 09:46:02 +0200 )edit

answered 2020-04-02 22:06:44 +0200

ziellos gravatar image

Attention: don't update your Xperia X yet. It seems updating breaks all communications on the device: mobile network, Wifi, bluetooth.

edit flag offensive delete publish link more



Someone has updated 2 devices Xperia X without flaws. His wife would already have killed him. :-D

ds1979 ( 2020-04-02 22:11:06 +0200 )edit

This also happened to my Xa2 device.

pasik ( 2020-04-02 22:12:43 +0200 )edit

+1 XA2. Flightmode icon is permanently shown even though no flight mode is activated. WLAN seems to work though.

lupastro ( 2020-04-02 22:56:55 +0200 )edit

I had to do ssu re + version --dup from cli until got a working XperiaX. Had only spinning wheel on the screen and could not open application menu.

teve ( 2020-04-02 22:58:10 +0200 )edit

I have updated Xperia 10, XA2 and also Xperia X. Everything without any problem.

Peter S. ( 2020-04-02 23:04:52 +0200 )edit

answered 2020-04-04 16:29:14 +0200

dumol gravatar image

updated 2020-04-04 19:44:52 +0200

Fingerprint recognition still not working on my XA2 H3113 where I flashed over Android 9, even though a similar issue is documented as solved: https://together.jolla.com/question/216242/xa2-10-fingerprint-scanner-not-working-dual-sim/

Have even reset back to 3.2 and updated again to 3.3 on a clean slate, but no luck… :-/

This one describes my issues a bit better: https://together.jolla.com/question/218003/xperia-xa2-fingerprint-process-at-100-cpu-draining-battery/

edit flag offensive delete publish link more


Yes, and even the battery consumption is not fixed so I"m wondering what did jolla fix ...

mousse04 ( 2020-04-05 00:07:36 +0200 )edit

One positive report here. I have XA2 Dual SIM. Fingerprint sensor works great. My battery often last 4 days. I don't use Android apps for many months.

Filip K. ( 2020-04-06 12:46:28 +0200 )edit

Fixed the fingerprint feature on all XA2 devices in OS update There was a problem with devices having Android 9 baseband and the "ET" type of fingerprint sensor.

jovirkku ( 2020-04-24 10:48:54 +0200 )edit

The Fingerprint feature does not work for me on my XA2 Plus (OS When attempting to set a fingerprint I constantly get a message that I need to clean the Fingerprint sensor... Well cleaning it does not resolve the issue.

WilliePre ( 2020-04-26 13:30:21 +0200 )edit

answered 2020-05-05 07:18:45 +0200

4carlos gravatar image

updated 2020-05-05 16:02:35 +0200

Android apps can no longer load any files or pictures with the "Open dialog" after the update. This also applies to attachments to messengers and email. Only "share with" is possible and this leads to an endless loop that can only be interrupted by the on / off switch.

Forgotten device: XA2 dual SIM

edit flag offensive delete publish link more

answered 2020-04-04 19:43:51 +0200

dumol gravatar image

updated 2020-04-04 19:46:27 +0200

Playing audio files in the default browser is distorted with Sailfish 3.3. For example, the OGG file at https://en.wikipedia.org/wiki/Clair_de_lune_(Debussy)#3._Clair_de_lune_(Moonlight).

But same thing happens for MP3s, wave files, etc. I've tried both 44.1kHz and 48kHz samples.

Audio playing is fine for videos though…

edit flag offensive delete publish link more


Can reproduce (Jolla phone). For me, this is a no-go bug, definitely. Other browser regressions introduced with Nuuksio still not fixed.

objectifnul ( 2020-04-05 01:54:57 +0200 )edit

I see this behavior only when using the player in wikipedia, opening the ogg-file and playing it - still in the browser! - it works fine.

Sebix ( 2020-04-05 10:40:05 +0200 )edit

Soundcloud.com is also not working (J1)

jello ( 2020-04-06 10:42:22 +0200 )edit

Funny ... It seems the problem is somehow related to wikimedia embedded player. If you klick on the song name and open ogg file itself (still in the browsers) it plays correctly.

Valentin ( 2020-04-06 11:22:28 +0200 )edit

Have reverted to 3.2, so can't test anymore, but this happened for me on other sites as well, including some that had no embedded players, only links to WAV or MP3 files.

dumol ( 2020-04-08 11:38:02 +0200 )edit

answered 2020-04-30 09:24:52 +0200

celeron55 gravatar image

updated 2020-04-30 09:26:47 +0200

There now seems to be a rather annoying problem getting back to an Android app that opened another Android app.

For example if you tap a link in Discord and Firefox opens a new tab to show the linked page, you cannot get back to Discord until you close the entirety of Firefox. If you try to, the OS will immediately switch you back to firefox, which may not even be showing the page anymore, if you closed the tab already.

In this example, to be able to look at Discord again, you have to close Firefox, then switch to discord, and then you can launch Firefox again without making it interfere with Discord. Until you open the next link in Discord, of course.

Am I crazy, or is this happening to others too? This is on the XA2. Any workarounds?

edit flag offensive delete publish link more



Yeah, getting the same sort if problem on my xa2. On a messaging app if i try to attach a file or send a photo through it, it opens the file manager or camera app seperately, won't let me attach anything and takes several attempts to exit either of the apps. Probably going to downgrade when i get the chance

ziggystan ( 2020-04-30 12:20:04 +0200 )edit

can confirm. h4113. very annoying. had these errors after a fresh install after factory reset.

samsy ( 2020-04-30 14:00:17 +0200 )edit

Did that still happen on a fresh install to Possibly only way round it for now is downgrade?

ziggystan ( 2020-04-30 14:13:26 +0200 )edit

I can confirm. I notice the same behaviour on xperia 10 (i4113). I followed the normal upgrade path, A fresh install is probably not a solution?

border ( 2020-05-08 11:57:48 +0200 )edit
Login/Signup to Answer

Question tools



Asked: 2020-02-04 14:21:28 +0200

Seen: 41,594 times

Last updated: Jun 07 '20