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

[release notes] 3.0.3 Hossa [released]

asked 2019-04-12 10:39:18 +0300

jovirkku gravatar image

updated 2019-06-14 10:10:59 +0300

In Hossa there have been many upgrades under the hood, fixing security vulnerabilities and improving stability and compatibility in several fundamental components such as Gecko, GCC, and the GNU C Library. This technology update mostly paves the way for new features in the next update (3.1.0) though it does also finally fix the long-standing IMAP idle problem. For XA2 devices we have solved the high WLAN-related power drain and the issue of the display turning off during phone calls, plus in Alien Dalvik there's improved file access and notification behavior, and mobile data now works with both SIM cards.

Technical blog about Hossa.

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

Table of content

Update version history

  • 2019-04-24: 3.0.3.8 was released to Early Access subscribers (Jolla devices and Xperia X/XA2).
  • 2019-05-07: 3.0.3.9 as an OTA update was released to all subscribers (Jolla devices, Xperia X/XA2, Gemini PDA).
  • 2019-05-29: 3.0.3.10 as an OTA update was released to all subscribers. XA2: issue with showing the calling line number fixed (all devices); improvements to Android Support of XA2. Flashing scripts of XA2 allow both vendor binaries (v16 and v17) now. Installable images for Xperia XA2 devices will become available at https://shop.jolla.com/downloads/ .

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 1 from 3.0.2 to 3.0.3: about 360 MB
- Jolla C from 3.0.2 to 3.0.3: about 400 MB
- Xperia X from 3.0.2 to 3.0.3: about 360 MB

Release Highlights

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

The instructions for installing Sailfish OS to Sony Xperia X and XA2 devices are here - covering Windows, Linux, and macOS.

IMPORTANT: do not update your XA2 device to Android 9, or else installing Sailfish OS would brick your device.
UPDATE: The flashing scripts for XA2 devices included in update 3.0.3.9 now prevent installing Sailfish OS on Android 9.

The supported Sony Xperia XA2 models are (they are the same as in update 3.0.2 - no change here):

  • 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 (no change here, either):

  • X single SIM F5121
  • X dual SIM F5122

Sailfish OS 3.0.3 is compatible with Gemini PDA variants x25 and x27.

Xperia XA2

  • High power drain while using WLAN fixed
  • The issue with proximity sensor is fixed - now the display does not go blank during phone calls
  • Preliminary support for NFC added
  • Preventing the calling line number from being shown fixed (CLIR), hence prefix #31# works again.

Accounts

  • Network connection checked before proceeding to account creation.

Android™ App Support

  • Android 8.1 App Support Beta for Xperia XA2 devices improved:
    • Mobile data works with both SIM cards for Android apps on XA2 devices now
    • Files recently added to Sailfish side appear now on Android side immediately
    • System UI notifications from Android side are hidden now (Sailfish OS to handle)
    • Notification handling improved, not to repeat grouped notifications on new notifications
    • SSH file transfer no longer crashes alien
  • Improvements in 3.0.3.10:
    • Tapping an Android notification opens the corresponding app now
    • Copy/paste from Android app to Sailfish apps fixed
    • Tapping Stop Android Support button does not blank the display any more
    • Android apps get proper covers now when an app is minimized
    • Watching Youtube videos with Firefox browser works now
    • Unnecessary battery-low notifications from Android apps blocked
    • Some crashes and deadlocks prevented from happening
    • Other small fixes
  • No changes for other products

Audio

  • PulseAudio upgraded to v12. This version of the fundamental audio component brings an improved A2DP latency handling, among other things

Backup

  • SD card is now shown as a storage option reliably

Browser

  • Gecko engine upgraded to esr45 version
  • User agent string updated to reflect engine version
  • User-agent override data created and updated for the new engine

Call

  • XA2: the issue with proximity sensor is fixed - now the display does not go blank during phone calls

Connectivity

  • Status of connections over mobile data now shown correctly on dual-SIM devices

Device Management (MDM) [Corporate API]

  • Cellular policy API introduced
  • Data counters policy API introduced

Email

  • IMAP push in idle fixed. Email synchronization works now even if the internet connection should change

Flashing

  • Flashing script of XA2 devices for Windows PC fixed

