[release notes] 3.2.0 Torronsuo [released]

Question

68

[release notes] 3.2.0 Torronsuo [released]

asked 2019-10-03 11:29:03 +0200

jovirkku

23703 ●213 ●311 ●247

moderator

updated 2019-11-22 10:25:21 +0200

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

Table of content

Update version history
Size of update
Device models supported by Sailfish X
Contributions from Sailfish Mobile OS RUS (Aurora)
Release Highlights
- Xperia XA2
- Accounts
- Android™ App Support
- Backup & Restore
- Battery & Charging
- Bluetooth
- Browser
- Calendar
- Camera
- Clock
- Connectivity
- Email
- Documents
- Messages
- People
- Phone
- Security
- Settings
- SIM
- Storage
- Sync
- UX
- WLAN
T.J.C: Issues reported by the community and fixed in this update
Technical changes
- Changelog
Updating your device
- Notification concerning apps from Open Repos
About SD cards
Known issues - generic

Update version history

2019-10-29: 3.2.0.12 was released to Early Access subscribers
2019-11-06: 3.2.0.12 was released to all subscribers
2019-11-19: 3.2.0.14 was released for Sony Xperia 10 and 10 Plus.

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.1.0 to 3.2.0: about 380 MB
- Jolla C from 3.1.0 to 3.2.0: about 410 MB
- Xperia XA2 from 3.1.0 to 3.2.0: about 630 MB
- Xperia X from 3.1.0 to 3.2.0: about 480 MB

Device models supported by Sailfish X

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

The supported Sony Xperia 10 models are:

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

The supported Sony Xperia XA2 models are:

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

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

The supported Gemini PDA models are x25 and x27.

Contributions from Sailfish Mobile OS RUS (Aurora)

Several of the key improvements in this release were developed for Sailfish Mobile OS RUS (OS Aurora) and contributed by OMP to the Sailfish OS.

Here are some of the key contributions and features developed with OMP's support

Phone redesigns and improvements: Call reminder feature introduced, Incoming call showing country for foreign calls, Call ending dialogue redesigned
Support for Active Sync out of office reminders
File Manager shows the folder size, and an error message was added for file and folder name conflicts
Ability to customize OS name and use customized name for example used in the default email signature
More enterprise EAP options are supported for WLAN connections
OpenVPN encrypted certificate password fixes
User data encryption developed further and SELinux prepared for deployment
Security fixes (CVEs) for dbus, expat, lua, openssh, patch, QualPwd, systemd
Added support for different types of Bluetooth Low Energy (BLE) devices
Battery notifications improved to reduce unnecessary notifications

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

Release Highlights

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

Xperia XA2

Kernel updated to 4.4.189
Sailfish OS 3.2.0 can be installed on Android 9 now (no need to downgrade to Android 8.1)

Accounts

Dropbox: Migrated away from deprecated media info API
If no accounts installed on a device that supports Presence, then Settings > Presence item is not shown
Hardcoded /home/nemo/ removed from sailfishkeyprovider; home path read from $HOME environment variable now

Android™ App Support

Android™ App Support for Xperia XA2 devices improved
- Android Support (a.k.a. aliendalvik) updated to android-8.1.0_r65
- Using the android.hardware.power service allowed. Makes different performance and low power modes possible
- Using the android.hardware.memtrack service allowed. Helps in getting information about used hardware resources
- Missing file browser added to make it possible for Android apps to share files by default
- Mobile data works now also when one of the SIM cards (dual SIM devices) is disabled
- Opening Android apps work better now
- Period/comma characters added to Android keyboard; Enter key recognised now
- Copying contacts from Sailfish to Android apps work smoothly now. Out-of-memory loop eliminated.
- Android keyboard pops up reliably

Backup & Restore

Backup service can now get the information on the available storage reliably. An API added to the PartitionModel to tell when external storages are populated.
Legacy git-tree vault code and libraries removed as the more recent implementation does not use them

Battery & Charging

Battery notification logic was rewritten to reduce the number of disturbing notifications

Bluetooth

Support for different types of Bluetooth Low Energy (BLE) devices added, i.e. pairing and connections from Sailfish do work. However, using the devices requires a BLE application which we do not have. Android apps are lacking access to Sailfish Bluetooth service, still.

Browser

Problems in accessing Twitter with Sailfish Browser fixed
WebGL support fixed

Calendar

Avoided forcing all calendars to be synced when making changes to one

Camera

Showing the SD card as the target for saving pictures fixed

Clock

