Related
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
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Have you tried resetting the phone ( as in completely wiping out everything including OS) and then try installing MIUI, if it still persists try a custom ROM
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Mine's now in a drawer, awaiting any form of fix.
I bought an Umidigi F1 Play while waiting......
Terrible issue and absolutely no support from Xiaomi.
Have personally owned Xiaomi phones since the Redmi 2 and never had any issues with flashing software.
Never again.
Try to flash china rom lowest version of miui 10 which is stable. Works for me.
Does not help, lowest u can flash is 1035 which will not fix the issue.
EDIT: flashed custom ROM, still issue persist
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Looks like there's a hardware defect in your device, maybe you got a faulty device, try going to a recognised mi store and get it replaced
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
mlackke said:
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
Click to expand...
Click to collapse
What If the phone was dropped or smth..
Hi,
I have the same problem which occurred after update.
Bump. Has there ever been a software-related fix to this issue? I currently have the same problem as described by the OP on a XIAOMI MI 8 Lite (128GB, 6GB RAM), although it only appeared after unlocking the bootloader and flashing a custom recovery. I've been flashing ROMs for quite a few years now and also double-checked all the software I've been using, I am certain that I made no software-related mistake. Since encountering the issue I have reflashed various original stock firmwares from xiaomi using both the flashtool and twrp, all to no avail. I've even relocked the bootloader, just to be absolutely certain. Since the entire touchscreen still registers input, I find it hard to believe that it is a hardware related issue, especially since I never dropped my phone and it also never experienced any physical trauma (so to speak). Would really appreciate any further input.
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
mlackke said:
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Has anyome fixed that yet? Is it even possible? I have tried everything, dowloaded tons of GB of roms, flashing programs, watched milion vids on YT, and still cant find anything. So i you find somethink, let me know <3
Prakashr09 said:
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Click to expand...
Click to collapse
Is there any update ? Strange thing is, it seems not that many devices have this problem ... or I couldn't find other threads about this
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! ;-)
tl;dr: I flashed to 11.0.7.1 which rendered the camera/torch unusable, only 9.5.11 should I try flashing back to the latest OxygenOS or rather use some custom ROM?
I was using the OnePlus 7 Pro I got a few months back used for ~200 EUR quite happily, except the front camera wasn't working (it pops up but the software freezes, keeps popping back and forth until I quit the camera app), which was probably somehow damaged by the previous user. We didn't discuss it, as he also didn't say anything about quite noticeable AMOLED Burn-in, cause he used the always-on navigational buttons... Something everyone should check when browsing through used deals.
I guess I was using the latest 11.0.6.1.GM21BA without issue, then the security patch and a few people on Reddit said their battery life improved, so I tried it.
All seemed fine, but the camera app has just thrown an error that the camera is damaged and I should go for repairs, torch in the quick menu said "Camera in use" so I did a backup and factory reset, which I recall I had to do in the previous update as well. But that didn't help. So in the angry rush, I said to hell with Oxygen OS and flashed cDroid, but there was the same issue there.
Finally using this great guide I managed to reflash to OxygenOS 10, but the issue still persisted. But with OxygenOS 9.5.11 finally, the camera works again. I didn't even put the phone online and I wanted to try upgrading to the latest OxygenOS 11 again, but I fear the issue will happen again.
Maybe OS9 somehow made the camera unstuck and unless I install the 'corrupting OxygenOS 10/11' and install rather some custom ROM it might be fine?
I will try later, I wasted too many valuable hours on this crap.
Googling in rage and reading other posts I see a similar camera issue happened across multiple OnePluses from 6 to 8. This really disappoints me and I'm sure I won't be looking for a used OnePlus ever again. Good thing I got a spare older OnePlus 5 for now.
Thanks for your testimony.
I indeed have this issue too. It appeared on June 10th. I tried to factory reset my phone yesterday and nothing changed.
I will also add that my front camera isn't working anymore since April. Can't figure out if this is software or hardware related
I really don't want to downgrade to OOS 9 but until the contrary is proved (by a fix or a comment by OnePlus), I would call it a case of planned obsolescence.
From now on I will keep my distance with this brand. Quite sad to admit because I was fond of their phones, but the management of issues / updates for the more dated ones isn't an example to follow anymore
klediouron said:
Thanks for your testimony.
I indeed have this issue too. It appeared on June 10th. I tried to factory reset my phone yesterday and nothing changed.
I will also add that my front camera isn't working anymore since April. Can't figure out if this is software or hardware related
...
Click to expand...
Click to collapse
Has your front camera stopped working after an update or during normal use?
It would make "sense" for OS 10+ to check if there is an issue with the front camera to disable all cameras altogether. Even if only to rush you into a repair shop...
I requested a repair which is in neighboring Poland, but they didn't wait for confirmation and requested UPS shipping from me right away.
I will check with them if the price would be within 50 EUR (from other posts not sure where in the world it was ~ 30 EUR if I recall correctly), then I'll get it repaired.