Ask / Submit

Double tap on Sailfish X

asked 2017-09-05 23:09:54 +0300

Dreej gravatar image

updated 2018-09-13 22:28:42 +0300

BonoNL gravatar image

I just read in a Jolla Blog comment by James Noori that the double tap gesture is not implemented and they're not sure do do it... Sony Xperia X AND Sailfish OS are supporting this feature. I love it on my Jolla1, JollaC and Jolla Tablet.

So please Jolla, Bring it back alive!!!

Thanks ;)

edit retag flag offensive close delete



clear!! double-tap is a must have...

cemoi71 ( 2017-09-06 01:25:03 +0300 )edit

Yes please, Bluetooth and this for me ASAP . . . . . . . . . . . . ..

davekelly ( 2017-09-06 20:42:38 +0300 )edit

Definitly! It's one of my favorites!!

And it's not there on my Sony with SailfishX ... :-(((

zemideluxe ( 2017-10-12 00:42:15 +0300 )edit

I was a bit puzzled when I played around with my new Xperia, and the double tap gesture would not work. I am definitely missing it.

Cmdr_Zod ( 2017-11-04 02:45:40 +0300 )edit

For me following worked fine:

mcetool --set-doubletap-mode=show-unlock-screen
mcetool -i disabled
mcetool -z proximity
mcetool --set-doubletap-wakeup=proximity
deloptes ( 2017-11-04 16:02:46 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2017-11-06 09:56:56 +0300

spiiroin gravatar image

updated 2017-11-20 14:12:38 +0300

jovirkku gravatar image

Doubletap on Xperia X is broken - which is why it is not enabled by default.

Enabling it can cause power drain (in the sense that device does not suspend anymore due unhandled interrupts), loss of touch interaction (touch panel does not switch from double tap detection to normal touch reporting), inability to power up display at all (glitches that allow powering down something that is then needed and assumed to be powered on).

Some issues happen silently without causing visible problems, some go away when display is power cycled with power key, and some require reboot.

The easiest way to break something is to toggle the double tap detection while display is off and then power up the display. Which is why one should not use the "proximity" type double tap wakeup setting. And possibly this also contributes to confusion around what settings need to be touched in order to make it work to the extent it does work (applying setting changes while display is off -> probably does not work as expected until display is power cycled and/or just doing it can already break something).

The setting that does affect double tap wakeup feature is:

  • mcetool --set-doubletap-wakeup=never -> keeps double tap detection disabled = the default = assumed safe
  • mcetool --set-doubletap-wakeup=always -> keeps double tap detection enabled = expect issues sooner or later
  • mcetool --set-doubletap-wakeup=proximity -> enables/disables dt detection based on proximity sensor state = problems pretty much guaranteed

So, if you want to try it out, the least-likely-to-cause-issues way to do it is:

  1. Make sure display is powered on
  2. While display is on, execute: mcetool --set-doubletap-wakeup=always

Also, the following mcetool incantations are not needed in order to activate the double tap wakeup feature:

  • mcetool -i disabled a.k.a --set-fake-doubletap=disabled -> stops double tap from working from "lpm", but does not affect the "real" double tap detection
  • mcetool -M show-unlock-screen a.k.a. --set-doubletap-mode=show-unlock-screen -> usually does nothing as this is the default anyway - also does not affect the "real" double tap detection in any way
edit flag offensive delete publish link more



Do you think it is broken for good or is there a possibility that Jolla/Sony solve the issue at some undefined time? At least, I read your message as it is unlikely to come in the near future ;-)

Second question: is it broken only for Xperia X or all Xperia?

pat_o ( 2017-11-06 12:44:19 +0300 )edit

@spiiroin its one of the definitive characteristics of SFOS and needs to work flawlessly. It would also be nice if gestures could be added on the blank screen.

ApB ( 2017-11-06 13:28:41 +0300 )edit

I am curious to try but... how to revert to standard setting? I mean as command line

minojolla ( 2018-01-30 13:03:57 +0300 )edit

What are the default settings for sailfish X ? I tried different variant but still have from time to time the screen not responding after waking up. I then need to lock and unlock again using the power button. I'd like to revert back to default settings untill it's officially supported Thanks

Dam ( 2018-03-14 16:43:41 +0300 )edit

I just did it, following moderators:

"Make sure display is powered on While display is on, execute: mcetool --set-doubletap-wakeup=always"

It works, now will see how affect battery

minojolla ( 2018-08-06 14:51:50 +0300 )edit

answered 2017-10-13 00:04:48 +0300