Snooze interval is configurable now - see Settings > Apps > Clock
Timers finally allow choosing seconds
Pulley menu action added for reseting the saved timers to the beginning

Connectivity

Edit view of WLAN connection extended with more enterprise EAP options
Adding a WLAN network: Save button fixed
Counters of mobile data fixed
After turning flight mode off, the device can connect back to mobile data
Swapping of SIM cards between the two slots does not disturb the subsequent connections.
Polling interface statistics when all interfaces are down stopped
OpenVPN encrypted certificate password dialogues and password use is fixed. VPNAgent is used for credential retrieval, an encrypted certificate password is not saved by VPNAgent.

Email

OS name used instead of "Jolla" in default email signature

Documents

Writing comments (annotations) to PDF files sometimes crashing Documents app fixed
Calligra backend updated to the latest upstream, bringing in many bug fixes to displaying of office formats - Community contribution from Damien Caliste - thank you!

Messages

We hope that the recent SMS problem got eliminated (at least alleviated) with this OS update

People

Performance regression in contact search fixed
Avoid duplicate empty fields in contact editor, one empty field is enough at a time

Phone

Call reminder feature introduced
- You can set reminder to call back when receiving an incoming call, or from call history
Call ending dialog redesigned
- If you end the call only non-blocking notification is shown
- If the remote side disconnects a new system dialogue is shown with actions to call back, send message or add a reminder
Incoming call now displays country of the caller if coming from abroad
More than two emergency calls possible in a row, now
An attempt was made to prevent calls from being accidentally held [Xperia X devices]. Proximity sensor utilization was tweaked to improve the reliability of in-call blanking behaviour. Unfortunately, this change also affects the Sneak Peek feature. Those users who have not experienced problems with in-call proximity blanking and wish to continue using Sneak Peek can revert back to the previous behaviour by executing mcetool --set-ps-on-demand=disabled from the command line.
Call UX improvements are ongoing work with further improvements planned

Security

User data encryption (a.k.a. encryption of Home partition, disk encryption) was developed further. However, on 3.2.0, this feature is mainly included in freshly flashed corporate devices and in one consumer device only: Xperia 10. User data encryption can be left out from a device configuration by not setting the security code during the initial startup of a device. However, if encryption is enabled during the startup then it cannot be disabled any more (other than by reflashing the device).
Security framework SELinux being developed in the background, not yet ready. Enabled in permissive mode on Xperia 10 Vulnerabilities fixed:
dbus 1.13.12: CVE-2019-12749, CVE-2015-0245
expat 2.2.7: CVE-2015-1283, CVE-2016-0718, CVE-2016-4472, CVE-2016-5300, CVE-2012-6702, CVE-2017-9233, CVE-2016-9063
kernel/sony/msm-4.4/kernel: CVE-2019-10538, CVE-2019-11477, CVE-2019-11478, CVE-2019-11479
lua 5.3.5: CVE-2014-5461, CVE-2019-6706
openssh 8.0p1: CVE-2019-6111
patch 2.7.6: CVE-2019-13638, CVE-2019-13636, CVE-2018-1000156
QualPwn CVE-2019-10538
systemd 225+git19: CVE-2013-4391, CVE-2018-16865, CVE-2018-16866, CVE-2016-7795, CVE-2019-3842

Settings

If no accounts installed on a device that supports Presence, then "Settings > Presence" item is not shown
Snooze interval is configurable now - see "Settings > Apps > Clock"

SIM

Swapping of SIM cards between the two slots does not disturb the subsequent connections

Storage

File Manager shows the folder size now in details page
"Cannot copy into itself" error message was added for file and folder name conflicts

Sync

Prevent extra spurious sync action during off-peak hours. Verify that sync schedule is compatible with a wake-up time

UX

Content deletion use cases redesigned to reduce confusion new users face. Further improvements are coming in the next release
Brightness of pulley menu indicator increased, users sometimes miss the indicator and are unable to access the functionality in the pulley

WLAN

Edit view of WLAN connection extended with more enterprise EAP options
Adding a WLAN network: Save button 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

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.

OS release 3.2.0.12 is a so-called Stop Release. There are several Stop Releases in the Sailfish OS update path. They are mandatory intermediate steps in the update path through which the update process must traverse if a device is updated starting from an early OS release. The previous Stop Release was 3.0.0.8.

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

