Ask / Submit
77

[release notes] 3.0.1 Sipoonkorpi

asked 2018-12-14 12:10:07 +0200

jovirkku gravatar image

updated 2019-01-18 13:41:53 +0200

Sipoonkorpi is mainly a bug fixing update, bringing in just a few new features. We've added Bulgarian language support and improved the handling of email folders. You can now create light ambiences, and respond to meeting invitations through Exchange and Google. We've also tuned up SD card encryption and protected critical Top Menu toggles with the security code.

Many thanks to you our active contributors for your feedback and proposals, again!

Table of content

Update version history

  • 2019-01-07 : 3.0.1.11 released to Early Access subscribers (Jolla devices, Xperia X and XA2).
  • 2019-01-16 : 3.0.1.11 released as an OTA update to all subscribers (Jolla devices and Xperia X and XA2). Installable images for Xperia X and Xperia XA2 range of devices will be 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.0 to 3.0.1: about 300 MB
- Jolla C from 3.0.0 to 3.0.1: about 340 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.0. The release notes of 3.0.0 can be found here: https://together.jolla.com/question/191509/release-notes-300-lemmenjoki/

The instructions for installing Sailfish OS to Sony Xperia X and XA2 devices are here - covering Windows, Linux and Mac computers. Note that the instructions of Xperia XA2 differ slightly from those of Xperia X.