Homescreen

  • Busy indication added to USB mode selection; this helps in setting up the MTP connection with devices acting slowly
  • PIN input view backspace visibility improved for Light Ambiences
  • Two-column layout created for PIN query and Device Lock views in Lock Screen for narrow landscape devices

Keyboard

  • Support for hardware keyboard layout variants of Gemini PDA added
  • Heuristics for using Escape key as Power key (e.g. Gemini PDA) without requiring also Fn key press adjusted to reduce chances of interfering with system dialogs

Media

  • Show full-width remorse item when deleting playlists

Messages

  • An issue in sending SMS to multiple recipients fixed
  • SMS delivery reports fixed

Phone

  • Call UI recovers better from subsystem crashes

Power management

  • Don't set battery warning notifications twice when passing low battery level
  • XA2: High power drain while using WLAN fixed

Security - vulnerabilities fixed:

  • glibc-2.24: CVE-2016-3075, CVE-2016-1234, CVE-2015-8779, CVE-2015-8778, CVE-2015-8777, CVE-2015-8776, CVE-2015-7547, CVE-2015-5277, CVE-2015-1781, CVE-2015-1473, CVE-2015-1472, CVE-2014-9761, CVE-2014-9402, CVE-2014-8121, CVE-2013-7423, CVE-2014-6040, CVE-2014-4043
  • glibc-2.25: CVE-2017-15670, CVE-2017-15671, CVE-2017-15804, CVE-2017-1000408, CVE-2017-1000409, CVE-2017-16997
  • gcc-4.9.4: CVE-2015-5276
  • openssh-7.9p1+git2: CVE-2019-6111, CVE-2019-6109, CVE-2018-20685
  • zlib-1.2.11: CVE-2016-9843, CVE-2016-9842, CVE-2016-9841, CVE-2016-9840
  • ncurses-6.1: CVE-2017-13734, CVE-2017-13733, CVE-2017-13732, CVE-2017-13731, CVE-2017-13730, CVE-2017-13729, CVE-2017-13728, CVE-2017-11113, CVE-2017-11112, CVE-2017-10685, CVE-2017-10684
  • pcre-8.42: CVE-2016-3191
  • cpio-2.12: CVE-2016-2037
  • util-linux-2.33: CVE-2017-2616
  • icu-63.1: CVE-2013-1569, CVE-2013-2383, CVE-2013-2384, CVE-2013-2419, CVE-2014-6585, CVE-2014-6591, CVE-2014-7923, CVE-2014-7926, CVE-2014-7940, CVE-2014-9654

Sensors

  • XA2: the issue with proximity sensor is fixed - now the display does not go blank during phone calls

Settings

  • Ensured that a notification to change the WLAN password is shown always after an incorrect one was typed - also when the password had been changed on the WLAN base station
  • Backup settings failing to offer memory card option fixed

UI components

  • Many text editor and menu view autoscrolling regressions fixed
  • Disabled text fields now look disabled

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

Changelog

Detailed changelog is available here. - Several fundamental components upgraded such as the browser engine Gecko (esr45), toolchain GCC (4.9.4) and the GNU C Library (2.25) - Gemini PDA: a memory fix to allow booting from Android 8 bootloader.

Behavioural changes in Sailfish OS

  • /home is no more mounted at init - it is handled later by systemd; this is to avoid problems when the /home directory is encrypted

For those porting Sailfish to other devices

  • (no particular news this time)

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: Sailfish OS does not support downgrading. Never try to downgrade the OS as this would brick your device.

Notification concerning apps from Open Repos

  • 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

  • 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

  • Bluetooth pairing and audio connections may still fail in some circumstances
  • Some Facebook services (syncing FB events to Calendar; uploading pictures to FB from Gallery) do not work (independent of your OS release) due to some changes at the FB end.
  • Light ambience concept of Sailfish 3 needs polishing and tuning up. There are still issues with the colors of different objects when using the ambiences that have light background colors.
  • Disabling a calendar account does not necessarily prevent the appointments from alerting.
  • The chacha20-poly1305 cipher is not currently working, which is often chosen for SSH. It has been disabled in the sshd configuration file, but if you have manually modified it then it will not automatically update. You can ssh into your device using 'ssh -c aes128-ctr' and check the /etc/ssh/sshd_config file against its 'rpmnew' version if present.

