[HiLord]

Hello!
The tablet is Samsung Galaxy Tab 2 10.1 3G, running some Android 6.0.1 build of AOSP (custom ROM, the stock one is way too outdated to use)
The phone is vivo Y12, running Android 11 build of FuntouchOS (stock ROM)

I tried both WiFi and USB connections, but I get the same result and on both devices. Can’t exactly tell the speed of internet connection, but my tablet is very old and so I can only broadly say that it’s slow. Phone is more or less modern, should be pretty fast.

Hope this helps, will wait patiently for a reply!
– HiLord Reilo

[HiLord]

I have some weird issues with these forums as well….

Hello!
It happens regardless of connection type and on both devices that I own.
Tablet is Samsung Galaxy Tab 2 10.1, running AOSP Android 6.0.1. It’s pretty old and has a pretty slow internet connection. Don’t know the exact values.
Phone is vivo Y12, running FuntouchOS Android 11

– HiLord Reilo

(Once again, sorry if it’s a duplicate post. The first one did not appear on my side after I sent it :/ )

[HiLord]

Hello!
Here’s the requested diagnostic files in a split archive, as well as video of an issue on my side (different device, Android 6):
https://drive.google.com/file/d/1RgLrcXp-SCqPjocHkkgY89D3RoyE9rb1/view?usp=sharing

A little hiccup happened while trying to reproduce this issue – the touchscreen did not work at all. Because of that I had to reconnect my viewer app and that might’ve created some additional garbage in diagnostic logs. Sorry if that’s true.
Hope this helps, will wait patiently for a reply!
– HiLord Reilo

(This is my second time writing this post. I don’t know what happened, but my first post did not appear on my side. I’m sorry in advance for duplicate post)

[HiLord]

Hello!
Here’s the requested diagnostic files, as well as the video with demonstration of this issue on my side:
https://drive.google.com/file/d/1RgLrcXp-SCqPjocHkkgY89D3RoyE9rb1/view?usp=sharing

A little hiccup happened when I tried to connect for the first time after enabling diagnostics – touchscreen stopped working at all. That’s why diagnostic data may have some garbage data because of reconnection.
Hope this would help, I’ll be waiting for a reply!
– HiLord Reilo

[HiLord]

Sorry, there were some upload errors. Didn’t know you can’t attach split archives :/
Here’s the diagnostic files.
– HiLord Reilo

Attachments:

You must be logged in to view attached files.

[HiLord]

Hello!
Here’s the requested diagnostic files in a split archive

A little hiccup happened while trying to reproduce this issue – the touchscreen did not work at all. Because of that I had to reconnect my viewer app and that might’ve created some additional garbage in diagnostic logs. Sorry if that’s true.
Hope this helps, will wait patiently for a reply!
– HiLord Reilo

(This is my third time writing this post. I don’t know what happened, but my first and second post did not appear on my side. I’m sorry in advance for duplicate post)

[HiLord]

Hello!
No, that issue is present everywhere. You can try reproduce it on any multi-touch testing app or website (like this one: “ https://skill-test.net/multi-touch-test “ Even though it says that test won’t work, it will)
Also I want to make a little correction. Turns out, multi-touch works if at least one of the fingers is moving (for example if you swiping with one finger back and forth, the second touch would register). Also, if you hold one finger still and trigger the second touch by swiping with second finger and let go of the second one, it would still register until you lift the first finger. It’s as if touch updates are not called.
Hope this helps, will wait patiently for a reply!
– HiLord Reilo

• Diese Antwort wurde geändert vor 1 Jahr, 8 Monaten von HiLord.

[HiLord]

Forgot to mention versions of software.
Server: 1.0.66 (Windows 10)
Client: 0.91.6 (Android 11)

– HiLord Reilo

[Autor]

Beiträge