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

[release notes] 3.1.0 Seitseminen [released]

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

jovirkku gravatar image

updated 2019-10-28 09:39:08 +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).
  • 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:16:21.246952

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"

Spam Hunter ( 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
23

answered 2019-08-01 01:23:53 +0300

benaryorg gravatar image

updated 2019-08-01 19:50:23 +0300

This is a very general thing to say after what seems and might actually be half a decade of using Sailfish OS and it's definitely not specific to this update, but I have the feeling that Sailfish OS is trying to become a C++ version of Android these days, the people app seems to be the most recent example.

I don't like that trend, not one bit. I remember using Sailfish OS v1.

It was easy to use, had great features, and it simply looked great. Remember the use of the tall background pictures? Or the locking for which probably a lot of people still install a patch? What about the truly buttonless usage, other than volume?

What do we have now? Pulldowns are being outphased, likely because their animation is so slow (patch for that). Locking requires taps instead of a smooth motion (patch for that). The ambience isn't as present anymore, think of the photos app.

What I really want is version 1 Sailfish OS with a modern browser engine, VPN support, security patches, maybe btrfs and crypto, and a lot of merged patches (snooze control, math in alarms, combined launcher, the old control centre in events view, .…).

Don't reinvent your UI every few months or years like a friggin' Twitter. Can't fix what ain't broken. Just patch the things that need patching, and add the things that need adding.

edit flag offensive delete publish link more

Comments

Sadly I have to agree.

Stefan P ( 2019-08-03 12:21:14 +0300 )edit
4

UX studies showed people (from various backgrounds) struggled with these phone, contacts and messages use cases. The subsequent study showed success rates improved and when asked to compare the clear majority preferred the new design over the old one.

Joona Petrell ( 2019-08-06 14:27:55 +0300 )edit

@Joona Petrell Thank you for the clarification and insight.

Stefan P ( 2019-08-06 23:48:00 +0300 )edit
1

Totally agree. Old Sailfish was the most clever system so far(basic user perspective). Sailfish has chance to be real alternative with be unlike and smart for exsisting operaring systems, but for now we have another clone and gloomy users.

Sure anything isn't perfect, can't be have everything, but enchanced sailfish 1 can't be too much to demand and have!

Our life degraded by corporations and fool people. That's very shame, the end.

Jk ( 2019-08-07 11:12:40 +0300 )edit
4

@Joona Petrell Thanks for the explanation, but for this comment, I'll be less diplomatic and objective.

Let's face it, Sailfish OS is niche software. You're trying to get out of that niche by appealing to a broader (and more mainstream) audience. I don't think however, you will get out of that niche any time at all. You can't stay like this, a half-finished Android with some major bugs. If you go more Android, people (at the very least me) will abandon you for there is a finished, battle tested, open source, much more secure Android, with a larger community and some huge baking corporations out there. If you go less Android, you'll keep those people interested in the niche software you built some five years ago (the one advertised as having Unique Features).

I see the latter one as the most satisfying. The second one would be pretty neat, if you were an Android fork or maybe just a custom launcher, but not a full blown OS with an out of date browser (like Samsung's stock one), a closed source UI, etc..

I see that I am not part of the market you are targeting, but I stick with you for nostalgic reasons (and the dev-mode). If people ask me about that fancy OS I have on my phone I give the root-shell in dev mode, the clean-ish Linux, the closed UI, patchmanager, and the antique browser as infos, staying neutral. The main-stream people I tell they should learn to flash themselves a Lineage OS instead.

Four years ago I tried talking techies into it, now I just regret suggesting Sailfish X to that tech-colleague.

Stay niche, but stay the good kind of niche.

benaryorg ( 2019-08-07 20:56:33 +0300 )edit
2

In my opinion one might discuss if it makes things easier to have these "register card style now" - which I don´t like by the way.- But what I really can´t believe is, that the brilliant contacts design - the "block of characters", has been eliminated. - It was nice to look at, and could easily be used with one hand, even on the go. - Now... you´ve got lists of contacts, not looking nice at all, and you´ve got to scroll like hell or to take a lot of attention and try to hit the right character at the right hand frame. Also... The new style of the contact cards doesn´t make life easier, - At least not for me. - Doesn´t look smooth to me. ---- So, in a nutshell: To me this change to the contacts-app is a really, really big step backwards. - Luckily I only updated my Jolla 1 so far. - I will not update my XPERIA X, which I use as my private phone, any more. - But I´ll update my new company phone, XPERIA XA2, but to the latest Android Version, as I´m sure I won´t migrate it to Sailfish OS. - Really a pitty. I liked the ease of the System Usage a lot. And I´m really sorry that I only recently pointed people to Sailfish-Usage. I really regret this now.

MaTi ( 2019-08-08 17:04:29 +0300 )edit
2

i also wrote this many many times here on the website. my j1 is still on v1 since its just better. my xx is still on v2 since patches work for it. i recently installed v3 on xa2. its not that much difference to v2 but: i want 1) quick lock option 2) cover actions by swipe 3) events view by swipe up (with buttons like patch did in v1, the new swipe down buttons are ok for that but swipe up is better reachable) 4) more speed using it (new pully menu is so slow) sonds almost exactly what you want :) and yes naybe people are not familiar with it but then please make it fully customizable to all users! what can be the problem? there is also one thing thats absolutely crap: when you receive a bt file transfer you have to push a button which is far from being reachable when holding the ohone in one hand. what a piece of crap! @joona-petrell the latter should be more considered than what "people" want. its all about a good guide. i wrote it many times, do a good guide and people will feel that old sf ux is just better. cover actions e.g. could be explained better. maybe once you change the way a phone call is accepted. i for my part have difficulty to understand the android way. i came from symbian to sf :)

