Ask / Submit
84

[release notes] 3.1.0 Seitseminen

asked 2019-06-27 15:26:52 +0300

jovirkku gravatar image

updated 2019-09-03 12:30:38 +0300

Sailfish OS 3.1 is our biggest update since the launch of Sailfish 3 last year. It features redesigns of many core apps, including People, Phone, Messages, and Clock, driven by extensive UX studies. It also brings small changes to the look of the documents and gallery apps. This all aims to make Sailfish more intuitive, encouraging a more natural usage of the device. The other big focus for this update is security: we introduce disk encryption support (to be rolled out to devices in phases), VPN changes to ensure that your traffic is secure from the first moment you use your phone, and enhanced isolation of many system APIs and functionalities. With many bugfixes and improvements to its Android™ App Support, plus the addition of fingerprint authentication, this update brings Sailfish X for Xperia XA2 officially out of beta!

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

Table of content

Update version history

  • 2019-07-18 : 3.1.0.11 was released to Early Access subscribers (Jolla devices and Xperia X & XA2).
  • 2019-07-25 : 3.1.0.11 was released to all subscribers as an OTA update (Jolla devices, Xperia X/XA2, Gemini PDA). Installable images for Xperia and Gemini devices are 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.3 to 3.1.0: about 360 MB
- Jolla C from 3.0.3 to 3.1.0: about 540 MB
- Xperia X from 3.0.3 to 3.1.0: about 440 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.3. The release notes of 3.0.3 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 .
Currently, Sailfish OS requires Android 8.1. If you already have Android 9 in your XA2 device, please downgrade it to Android 8.1 and install Sailfish OS only then. Please follow these instructions.

