Database Info

[Q] Cubot A890/ M6589 (MTK6589) screen issues during/after call

Hey!
The Issue: During a phone call the screen turns dark and will not reactivate...it will pop back up after the call disconnects. Hitting any of the site buttons does nothing.
I have tried flashing with the newest firmware (http://blog.geekbuying.com/index.ph...-firmware-released-0502-version/#.UtMOWM93vVI), and although it says this issue has been resolved, it does not fix the problem for me.
I heard that custom ROM fix the solution? (Saw it on this http://forum.xda-developers.com/showthread.php?t=1518663).
But last time I tried one of those, the phone bricked and it took me a while to get it back working (finding stock followed by lost IMEI).
Anyone know a solution? Or possibly a good solid custom ROM that will work? I would really appreciate your help!

I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help

alrightiwill said:
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
Click to expand...
Click to collapse
Hey! Not sure if this be of any help, but for me removing the screen (plastic) cover fixed the issue. I assume the screen cover was blocking a sensor thus resulting in my issues.
Just thought I let you know what worked for me...although I doubt your issue can be solved like this.
BTW, I suggest you start a new post, as this one is old and I doubt anyone will read it! also, check out geekbuying.com blog in regards to your phone. They might have more info.

Touchscreen issues are finally gone?

I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.

Elvecio said:
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Click to expand...
Click to collapse
Not yet they aren't. It appears to have affected the functionality of double tap to wake for some people.
Doesn't seem like they're updating us on the investigation either. If they've fixed it using software, at the very least they should tell affected users why all the previous updates didn't work for them.

I've been on the nightly road since mid August, in my experience touch issue improved a lot after the touch firmware update in October, however there are still very rare cases where finicky / unresponsive touch happens, you don't want that when you ask someone for her contact in a bar on Halloween and she can't input the letter 'n'.
After that I think I experienced touch issue twice, I foolishly thought this was fixed sometime ago, however it came back big time the day before yesterday, and I was on the latest nightly... So in short, touch issue is not gone

touch issue
even im having touch issues with double tap and typing.

Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app

anuradha1208 said:
even im having touch issues with double tap and typing.
Click to expand...
Click to collapse
William Haven said:
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?

I'm thinking about downgrading... I'm currently running CM12 nightlies and the touchscreen is annoying me

vantt1 said:
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
Click to expand...
Click to collapse
Everywhere

this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/

st11 said:
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
Click to expand...
Click to collapse
There are at least two different touchscreen issues as far as we know:
One is where the touchscreen is semi-terrible all the time regardless of temperature
The other is where the touchscreen becomes unresponsive with the increase in temperature, and subsides if the phone is restarted or cools down

Is there a way of finding out which firmware is being used for colorOS?
I can't take this anymore, I am considering flashing either 44s or color OS

Possible input lag/ Ghost Touches once again

A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?

Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.

I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.

hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again

What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.

Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.

My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.

ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.

Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.

It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.

patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.

hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!

goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x

I have the same frustrating issue

Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)

I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.

This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.

I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...

HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!

The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version

Xperia 1 Fingerprint status test

Open the dialer app, and type *#*#7378423#*#* to open the Service Menu, from there go to Service Tests and scroll down until you find Fingerprint test.
Please post the results here with your device model number (J8110, J9110, J8170), device build number (55.x.x.x.x), age of your device and whether or not you have issues with the fingerprint scanner.
Trying to figure out a pattern and it seems like XDA is more active (in comparison) than other forums for Sony devices.
Thanks.

J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.

iArvee said:
J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.
Click to expand...
Click to collapse
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?

MeltdownSpectre said:
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?
Click to expand...
Click to collapse
It works 90% of the time for me. Especially after I "trained" the fingerprint sensor. Basically open up the fingerprint settings, then constantly tap your finger, moving your finger slightly with each tap to cover your whole thumb.
IMO the update is fine! Well at least for me. I did a software reset after updating.
OTA updates fine Haven't tested out the dual sim, but I'm assuming it won't work. The only time I had to flash a new build was when I updated from Pie to 10, because I usually do a full wipe during a major update.

I'm using J9110 with latest stock EU firmware. The sensor does not work at all. Even weirder, there is no option to test the sensor in service menu and I cannot find fingerprint scanner in device options. Out of the box the sensor worked great, but gradually started failing after 1 year of use.

Update: I took some screenshots and compared them to other Sony device with working FPS - there is clearly something fishy going on.
The third screenshot is what happens when I launch Fingerprint Manager with Activity Launcher app and try to register a new fingerprint.

@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.

b1nly said:
@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.
Click to expand...
Click to collapse
Same thing as mine, it is completely dead and no longer works.
Already try repair with sony companion but nothing work

@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there

LoneWolfL4rs said:
@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there
Click to expand...
Click to collapse
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.

problem is same, fingerprint menu is gone.
J9110
build 55.1.A.12.28
anyone solved this problem? please share ..

Since new firmware 55.2.A.4.47, fingerprint works for 1hour, then just start detecting ton of wrong prints even without finger on the sensor, and shut down completely until the phone is restarted. FingerprintTest showing "NOT OK" at this time. FingerprintTest showing OK after a restart.
I'm so sad I'm not able to get Flashtool working to go back to previous firmware. The fingerprint was working really great for the last 10 months (first months were really hit or miss tho).

if u are on Android 11 now u can't downgrade to Android 10 anymore...u can but it's not working well anymore.!
i tried many times going back to Android 9 after updated to Android 10.
after flashing older Android 9 fw Gyroscope sensor isn't working anymore on lower version of Android

I succeed to revert back to Android 10, but it didn't solve the issue with the fingerprint. If you got some issue with another sensor, I will guess that the "drivers" for the sensor can be changed by an update but are not rolled back correctly, thus the creating issue or not solving mine since the faulty "driver" for the FP reader stay the same.
After a day of not even having the fingerprint management in the security options, Support asked me to do a forced reboot (volume up + power) to see if it solves momentarily the reader, there is a well known issue and they are working on a fix. It did solve the issue momentarily so I guess my FP reader is not completely dead (it was my conclusion seing it was still an issue once reverted to Android10) and I just have to wait for a fix.

thehumble1 said:
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.
Click to expand...
Click to collapse
Sorry for really late answer. Yes I updated to 11 right after it came out.
To prove the theory of update bricking it I bought a replacement sensor from AliExpress (when it arrived, it was clearly a new one, in OEM packaging) and it didn't work either.
In the process of replacement I accidentally broke the screen (because was really hard to replace, at least with my experience, way harder than battery, motherboard, etc.). So I really don't recommend trying this to anyone.
Now there is no point to downgrading, heh.
And no, on 11 firmware shutting the phone down completely or force reboot does not help. I tried everything I could before going for replacement, including full data wipe and disconnecting the battery with inside connector for some time.

Been having the same issue but I can get the fingerprint sensor to work sometimes after booting into safe mode and then booting normally, read that from another post somewhere but can't seem to find it. Mine also keeps disconnecting from LTE and drops to H+ and has been doing that a lot recently I hope that they will update some of this soon getting pretty frustrated with it, any of you been seeing that in addition to the fingerprint issue?

My fingeprint sensor on XPERIA 1 is there in menu but it is not working at all. Can't recognize my finger at all. Resset didn't help as well as restart to safe mode. I gess it is dead. Or is there something else wrong?

The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)