NuklearFart ( 2019-08-09 12:20:40 +0300 )edit
1

@NuklearFart exactly I agree whole speech. It doens't mean tere must be setting for every ui change even just simple harsh switch to traditional android like UI or Avanced/modern UI would be really great!. How about that?

Jk ( 2019-08-09 23:19:01 +0300 )edit

@Jk would be fine with me and choice modern or droid like sounds matching :)

NuklearFart ( 2019-08-10 08:43:38 +0300 )edit

Pulldowns are being outphased

That is a wild assumption to make.

likely because their animation is so slow

Pulley selection animation was accelerated in Sailfish 3, we will make another speed improvement in 3.1.1.

We are not trying to make a carbon copy of competing operating systems, but whatever route we go needs to be empirically, measurably better.

One reason why Sailfish 1 felt faster to people was due to no textures ever being dropped (and subsequently reloaded) from the memory, which is totally not feasible in higher resolution screens, and considering the sudden memory slowdowns in Jolla 1 could argue wasn't really feasible there either.

the brilliant contacts design - the "block of characters", has been eliminated

I liked alphabet grid too, but it had plenty of issues. E.g. when you browse through your contacts it is not nice to have to tap each section before you see anything.

Maintaining two versions of the operating system UX and/or apps is not technically or work effort-wise feasible.

Joona Petrell ( 2019-08-12 13:44:18 +0300 )edit
2

sf1 did not simply feel faster, its usability was simply superior. with 1 handed use i'm not able to do a swipe from left screen edge (to come to eventsview), on sf1 it was a swipe up. i really don't need the appgrid from everywhere. there was no button anywhere to press, accepting bt file transfer e.g. or buttons on covers, nowadays you need to hit exactly the button, beforehands it was simple gesture. also the ui was consistent at any point. e.g. close a photo to go back to gallery is a pull down which usually is a open menu gesture in sf. there also are buttons to share etc. you had the most beautyful ui ever seen on.sf 1, i never understood the change here. i at least would make it choosable what is bound on global gestures like swipe from any side. i'd choose swipe from top to be close app / lock device, swipe from bottom the menu u get by swipe from middle of top right now and swipe from any side to go back to home screen. what a nice thing to do.

NuklearFart ( 2019-08-12 14:15:52 +0300 )edit
1

@Joona Petrell

but whatever route we go needs to be empirically, measurably better.