The supported Sony Xperia XA2 models are (they are the same as in update 3.0.0 - 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.1 is compatible with Gemini PDA. Initial support only as of now.

Accounts

  • You can now accept/reject meeting invitations of Google

Aliendalvik

  • Android Support for Xperia XA2 will be released separately later
  • No changes for any products

Ambiences

  • You can now create your own light ambiences in Gallery
  • Calculator operation buttons and field legibility improved
  • Media cover polished for light style
  • Call dialog polished for light style

Camera

  • Video timer value not shown on Stop button any more when recording
  • Fix invisible toggles being interactive
  • Hide settings overlay menus when controls are hidden

Calendar

  • You can now respond to Active Sync and Google meeting invitations from Calendar
  • Calendar event view layout polished
  • Deleting open event at remote end pops the page on the device
  • Adjusting event start times now moves the end times to maintain event length

Connectivity

  • Support added for reading NFC tags - initially limited to a customer device
  • A new firewall system using iptables is implemented (rules set in configuration files), no UI yet
  • Firewall is set to block ICMP
  • Firewall configuration for developer mode allows SSH (in addition to usb) over WiFi only
  • Xperia X: an improvement mobile data connectivity
  • Allow enabling hotspot even if mobile data is not connected
  • MTP: Support added for M4A audio file format

Email

  • Email folders can now be created, renamed, moved and deleted on the device
  • Added option to "Sync" to the context menu of email accounts
  • Made possible to accept/reject meeting invitations for Google
  • Exchange attachments prevented from getting corrupted
  • Fix for the issue of "Problem with sync" appearing on email cover
  • Email recipient field not reacting to touch after defocusing fixed
  • Email sync peak start-stop time selection fixed
  • Support for user-generated light ambiences added Or "You can now create your own light ambiences"
  • Redesigned image editing dialog that combines crop, brightness, contrast and rotate dialogs into one
  • The edited photo is now opened after editing

Hardware adaptation

  • HWC2 graphics support for XA2 and future devices implemented

Homescreen

  • Screenshots are now written to disk asynchronously to keep system responsive
  • Regression with App Grid layout on landscape orientation fixed
  • Password dialog handles long texts better

Localisation

  • Bulgarian language added to Sailfish OS. Massive thanks to a handful of Bulgarian students for translating the OS from scratch, благодарим!

Messages

  • SIM selection prompt shown only once now when selecting multiple recipients

People

  • Issue of Google contacts getting sometimes lost was fixed

Security - vulnerabilities fixed:

  • kernel: CVE-2017-1000112 (not yet fixed for jolla1)
  • Access to SSH port restricted
  • Crypto API implemented for Sailfish OS. Centralized point for certification assessments and encapsulating crypto keys

Settings

  • Account credentials are no longer backed up

Storage

  • After unlocking an encrypted SD card it is now mounted automatically

Top menu

  • Top Menu is now protected when device is locked up
    • Organise is disabled until the device is unlocked
    • Most of the toggles and shortcuts cause the security code dialog to appear (but not flash light or ringing volume and the like)
    • Unlocking device after toggling settings now commits the action instead of opening respective settings page
    • Shortcuts are now only triggered after unlocking the device (before only access was blocked)
  • Introduced short system setting name variants to Top Menu
  • Introduced font size toggle for Top Menu

UX

  • Blur backgrounds added for Top Menu, App Grid and system dialogs for style and better legibility
  • Prevent dialog header blinking during transitions

Weather

  • Current weather information is shown now without unlocking the device
  • Use localized decimal separator on precipitation

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.

Changelog

For detailed changelog, see https://together.jolla.com/question/195733/changelog-301-sipoonkorpi/

For those porting Sailfish to other devices

We have applied some new kernel configuration options in Sailfish OS release 3.0.1. If you have ported Sailfish OS to some devices then you may need to apply the corresponding options to successfully use release 3.0.1 in yout target device.

  • Devices affected: All devices which do not have CONFIG_NETFILTER_XT_MATCH_CONNTRACK kernel config enabled
  • Changes needed: Enable CONFIG_NETFILTER_XT_MATCH_CONNTRACK kernel configuration, see this reference

Updating your device

Your device must be connected to the Internet and signed into your Jolla account. If your Jolla account is registered for Early Access releases you should receive an OS update notification when an update is available. If you have decided not to take the Early Access registration then you will get the OS update typically one week later.

We warmly recommend making some 3-4 GB of free space to the internal storage of your device before starting the update. Move your pictures and videos to the SD card (or to your PC or cloud service). After the upgrade turn on the option to save pictures and videos directly from the camera to the memory card (Settings > Apps > Camera). This is important particularly in case of "Jolla 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, visit Zendesk: https://jolla.zendesk.com/hc/en-us/articles/201836347

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

  • An encrypted but unlocked SD card is not reachable via MTP/USB to/from a PC.
  • Due to the introduction of new firewall (see chapter "Connectivity") it may be that some of the incoming connections fail to work now with update 3.0.1. We are looking into fixing this.
  • 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 colours of different objects when using the ambiences that have light background colours.
  • Use of IPv6 iptables rules is limited due to a bug (to be fixed in 3.0.2)
  • Disabling a calendar account does not necessarily prevent the appointments from alerting.

Known issues specific to Xperia X

  • NFC not working
  • 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: https://jolla.zendesk.com/hc/en-us/articles/115004283713
  • Manual network/carrier search lists all networks by the same name (the name of the SIM provider). Use automatic search. If not possible, you need to try several items in the manual search results, unfortunately. The top most item is not necessarily the one that can serve you (still valid with most SIM cards)
  • [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
  • Xperia X does not power up when alarm time has elapsed
  • Bluetooth: Still problems with car equipment, some audio devices and computers.
  • Sensors:
    • Not working: step counter, NFC
  • Waking up the device by double-tap does not work
  • Loudspeaker volume level cannot be adjusted high enough (but echo cancellation was added to the audio path in 2.1.4)
  • FM radio missing
  • Not all SD cards are recognised and mounted.

Known issues specific to Xperia XA2

  • Flashing Sailfish X to XA2 might still fail (so far seen to happen on Ubuntu 18.04 when using USB3 port). Please read https://jolla.zendesk.com/hc/en-us/articles/360012031854
  • NFC not working
  • Fingerprint detection not working
  • Bluetooth: initial support only
  • FM radio not implemented
  • XA2 does not power up when alarm time has elapsed
  • Display blanking is unstable during phonecalls or alarms (due to proximity sensor).
edit retag flag offensive close delete

Comments

10

Thank you guys... Great work... Keep on going !!

xneo ( 2019-01-07 16:47:51 +0200 )edit
7

Nice to see another update :)

Dylan Van Assche ( 2019-01-07 16:56:42 +0200 )edit
5

Thanks, gonna try to update.

Jarno ( 2019-01-07 17:27:43 +0200 )edit
2

Still no Qt upgrade. Come on!

LemD ( 2019-01-07 17:30:43 +0200 )edit
7

Great so see progress! Unfortunately no progress regarding Android support.

SagaciousT ( 2019-01-07 17:33:59 +0200 )edit

14 Answers

Sort by » oldest newest most voted
7

answered 2019-01-08 07:46:44 +0200

ghling gravatar image

Great to see another update, thanks for the work.

What exactly do you mean by

Support added for reading NFC tags - initially limited to customer device

?

Can you please explain the "limited to customer device" a bit more?

edit flag offensive delete publish link more

Comments

7

Currently NFC is being developed for one device model of a business customer.

jovirkku ( 2019-01-08 09:50:13 +0200 )edit

Ah, like the INIO R7 or the Jala Accione?

Venty ( 2019-01-08 12:45:24 +0200 )edit
6

answered 2019-01-09 00:59:20 +0200

Armadillo gravatar image

updated 2019-01-09 01:01:03 +0200

It's good to see more updates, but the issues with car equipment are annoying. Guys do you ever plan to fix this or do I have to change back to Android? It really sucks and it's dangerous if you can't call hands free while driving... This issue exists since Xperia X got SFOS. I'm running out of patience.

edit flag offensive delete publish link more

Comments

Which issues? I had never any problems using my Jolla, Jolla C or Xperia XA2 in my Opel Astra.

balta ( 2019-01-09 04:00:50 +0200 )edit
1

Connections between my Jolla C and a couple of VWs have been consistently unreliable. Dual SIM HFP, A2DP - there are several threads about these.

DaveRo ( 2019-01-09 10:28:36 +0200 )edit
1

@balta there are numerous entries here on TJC mentioning problems with (car) BlueTooth equipment that worked (pre-2.0-ish). Every update seems to add devices to the problem list. As far as I understand, noone puts work into the bluez4 version of JP1 (and probably other devices) and bluez5 (used on more modern devices) is significantly different in design concepts, making it very difficult to support all features across all platforms with so many layers in-between (bluez, QT, hardware drivers, ...). I seriously hope they manage to at least upgrade all devices to bluez5 and get rid of much code ...

Maus ( 2019-01-09 11:00:44 +0200 )edit
1

@balta: As @Maus already said, there are multiple reported issues. I for myself can not even pair my Xperia X with my Hyundai i40 navigation system. Every time I need to enter the pairing code the pairing instantly fails. With some systems it works (e.g. in a Ford Kuga I rented some days ago), but with many it doesn't pair.

And if it pairs there are other issues like bad sound quality, because of bad sound quality negotiations between the smartphone and the navigation system.

Armadillo ( 2019-01-09 11:07:38 +0200 )edit

I know about a lot of threads about that issue and I had some problems with VW car system as well. However: my wife has an iPhone and she has exactly the same problems. So maybe it's a problem with the car system and not with Sailfish?

naytsyrhc ( 2019-01-11 11:58:33 +0200 )edit
4

answered 2019-01-08 12:58:29 +0200

jsommer gravatar image

updated 2019-01-09 00:39:23 +0200

olf gravatar image

Hello Sailfish friends. Just ine note. The regular update approach failed:

 devel-su
 ssu re 3.0.1.11
 version --dup
 reboot

The following approach was successful on my Intex Aqua Fish after the first one failed.

devel-su 
pkcon refresh 
pkcon -v update

Have fun with the light ambience, that is available now.

edit flag offensive delete publish link more

Comments

4

Why type 2.2.1.18 when this update is named 3.0.1.11 ? , probably why it failed or is this just an example?

'Light' ambience has been available since 3.0.0.5 / 3.0.0.8

Edz ( 2019-01-08 15:07:24 +0200 )edit

Sorry, a typo. I'll edit this. Thanks for the hint.

jsommer ( 2019-01-08 22:17:41 +0200 )edit
2

The amendment has failed in the first attempt. The typo has only evolved slightly and still prevails in a new manifestation. Only two more digits till its done ;-)

