The touch point on screen does not match the real devices screen

[rafaelb-lang]

The Rhino tablets (T85 and T105) display correctly in DeviceFarmer/STF, but the touch location does not line up with where the user clicks.

The Rhino tablets (T85 and T105) display correctly in DeviceFarmer/STF, but the touch location does not line up with where the user clicks.

What We Have Already Investigated

Android Rotation
The tablets were initially running with different orientations ( 90 and 180) this have been forced to ( Rotation_0 )

Density Override
Before:
Physical density: 260
Override density: 324
Now:
260

Resolution Overrides ( same behavior remains)

Browser Test (used Chrome and Edge )

Touch Screen Hardware
For example:
T105:
X = 0 to 1199
Y = 0 to 1919
This matches 1200 x 1920

Android input Manager ( tested multiple devices, Input Manager does not appear to be root cause)

Currently STF / Minicap Findings
The new logs show STF repeatedly launching minicap with:

-P 1200x1920@572x817/0
minicap reporting:

INFO: 1200x1920@511x817/0
Later:

Setting frame producer projection to 692x692 and minicap reports:

INFO: 1200x1920@433x692/0, Then STF switches back again.

The tablet itself is:
1)1200 x 1920
but the stream being rendered is:

1)511 x 817
2)433 x 692
3)572 x 817
Depending on the current projection STF selected.
Provider startup configuration shows STF is relying entirely on automatic detection.
The current assumption is not using the exact same coordinate space.
The image the user sees appears to be scaled differently than the coordinate system STF is using for touch injection.

Please advise.

[rafaelb-lang]

Also on this matter, after testing with other tables we can see that we are missing SDK 36 minicap libraries in our deployment.
The missing minicap.so libraries are tied to Android SDK versions, not specific device models.

So these libraries are not unique to Rhino devices that fail.
Rhino is:
Android 16
SDK 36
The container does not contain:
arm64-v8a/lib/android-36/minicap.so

Therefore STF cannot launch native minicap for SDK 36 and falls back to: (minicap-apk) that as seen on our testing clicks on wrong coordinates on the screen.

[matanbaruch]

Test it in this order: set the tablet to Rotation_0 first, then restart the provider, then check touch again. If it lines up after that, this is DeviceFarmer/STFService.apk#184, where the minitouch agent snapshots the already rotated display size once at startup and never updates it, so rotating back afterwards cannot fix it.