The supported Sony Xperia XA2 models are (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 X single SIM F5121 and X dual SIM F5122

The supported Gemini PDA models are x25 and x27.

Xperia XA2

  • Fingerprint authentication is supported now - see Device lock below

Accounts

  • Signing in/on Dropbox fixed

Android™ App Support

  • Android 8.1 App Support for Xperia XA2 devices improved:

    • WhatsApp behaves better after closing video/voice call
    • Android apps work now after invoking them from Events View
    • WLAN support improved. Android apps can detect active WLAN connections now
    • Notifications framework improved. This should make Telegram notifications, for instance, wake up the device, and to make a sound, and to turn LED on
    • Improved stability
    • Translations for recently added display texts added
    • Dimmed app covers should not appear now
    • Closing of Android apps fixed
    • Behaviour of media control buttons fixed during Spotify playback and at lock screen
    • Out-of-memory handling improved
    • Setting 'Allow apps to run in the background' fixed
    • Default AOSP apps (Camera, Gallery, Contacts) removed
    • Telegram and other apps can detect touch-on-display correctly now
    • Adding contacts from Android apps (e.g. Whatsapp) to People app now possible.
  • Android 4.4 App Support for Xperia X and Jolla C

    • TLS v1.2 enabled by default

Bluetooth

  • Bluetooth engine, Bluez, updated to v. 5.50 (on newer devices than Jolla phone and Jolla Tablet). This improves stability, fixes some errors and enables new features

Browser

  • Debugging Browser has been documented now here
  • Support for WebGL (an API used to create 3D graphics in a Web browser) enabled

Calendar

  • You can create ActiveSync (and Google?) meeting invitations in Calendar
  • Delete option disabled for read-only events
  • Calendar event remind me option fixed to remember the last selection by the user again (community contribution)
  • Calendar all day events showing incorrectly fixed
  • Missed calendar event notifications renamed to talk about past calendar events (you may have missed calendar alarm, but not necessarily the event)

Camera

  • Just tap to zoom out of zoomed photo in camera roll (previously was double tap)

Clock

  • Timers, alarms and stopwatch organised as tabs

Connectivity

  • Enabling VPN without (prior to getting) network connection is now possible. This is to ensure that all your traffic is secure from the beginning. The text "Waiting for network..." is shown in Settings in this situation. The Top menu toggle can be enabled regardless of network state.
  • DNS server list is now cleaned up at service disconnect. This makes DNS work faster when changing networks with VPN set to autoconnect
  • VPN credentials dialog customisable by external VPN providers
  • Managing VPN connections is more robust now
  • Password-protected OpenVPN configurations are now supported
  • WPA-EAP extended with ability to include CA certificates and select PEAP method
  • Security code authentication required before user can see WLAN hotspot, mobile access point, tethering and VPN passwords in settings

Device Management (MDM) [Corporate API]

  • VPN policy API introduced
  • MDM Email API regression fixed
  • Fixed an issue where App couldn't be added to autostart

Device lock

  • XA2: Fingerprint authentication can be used instead of typing the security code when unlocking the screen of XA2 devices now. NOTE: Because of this, the implementation of the device lock is different, meaning that the whole feature is re-installed when taking the 3.1.0 update. Consequently, you will need to enable the device lock again after the OS update. Therefore, do not forget to visit Settings > Device lock.
  • Cancel and accept text buttons changed to icon buttons

Display

  • API to prevent screen blanking implemented. Multiple items can prevent blanking - it happens as long as at least one of those wants to have it that way

Documents

  • Redesigned document viewers for PDF, text documents, spreadsheets and presentations (split view UX pattern dropped)
  • Documents app now shows errors with proper Sailfish-style layout
  • Supports opening plain text files, when opening txt file the user is now prompted whether they want to open the file in Documents or import to Notes
  • RTF file text encoding and inline picture handling issues fixed

Email

  • Out of office reminders now supported for Active Sync emails. Exchange account settings has a new section "Automatic replies" with button Modify for this feature.
  • Setting up an Exchange account is more robust now. Busy states with spinners should not remain active too long [https://bz.jollamobile.com/show_bug.cgi?id=44739]
  • Option for signing email messages (using pgp) implemented initially, not enabled by default. This feature is currently only for developers, and advanced users. Email signing only works for generic email accounts.Thanks to Damien Caliste who developed this.

First time use

  • You can now disable hints and tips often shown when you use an app or feature the first time in "Settings > Gestures > Show hints and tips"
  • You can now reset hints and tips when long-pressing the "Show hints and tips" setting and selecting "Reset hints" action
  • Return to home hint shown when user opens app the first time, teaching how to return to home with edge swipe
  • Change keyboard gesture hint shown when user opens the keyboard the first time
  • Close keyboard gesture hint shown few days later
  • Close all apps hint shown when user enters the home (active covers) housekeeping mode the first time
  • Empty Screenshot album instructs user to press left and right Volume keys down to take screenshots
  • Incoming call now always displays answer and reject call hints, tapping answer and reject icons still plays pulley hint animation
  • Just tap to zoom out of zoomed photo (previously was double tap)
  • Don't try to crop with none option
  • Fix timing issue sometimes causing image editing to fail

Homescreen

  • Unresponsive dialog regression fixed

Media

  • Empty search field now shows close icon button
  • Scrolling down to see more search results automatically closes keyboard

Messages

  • Redesigned conversation view
  • Header area introduced that shows the contact of the conversation
  • Message bubbles are better organised visually and in relative date groups
  • Tap message bubble to see full timestamp, used SIM cards and numbers, delivery and read status
    • Info only shown where it makes sense, if the device supports Dual SIM, recipient contact has multiple numbers, read receipts have been enabled, and so on
  • Reply field disabled for service messages from senders with no phone numbers
  • You can now save and edit contacts without leaving the Messages app

Notes

  • Empty search field now shows close icon button
  • Scrolling down to see more search results automatically closes keyboard

OS updates

  • Some stability issues fixed

People

  • Redesigned People app: contact picker, contact card and contact editor
  • Contacts reorganised as alphabetically grouped list, armed with new scrollbar component
  • Contact card shows more efficient layout
  • Contact editor orgranized to prioritise common fields
  • Contacts now support adding note fields
  • Show contact card after creating a contact
  • Selecting and deselecting all contacts is now possible
  • Contacts multi-selection now allows reviewing already selected contacts
  • Search field now always shown on Phone contacts view and People app, but search pulley action still provided for easy one-handed activation
  • Fixed an issue where importing contact with special characters from vcard file lead to crash of People app

Phone

  • Phone refactored into three tabs: Dialer, History and People
  • Redesigned dialer for easier one-handed use
  • Redesigned call history view, supporting basic and detailed modes. Detailed call history allows you to see additional information like call duration and Dual SIM info
  • Incoming call dialog now allows replying to the caller easily with predefined quick messages (ability to customise quick messages is coming in the next release)
  • You can now save and edit contacts without leaving the Phone app
  • Dialer and contacts phone number fields support "." and "," DTMF pause characters common in other OSes in addition to the previous "p"

SDK

  • MDM API added to SDK

SIM

  • SIM indicator shown on Phone call loghistory entries to know which SIM (on dual SIM phones) was used to make the call

Security

  • [XA2] Fingerprint authentication added. .
  • User data encryption (a.k.a. encryption of Home partition) is now supported by the OS. However, this feature is in 3.1.0 only supported for freshly flashed corporate devices and will be deployed in upcoming Sailfish updates to consumer devices.
  • Security code authentication required before a user can see WLAN hotspot, mobile access point, tethering and VPN passwords in settings
  • Malicious use of Phone and Messages interfaces restricted
  • Vulnerabilities fixed:
    • glibc 2.27: CVE-2017-15670,CVE-2017-15671,CVE-2017-15804,CVE-2017-17426,CVE-2017-1000408,CVE-2017-1000409,CVE-2017-16997,CVE-2018-1000001,CVE-2018-6485
    • glibc 2.28: CVE-2016-6261, CVE-2016-6263, CVE-2017-14062, CVE-2017-18269, CVE-2018-11236, CVE-2018-11237
    • openconnect 8.02: CVE-2018-20319
    • libxslt 1.1.33: CVE-2019-11068
    • gdb 8.2.1: CVE-2017-9778
    • binutils 2.32: CVE-2014-9939, CVE-2017-12448 to CVE-2017-12459
    • wpa-supplicant 2.8: CVE-2017-13082, CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088, CVE-2018-14526

UI components

  • Palette API introduced for custom coloring Silica UI components
  • UI components implicitly handle press effects, no need to explicitly bind to highlighted property to implement press effects
  • Text editor cursor now blinks to better visualize what field has the focus
  • The issue with context menus opened at the bottom of the page getting clipped fixed

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 kept here - Extra file systems for Xperia X kernels (e.g. NFS) enabled

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.
  • 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.
  • Problems in accessing Twitter with Sailfish Browser.
  • Gallery and Mediaplayer cannot show any media from an encrypted SD card.

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 .
Currently, Sailfish OS requires Android 8.1. If you already have Android 9 in your XA2 device, please downgrade it to Android 8.1 and install Sailfish OS only then. Please follow these instructions.

  • Not implemented features: 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 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.
  • Voice calls with Whatsapp are not usable as the voice volume level is minimal (if can be heard at all).

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

Comments

1

Downloading now, thanks.

One idea springs to mind, I think it's about time we had an option to hide the wretched tutorial icon, perhaps with a simple option in Settings to hide/unhide it.

Many of us seasoned users have to revert to patches, editing application files or making a 'misc' folder to put unwanted icons - really?, surely we can shake those days of "If we can't hide it, we'll make a feature of it"

Edz ( 2019-07-18 20:28:30 +0300 )edit
5

Should be mention signature spoofing and microg support in there?

TMavica ( 2019-07-18 20:57:19 +0300 )edit

Downloading 3.1.0.11 for XA2 succeeded well on the road in Sweden. :) :)