VPN does not work in case of Android apps
Sailfish can connect Bluetooth Low Energy devices now. However, Android apps cannot use peripheral devices via Bluetooth - other than for playback of the sound. Therefore smartwatches, for instance, cannot be controlled from Android apps
Bluetooth pairing and audio connections may still fail in some circumstances
The chacha20-poly1305 cipher is not currently working, which is often chosen for SSH. It has been disabled in the sshd configuration file, but if you have manually modified it then it will not automatically update. You can ssh into your device using ssh -c aes128-ctr and check the /etc/ssh/sshd_config file against its rpmnew version if present.

Known issues specific to Xperia X

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

Known issues specific to Xperia XA2

Not implemented features: FM radio, double-tap
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). This is expected to get fixed in the next OS update (3.2.1). (This should get fixed with OS release 3.2.1 "Nuuksio")
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...
A locked-up device with display dimmed does not indicate an incoming Whatsapp call in any way
Pictures/videos on SD card are not visible to Android apps.

Known issues specific to Xperia 10

Fingerprint recognition may sometimes fail to work. In such a case, restart the device and it works again.
Rarely, audio playback and sensors (display rotation) may stop working. If this happens, please restart the device
No support for FM radio
No support for the dual-lens camera
Whatsapp video call, incoming calls and video playback might have issues - but often caused by the lack of settings and permissions. Please see our Whatsapp help article
In some cases, the acceptance of SIM/PIN may take up to 12 seconds
During the decryption of user data in device start-up, there is a period of 10-20 seconds such that the display is black

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:19:21.591228

Comments

14

First try:

It downloads too quickly, it goes through the install procedure far too quickly, the white loading bar zips across the screen and the reboot is extremely quick as well, but upon checking the OS has not been updated.

Second try:

Same as above, when restarted, the device is NOT updated

Third try:

Same as above.

Fourth try:

No, I'm going out, fresh air and sunshine

Spam Hunter ( 2019-10-29 14:01:48 +0200 )edit

4

Haha, same here at first try on an XA2 ;-p

The download ends at ~10% and says ready to install.

One should try using the command line.

Maximilian1st ( 2019-10-29 14:15:49 +0200 )edit

4

experiencing the same with XA2. Two times tried.

peakki ( 2019-10-29 14:16:42 +0200 )edit

9

On my Xperia X (3.1.0.11), the size of the update is indicated as 70 MB which seems rather small.

And, to be honest, the list of improvements appears disappointingly short given the three months since the last update. At least for Xperia X, where some of us expected an update to Android app support.

ziellos ( 2019-10-29 14:18:08 +0200 )edit

6

Will try later in the evening when I am next to my device. Seems that the majority of work is coming externally from Aurora. Not necessarily a bad thing since there is progress and someone is driving the development forward but still a bit of a concern with regards to the future.

cquence ( 2019-10-29 14:25:12 +0200 )edit

First try:
It downloads too quickly, it goes through the install procedure far too quickly, the white loading bar zips across the screen and the reboot is extremely quick as well, but upon checking the OS has not been updated.
Second try:
Same as above, when restarted, the device is NOT updated
Third try:
Same as above.
Fourth try:
No, I'm going out, fresh air and sunshine
Spam Hunter ( 2019-10-29 14:01:48 +0200 )edit
Haha, same here at first try on an XA2 ;-p
The download ends at ~10% and says ready to install.
One should try using the command line.
Maximilian1st ( 2019-10-29 14:15:49 +0200 )edit
experiencing the same with XA2. Two times tried.
peakki ( 2019-10-29 14:16:42 +0200 )edit
On my Xperia X (3.1.0.11), the size of the update is indicated as 70 MB which seems rather small.
And, to be honest, the list of improvements appears disappointingly short given the three months since the last update. At least for Xperia X, where some of us expected an update to Android app support.
ziellos ( 2019-10-29 14:18:08 +0200 )edit
Will try later in the evening when I am next to my device. Seems that the majority of work is coming externally from Aurora. Not necessarily a bad thing since there is progress and someone is driving the development forward but still a bit of a concern with regards to the future.
cquence ( 2019-10-29 14:25:12 +0200 )edit

Answer 1

23

answered 2019-10-29 14:30:35 +0200

addydon
807 ●15 ●20 ●27

So it is mostly a bug fix release, but good to see that Aurora OS is contributing changes back to upstream. Hope to see more of this in the future! Now, really looking forward to the next exciting release!

edit flag offensive delete publish link

Comments

8

I do agree, finally things are coming back to Jolla. This could be a game changer, even more if other (Huawei?) would jump on the train. Great!

magullo ( 2019-10-29 15:44:23 +0200 )edit

