Broken edge swipes in landscape in Äijänpäivänjärvi
After the upgrade to Äijänpäivänjärvi, edge swipes in landscape behave inconsistently. They work fine for some apps but they act as if the device were in protrait for others. So, for example, a left edge swipe is interpreted as a top edge swipe and closes the app instead of switching to the home screen. Likewise for other edge swipes.
Steps to reproduce:
- Turn your phone to landscape: speaker and USB port on the left, mic and LED on the right, buttons on the top.
- Start one of the affected apps, e.g. File Browser.
- Swipe from the left edge.
- Tada!
It does not behave like that for all the apps, only for some. A quick test found: File Browser, Webcat, Modrana, Web Pirate, LLsvPlayer. It worked fine before the OS update.
EDIT Addition to the steps to reproduce. Once an affected application is started in portrait, the issue does not show until it is started again in landscape TWICE. Curiouser and curiouser.
First need to heck these applications, as for example my applications are not affected, and i didn't added any hacks for orientation in it.
coderus ( 2015-04-28 13:09:23 +0200 )editThanks for the suggestion, @coderus. And to @szopin on TMO. It turns out the problem is caused (or at least triggered) by the "Eventview controls attached page" patch. See also this TMO post for details.
(Caveat: It is possible that other patches trigger it too. I stopped experimenting on the first hint of success.)
pichlo ( 2015-04-28 15:43:31 +0200 )editunfortunately, it's not true and this patch is not related to your problem.
coderus ( 2015-04-28 15:55:57 +0200 )editdenial n.
(Psychology) a psychological process by which painful truths are not admitted into an individual's consciousness.
:)
It is unfair to blame the patch and I was not trying to do that. Only trying to explain why some users were able to reproduce it whilst other were not. I suspect the patch somehow exposes a code path - a switch from the launcher to the app's own screen perhaps - that is otherwise not exercised and thus exposes the bug.
We can continue arguing and/or pretending that the issue does not exist or we can work together on finding the true cause and a solution. Your call.
pichlo ( 2015-04-28 17:20:52 +0200 )editomg, i'm developer of this patch, and i know it's not related. you can reproduce same on clean system with no patches enabled.
coderus ( 2015-04-28 17:33:15 +0200 )edit