Vieno ( 2019-01-08 23:25:00 +0200 )edit

Thank you @jsommer for sharing this. I had to upgrade that way since 2.0=>2.1, as I always got those dreaded "Could not determine size of update" messages from the GUI, version --dup told me that I could not install two identical packages of a hardware abstraction package at the same time and the information on the corresponding Zendesk page did not help at all.

Today, after successfully updating to 3.0.1, I decided to factory reset the device, because Email (well, the UI part at least, com.jolla.email.ui) refused to start (background services still worked well, as "new email" messages were shown).

Unfortunately, the phone stopped working after the factory reset while downloading some SFOS 1.1 version and refuses to boot from now on. The Zendesk recovery article "explicitly for Jolla 1" mentions Xperia phones and seems to be outdated for certain OSes. Bummer.

Maus ( 2019-01-09 10:19:22 +0200 )edit

I've bricked my Intex Aqua after updating from 3.0.0.5 -> 3.0.0.8 -> 3.0.1.11, I had to do reset to factory :( Actually I've done @coderus "Intex think it's Jolla C" and I'm going to update till my setting let it me to the last possible update. Then maybe I'll stop on 3.0.0.8, that update boots without problem.

tom.i ( 2019-01-10 20:25:42 +0200 )edit
2

answered 2019-01-08 10:35:01 +0200