Hopefully. E.g. today I tried unsuccesfully e-sim for my Galaxy Watch. As you all allready quessed, it did not succeeded in. The unfunction of the Galaxy Wearables app in XA2 SFOS X made the last hope impossible. As you allready noticed from other part, Magisk and Magisk Manager did not worked in XA2 SFOS, either. Thus, noticeable progress is required ASAP. I wont't spend my life in waiting for something which does not exist.

N9Sailfish ( 2019-10-29 16:05:17 +0200 )edit

1

battery life is much better on my Xperia X.

danfin ( 2019-10-31 09:49:29 +0200 )edit

@N9Sailfish I'm curious, what do you want to achieve with Magisk on SailfishOS? I've used it one of my android phones, and it was excellent, but I can't think of anything I want from it on SFOS, or that can't be done other ways.

ksandom ( 2019-11-01 15:30:39 +0200 )edit

@ksandom It is just to test if my Galaxy Watch could work with XA2 SFOS (prior to jump back ...). But I quess allready, that answer is NO. Galaxy wearables won't work due to limitations of Android support. Not working, not working, not working ... The phone and just UI are not enough only themselves in a world of today.

N9Sailfish ( 2019-11-02 07:38:22 +0200 )edit

Answer 2

10

answered 2019-10-29 16:08:50 +0200

cemoi71

14264 ●310 ●434 ●439

Really cool guys that for xa2 devices is possible to flash directly from android !! no need anymore to downgrade to android v8.1. Great job!!!

edit flag offensive delete publish link

Comments

Did you try? I am still waiting for 3.2 images, still not available on jolla website.

magullo ( 2019-10-29 20:29:59 +0200 )edit

feels very snappy now, after the update on xa2! what does this mean, can we update the hardware abstraction layer?

manu ( 2019-10-29 22:11:34 +0200 )edit

@magullo no i'm not early access but reading about it is really encouraging... i believe that it works, otherwise they didn't declare it...

cemoi71 ( 2019-10-30 01:25:35 +0200 )edit

7

@magullo: We will publish the flashable images for Xperia devices (and Gemini) soon after we have rolled out this 3.2.0 update to all users (in the best case, after one week). This is the way we have had it.

jovirkku ( 2019-10-30 08:39:16 +0200 )edit

Installed on XA2 (52.someting) and it all went smooth. Thank you.

magullo ( 2019-11-06 21:27:44 +0200 )edit

Answer 3

9

answered 2019-10-30 13:42:58 +0200

santhoshmanikandan
850 ●24 ●30 ●39

Brightness of pulley menu indicator increased, users sometimes miss the indicator and are unable to access the functionality in the pulley

Rather than this change, the old Pulley menu will be easier to find. Even with this change I sometimes miss the pulley options.

edit flag offensive delete publish link

Comments

1

Actually one of the main reason to develop new pulley indicator for Sailfish 2 was because the old pulley glass item was very subtle and much thinner and thus missed by the users. The indication regressed on Sailfish 3 with the introduction of light ambiences, where the legibility issue has more to do with ambience coloring than the pulley style.

Joona Petrell ( 2019-11-11 21:04:26 +0200 )edit

Answer 4

6

answered 2019-10-30 19:10:19 +0200

Marcel Pol
365 ●8 ●11 ●16

Just updated my Jolla 1 from 3.1 to 3.2.0.12. Everything is fine, except the setting for the lockscreen was suddenly disabled. When enabling again it requires a new passcode, so now I have to remember a new one :) Upon reboot it was fine again. (to avoid confusion, I mean lockscreen passcode, not sim pincode).

edit flag offensive delete publish link

Comments

3

I can confirm, after upgrade the device lock (use security code) has been fully reset. Also I had to re-setup - enter the security code.

mastal ( 2019-10-30 21:55:05 +0200 )edit

for my Jolla Phone, device lock settings (security code and automatic locking delay) have been reset, but I was able to re-enter my old lock code. I haven't tried a manual reboot, only the automatic one during the update.

jaacoppi ( 2019-10-31 11:45:25 +0200 )edit

I also can confirm this. But sadly I forgot it my new one, so I have to send my Jolla1 in to Jolla :/ But nevertheless the upgrade is really nice !

yajo ( 2019-11-02 14:39:52 +0200 )edit

1

I had to change the lock code as well. Even if I change it a few times always to different codes, I cannot use the original code I had. Even after rebooting. Oh well..

reinob ( 2019-11-09 14:40:16 +0200 )edit

