[Alien dalvik][XA2][bug] Android side misbehaviour on screen actions/functions

Tracked by Jolla

asked 2019-04-22 17:36:47 +0300

Sakke gravatar image

updated 2019-05-18 11:36:20 +0300

Hi sailors!

I'm not quite sure how to represent this issue that at least I'm having but let's try. So ever since the beta phase rolled out I've noticed this weird behavior of at least some Android apps. didn't fix this issue I'm having.

The issue itself; sometimes something triggers the Android side screen actions to work improperly or not working at all. I give some examples how this occurs

Examples after the issue is on / triggered:

1) Telegram: normal quick tap to the screen causes long press action. So when you want more options you long press some ui element (in Telegram pin, mark as read etc.) but now this is triggered by any tap regardless of your tap type

2) Google Chrome: No quick tapping does anything, sometimes even whole screen becomes unresponsive. Long pressing some options that would normally require quick tapping works though. Other example is that you aren't able to close the browser tab since it requires quick tap action.

3) Sricam (camera app): no tapping works, can't turn the camera at all. So no actions available

4) Also very usual in every app: becomes totally unresponsive, you can't control the screen (like move up, down etc.) Sometimes zoom action is triggered by quick tapping screen

I have also noticed that Google Chrome is usually the main trigger for the problem. I also want to mention that even when this issue is triggered some apps like WhatsApp might work properly.

Other information:

I'm not too sure how this issue is triggered. Although, I have noticed that this usually triggers when on Android app open the view some how flashes from Sailfish multitasking view back to Android app (like it would've been opened again).

Now the workaround has been to reboot the whole phone since restarting Alien dalvik service usually helps only for a few minutes.

Sailfish with Sony Xperia XA2 H4113, dual sim

Edit: I've been able to reproduce this issue in a certain way. Sometimes when I'm browsing on an Android app and I get for example WhatsApp message from someone => there will be the small notification box that would be on Android lock screen, I assume, and to which you can write quick message etc. I hope you know what I mean. Anyways, when this is occured and I pass this box by clicking show or close => sometimes the app that was on (when the message box appeared) becomes unresponsive or this screen action bug starts again.

edit retag flag offensive close delete



I often encounter a similar thing: When trying to switch tabs in firefox for android, it is sometimes not possible to select some tab. After some tries it sometimes works, sometimes only restarting firefox works.

I have two XA2 phones, each with Hossa installed and both have the same issues in this regard.

bomo ( 2019-05-18 15:51:00 +0300 )edit

@bomo, I got the same with Chrome on XA2/Hossa. It's like the screen positioning is a bit off in relation to the touch screen digitizer or something; the tab I'm trying to close jumps down like I touched it's banner instead of the X button.

Tapping around the X button it sometimes accept my press as X and finally closes the tab in question.

teemu ( 2019-05-18 22:34:50 +0300 )edit

@teemu, I haven't found any way to close the tab etc. but maybe I'll need to try this your method too :D. Indeed does it seem that the screen position is awkward/not normal

Sakke ( 2019-05-19 10:07:39 +0300 )edit

@Sakke, try touching a little to the right from the X button? I got the feeling that pressing exactly on the button is interpreted to as touching the tab banner which causes the tab to jump downwards.

So, it's like the touch is interpreted to go a bit left from where you actually touch.

teemu ( 2019-05-19 13:55:12 +0300 )edit

Maybe it is the same problem as this?

https://together.jolla.com/question/206346/303-android-apps-touch-screen-proplem/ (here are some additonal examples when it is not working)

tomas3000 ( 2019-05-20 09:07:22 +0300 )edit