this post is marked as community wiki

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

updated 2019-01-08 10:35:01 +0200

OptimistiJolla gravatar image

While eagerly waiting for an update / fully functional OS for Xperia XA2 how has the phone easily slides onto hold / activates loudspeaker / adds second call / activates number pad bug been adressed?

I have understood this is a proximity sensor issue. What other causes, and more specifically, fixes for this issue are there?

At this rate as long as it is not addressed the Xperia XA2 isn't really usable.

Please do fix this.

edit flag offensive delete publish link more

Comments

The simplest workaround is simply to lock the phone screen with power key before putting the phone on your ear.

There is also a way to disable the proximity sensor, but that has concrete drawbacks.

Direc ( 2019-01-08 10:44:46 +0200 )edit
2
2

answered 2019-01-09 01:56:46 +0200

FireFly gravatar image

(XA2, regression) Unstable tethering

After installing 3.0.1.11 on the XA2 (regular GUI update process), hotspot functionality seems to have regressed somewhat. Specifically, I'm noticing the following behaviour: when USB cable is connected and screen remains on (with "keep screen on when charging" being set), tethering works just fine, as before. However, if I enable hotspot whilst not charging and turn screen off, tethering remains up but my connection drops out every few minutes, periodically.

This feels like an issue with the hotspot not grabbing a wakelock/similar properly... I don't recall having any issues with tethering prior to this update (and I just got back after a visit abroad, which involved plenty of tethering). I haven't investigated the issue in-depth, but it seems like a problem that should be easy to reproduce.