Do you mean measurably better than the other OSes (Android, iOS), or do you mean each new version of Sailfish OS needs to be better than the previous one?

FWIW, the latter one might've suceeded with SFOS 1. Measurements: number of bugs fixed, number of community patches merged, speed/memory improvements, number of CVEs fixed, number of new features that do not change anything else (hence excluding UI rewrites).

For the former? You had a community back at SFOS 1. That pretty much shows you had something good back then. From what I hear, what you had was a great UX, with all the right looks and feels. You've changed almost all of that by now, and trust me, the day you make changes to the keyboard is the day I switch to Android. Measuring how your product compares to other products is hard, but why don't you start by simply heading over to OpenRepos and have a look at what patches there are to install currently? That pretty much reflects what people are missing from your product. If that patch adds something the competition doesn't have, that's a unique feature. If the competition has it already then it's debt of sorts.

In any case however there is a really peculiar thing about how you try to improve your product; you literally ignore any attempts of improvement by the developer part of your community. On prime example: Sneak Peek. That patch exists forever by now, and you never made an attempt to expose that option by default, did you? If you were trying to improve your product, you would have merged that thing upstream in 2014 or something. Instead of fixing an obvious thing, you are more interested in making UX studies.

Can you please explain to me why you haven't merged the Sneak Peek patch instead of creating the UX study?

benaryorg ( 2019-08-15 01:45:31 +0300 )edit
1

Measurably better than other prototypes.

Sailfish 1 had plenty of UX gotchas people repeatedly got stuck with.

Sneak Peek has reliability issues, it is tough to do well across many devices with different sensors, displays, etc. We have maintained support in Homescreen and for enabling it from command line. Would love to try to finish it provided we get a customer project.

Joona Petrell ( 2019-08-15 09:32:13 +0300 )edit
12

answered 2019-07-19 10:11:28 +0300

Mario gravatar image

"No connection over mobile data for (some) Android apps" is missing in the known issues section. However, the issue still persists, e.g., for Conversations (XMPP messenger). Is this still tracked by Jolla? Since this is a real blocker for using the XA2 in practice.

edit flag offensive delete publish link more

Comments

2

This concerns the messenger Telegram, too.

Karin ( 2019-07-19 10:24:51 +0300 )edit
9

answered 2019-07-19 13:52:27 +0300

Xeno_PL gravatar image

Apps update looks nice but still no call history for numbers not stored in people app nor dial autocompletion ... (sigh) Maybe in 3.2 in next 5-10 years ...

edit flag offensive delete publish link more

Comments

1

I have plenty of non-stored numbers in my history... But you mean per-number history i guess? You had me worried there for a while.

attah ( 2019-07-19 14:10:49 +0300 )edit
12

I mean if in history there's a call from lets say a number 501 345 678, you cannot see if there was any previous activity (ie if tere were any previous calls or messages from/to this number), just last action. But if you add this number to your contacts in people app you can see all the previous calls. So the information is there, just call history app is not showing it. That's the way call history works in Sailfish OS from the wery beginning and is wrong imho (past activity should be shown for all the numbers, regardless if its stored in contacts or not).

Xeno_PL ( 2019-07-19 14:17:07 +0300 )edit

@Xeno_PL Is there a question about this already? If not, you should make one, because that really should be fixed, in my opinion.

Direc ( 2019-07-22 23:57:32 +0300 )edit
9

answered 2019-07-23 00:14:41 +0300

Direc gravatar image

There are two kind of important things missing from known issues:

  • Moving cursor in Android applications' text field results in text inserted/removed from wrong (the previous) spot (XA2+Android)
  • 3.5mm plug doesn't route audio (but headset does) (XA2)

Both are common activities for many end users, both in business and private use.

Thanks!

edit flag offensive delete publish link more

Comments

Lineout cable should be supported in the next release. Could you describe the exact repro steps for the text input issues you are having to better understand what is going wrong?

Joona Petrell ( 2019-08-08 11:52:22 +0300 )edit
5

answered 2019-07-19 08:46:59 +0300

Yunwu gravatar image

updated 2019-07-19 08:47:57 +0300