Known issues specific to Xperia X

  • Not implemented features: NFC, FM radio, double-tap, step counter
  • 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 try to take a shot - but the pictures seem to be better focused now
  • If a device is powered off alarms are not functional
  • Bluetooth: problems with some car equipment, some audio devices and computers may appear
  • Loudspeaker volume level cannot be adjusted very high
  • Not all SD cards are recognized and mounted.

Known issues specific to Xperia XA2

IMPORTANT: do not update your XA2 device to Android 9, or else installing Sailfish OS will brick your device. Currently, Sailfish OS requires Android 8.1. UPDATE: The flashing scripts for XA2 devices included in update 3.0.3.9 (and 3.0.3.10) now prevent installing Sailfish OS on Android 9.

The renewed flashing scripts of update 3.0.3.9 and 3.0.3.10 prevent installing Sailfish OS on top of Android 9 (which has baseband version 50.2.A.xx.yyy).

  • Not implemented features: fingerprint detection, FM radio, double-tap
  • 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 have 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. The renewed flashing scripts of update 3.0.3.10 allow you to use either of the two versions. You can also reflash just the vendor image of your choice (and not Sailfish OS) by following the instructions in here.
  • Voice calls with Whatsapp are not usable as the voice volume level is minimal (if can be heard at all).
  • Video playback in Whatsapp requires special actions: 1) Tap on video 2) Tap the share button (top right) 3) Tap back arrow 4) Tap Play on the video. Now it starts playing...

Known issues specific to Gemini PDA

  • 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 reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2019-12-28 22:18:46.834475

Comments

3

Excellent, this update came earlier than expected. I can confirm that I can use mobile data <edit>on XA2</edit> now with Android app "DB Navigator" (Ticket app of Deutsche Bahn) with SIM1, SIM2 and on Wifi. Its network access has been very sensitive so far. Hope it will stay like this in every days use.

Cheers mates!

jollajo ( 2019-04-24 15:59:28 +0300 )edit
2

Interesting in my case it doesn't even work on Wifi. Also the other Android apps that had no mobile connection before are unable to connect.

scharelc ( 2019-04-24 17:28:20 +0300 )edit

@scharelc it didn't work instantly. First I updated my tickets and then checked for connections. Loading tickets has been more robust on XA2 than searching for connections. Just tried my banking app by Sparda-Bank, which used to be also rather picky and it also works. However switching from SIM2 to SIM1 didn't work without restart of the app.

jollajo ( 2019-04-24 18:52:24 +0300 )edit
16

Gecko engine upgraded to esr45 version

This is the single most important thing in this update. 45 is a lot better than what we have, but it's not enough. Is there a plan for when Gecko will be updated the next time, and to what version?

bocephus ( 2019-04-24 19:37:49 +0300 )edit

"Issue with proximity sensor is fixed - now the display does not go blank during phone calls" sounds good.

But my problem was not only that the display went blank, it was that the touch display was not disabled and I've inititated unwant actions with my ear, such as turning microphone off.

Is this also fixed?

SagaciousT ( 2019-04-24 20:55:00 +0300 )edit

25 Answers

Sort by » oldest newest most voted
0

answered 2019-04-25 14:25:51 +0300

martijntje gravatar image

Can anybody tell me what I can do after a download got interrupted and now prevents downloading again due to too little space available on the root device?

I have rebooted the phone - in case some process kept the file open - but / has only 408 MB available, which is not enough. First time I opened the update tool there was enough space, so I'm quite certain it's due to this interrupted update.

edit flag offensive delete publish link more

Comments

Thanks. This didn't work, but extending the / partition did. I shrunk /home (to 32GB) and extended / by 2GB. Nice thing is the volume group now has almost 30GB free, to allocate when I need it.

martijntje ( 2019-04-26 11:48:16 +0300 )edit
0

answered 2019-05-02 16:49:55 +0300

Filip K. gravatar image