Ich kann die Aussage von @reinob bestätigen: neuer Code nötig und alter nicht erneut nutzbar.

I can confirm the Info from @reinob: I needed to enter a new code and I can not reuse the old one! @Jolla: how can we fix this?

M.Bln. ( 2019-11-12 01:04:04 +0200 )edit

Answer 5

5

answered 2019-10-31 11:31:49 +0200

DrDweeb
681 ●13 ●24 ●27

Thanks for the upgrade for my F5122 ... Seems to be working just fine, so Sailing onwards :D

ps: Obligatory Android upgrade please ;) Also, the kernel 3.10.84 is getting long in the tooth

edit flag offensive delete publish link

Answer 6

3

answered 2019-10-30 01:19:57 +0200

KuroNeko

158 ●6 ●9

updated 2019-11-02 18:40:04 +0200

Seems like this update broke the android support on my Xperia X (Compact): Android apps don't open anymore and even reiinstalling and removing all android directories didn't seem to help. Installing an app shows the following in the journal:

Okt 30 00:12:49 Sailfish apkd[808]: Asking ACL to install (inside chroot): /data/app//incoming/im.pattle.app.apk
Okt 30 00:12:49 Sailfish apkd[808]: Installing /data/app//incoming/im.pattle.app.apk
Okt 30 00:12:49 Sailfish mapplauncherd[1299]: Boosted process (pid=5337) exited with status 0
Okt 30 00:12:50 Sailfish invoker[2871]: WARNING: An inactive plugin is misbehaving - tried to show a window!
Okt 30 00:12:50 Sailfish invoker[2871]: WARNING: requestActivate() called for  QQuickView(0x2570b0)  which has
Qt::WindowDoesNotAcceptFocus set.

Edit:

As @kaulian said, this is related to the X Compact patch and the link he provided fixed things for me. For convenience, you need to run the following commands to fix things:

devel-su
zypper ref -r compat-f5321
zypper dup -r compat-f5321
add-preinit-oneshot /var/lib/platform-updates/flash-bootimg.sh
reboot

Source: https://talk.maemo.org/showpost.php?p=1561387&postcount=162

edit flag offensive delete publish link

Comments

XA2 (H4493) Correctly upgraded, next step test the battery consumption if it is inormal with the WIFI, I archive my K10 and use Sailfish exclusively.

manu007 ( 2019-10-30 12:11:27 +0200 )edit

3

@KuroNeko: there were no changes to the Android Support of Xperia X in this 3.2.0 release. It is unclear what is causing the problem you reported.

jovirkku ( 2019-10-30 13:13:25 +0200 )edit

1

Android seems to work on my Xperia X Compact. The version installed on mine is aliendalvik-1.0.90-1.armv7hl.

Manatus ( 2019-10-30 13:41:10 +0200 )edit

@jovirkku: It seems like I'm not the only one with the issue, see Rafaelvlmendes in the comments of the main topic. It could be one of those aliendalvik breakages, that seem to happen randomly on upgrades from time to time (some people seemed to be affected on the last release with the same issue). The usual fixes don't seem to apply though (and I would like to avoid a factory reset). The cause is unclear to me too, btw :D

@manu007: The XA2 and the X series use different android runtimes, so this doesn't really surprise me.

@Manatus: Well, sounds like some upgrade failure specific to my phone then?

KuroNeko ( 2019-10-30 22:35:15 +0200 )edit

I just upgraded ... FB and Here(WeGo) started fine. YMMV

DrDweeb ( 2019-10-31 11:26:20 +0200 )edit

Answer 7

3

answered 2019-10-30 20:45:42 +0200

pawel

14895 ●231 ●341 ●376

all fineon xperua x! thanks

edit flag offensive delete publish link

Comments

Same here, good to go on xperua x! concrete repair

BarryEZE ( 2020-04-09 01:07:26 +0200 )edit

Answer 8

2

answered 2019-11-04 20:38:45 +0200

Chris_
188 ●6 ●12 ●18

updated 2019-11-05 13:52:26 +0200

Thank you for the updating BLE. It's nice that you added Bluetooth Low Energy, I hope that someday a native application will also be created to connect with hearing aids? :)

More details about the behavior of the mobile data icon?

Will there be more information? Where can it be checked / set?

Using the android.hardware.power service allowed. Makes different performance and low power modes possible
Using the android.hardware.memtrack service allowed. Helps in getting information about used hardware resources

edit flag offensive delete publish link

Comments

2