vantrung1_2 said:
The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)
View attachment 5431097
Click to expand...
Click to collapse
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem

Elysiumx said:
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem
Click to expand...
Click to collapse
So, the warranty on mine was over and they asked me 335 euro for "REPLACEMENT FRONT COVER WITH FINGERPRINT READER" (also change the internal fingerprint reader module)
According to them so it is a hardware problem, but at that price certainly not worth it to repair it.

Ghost touch 👻

Anyone here getting ghost touch issue and sometimes proximity sensor issue too?
I tried with different firmware as well as stock miui and custom...
Upto 12.0.7 I didn't face that issue ..
After 12.0.8... I think my phone evolved into android robot
Oh man, it is automatically working

rhudsonsamuel said:
Anyone here getting ghost touch issue and sometimes proximity sensor issue too?
I tried with different firmware as well as stock miui and custom...
Upto 12.0.7 I didn't face that issue ..
After 12.0.8... I think my phone evolved into android robot
Oh man, it is automatically working
Click to expand...
Click to collapse
I didn't have that problem.
btw you posted in the wrong place.

Huh?
Posted in X3 thread only!

I have faced that issue too, but my phone has been dropped already and has a broken screen in the bottom. I guess this could be the reason my scenario.

Not a single damage on display.
now trying with latest firmware with custom rom and up to this time I didn't face it..
proximity working well

I have also ghost issue for months. It start after 5 or 6 months. I saw a lot of threads on reddit, and some here for other POCO or X3 Pro.
My issue is that sometime, 1 or 2 times a day, the screen goes crazy. Touch appears on all the screen and the only solution is to lock and unlock the screen.
I tried to disable 3 touchs option, stays à 90Hhz, update rom... I even tried to RMA but my local official xiaomi affiliated can't reproduce the issue.
At last I tried to install ArrowOs but crazy ghost touch reappears after 2 days. Do you think we can find some kernel or "touch driver" that can help ? What for an "indonesian" rom ?

It's a Hardware Problem.

I'm still looking for a way to mitigate this issue.
I just have to shut down the screen and then it's ok. It could be a software solution to reset some memory or electric level somewhere.
I saw tens of reporting, it look like a common issue on POCO device

Try and install: Touch Improvement magisk module of Akira
I think it need time for it to work right (somehow), but I don't have any issues anymore, while my phone was flipping like...

You're welcome! ;-)