Do you find fingerprint diagram on xa2 is still Xperia's Side fingerprint ?It should show back fingerprint on xa2.Maybe somebody will misunderstand because of the side fingerprint diagram.

edit flag offensive delete publish link more

Comments

Nice catch!

Xperia X has the fingerprint reader on the side, XA2 models on the back.

Direc ( 2019-07-23 00:00:24 +0300 )edit

Yepp. I was puzzled by the side image, using XA2. Thought sth went wrong.

spheniscus ( 2019-08-16 23:30:21 +0300 )edit
5

answered 2019-07-22 05:16:59 +0300

ShinAkuma gravatar image

Sulerbe nouvelle... Merci pour la mise a jour!! faut continuer... beau travaille pour le fingerprint et l'organization... faut rester Original.

good major update.. but I still think “WE” are still in beta!

edit flag offensive delete publish link more
4

answered 2019-07-19 10:14:09 +0300

nthn gravatar image

Oh no, the message aligment is now reversed! I can see why, as right-aligned text isn't particularly easy to read, but it's going to take some getting used to after 4,5 years of seeing the contact's messages aligned to the right. I guess someone will create a patch for it anyway.

I think the mosaic layout of the People application was both better looking and nicer to use, it could have used some improvements but overall it was a great idea.

Otherwise, nothing to complain about, the UI changes in the Clock application and such are for the best. A very solid update overall that was worth the wait.

edit flag offensive delete publish link more

Comments

1

I downloaded 3.1 immediately. Typing this on my XA2 while ourside, which means an improvement. It's my daily device and it is more stable and usable now. But concerning the People app., I agree. The first UI was more authentic, more original and easy to use (less taps for a call), so I too regret this change. The rest is fine.

Kea ( 2019-07-23 14:52:49 +0300 )edit

Having "me" on the left side of the dialog and "you" on the right seems more logical as the "contact" page is a swipe away in that direction.

vattuvarg ( 2019-07-30 21:51:22 +0300 )edit
4

answered 2019-07-19 23:23:38 +0300

Kopekenscheich gravatar image

Big thanks for the update! Sailfish OS becomes continuously better and more and more a joy to use as a daily driver! The now working fingerprint sensor is a big step ahead in my book.

edit flag offensive delete publish link more
4

answered 2019-07-22 16:26:34 +0300

this post is marked as community wiki

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

updated 2019-07-22 16:26:34 +0300

sjollaman gravatar image

mostly when you open the clock you are searching alarm function not timer, and mostly when you open the phone you are searching dialler not previous calls

edit flag offensive delete publish link more

Comments

3

I mostly start a call from the recent calls side ;-).

s_mario ( 2019-07-22 22:02:51 +0300 )edit
1

I read somewhere that it's going to be fixed in later update.

Direc ( 2019-07-23 00:09:33 +0300 )edit

@Direc I hope that fixed in Phone means removed those tabs and back to Sailfish spirit. ;)

Piotr ( 2019-07-23 00:26:17 +0300 )edit
3

The best solution probably would be if the last-used tab was opened by default.

Federico ( 2019-07-25 15:15:44 +0300 )edit
1

Agree with last-used tab, because mostly when I open the clock I search for timer and not alarm, contrary to what @sjollaman wrote ;)

Xavier_OM ( 2019-07-29 14:05:15 +0300 )edit
3

answered 2019-07-19 03:17:26 +0300

Thaodan gravatar image

The CVEs fixed in the latest 4.4.y stable updates are missing. Please see my commit on github

edit flag offensive delete publish link more

Comments

1

4.4 of what?

Pekka Vuorela ( 2019-07-19 10:54:25 +0300 )edit
1

I believe it is a reference to https://github.com/mer-hybris/android_kernel_sony_msm/pull/34

pat_o ( 2019-07-19 11:37:01 +0300 )edit

@Thaodan: Thank you for the fix. It has not been included in 3.1.0.11. We will add it to a later release.

jovirkku ( 2019-07-22 15:17:06 +0300 )edit

Question tools

Follow
19 followers

Stats

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

Seen: 35,765 times

Last updated: Oct 28 '19