Ask / Submit
49

[2.1.0] Swipes lag behind on Jolla C / Aqua Fish

asked 2017-02-09 21:09:09 +0300

Giacomo Di Giacomo gravatar image

updated 2017-04-11 12:14:48 +0300

alain gravatar image

In version 2.1.0.11 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. I strongly suspect this is due to excessively aggressive Kalman filtering. Other problems caused by the same issue is that sometimes a quick swipe is recognised as a tap instead triggering some unintended actions. Jolla 1 and Jolla Tablet seem to be unaffected by this issue.

Here's how to reproduce the issue:

  1. Open a text box.
  2. Type Q button for a long time enough to fill two lines.
  3. Do a quick swipe right after typing and hold your finger.
  4. You should see the edge lag behind your finger.
  5. Try a couple of times since it doesn't seem to work every time.

Misinterpreted swipe resulted in a stuck hold

edit retag flag offensive close delete

Comments

8

Just was about to fill out the same bug with the same suspect (Kalman filter). They are also very slow and sluggish - to my experience, it happens with the first edge swipe - when you do not lift your finger from the screen and keep swiping back and forth, subsequent swipes are swift. Only the first one is very (!) sluggish. It almost feels like pushing away a heavy rock, compared to the situation before.

Not sure if related, but lags reported with the Developer mode frame rate visualization are twice as big for the first swipe.

nodevel ( 2017-02-09 21:50:55 +0300 )edit
1

totally agree on this!

tortoisedoc ( 2017-02-09 22:57:00 +0300 )edit
2

@tortoisedoc please convert that into a comment...

ced117 ( 2017-02-09 23:00:54 +0300 )edit

I strongly suspect you having something cluttering, as apart from the occasional lag, I do not see what you mean.

chemist ( 2017-02-09 23:49:21 +0300 )edit
4

Apparently he's not the only one to notice... It was the single biggest issue I have with the new update. This Kalman Filter thing is either not optimized or simply not suitable for quick interaction. I have adapted to the old UX, I NEVER made swiping mistakes or anything that would justify this. If people have problems with fine motorics okay. But forcing this on everyone is bad.

MoritzJT ( 2017-02-10 01:11:15 +0300 )edit

2 Answers

Sort by » oldest newest most voted
32

answered 2017-02-10 12:46:40 +0300

Joona Petrell gravatar image

We did change how the touch filtering is implemented. Now the touch and painting frames are better synced together, removing stutter during drag and flick animations. But at the same time it is true that the reliability of edge swipes has regressed, quick swipes don't always get detected (especially during system load or if you haven't used the device for over half-dozen seconds).

Sorry, we will look into it.

edit flag offensive delete publish link more

Comments

2

I hope we can get this fixed before the whole update goes public. I'd be really sad to have to live with this another update cycle. Downgrading also isn't really an option.

Keep up the good work!

MoritzJT ( 2017-02-13 17:34:02 +0300 )edit

there was no problem for me before the update, now it is.

please just undo it

pawel ( 2017-02-14 23:55:28 +0300 )edit

I hope closing app cover from Home screen may become faster After official release Iijoki 2.1.0.9, Till then It needs to force close app by swipe down gesture

p_pahare ( 2017-02-15 08:48:44 +0300 )edit

Is there any command-line magic that could be applied to revert this behaviour in the meantime? Using Sailfish on Jolla C is very frustrating experience at the moment.

ajalkane ( 2017-03-22 08:11:47 +0300 )edit
1

I noticed after the latest update, the problem still occures when you try to dismiss an alarm for example and when you swipe up you pull over your finger the screen edge, usually is not working, but when you don't pull over it is usually working... Strange behavior, better, but still not same good as it was before.

bagatel ( 2017-03-27 01:56:59 +0300 )edit
4

answered 2017-03-23 16:01:47 +0300

p_pahare gravatar image

updated 2017-04-05 11:26:36 +0300

thanks to jolla for killing the lag. Now No lags & Closing from app cover is a Nice Experience now , Uninstalling patches for closing Apps.

Edit 05-04-17 : After downgrading to Pre 2.1.x Version I also felt in Jolla C it is Properly Not fixed and lag is visible when swiping forward and backward 2-3times without leaving thumb from screen

edit flag offensive delete publish link more

Comments

After updating to Sailfish OS 2.1.0.10?

Alex ( 2017-03-23 16:13:03 +0300 )edit

yes , It is good update for me as i dont like Swipe down to close App.( or Android like Gesture to Exit the App)

p_pahare ( 2017-03-23 16:18:34 +0300 )edit
1

To fix the issue of "Quick edge swipes are unreliable after the system has been idling for half-dozen seconds" or https://together.jolla.com/question/156475/2109-swipes-lag-behind/
the following changes were included in 2.1.0.10:
lipstick-jolla-home-qt5
- [lipstick-jolla-home] Progress peekfilter also on touch release.
- [lipstick-jolla-home] Take activation threshold into account when updating progress of peekfilter.
- [lipstick-jolla-home] Use 14 mm peekfilter threshold.
- [lipstick-jolla-home] Use touch press area in PeekFilter's boundary detection.

jovirkku ( 2017-04-06 14:05:19 +0300 )edit

Doenst work for me delay still exist.

DarkTuring ( 2017-04-08 09:30:00 +0300 )edit
1

I updated my intex (Jolla C "mod" installed) to 2.1.0.11 and I have noticed that there is that huge swipe lag on alien dalvik while playing clash royale. It makes game almost impossible to play. Before update game was running smoothly. Now if i drag my finger from bottom to up, cursor comes about centimeter after finger at middle of screen. I think I should try to downgrade sailfish version and wait that this huge problem ia solved.

MJolla ( 2017-04-15 09:52:00 +0300 )edit
Login/Signup to Answer

Question tools

Follow
15 followers

Stats

Asked: 2017-02-09 21:09:09 +0300

Seen: 2,241 times

Last updated: Apr 07