[Q] OnePlus One Screen Problem 44S - ONE Q&A, Help & Troubleshooting

Hi,
Is there already a thread for OnePlus One screen responsiveness issues running on 44S? I've had a look but haven't found any.
I'm experiencing screen issues:
Two separate taps are sometimes registered as a swipe
Sometimes a single tap is not detected (hard to reproduce, though)
I have made two videos in preparation for a warranty claim, but I want to see if there's anything I can do before having to send it in for a month. The first video is of me typing - not using swipe/glide gestures, only tapping normally. On several occasions it thinks I'm swiping, however.
Sorry! I really want to post links to my videos, but I'm a new user.
OnePlus have admitted that there is a problem, but I heard they completely fixed it with the 44S update. Could it be that there's still something wrong, or maybe I have defective hardware?

Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck

Related

[Q&A] [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project

[Q&A] [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project
Q&A for [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
After the update jbbl-141 118-release, my CAM died no longer opens.
:crying:
Hi guys.. Anyone knwos if the razr hd support USB otg? I'm on kk jbbl of november.. I tried but it didnt work for me
Sent from my RAZR HD using xda app-developers app
Don't know if this is of use to the DEV but I'm posting anyways for any bugs they may be trying to fix.
Device: Razr Maxx HD
MoKee Version: MK44.4-moto_msm8960-150124-RELEASE
I've run with this ROM now for a few months, mostly because anything is better than running stock. The ROM runs very smoothly, I hardly ever have lag anymore and navigation is a breeze. I really wanted to thank the devs for this. I do however have a few issues that bother me, some more than others.
First off, the lock screen seems to have difficulties unlocking, to the point that I have to make several attempts at unlocking my device as the pattern entry looses touch sensivity or something during entry. This might not be an issue with the ROM itself as stock did this too only way worse and more often. the bigger issue is that at times it even changes the pattern size on me for no reason that I can gather. Like, the pattern entry will become quarter the size of the normal one and turning the screen off then on again doesn't fix it.
Second, back to the screen, there is often some sort of error going on with the notifications that appears on screen. So, I'll have notifications appears that will now and then lap over code entry and get locked in place that a swipe to the side does not fix. This then makes the phone inaccessible because my pattern lock no longer acknowledges my touch as a notification is now taking the space above it. It is not a hard lock of the phone far as I can tell as my device doubles as my main MP3 playback device and the audio continues playing, the volume rocker increases and decreases the volume levels and the power button turns the screen off and then off again. This has also occured when switching to the lock screen camera where the screen gets half way between screens and then locks into place
Third, last time on the screen, I promise. What has happened today and several times prior to today is that sometimes when I lock the device and turn off the screen via the power button I can then not turn the screen back on via said power button. So today I had this happen while playing music and just like the issue above I could once again control volume but my screen whould not turn on unless I did a full reset via power/vol down. Funny thing is that the snap shot notification goes off when doing this but the screen doesn't come back.
I do use the music control lock screen features off PowerAMP on my pattern screen but I had never experience issues like the above three on stock.
Forth, my GPS is now useless. Though I have an Otterbox Commuter Series case, I have a hard time believing this at fault for absoulutly no ability at using GPS. In my profession I act as a service tech some weeks and may in fact need to be dispatched out to a site I may have never been to before. The GPS on my phone is a life saver as I'm a horrible driver and get lost often, I tend to stay in a lot. Anyways, I tried using it my last service call for Google Maps and though it found where I was, it was unable to give me instructions on the way to the site as it kept claiming the GPS signal was lost. It did provide turn-by-turn instructions which helped but made my journey that mach more difficult. Maybe an app issue but I had my mobile and GPS on pluse setting my options between battery and high accuracy to no avail.
WCDMA stopped working
Since I installed this rom my 3G (WCDMA) signal stopped working. Could anyone help me fix this?

[HELP] Partially Blank Screen but otherwise active device OR Sleep of Death

Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.

Oneplus 6 - Unresponsive Screen (Video Included)

I've had the phone since the day it came out. It took me a while to notice but the screen is definitely unresponsive at times. It is actually difficult to notice because, if you are like me and spend hours on your phone every day, if every so often if a touch doesn't register, your brain automatically make you repeat the gesture and you don't even think about it. And, it's OK if it happens like once a day. But with this phone, it's hundred times a day. I thought I was crazy so I recorded a video with my OP5.
See here: https://imgur.com/a/lZS4eVP
OK so this is kind of a very bad occurrence. Usually, it's not always like that. Sometimes it works perfectly fine. I also wonder if this could be the reason why the double tap to wake is also inconsistent, when the screen is off.
Also, yes, I do have a screen protector, but I've had them on all my phones and never had an issue.
Looks like this is happening only with you, is this problem occurring only in specific apps? or globally..
The touch here works snappy and very responsive. Maybe a faulty device? report to service center, I guess.
I also noted unresponsive screen once in a while while trying to click some hyperlinks or items with small clickable icons. But it's not anywhere close to what your video showed. Best and fair thing to do would be: Fresh flash the stock rom, don't install any additional apps then see if the problem persists. If it does, time to call customer service for a replacement unit. Good luck!
I've had similiar issues with my Essential PH-1, turns out it was a defect in the digitizer and I was RMA'd on it.
Nope working great here.
Do I get a new phone if I rma it? Or refurbished?
No I get this sometimes as well. Not nearly as bad as shown in your video, but sometimes it just doesn't register the touch properly and you have to touch it harder for it to register. Or when scrolling it only registers the scrolling partially
i have same problem in the same position
It happens to me sometimes when I tap the screen (for example tapping on a contact in whatsapp) that the screen doensn't respond good. When I tap a few times more and with a little more pressure it's going well. (I didn't test without the factory applyed screen protector)
Do people who have this problem use gestures? For me, the problem also occurs (no reaction when I tap the hyperlink or a small icon) but I noticed that it only occurs when the gestures are on. Maybe there is a problem.

Multitouch/screen issue ?

Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
lafritte57 said:
Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
Click to expand...
Click to collapse
Hardware issue, I have the same issue.
https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/miui-im-swiping-t3803874
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
lafritte57 said:
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
Click to expand...
Click to collapse
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
hayatesan said:
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
Click to expand...
Click to collapse
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
rodaven said:
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
Click to expand...
Click to collapse
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
lafritte57 said:
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
Click to expand...
Click to collapse
Fine, I'll tell you my experience. I use to had the same problem, it's only noticeable using the keyboard and specially when you tap the letters located near the edge of the screen, specially like the Q and P. I'm almost completely sure that the problem is related to gestures, because the system thinks you're swiping, in my case I got some lag too in addition to the false back gesture. What I did to fix this is use the keyboard (Google keyboard) in one hand mode (long press the "," and this option will pop up next to the emoticon) and moving it to the center and the problem is gone. It's actually more comfortable this way because the space bar moves up and it's more accessible. You can play then with the keyboard size if you think it's too small. There are two others threads talking about the same problem and I recommended this solution in both, and it seems to work for others too. Try it and tell us.
https://forum.xda-developers.com/showpost.php?p=76789600&postcount=13
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
stark0 said:
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
Click to expand...
Click to collapse
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
lafritte57 said:
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
Click to expand...
Click to collapse
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
stark0 said:
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
Click to expand...
Click to collapse
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
lafritte57 said:
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
Click to expand...
Click to collapse
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
stark0 said:
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
Click to expand...
Click to collapse
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
I changed my screen
Actually i cracked my screen and replaced new lcd from aliexpress claimed original. I checked it is JDI. But the touch issues still persist. I think its xiaomi driver.. or i dont know.. i really regret having this phone
lafritte57 said:
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
Click to expand...
Click to collapse
I tested more, disabling fulls creen gestures and the problem persist. There is a video with the keyboard trying to type "alguna", sometimes it makes a gesture "left to right":
https://www.youtube.com/watch?v=N8EgUfaN5C0
It's very disapointing, I had touch screen problems with my oneplus one and now with the mix 2s.

[Fix] multi touch/ghost touch issue

Those who don't know there are some people having ghost touch issues on POCO f1 and one guy able to capture it on the video. I personally didn't had the issue but after trying I was able to recreate the issue on my device. soon after I found the cause and able to fix the issue. this may or may not work on your device but absolutely worked for me. this seems to be a software bug. and no-one needs to panic. hopefully it will be fixed in next update.
how to recreate the issue?
Steps
1. download a multi touch tester app I used this
2. first do some testing yourself see if you can spot the issue
3. now do 3 finger swipe down (phone will take screenshot)
4. now randomly touch your screen with 1 or 2 fingers you'll notice 1 or 2 ghost touches.
How to fix Fix it?
Steps
1. go to settings>additional settings>button and gesture shortcuts>take a screenshot
2. and set it to none.
3. reboot
that's it!
the issue should be fixed
please let me know whether this worked for you or not
Yes.
As you mentioned issue was there.
But fixed with those steps.
okaraosp29 said:
Those who don't know there are some people having ghost touch issues on POCO f1 and one guy able to capture it on the video. I personally didn't had the issue but after trying I was able to recreate the issue on my device. soon after I found the cause and able to fix the issue. this may or may not work on your device but absolutely worked for me. this seems to be a software bug. and no-one needs to panic. hopefully it will be fixed in next update.
how to recreate the issue?
Steps
1. download a multi touch tester app I used this
2. first do some testing yourself see if you can spot the issue
3. now do 3 finger swipe down (phone will take screenshot)
4. now randomly touch your screen with 1 or 2 fingers you'll notice 1 or 2 ghost touches.
How to fix Fix it?
Steps
1. go to settings>additional settings>button and gesture shortcuts>take a screenshot
2. and set it to none.
3. reboot
that's it!
the issue should be fixed
please let me know whether this worked for you or not
Click to expand...
Click to collapse
Good stuff. I was skeptical at first since I knew something was off sometimes. Thanks for confirming it. Should be fixed if they took notice of this bug.
Thanks! The issue is 100% reproducible with the app. By turning off 3 finger screenshot shortcut, the issue goes away.
Guys, please file a bug, so this can be fixed and we can go back to using this feature.
1.Yes, that issue is due to the screenshot feature, but shouldn't the phone be able to distinguish between 3 finger touch and more than 3? Either take screenshot on four finger swipe or register it.
2.Can you please confirm if there is accuracy problem in PUBG aiming when you use multitouch? Like the multitouch bugs in Pixel and Zenfone Max Pro but quite subtle, the thing about the other devices are, they look and have been acknowledged by the respective companies regarding the issue but in our case, Xiaomi or Poco is making no announcement or anything.
https://www.youtube.com/watch?v=e5K2N6McC_s
The issue comes up after taking a 3 finger screenshot, but disabling may not be the only solution as this feature is quite useful also
What I have noticed is that after taking screenshot ghost touch is there till we use 1,2 or 3 fingers. Once we use 4, 5 or higher fingers the issue goes away.
Isn't it better to just touch screen with 4 fingers after taking a screenshot which somehow resets the ghost touch issue.
Have tried this solution with multi touch tester app
Mine is just fine even when 3 finger swipe screenshot is switched on
I can confirm that ghost touch issue still persist even when disabling three finger screenshot.
Mostly visible in pubg.
Great, fix worked
I didn't relize the issue but nice posting
Stop it! This is not an issue. It happens on mostly every phone that supports gestures. Test it on OnePlus 6 and you will get the same result.
GizmoFreak said:
Stop it! This is not an issue. It happens on mostly every phone that supports gestures. Test it on OnePlus 6 and you will get the same result.
Click to expand...
Click to collapse
it is software bug which creates inconvenient experience with touch screen.. this fix is just a workaround until official fix..
raj7749 said:
it is software bug which creates inconvenient experience with touch screen.. this fix is just a workaround until official fix..
Click to expand...
Click to collapse
Okay, show me how this affects your usage of phone. Don't show me on touch testing apps. Show me a real use problem.
GizmoFreak said:
Okay, show me how this affects your usage of phone. Don't show me on touch testing apps. Show me a real use problem.
Click to expand...
Click to collapse
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
raj7749 said:
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
Click to expand...
Click to collapse
Okay, please record a video of you playing and of course don't show me but share for the benefit of the community.
GizmoFreak said:
Okay, please record a video of you playing and of course don't show me but share for the benefit of the community.
Click to expand...
Click to collapse
xD, if needed will do M too lazy to do that for now
raj7749 said:
lol.. i don't need to prove to you anything about this, don't care wht u think.
However ill tell for the benefits of the others, it was effecting me while playing games.. specially RPG games where multitouch is heavily use. I was seeing weird behaviours sometimes, when selecting troops.. thts how i came to know
Click to expand...
Click to collapse
Exactly! There is no need to prove this issue because Google itself confirms that they have done a mistake by releasing it in Oreo and they have also promised to give a fix in later Pie updates. And people who wants proofs can look up in the internet about the "Multi touch Oreo Bug" problem and how it effects user experience rather than spamming here to make a point.
$hivaM Manav said:
Exactly! There is no need to prove this issue because Google itself confirms that they have done a mistake by releasing it in Oreo and they have also promised to give a fix in later Pie updates. And people who wants proofs can look up in the internet about the "Multi touch Oreo Bug" problem and how it effects user experience rather than spamming here to make a point.
Click to expand...
Click to collapse
Dude, google fixed the issue in the May or June patch and all other OEM's had to merge their builds to fix it. The problem is not there in MiA1 or MiA2.
Here is the bug:
http://en.miui.com/thread-3746297-1-1.html
Thanks
Maybe the original solution for 8.1 and P devices will work for this? It will either cause a bootloop, do nothing, or fix it... worth trying! Obviously an unlocked bootloader is needed for this (Magisk).

Categories

Resources