N9Sailfish ( 2019-07-18 22:03:57 +0300 )edit

Great!! Am installing 3.0.11 on a Xperia X, XA2 and XA2 Plus,.wil install it on Jolla C and Jolla 1 later.

WilliePre ( 2019-07-18 22:13:03 +0300 )edit

@Edz I think they trying to do something with tutorial icon. Look at changelog "[jolla-startupwizard] Work also without tutorial installed,"

atlochowski ( 2019-07-18 22:20:07 +0300 )edit

35 Answers

Sort by » oldest newest most voted
3

answered 2019-07-26 18:53:18 +0300

zlutor gravatar image

updated 2019-07-26 18:54:13 +0300

Please, make Alarms tab the default, visible one in Clock app.

c'mon, alarms are in daily use but timers...

edit flag offensive delete publish link more

Comments

4

Known issue, Alarms will be the default in the next update.

nthn ( 2019-07-26 19:45:06 +0300 )edit
3

answered 2019-07-31 06:48:24 +0300

Default AOSP apps (Camera, Gallery, Contacts) removed

Xperia XA2 plus, everything ok so far, but now Android app requiring file access cannot find a compatibile file browser.

Did you do on purpose? I think the manager should be available without installing 3rd party app.

edit flag offensive delete publish link more
3

answered 2019-08-06 13:36:41 +0300