How about the whole Android 9 base that can be used from now on with Sony Xperia XA2? Does it have advantages to upgrade the system to Android 9 and than install Sailfish X?

Rudge79 ( 2019-11-04 21:33:37 +0200 )edit

5

@Rudge79: No.

olf ( 2019-11-04 21:40:48 +0200 )edit

I also thank you for this. Learned much! Not that this has anything to do with appliances but it gave me the courage, getting one thing done, to go ahead and do something I've been procrastinating about, namely appliance repair service for my freezer in the basement. So thanks again!

nommy88 ( 2020-02-17 22:41:14 +0200 )edit

Thanks for the insight! Tons of informative info here for sure. Nommy, if you are ever needing a Pressure Washing San Antonio Company, just feel free to reach out and let me know! Ed

EduardoRomero ( 2020-08-31 20:55:43 +0200 )edit

I also partially own a Pressure Washing Orlando company as well, so if you'd like to check that out instead, feel free to!

-Ed

EduardoRomero ( 2020-09-01 04:36:22 +0200 )edit

Answer 9

1

answered 2019-11-01 00:04:15 +0200

luen

5879 ●73 ●103 ●101

There is no picture (just black) in the camera live view after the upgrade. Neither Jolla Camera, the lock screen camera, piggz Advanced Camera nor CodeReader show anything. Advanced Camera shows resolution -1x-1, and the resolution list is empty. My device is an Xperia X Compact. I have tried reinstalling jolla-camera, but that didn't help.

edit flag offensive delete publish link

Comments

1

@luen, this was already asked in this thread and answered!

olf ( 2019-11-01 02:36:23 +0200 )edit

1

@olf I can't find anything about the camera in that TJC answer (I did search TJC before posting). The thread on TMO appeared to be only about broken Android support, so I missed the mention of the camera. Thanks for pointing this out.

luen ( 2019-11-01 06:21:23 +0200 )edit

I had a look through a friend and he said that the android support for the Xperia X is all good and you should have no problems. Source - https://www.handymanservicesbrisbane.com/

BarryEZE ( 2020-05-01 05:08:47 +0200 )edit

Xperia X Compact is not a device I have used before. Will need to look into that.

-Eduardo, Owner of a Cleaning Services Sioux Falls Company

EduardoRomero ( 2020-08-31 06:20:40 +0200 )edit

Also, if anyone wants to discuss the updates or coding, just feel free to reach out!

Ed, Co-Owner of a Carpet Cleaning Waco TX Company

EduardoRomero ( 2020-08-31 08:48:42 +0200 )edit

Answer 10

1

answered 2019-11-06 15:39:08 +0200

danfin
3498 ●105 ●144 ●152

Do we have a hardware button to terminate phone calls in 3.2.0? Or is there a way to assign a button to that? Camera button would be suitable.

edit flag offensive delete publish link

Comments

4

How is that an answer?

Filip K. ( 2019-11-06 15:49:27 +0200 )edit

no answer at all but then I see people putting all kinds of problems into answer containers here, and if, for example, a problem gets reported but a question mark is avoided, I'd still consider this a question but this platform offers only answer or comment containers. So, which to take for a new theme?

danfin ( 2019-11-07 12:59:23 +0200 )edit

Agree, sometimes after call, the display stays off, and it had to be wake up by button and only then terminate the call.

kriziak ( 2019-11-11 11:04:13 +0200 )edit

Absolutely composed subject matter, thanks for this release of Torronsuo. house cleaning

casseverhart13 ( 2019-11-18 04:05:44 +0200 )edit

I agree on the camera button. We be very great feature to have. Looking forward to something like that in the future. Ed, Co owner of a tree removal company

EduardoRomero ( 2020-09-01 03:16:23 +0200 )edit

[release notes] 3.2.0 Torronsuo [released]

Update version history

Size of update

Device models supported by Sailfish X

Contributions from Sailfish Mobile OS RUS (Aurora)

Release Highlights

Xperia XA2

Accounts

Android™ App Support

Backup & Restore

Battery & Charging

Bluetooth

Browser

Calendar

Camera

Clock

Connectivity

Email

Documents

Messages

People

Phone

Security

Settings

SIM

Storage

Sync

UX

WLAN

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

Technical changes

Changelog

Updating your device

Notification concerning apps from Open Repos

About SD cards

Known issues - generic

Known issues specific to Xperia X

Known issues specific to Xperia XA2

Known issues specific to Xperia 10

Known issues specific to Gemini PDA

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

Comments

18 Answers

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

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