zemideluxe gravatar image

updated 2017-10-13 00:06:49 +0300

Look here, this seems to be an workaround. It Worked out for me :-))

reviewjolla on twitter:

To enable double tap to wake up: Activate Developer mode, launch Terminal app. Write in terminal:

devel-su [passwd, hidden writing]

pkcon install mce-tools

mcetool -–set-doubletap-mode=show-unlock-screen

mcetool -i disabled

mcetool -z always

Or look here in together.

edit flag offensive delete publish link more



its so simple - what is the reason, that jolla doesnt support it? has it any bad impact - low battery life or so?

mettska ( 2017-10-13 00:14:51 +0300 )edit

@mettska: That simple part is just "standard" sfos side userspace config/settings. And while things work on "happy path", deviating from it easily leads to unexpected things happening at kernel driver side so that the device is no longer able to suspend properly / whole touch input is lost and reboot might be needed to recover -> It just can't be enabled by default at the moment.

Also, some of the mcetool invocations above do not make sense to me...

"mcetool -–set-doubletap-mode=show-unlock-screen" = what it is the default anyway => is a nop unless user has already fiddled with the setting.

"mcetool --set-fake-doubletap=disabled" = does not affect the "real" hw+fw+kernel double tap in any way, just disables the "fake" user space side sw double tap detection in "lpm/glance/sneak peek" view and similar situations => unlikely that anybody would want or need to do this.

But "mcetool --set-doubletap-wakeup=always" is needed. And probably is a safer bet than "proximity" because it avoids among other things toggling the double tap detection mode while display is off (which is one thing that driver does not handle too well).

Some confusion in this might be due to the fact that detection mode gets acted on when display makes on->off transition -> if the settings are changed while display is already off, the display might need to be power cycled before the setting changes have any effect. But preferably these settings should be changed only while the display is powered up (to avoid triggering more serious while-display-is-off issues).

spiiroin ( 2017-10-13 10:32:05 +0300 )edit

Nevertheless this would be a useful feature to have on the Xperia X, solely from a usability point of view. I found that putting the dive in a protective case makes the side buttons somewhat difficult to use. Double tap handles much better in my case. I will watch for any negative impact re battery life or crashes.

BTW is there anything similar for volume adjustment?

Kao ( 2017-10-13 13:41:58 +0300 )edit

thanks for explanation!

mettska ( 2017-10-13 20:27:32 +0300 )edit

doubletap works fine here but not from sneak peak (low power mode). Only from sleep. Now i am very half happy. maybe because I set mcetool --set-doubletap-mode=unlock it will not work in LPM?

danfin ( 2017-11-05 14:34:29 +0300 )edit

answered 2017-11-05 21:36:04 +0300

deloptes gravatar image

Following seems to work fine on Sailfish X

mcetool --set-doubletap-mode=show-unlock-screen
mcetool -i disabled
mcetool -z proximity
mcetool --set-doubletap-wakeup=proximity

powersave is always on, no problem with the unlock screen anymore after adding the line doubletap-wakeup=proximity.

edit flag offensive delete publish link more



I tried to install MCE Tool, but get the following error:

[root@Sailfish nemo]# pkcon install mce-tools
Waiting in queue
Refreshing software list
Resolving dependencies
Fatal error: mce-tools-1.90.0-1.11.1.armv7hl requires mce = 1.90.0-1.11.1, but this requirement cannot be provided
White ( 2017-11-05 21:56:40 +0300 )edit

You'll have to install mce first

[root@Sailfish nemo]# pkcon install mce

or combined

[root@Sailfish nemo]# pkcon install mce mce-tools
deloptes ( 2017-11-05 22:16:17 +0300 )edit


[root@Sailfish nemo]# pkcon install mce mce-tools
Waiting in queue
Refreshing software list
Resolving dependencies
Installing packages
Waiting in queue
Waiting for authentication
Waiting in queue
Refreshing software list
Resolving dependencies
Installing packages
Downloading packages
Fatal error: File './core/armv7hl/mce-1.90.0-1.11.1.armv7hl.rpm' not found on medium ''
White ( 2017-11-05 23:46:46 +0300 )edit

I have as system - no idea why you or the tool is looking at seems to be the original based system.

deloptes ( 2017-11-06 00:48:50 +0300 )edit

Tool is looking to because I have this build os SailfishOS X. It is latest stable version.

White ( 2017-11-06 00:54:08 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2017-09-05 23:09:54 +0300

Seen: 5,606 times

Last updated: Sep 13