Maus gravatar image

I just want to note that EA channel detection is seemingly broken.

I opted out of EA a couple of months ago for reasons that don't have to be discussed here. On July 27, I was surprised to see an offer to update to 3.1.0.11 on my J1, and while I was aware of a couple of things that I would rather see fixed ahead of installing 3.1, I was under the impression that this version would have been declared stable/final for 3.1.0. So I accepted the update.

Interestingly, I was not offered to create a backup within this dialog, nor did the mandatory pre-upgrade preparations run. No btrfs-balance, no backup.

After completing the installation process, the phone rebooted, but into 3.0.1. It then offered me an update to 3.1.0.11, weighing a surprising 3 MB only. And interestingly, this time I was offered doing backups and the preparation steps were worked through. The installation process then finally rebooted into 3.1.0.11.

In another question, @sailaway sees a "downgrade" notification after leaving the EA channel. While I am no longer on EA, I wonder why my phone got EA software and why I am not offered a downgrade.

edit flag offensive delete publish link more

Comments

1

The Jolla blog suggests that 3.1.0.11 is stable, while this document does not (yet). Thanks to Filip K. for pointing this out.

Maus ( 2019-08-09 14:20:41 +0300 )edit
2

answered 2019-07-19 01:07:30 +0300

Georgi Kolev gravatar image

Updated to 3.1 on XA2.

So far no issues. Updated went okay. Fingerprint works!

edit flag offensive delete publish link more

Comments

9

I find it weird that you have to scan your finger twice to actually unlock. The first tap wakes the screen which also allows to use the pincode, but only the second unlocks the phone. And because of a delay for the screen to fade in, you can't tap twice in rapid succession, but have to wait a second or so.

Fuzzillogic ( 2019-07-19 01:48:47 +0300 )edit

yes...very weird. Though, u can wake the device amd then unlock it with 1 tap

babo ( 2019-07-20 15:58:32 +0300 )edit

True, but... The way I see it, it decreases the probability of accidentally unlocking the phone in your pocket - which has happened many times with my Android devices...

Direc ( 2019-07-23 00:03:44 +0300 )edit
2

answered 2019-07-19 01:29:11 +0300

Yunwu gravatar image

Pull down menu strings "Record a selfie video"and"StopWatch"still English .They should be translated into Chinese :)

edit flag offensive delete publish link more
2

answered 2019-07-19 14:18:40 +0300

treeman gravatar image

Went well on XA2 Plus. BUT: imho the UI especially phone, messages, contacts is a step backwards. Where is this "clean" glass-design? Where is the character and the spirit of Sailfish? Now it looks like a hybrid from android and SFOS, like a temporary tinker solution (eg. the ribbon in "calls"). Please think about it.

