bug: some gestures broken [duplicate]
asked 2014-02-04 15:11:28 +0200
I've hit this twice now since upgrading to 1.0.3.8 First time I noticed it I was in an android app, this time fingerterm but that may just be anecdotal.
Symptoms:
- I'm unable to peek to the home screen from within apps, it's as though the device doesn't recognise it, for example if I do it in the mail app in the bottom half of the screen (where the message previews are) it attempts to highlight them instead and
- I'm able to get to the home screen but in order to do so I must swipe horizontally very quickly
- Swipe down to go to sleep works normally, however swipe to close an app must also be done very quickly
- Swipe up to notifications peeks and works as normal.
- All gestures in apps themselves seem to work normally (e.g. vertical scrolling, tapping, horizontal scroll to sub-dialogues etc.)
- Horizontal swipe to ambiances works as normal in the homescreen/lockscreen
Nothing will recover the device to normal behaviour except a reboot.
I'd say this is a duplicate of https://together.jolla.com/question/9112/swiping-is-too-sensitive-about-direction/. Depending on how you do the swipe it's sometimes not recognized.
Mohjive ( 2014-02-04 15:25:31 +0200 )edit@Mohjive Ehrm, read the last line...
chemist ( 2014-02-04 16:59:45 +0200 )editNo I think it's a bug, well certainly is aberrant behaviour but is tricky to pin down. I don't remember it happening pre 1.0.3.8 and it doesn't affect in-app gestures, but I'm unclear how to cause repeatably or how to test/diagnose/log once it gets into that state. Once the device gets into this mode it's quite obvious though that the behaviour isn't nornal
steph ( 2014-02-04 18:36:48 +0200 )edit@chemist: I've removed my OT comments. Fell free to remove this comment when/if you do the same. :)
Mohjive ( 2014-02-04 18:43:47 +0200 )editI have experienced the same behaviour yesterday, for the first time. had 4 apps open - settings, e-mail, browser and an android app.
Didn't try doing the swipes very fast as steph states. Reboot fixed the problem. Definitely a bug in my eyes.
casanunda ( 2014-02-04 19:11:21 +0200 )edit