Constant Screen Offset on Tab X - Software or Hardware problem

[Kindleschokolade]

Hello,

after starting up my Tab X I got a weird screen offset issue.
The device's active screen is somehow offset with the touch input still in the right place.
Sometimes I get a normal screen back with a screen refresh but it comes back again.
A restart / shutdown did not help so far.

Anyone have an idea if this could be a hardware issue? The device is fairly new ( October 2023 )
Or are their any other software things I could try?

Thanks a lot for all suggestions

[Renate]

That is very weird. But the TabX is not a BSR device so I don't think it's hardware.
Are you running on the latest software?

Model:  TabX
Finger: Onyx/TabX/TabX:11/2023-11-22_10-35_3.5_946657f755/43508:user/dev-keys
Link:   http://firmware-us-volc.boox.com/2c3cede7f3fc0a3a70a3b2a65c8fe77a/update.upx
Size:   1,561,114,386
MD5:    2c3cede7f3fc0a3a70a3b2a65c8fe77a

[Kindleschokolade]

I am running
Version:
2023-04-19_12-03_3.32_37262e9621
Kernel Version:
4.19.157-perf-g39e1c0
b927e0-dirty
onyx@onyxUbuntu
#2222
Mon Apr 10 19:13:32
CST 2023

if I do an Update Check it tells me "This is already the latest version"

[Renate]

Originally Posted by Kindleschokolade

If I do an Update Check it tells me "This is already the latest version"

Then don't do an Update Check.

Download the file above on your desktop. Then:

adb push update.upx sdcard
adb shell am start -a onyx.settings.action.firmware

And say, "Update".

[Kindleschokolade]

Thank you.
I did install and update, however there is no change in the behaviour.
Any other ideas, short of resetting the device? ( Which would lose all data and settings I suppose )

[Renate]

Well, this is a weird one.
I'd almost suspect the controller built into the Eink panel itself.
Me, I'd probably reseat the orange flex PCB connector on the panel.
You did check that the version changed to 3.5?

[Kindleschokolade]

Thanks. The system did change to 3.5 ( 2023-11-22_10-35_3.5_946657f755 )
Reseating the connector would mean opening up the device and thus voiding warranty, no?

[Kindleschokolade]

Wow. This is weird. I just accidentally started VLC since my touch points are off and the device did go back to normal ...
Will see how it behaves from now on.

Edit: Update... problem came back out of the blue. Starting VLC did not do the magic.
Probably unrelated.

Just to know:
What is the deal with the system update not showing up in the System settings?

[Renate]

getprop | grep finger

And try this:

wm size reset

[Kindleschokolade]

Originally Posted by Renate

getprop | grep finger

[ro.bootimage.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.odm.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.product.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.system.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.system_ext.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]
[ro.vendor.build.fingerprint]: [ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys]

And try this:

Originally Posted by Renate

wm size reset

No difference.

Update: Did a reboot. Screen back to normal ...

[Renate]

That's weird, the fingers.
It looks like the update didn't go through.
All those fingerprints don't show normal model/model/version.
My Poke3 says:

[ro.build.fingerprint]: [ONYX/Poke3/Poke3:10/2023-12-12_23-45_3.5_4687b1901/12699:user/dev-keys]

My Poke5 says:

[ro.build.fingerprint]: [Onyx/Poke5P/Poke5P:11/2023-11-17_05-41_3.5_801526b7d/6777:user/dev-keys]

And yours doesn't look like anything I pasted with the link.

[Kindleschokolade]

just for good measure I did run the update again. But it would refuse to update as it is already on the latest version. ( see Screenshot )
I can also see the differences.
However finger still puts out the same info as posted earlier.
Works though ��

Thanks for your help!

[Kindleschokolade]

Update: After some hours the issue came back.
Not really related to any special activity that I could specify.
Left the device and when I came back found the display with the offset again.
Only noticable irregularity was, that there was no sleep screen image.
Display showed the home screen with the offset but device was asleep.