edit flag offensive delete publish link more

Comments

2

I can just agree with you, wouldn't it be better to change the design in phone as follows, keep the 3 tabs but have the same behaviour like then the keyboard, so holding the Headline-tab and tearing to the side would change the view in which you are, that would be more consistent with all the rest of the ui. Just an idea, but i also felt that the design of this function isn't fitting at all to the principles of design of Sailfish OS

Firefox84 ( 2019-07-21 00:01:50 +0300 )edit
1

I don't know if i understand you in the right way. But do you mean the behavior like in "email"? That's ui-consistent, a swipe brings you to "drafts" (eg) another swipe brings you back. The dot on the upper screen indicates that there it goes further. Calendar: the same thing for cancel or save the entries. So i don't know why they invented something new. Wheres the problem to swipe in "Clock" between Alarm/Timer/Stopwatch as we already do in other apps? Excuse my English, it's not my mothertongue...

treeman ( 2019-07-22 08:49:02 +0300 )edit

@treeman, yes exactely that was what i meant, i just took the example of the keyboards, where you have the same behaviour. The only reason why i would switch through the top ribbon would be to not mistakenly make a call when swipping :) Like that tge whole would be more consistent, the buttons now, are like you said just a copy and paste of Android, and destroying the actual UI of Sailfish OS...

Firefox84 ( 2019-07-22 13:50:32 +0300 )edit

I've posted this (small corrections here) in "tabs srsly" thread, but reposting here: Well, sorry for sailors, but I have to say: this new phone app sucks. Not sure what "studies" was happening, but it seems that it's like "lets throw tabs and shit together in one app yey!". Theres a pulley in Friends with Find and pulley is visible only when you are on top... and, over there on top, just below those cool tabs is "find". Do we need two Finds to find something?

I liked dialer on top of the "history" screen.

Sometimes Im using "the other hand" for the phone - mosaic was, by default, both hands friendly (not like using both hands, but like using left OR right hand). Step backwards. There are left handed people out there...

I would love chronological history. I called A, then got a call from B, then got a call from A, then called A and then B. It should be from top to bottom: B A «A «B A and in history it still is just: B A (and you have to DIG to see chronological order)

I dont like new icons in history. Previous icons where self explaining. I call A, no icons! B called me, small arrow. Simple stuff. We dont need tons of emoji to check call history.

Another note: I would love "chronological activity history" - calls + messages (mms/sms) (and in some future world maybe, just maybe, even others - like e-mail, xmpp etc. sky is the limit).

Piotr ( 2019-07-23 14:36:03 +0300 )edit
2