Please keep us in info loop about not updating "XA2 device to Android 9" before flashing SFX as the warning was too late for me :(.

edit flag offensive delete publish link more
0

answered 2019-05-17 09:49:43 +0300

skkayman gravatar image

I just bought XA2 (which was pretty hard to find with unlockable bootloader) and Sailfish X to find out that I cannot install Sailfish because the phone already has Android 9 :(. What now? Even factory reset and not allowing updates = android 9. Can I downgrade it to Oreo? How??

edit flag offensive delete publish link more

Comments

Maybe check whether you can downgrade using https://developer.sony.com/develop/open-devices/get-started/flash-tool after unlocking your bootloader.

bomo ( 2019-05-17 12:52:03 +0300 )edit

I have to find working windows pc for Sony toole - Emma..

skkayman ( 2019-05-17 18:48:06 +0300 )edit

@bomo, it has only Pie availabe.. 50.1.A.13.123 :( EDIT: I just realized that 50.1 is Oreo and 50.2 is Pie, flashed to Oreo with Emma. Now, Sailfish, I hope it will works as there was Pie previously.. :)

skkayman ( 2019-05-17 21:32:40 +0300 )edit

I hope it did work.

Filip K. ( 2019-05-29 22:49:45 +0300 )edit

How to flash Andoid back without Windows? Could a virtualization application be used on linux desktop?

VoPa ( 2019-05-30 13:35:30 +0300 )edit
0

answered 2019-06-03 02:50:50 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2019-06-03 03:09:08 +0300

shatunga gravatar image

i really like the update and i will naver stop updating my phone when never there's a new update available. And please when you are going to release a new update please make sure that you add some notification settings where we will be able to turn Off and On some notifications. Because some notification are very irritating like whatsapp notifications and notifications from browsers when you're downloading somethings. These notification will popup and when you slide to remove them they will go away but just within a second they will popup againg and againg and they will be like they frozen up.

This irritates me so much like when never I'm playing my games or doing something els with my device, it brocks my view. And please the last thing is introduce an auto phone unlocker like when you have just punched in a correct your phone pin it will unlock automatically or please if not then try to introduce another mathod of unlocking these devices please, one method is not just not enough.

edit flag offensive delete publish link more

Comments

1

If you're on XA2 (and Android 8.1), you can turn notifications on and off and do other Android related stuff by using AliendalvikControl. You can get it from OpenRepos

teemu ( 2019-06-03 06:43:57 +0300 )edit

nop my android is below that bro.

shatunga ( 2019-06-06 20:01:57 +0300 )edit

I have been looking for this information for a long time, I was very surprised when I found it here. 192.168.1.1

malkovich ( 2020-08-31 12:10:22 +0300 )edit
0

answered 2019-06-04 23:01:29 +0300

meolic gravatar image

Right now, I started update checking an my XA2 offer me an update to 3.0.3.10. But, I have this update from day one, i.e. for weeks. Morevoer, the size of the proposed update is only 1MB . What is going on??!!

edit flag offensive delete publish link more

Comments

1

You are probably on 3.0.3.9, not .10. It updates only a few android libraries. My personal advise is: do the update only if you currently see problems with connectivity on Android. There are reports that this patch makes things actually worse: https://together.jolla.com/question/206919/bug-wlan-issue-in-android-30310/

Dakon ( 2019-06-04 23:13:03 +0300 )edit
1

The update from 3.0.3.9 to 3.0.3.10 was 1 MB for me too (and hopefully for everyone). It is what it is.

teemu ( 2019-06-05 00:37:52 +0300 )edit
1

@teemu: on the XA2 the update was much larger, >200MiB, due to the updated Android packages.

Fuzzillogic ( 2019-06-05 00:41:13 +0300 )edit

@Fuzzillogic, I updated two phones (aqua Fish and XA2) from 9 to 10. I can't swear but I think it was very small download for both phones.

teemu ( 2019-06-05 04:02:27 +0300 )edit

I can read the following:

Update version history

2019-05-29: 3.0.3.10 as an OTA update was released to all subscribers. XA2: issue with showing the calling line number fixed (all devices); improvements to Android Support of XA2. Flashing scripts of XA2 allow both vendor binaries (v16 and v17) now. Installable images for Xperia XA2 devices will become available at https://shop.jolla.com/downloads/ .

So, is it true, that 3.0.3.10 is available from 2019-05-29? Because, I updated my XA2 long time ago and the phone reports, that I am using Hossa (3.0.3.10). I have not installed this 1MBupdate, yet.

meolic ( 2019-06-05 14:29:57 +0300 )edit

Question tools

Follow
21 followers

Stats

Asked: 2019-04-12 10:39:18 +0300

Seen: 29,651 times

Last updated: Nov 13 '19