Edited by CodeSculptor at 8-6-2017 01:01 |
For the beginning explanation: I don't think this is the legendary freezing issue (reason is that I saw no precise description of this infamous thing and all freeze issue fixes didn't work for me). I have a video showing the issue:
Regardless of what you see below, I'm still left with no resolution for this problem. I didn't receive response from Official Chuwi Support after quite a bit of time already, so I don't know if I'm not left alone with the problem. Please help with any ideas you have.
EDIT: Today I have seen that it seems to be hardware issue. ~10% of screen on top doesn't react to touch at all, ~10% of screen on bottom reacts to touch, but event goes to same point horizontally, but vertically above that ~10% (while swiping bottom 10% I will draw perfect line above that 10%). Together with touch freezing periodically like on video, do you have any idea what kind of issue is that?
Leaving remainder of post intact, but it may not be relevant anymore.
- Issue happens regardless of what I do. It just freezes and unfreezes over and over (it means that first ever touch after launching tablet may already be ignored while freeze is in progress).
- It happens all the time. Restarting doesn't help. Even flashing a fresh firmware, either official using flash tool or custom using TWRP.
- I can freely use tablet if I connect mouse and/or keyboard over USB OTG. Even during touch freeze, I can freely click/swipe with mouse).
I have performed probably all possible fixes:
There's one behavior that gives me hope it is not hardware issue.
Expected if it's hardware issue: If I hold an icon on home screen, then it will be held until freeze will go off.
Not expected if it's hardware issue: When freeze happens on swipe, even if freeze stops the swipe, it doesn't lose momentum and on unfreeze swipe is finished with a lot of momentum. I'm not sure if momentum is right word for that vector, it's almost 10 years since I have done some presentations on Android architecture. But programmer's mode debug options for touch show me that it still works this way
Going back to topic, my understanding of this unexpected behavior is that - if you would consider 3 layers: hardware, driver, system, I think that first one would provide only raw touch data and only driver or system layer would convert it to x,y and momentum vector as it is used in Android applications.
Do you know what diagnosis or fix can I do? I have been looking through ADB logcat output, but didn't see anything suspicious yet (although I didn't check all yet - 10 seconds of log == 7000 log entries).
Throw even most advanced ideas on me. I had few Android devices already, flashed, rooted, bricked, diagnosed, unbricked and done a lot of sick things to save Java production servers at work. Despite that, I don't want to get tan in front of ADB logs this summer, so please please help