Ask / Submit

From Jolla 1 to Xperia XA2 first impressions, issues

asked 2019-05-10 10:54:00 +0300

u-dash gravatar image

Hi there,

I just switched from my beloved Jolla 1, mostly because it has now several hardware issues ( display, touchscreen ). I bought a SailfishX license, and made a successful flash on my new Xperia XA2.

Issues/questions I have at first sight :
1. Unable to turn on bluetooth ( it is trying for about 1-3 hours, but without success )
2. Unable to wake-up the phone with the double tap ( I'm not sure, if it is an issue, but I miss this function a lot )
3. It seems, that the original Android OS remained in it's place, since the free space with Android was ~19GB, after instaled Sailfish OS, the free space is ~17GB ( Is there a way, to completly remove the Android partition and use it for Sailfish OS ? )
4. Regarding to this last one, the Android Strore tells me, that there are two available updates for applications, which are not part of my current setup, so I think, the Store application somehow detected the old Android partition? ( need to fix this, I don't need anything from the old OS )
5. If I connect a NON headset earphone, which does NOT have a microphone, so it has only 3.5mm stereo jack, the music is heard from the device's loadspeaker.

Further then that, I'm really enjoying to use my new device, the OS is smooth, most of my previously used applications are working fine.

edit retag flag offensive close delete


Double-Tap: I'm missng that too on my Xperia X. But instead of enabling via CSD-tool (which gives unreliable double-tap-unlock), I enable lowPowerMode (sneak_peek). On my Xperia X, lockscreen reliablyenables sneak_peek after opening my wallet-case and during the sneak_peek display, it reliably unlocks with double-tap – all that I need :-) All you need is to uncomment code in usr/share/jolla-settings/pages/display/display.qml: But there's a patchmanager-patch on openrepos ( which adds settings and translations – I don't know if it is supposed to work with Sailfish 3, but it's easy to take the diff and apply manually.

Sunny ( 2019-05-10 13:35:19 +0300 )edit

triedbthat too: lpm works but double click not, do.more than that?

pawel ( 2019-05-10 17:48:28 +0300 )edit

Nothing that I'm aware of ;-) Seriously, I botched in analog-clock and many other patches I collected/adapted for my JP-1301 for Saimaa, so currently I'm not sure what else I accidentally did... But will reset my Xperia X soon, I'm almost finshed with my Hossa-Patchset (giving up on close button in power menu due to time constraints and analog clock doesn't handle light-ambient+largeScreen for the same reason, mainly manually copied Ancelad's version I'll get back to this as soon as I verified my minimal-diff for double-tap.

Sunny ( 2019-05-10 18:11:05 +0300 )edit

Thanks !!!

pawel ( 2019-05-10 18:26:28 +0300 )edit

Confirmed. It's sufficient to do the following uncommnet:

--- usr/share/jolla-settings/pages/display/display.qml
+++ usr/share/jolla-settings/pages/display/display.qml
@@ -104,7 +104,6 @@

-            /*
             TextSwitch {
                 automaticCheck: false
                 checked: displaySettings.lowPowerModeEnabled
@@ -115,7 +114,6 @@
                 //% "Automatically show time and status information when taking the device out ofpocket."
             description: qsTrId("settings_display-la-sneak_peek_description")
-            */

             ComboBox {
                 id: dimCombo

This allows you to enable lowPowerMode (aka sneak_peek) via settings->display. And I also took the opacity altering from the original patch:

--- usr/share/lipstick-jolla-home-qt5/lockscreen/LockScreen.qml
+++ usr/share/lipstick-jolla-home-qt5/lockscreen/LockScreen.qml
@@ -185,8 +185,8 @@
                 updatesEnabled: lockScreen.locked
                 color: lockScreen.textColor
                 opacity: systemStarted.value && vignette.opened && Desktop.deviceLockState <= DeviceLock.Locked
-                         ? (deviceLockContainer.isCurrentItem ? deviceLockItem.opacity : lockItem.clock.transitionOpacity)
-                         : 0.0
+                         ? (deviceLockContainer.isCurrentItem ? deviceLockItem.opacity : 1.0)
+                         : 1.0
                 z: 1

And then there's also translation files and settings in the original patch. Since I don't use patchmanager, I simply diffed the .qm files against /dev/null and have a single diff file doing the same as the patch with patchmanager. And this enables double-tap-unlock during sneak_peek reliably on my Xperia X. So the code (displaySettings.lowPowerModeEnabled) is already in base, it's just about unhiding it! It's not the double-tap wakeup of JP1, but no difference for wallet-case-users :-)

Sunny ( 2019-05-13 09:49:03 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2019-05-10 11:11:53 +0300

Giacomo Di Giacomo gravatar image

updated 2019-05-10 11:14:16 +0300

  1. This is weird. Launch CSD-tool and run a hardware Bluetooth test.
  2. Double-tap is not officially supported. It can be enabled (see but, at least on Xperia X, it does not always work fine.
  3. The partition scheme has not been changed. In particular, Sony reserves a 7 GB partition for the system image. The 19 GB partition has been split into a 2 GB system and 17 GB home partition. It's not possible to use the remaining space, unfortunately.
  4. (Don't know, sorry.)
  5. Weird again. Did you try with another earphone? Mine works.
edit flag offensive delete publish link more



Hi there,

Thanks for your answers. 1. Sadly CSD tools said, Bluetooth is not available. ( Strange ) 2. I'll check this later, perhaps it is working for me. 3. suxx 4. I'll delete the store app, since I don't really need it 5. Your point, my Beyer Dynamic dt770 is working just fine.

u-dash ( 2019-05-10 11:37:44 +0300 )edit

Hi, 1. Have you already tried it after rebooting? Worked for me... 2. This does not work with the XA2. It is not supported for the XA2... And for the other ones I have no idea...

yajo ( 2019-05-10 16:12:04 +0300 )edit

Hi, 5: I had this problem on my XA2. I just turned BT several times on and off in the settings. Since that I have no Bluetooth problems any more... Strange, but true

me_on_the_road ( 2019-05-10 17:23:45 +0300 )edit

@yajo whoa, you are right, I just made a reboot, and now bluetooth seems to work. Thanks

u-dash ( 2019-05-10 21:05:20 +0300 )edit

answered 2019-05-10 17:44:03 +0300

Pirkka gravatar image

I also got a new XA2 a week ago. I bought the licenced XA2 build from Jolla and installed that. Which version of the SailfishOS did you install? (You mention Xperia X ... but you did use the XA2, right?)

  1. I have some disconnect/reconnect problems with bluetooth headphones, but the initial connection always works. As long as I keep the headphones connected it is fine. Seems to need a reboot a day.

  2. I saw that too. I think the two applications are hidden android apps. There is a contacts app and a camera app that are not shown in the application tray. These are needed by the other android applications you install. E.g. if you install WhatsApp and add a new contact with it, you get to an android contacts app that allows you to add the contact. I allowed the android store to upgrade the all the apps and everything seems fine so far.

edit flag offensive delete publish link more


I didn’t mention XperiaX, but SailfishX and Xperia XA2. I already deleted the android store app, since I don’t like the situation, and I don’t care, if there are hidden Android apps. I decided to use apkpure, to have an application, which I don’t handle other ways.

u-dash ( 2019-05-10 21:11:24 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2019-05-10 10:54:00 +0300

Seen: 664 times

Last updated: May 10 '19