In version 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right behind the finger. I strongly suspect this is due to excessively aggressive Kalman filtering.
2 | No.2 Revision |
In version 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right behind under the finger. I strongly suspect this is due to excessively aggressive Kalman filtering.
3 | No.3 Revision |
In version 2.1.0.9 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.
4 | No.4 Revision |
In version 2.1.0.9 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.
5 | No.5 Revision |
In version 2.1.0.9 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.
6 | No.6 Revision |
In version 2.1.0.9 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.filtering. Jolla 1 and Jolla Tablet seem to be unaffected by this issue.
Here's how to reproduce the issue:
7 | No.7 Revision |
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:
8 | No.8 Revision |
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:
9 | No.9 Revision |
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:
10 | retagged |
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:
11 | retagged |
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:
12 | No.12 Revision |
In version 2.1.0.11 2.1.1.23 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:swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: This is still happening in 2.1.1.23 EA despite the improvements on edge gesture detection. After a long time of use of 2.1.0 update I can say that I have become more wary with my swipe interactions due to the numerous bugs and unresponsiveness with the karman filter. Often you need to exaggerate edge gestures for them to work and if you're like me and like to do gestures fast, it does not respond to the gestures as well as it did before. I fail to see what this filter was trying to fix in the first place as I did not see any problems with the old system. It was supposed to improve responsiveness but it is doing the contrary and I think this filter does not work as intended and should be either removed, adjusted heavily or replaced by a more reliable system for touch detection.
13 | No.13 Revision |
In version 2.1.1.23 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering. filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: This is still happening in 2.1.1.23 EA despite the improvements on edge gesture detection. After a long time of use of 2.1.0 update I can say that I have become more wary with my swipe interactions due to the numerous bugs and unresponsiveness with the karman filter. Often you need to exaggerate edge gestures for them to work and if you're like me and like to do gestures fast, it does not respond to the gestures as well as it did before. I fail to see what this filter was trying to fix in the first place as I did not see any problems with the old system. It was supposed to improve responsiveness but it is doing the contrary and I think this filter does not work as intended and should be either removed, adjusted heavily or replaced by a more reliable system for touch detection.
14 | No.14 Revision |
In version 2.1.1.23 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: This is Seems to be still happening there somewhat in 2.1.1.23 EA despite the improvements on edge gesture detection. After a long time of use of 2.1.0 update I can say that I have become more wary with my swipe interactions due to the numerous bugs and unresponsiveness with the karman filter. Often you need to exaggerate edge gestures for them to work and if you're like me and like to do gestures fast, it does not respond to the gestures as well as it did before. I fail to see what this filter was trying to fix in the first place as I did not see any problems with the old system. It was supposed to improve responsiveness but it is doing the contrary and I think this filter does not work as intended and should be either removed, adjusted heavily or replaced by a more reliable system for touch detection.2.1.1.23.
15 | No.15 Revision |
In version 2.1.1.23 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: Seems to be still there somewhat in 2.1.1.23.
16 | No.16 Revision |
In version 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: Seems to be still there somewhat in 2.1.1.23.
EDIT 08-09-2017: The problem is still there stronger than ever. Swipes often fail, I have to swipe three to four times to close an app, a full horizontal swipe is not enough to show the home screen, and unwanted calls are made due to poor responsivity of the dialer interface.
17 | No.17 Revision |
In version 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: Seems to be still there somewhat in 2.1.1.23.
EDIT 08-09-2017: The problem is still there stronger than ever. Swipes often fail, I have to swipe three to four times to close an app, a full horizontal swipe is often not enough to show the home screen, and unwanted calls are made due to poor responsivity of the dialer interface.interface. I had to disable the filter to make the phone usable, so I won't be able to give further feedback. I will enable it again when/if any change is made to the behaviour.
18 | No.18 Revision |
Testing on Intex Aquafish 2.1.1.26 swipe lag exists while it was gone on 2.1.0.11.
In version 2.1.0.9 swipes are lagging almost 1 cm behind my finger. In earlier versions the swipe edge lied right under the finger. Problems often occur when the user is typing fast on the keyboard or any other fast touch interaction and then try to swipe from the edge. I strongly suspect this is due to excessively aggressive Kalman filtering that is unable to predict the movement. 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 swipe lag:
Here's how sometimes swipes get interpreted as taps:
EDIT: Seems to be still there somewhat in 2.1.1.23.
EDIT 08-09-2017: The problem is still there stronger than ever. Swipes often fail, I have to swipe three to four times to close an app, a full horizontal swipe is often not enough to show the home screen, and unwanted calls are made due to poor responsivity of the dialer interface. I had to disable the filter to make the phone usable, so I won't be able to give further feedback. I will enable it again when/if any change is made to the behaviour.