Also, in general, do you want reports of regressions in an early-access update like this to be reported in answers, or as separate questions? In this case, and for future reference. (It'd be useful to mention explicitly how you want issues reported, perhaps).


Also, super minor point: the wording "3.0.1.11 to be released to Early Access subscribers (Jolla devices and Xperia X)" confuses me a bit: "Xperia X" is a specific model, so I was slightly surprised when I saw the update on my XA2. Either "Sailfish X devices" or "Xperia devices" or perhaps "Xperia X & XA2" would've been more easily understood, I think.

edit flag offensive delete publish link more

Comments

I have Xperia X and Xperia XA2 Plus both with 3.0.1.11 Since update to 3.0.1.11 USB Tethering with PC (Linux) works only when i have Development Tools (Development Modus) activated.

naalaa ( 2019-01-10 18:38:43 +0200 )edit

I suspect your problem has probably got something to do with how they added a new firewall (iptables) in this update and it's not really been configured for tethering just yet. The notes add that they've already got some known bugs related to it.

L_A_G ( 2019-01-11 12:52:39 +0200 )edit
1

FireFly wrote: Also, in general, do you want reports of regressions in an early-access update like this to be reported in answers, or as separate questions? In this case, and for future reference. (It'd be useful to mention explicitly how you want issues reported, perhaps).

I would think regressions, other detailed observations regarding functionality and feature requests should preferably be reported as separate questions, tagged with the relevant update ID (e.g. 3.0.1 - leave the last digit away from the tag).

Thanks, goading, general complaints and blames should appear as answers or comments here, in the context of the release notes.

jovirkku ( 2019-01-16 12:45:50 +0200 )edit
1

answered 2019-01-11 12:08:14 +0200

naytsyrhc gravatar image

With 3.0.0 a security feature was partly introduced, that disabled access to toggles in Top menu if device is locked. I posted a question about that: https://together.jolla.com/question/193459/allow-top-menu-shortcuts-toggling-on-locked-device/

With 3.0.1 you made the changes more consistent, but now all toggles are disabled on locked device and I always have to unlock device now (except for torch toggle). I appreciate a consitent UI but I'd still be happy to have that behaviour configurable. I want to start VPN without unlocking device or enable/disable Wifi without unlocking. So my question above still persists.

Do you have plans to make this configurable?

edit flag offensive delete publish link more
1

answered 2019-01-12 13:17:13 +0200

Bart S gravatar image

I see that ICMP is disabled in the firewall now.

I use ping's in my home network to detect if my phone is connected to wifi, and then do some actions. That does not work anymore. How can I change the firewall settings to allow pinging the phone again ?

edit flag offensive delete publish link more

Comments

1

Check devel-su iptables -S for ICMP rules and just remove the corresponding rule with iptables -D .... if thats a rule that rejects somehting, or just add another exception to allow ICMP.

bomo ( 2019-01-12 15:03:22 +0200 )edit
2

Good catch; I just now realised that this is the case.

In my opinion it is fairly useless thing as a security measure to block ICMP, as arp anyway shows that the device is present.

To fix this, do "iptables -R connman-INPUT 4 -p icmp -j ACCEPT" as root

juiceme ( 2019-01-12 15:10:20 +0200 )edit
2

And as I now checked you can make the change permanent by editing the firewall rule file that blocks icmp; /etc/connman/firewall.d/10-block-icmp-firewall.conf

juiceme ( 2019-01-12 16:17:14 +0200 )edit

been there, done that, and it works. both INPUT and OUTPUT are set to ACCECPT. The 10-block-icmp-firewall.conf then contains these two lines for IPv4 : IPv4.INPUT.RULES = -p icmp -m icmp ! --icmp-type 8/0 -j ACCEPT and IPv4.OUTPUT.RULES = -p icmp -m icmp ! --icmp-type 0/0 -j ACCEPT

Bart S ( 2019-01-12 17:11:19 +0200 )edit

Yes, you need to edit those so that it contains;

IPv4.INPUT.RULES = -p icmp -j ACCEPT

IPv4.OUTPUT.RULES = -p icmp -j ACCEPT

juiceme ( 2019-01-12 17:13:35 +0200 )edit
1

answered 2019-01-16 09:59:18 +0200

Nekron gravatar image

New features and new (minor) bugs: The weather information on lockscreen does not update automatically if device is woken up. It's also visible if weather widget is turned off on notification screen (this should also turn off the info on lockscreen).

Other than that great update and works flawlessly on my Sony X.

edit flag offensive delete publish link more
1

answered 2019-01-16 19:55:28 +0200

this post is marked as community wiki

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

updated 2019-01-17 16:14:16 +0200

carmeloferso gravatar image

2019-01-16 : 3.0.1.11 released as an OTA update to all subscribers (Jolla devices and Xperia X). Installable images for Xperia X and Xperia XA2 range of devices will be available at https://shop.jolla.com/downloads/ .

Still not available in the shop page the 3.0.1.11, the files downloaded are for the 3.0.0.8

Update: 3.0.1.11 is available

edit flag offensive delete publish link more

Comments

Correct. Also I don't know why they don't simply offer it as an OTA-update. I think it's going to be quite a hassle to update my SFOS via this route...

Do you know how updating will work? Do I have to completely reflash my XA2 with a new image? I would definitely like to avoid that.

laubblaeser ( 2019-01-16 21:22:38 +0200 )edit

Maybe XA2 will get an update with Android layer?

wosrediinanatour ( 2019-01-17 11:33:15 +0200 )edit
3

@laubblaeser: we do offer the updates for XA2, too, as OTA updates, they have been available since yesterday. I just forgot to and "XA2" to my text in the beginning of the release notes. Sorry. Seek for updates in Settings > Sailfish OS updates.

@carmeloferso: the downloadable 3.0.1 images of X and XA2 will be available in an hour or so.

jovirkku ( 2019-01-17 13:58:17 +0200 )edit
0

answered 2019-01-08 16:06:04 +0200

tabasko gravatar image

First update attempt failed. On second try updater booted automatically. It seems some packages were left updated as volume rocker didnt work after multiple boot ( no volume visualization or affect to volume level which was mute). After running version --dup from terminal multiple packages were uodated and volume rocker started to work after reboot

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
19 followers

Stats

Asked: 2018-12-14 12:10:07 +0200

Seen: 13,628 times

Last updated: Jan 18