The spirit of Sailfish has to consider mass appeal. Thinking about mainstream (and corporate users) means compromises. -- Big thank you to jolla, btw, for continued Jolla 1 support! (if there were a compact sized new sailfish phone I'd switched already (but this is not mainstream enough, I know))...

chappi ( 2019-07-23 18:20:20 +0300 )edit
2

answered 2019-07-23 20:32:46 +0300

Kea gravatar image

Thank you for this update! Uploading pictures to Telegram works fine, making calls with Telegram is ok, linking to the browser works flawless, we can now install Android apps with newer updates, etc. I am very pleased with my Sailfish device (XA2) ! However, still waiting for a few improvements: I wished sharing to Piepmatz and to Mastodon clients ( from the Guardian or the BBC or whatever) would be possible. now I try to do that with Telegram as intermedium. About the camera: Sony devices have a lot of cyan, blue is dominant. This makes the colours of pictures unnatural. Red is too crimson. In Android you can change this a little by pushing green and red and leaving blue behind. In Sailfish this is not possible. Next time a camera update? About the Jolla store: some apps really need an update. The Youtube player e.g. Can someone check these apps?

edit flag offensive delete publish link more
2

answered 2019-07-25 14:09:14 +0300

vision gravatar image

Did I miss something? Or is 3.1.0.11 already released for everybody?

I am just downloading 3.1.0.11 on Xperia X, Jolla C and Jolla tablet even though I never have subscribed my account for Early Access.

Or is just the Update Version history not yet updated?

edit flag offensive delete publish link more

Comments

3

Ok... seems to be released since today:

https://blog.jolla.com/seitseminen/

vision ( 2019-07-25 14:12:12 +0300 )edit

Download stopped - same when I retry. Eventually 'Problem with Store. Could not update SFOS' Though you only see that error if you're watching the screen at the time. Servers overloaded perhaps

DaveRo ( 2019-07-25 16:11:24 +0300 )edit

Eventually I tried pkcon refresh and got a certificate error. (Re)generated the device's jolla account keys and the GUI update worked. 'Problem with Store' is a useless and misleading message!

DaveRo ( 2019-07-27 18:52:34 +0300 )edit

3.1.0.11 seems to be for Early Access users only. I got also the notification to upgrade, even though my account is not Early Access.

According to https://together.jolla.com/question/201831/bug-early-adopter-update-to-302-available-but-i-never-opted-in/ this happened also earlier because of an error by Jolla.

hsjpekka ( 2019-07-30 22:19:14 +0300 )edit
2

answered 2019-08-21 19:59:39 +0300

Raymaen gravatar image

The "known issues" XA2 part schould be extended and updated. as i am missing the 3,5" audioplug issue Jolla is tracking (for example)... and so on...

edit flag offensive delete publish link more
2

answered 2019-08-23 08:59:54 +0300

Not strictly related to this release, but as stated here: https://together.jolla.com/question/126146/bug-manual-off-peak-email-synchronisation-settings-are-not-respected/ off peak synch is not reliable. Last night no notification, tonight happened again:

[nemo@Sailfish ~]$ devel-su cat .cache/msyncd/sync/syncemail-12.xml
Password: 
<?xml version="1.0" encoding="UTF-8"?>
<profile type="sync" name="syncemail-12">
    <key name="accountid" value="12"/>
    <key name="destinationtype" value="online"/>
    <key name="displayname" value="XXXXXXXXXX@XXXX.net"/>
    <key name="enabled" value="true"/>
    <key name="hidden" value="true"/>
    <key name="scheduled" value="true"/>
    <key name="sync_always_up_to_date" value="true"/>
    <key name="sync_externally" value="false"/>
    <key name="sync_since_days_past" value="30"/>
    <key name="use_accounts" value="true"/>
    <profile type="client" name="syncemail">
        <key name="Sync Direction" value="from-remote"/>
    </profile>
    <schedule days="3,2,1,7,6,5,4" time="" enabled="true" interval="0" syncconfiguredtime="">
        <rush days="3,2,1,5,4" begin="07:00:00" enabled="true" externalsync="true" interval="15" end="21:00:00"/>
    </schedule>
</profile>

and

[nemo@Sailfish ~]$ devel-su cat .cache/msyncd/sync/logs/syncemail-12.log.xml
Password: 
<?xml version="1.0" encoding="UTF-8"?>
<synclog name="syncemail-12">
    <syncresults majorcode="0" minorcode="0" scheduled="true" time="2019-08-21T03:21:37"/>
    <syncresults majorcode="0" minorcode="0" scheduled="true" time="2019-08-21T19:21:34"/>
    <syncresults majorcode="0" minorcode="0" scheduled="true" time="2019-08-21T21:21:35"/>
    <syncresults majorcode="1" minorcode="1" scheduled="true" time="2019-08-22T19:21:42"/>
    <syncresults majorcode="0" minorcode="0" scheduled="true" time="2019-08-23T03:21:37"/>
</synclog>

I got a notification at 03:21:37AM.

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

Question tools

Follow
21 followers

Stats

Asked: 2019-06-27 15:26:52 +0300

Seen: 23,477 times

Last updated: Sep 03