Touch joysticks have issues with maintaining boundaries about openmw-android

[Vikutomaru]

Same issue with Android 11 with OneUI 3.1 (recently updated) on my Samsung Tab S6 - camera view jumps 90 degrees downwards while holding viewing touch control and touching on the movement touch control circle. The same occurs while holding attack button (with weapon ready) and touching on the movement touch control circle. Furthermore, when holding a direction with the movement touch control and simultaneously holding the viewing touch control, my movement would drift to the right. This is abolised by dragging my movement touch control point to above the midpoint of the screen, which makes it tricky for navigation during combat. Otherwise, there is no issue when using bluetooth controller or mouse + keyboard. FYI, the above issue was not present with Android 10 on my tab previously.

[agung0k]

Android 11 have same issue. camera touch affecting the movement touch when used at the same time. resulting in drifting to the right.

[licaon-kter]

I think I see this often too.

[xyzz]

cannot reproduce on pixel 1

[Laezhesto]

Same issue on s10+ exynos after updating to android 11

[onceagainifindmyselfhere]

Sooooo. Many. Touch issues with Android 11 in general and mouse function is all but broken in everything except OMW ironically

…

On Tue, Feb 2, 2021, 8:00 AM Laezhesto ***@***.***> wrote: Same issue on s10+ exynos after updating to android 11 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR7K65GODGQFSL6OSV4CLSTS47ZPLANCNFSM4W3YKRWA> .

[JFrostNC]

I am having the exact same issue on Samsung Galaxy Z Fold2 with Android 11. Actually signed up just so I could post this problem.

[JFrostNC]

Just an update from me: I discovered that I have the issue when using the Nightly build, but using the current OMW from the Playstore does not have this problem; the control sticks work fine.

[licaon-kter]

@JFrostNC how old is that?

[JFrostNC]

@licaon-kter how old is what? The version that works is 0.46.0-38. The Nightly build (that has the issue) is 0.47.0-41-nightly

[xyzz]

so I tried reproducing this using samsung remote device lab, out of like 10 devices only 5 I was able to connect to and then only 1 of these had working adb, and the issue didn't reproduce on it, perhaps due to different touch handling :/

[onceagainifindmyselfhere]

Just noticed this too but whats weird is that i had the play store version when i initially noticed it. I uninstalled, installed several other builds, then finally relented and hoped the play store reinstall would work. 🤷 It did. Is it possible this isnt just my imagination?

…

On Sat, Feb 6, 2021, 11:42 AM JFrostNC ***@***.***> wrote: Just an update from me: I discovered that I have the issue when using the Nightly build, but using the current OMW from the Playstore does not have this problem; the control sticks work fine. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR7K65ERUGVNQCDOYWHLICLS5VWNVANCNFSM4W3YKRWA> .

[xyzz]

Ok, can you go through nightly releases at https://github.com/xyzz/openmw-android/releases (marked with -nightly) and let me know which is the earliest version that has the issue.

[JFrostNC]

None of them have the problem for me anymore, including the latest version. I don't know if uninstalling/ re-installing did the trick, or what. I haven't changed or updated anything else.

Sorry it took so long for me to check!

[licaon-kter]

Is this the issue or should I open a new one?

2021_02_13_19_13_17_3.mp4

[onceagainifindmyselfhere]

It's a different issue, I'll try to install one of the old apks and replicate it.

…

On Sat, Feb 13, 2021, 3:13 PM Licaon_Kter ***@***.***> wrote: Is this the issue or should I open a new one? https://user-images.githubusercontent.com/2282799/107860561-cad2c780-6e37-11eb-8a9f-478e416e9f59.mp4 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR7K65CNRHV2ISYMZZE6M6DS63MORANCNFSM4W3YKRWA> .

[licaon-kter]

@onceagainifindmyselfhere

in one frame, be immediately facing the opposite direction, the right joystick having understood your left thumb on the left joystick as being a touch on the right joystick.

This happens in the actual video at 00:14.

[onceagainifindmyselfhere]

Also, it had stopped, it's happening again. A config file conflict or something maybe? I'm not noticing a mod connection On Mon, Feb 15, 2021, 9:43 PM mark stevens <[email protected]> wrote:

…

I'll have to rewatch I was probably misinterpreting what was going on but if it's this then yeah On Sat, Feb 13, 2021, 6:40 PM Licaon_Kter ***@***.***> wrote: > @onceagainifindmyselfhere <https://github.com/onceagainifindmyselfhere> > > in one frame, be immediately facing the opposite direction, the right > joystick having understood your left thumb on the left joystick as being a > touch on the right joystick. > > This happens in the actual video... > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#63 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AR7K65GATQX4XZH7ZWZUEK3S64EW5ANCNFSM4W3YKRWA> > . >

[Sisah2]

I think it alwais happened, at least on my note 8,9,10. Worst it is when using bow, on borderless phone accidentaly touching lower right corner result in shooting to ground after releasing attack button.

[HighDarkElf]

It must be the android 11 update as it used to work on android 10 fine. I have the exact same files and config in a lesser oppo phone and that runs everything fine tried wiping config and adjusting settings also installed the nightly version and tried on that with the same problem replicated. * Move left stick and touch right stick = unwarranted right strafe *move right stick and touch left = unwarranted 180 flick of view. The combination makes the application unusable

[Sisah2]

Maybe we speaking about different issue, im speaking about if you look up still hold that button and touch somewhere else (bottom) on the screen, then release that finger you used to look, the view jump to diferent position as if you moved your "look" finger to position of second finger.

Android 10 here.

[xyzz]

What is your device?

[HighDarkElf]

What is your device?

I have Samsung galaxy s10 lite.

A temporary bypass to use the game I've found is to connect a Bluetooth controller like a ps or xbox controller.

[agung0k]

What is your device?

Samsung Galaxy A52

[notsodorp]

Pls fix

[onceagainifindmyselfhere]

Still present on the nightly build but stable claims not to be compatible with my device anymore

…

On Wed, Apr 21, 2021, 10:48 AM notsodorp ***@***.***> wrote: Pls fix — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR7K65FSC455PEZD2MY7233TJ3QTPANCNFSM4W3YKRWA> .

[xyzz]

Yes, as mentioned in the linked issue #92

Samsung devices which received android 11 update were manually excluded due to #63

Basically, Samsung broke/changed something wrt touch controls in 11 (which is not reproducible on other manufacturers' devices), and samsung users were posting a lot of 1-star reviews due to controls not working properly, so it's temporarily excluded.

Unfortunately I don't have any samsung devices so at the moment I cannot reproduce or fix the bug.

[onceagainifindmyselfhere]

Samsung and google really fucked up after the s9. This phone is unbelievably powerful and feels every day like a more expensive brick. I feel bad for it. For the people who made it. It's like cutting a bird's wings off. I'd like to, shortly into the future, donate to the cause specifically to a used device that can replicate the issue. How much would it be

…

On Mon, Sep 6, 2021, 9:37 PM xyzz ***@***.***> wrote: Yes, as mentioned in the linked issue #92 <#92> Samsung devices which received android 11 update were manually excluded due to #63 <#63> Basically, Samsung broke/changed something wrt touch controls in 11 (which is not reproducible on other manufacturers' devices), and samsung users were posting a lot of 1-star reviews due to controls not working properly, so it's temporarily excluded. Unfortunately I don't have any samsung devices so at the moment I cannot reproduce or fix the bug. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#63 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR7K65CTBMHAJ36NOWFSERLUAVUE5ANCNFSM4W3YKRWA> .