Related
Hey there,
Playing with my GT-N8010 and drawing on photoshop touch i suddenly noticed that in the some areas of the screen I couldn't get the full width of the brush. So I started testing the screen.
In this image there are 2 clear pressure drops while I draw a line. This is not because I suddenly change the pressure myself, this is within the tablet. I've tried this many times as I wanted to be sure and it seems the middle area almost always has this problem. It never allowes the full pressure to be detected.
Now I was wondering, is this something specificly with my tablet or do other users have this same problem? So could other people help me with this and try this same test to see if this happens with your tablet as well. I'd like to know if something is wrong with my tablet or if this is something all tablets have as a problem.
Thank you in advance.
uhm, am I impatient or does nobody really feel like helping me out here?
Just a simpel check on an app that is already installed would be enough.. screenshot not necessary
Only tryed in S note. Very hard to make a uniform line, you have to keep constant speed and pressure. I'm not a painter so this does not bother me.
Sent from my GT-N8010 using Tapatalk 2
There are lots of videos showing this problem: after you have touched the screen sometimes the screen registers finger presses even after you've removed them.
It's very hard to see what is going on if you don't turn on "show touches" in settings, so I suspect many reports about touch screens being unresponsive, or acting strangely is really the same problem.
It occurs both in stock ROMs and aosp, but subjectively more often in stock roms. It's not about moisture remaining, I've wiped the screen completely clean and dry and the phantom touches are there before, during and after cleaning.
Is there a software solution to this or is it hardware? Any thoughts of how this problem could be approached? I'm having trouble even reproducing it reliably.
yet another video of the odd problem: https://www.dropbox.com/s/mglol5qon6vy67g/2013-08-11 20.15.01.mp4
I replaced my Asus TF300 because of a similar issue. Asus fixed it once under warranty (replaced the entire LCD and digitizer, I think) but the issue came right back within a few months after RMA. By then the warranty had expired. In my case, the ghost touches were prevalent in a specific part of the screen; couldn't tell from your video whether the false touches were in the same general area every time or not.
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior. Just to be sure, though, I did flash a stock ROM prior to sending back to Asus and verified the issue existed there, labeled the area with tape so they could not miss it, and described in details the steps to reproduce.
Good luck.
Sent from my GT-N8013 using xda app-developers app
bsaman said:
I
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
This is my experience also, the aosp revolt rom, seems to suffer much less so than the stock roms.
It does seem to be the same area but it might be just because it's the side that is used most often for scrolling due to me being right handed.
The difference between how the roms behave is what make me suspect it's a software issue.
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
PremiumMediocre said:
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
Click to expand...
Click to collapse
No, my note has been rock solid, but I haven't enabled show touches so I can't say for sure.
Sent from my Vivid 4G using xda app-developers app
I'm thinking it might be possible to alter the idc file that specifies the behaviour of the touchscreen (https://source.android.com/devices/tech/input/input-device-configuration-files.html). But it's all a bit over my head.
I'm not alone at least:
http://www.youtube.com/watch?v=ii7m2696T3Y
A simpler cause?
I'm not alone at least:
(YouTube Video URL that I'm not allowed to post, yet)
Click to expand...
Click to collapse
The guy in the video did a great job with research. Did you catch the part where he found nearly imperceptible damage to the screen that was a possible cause? The ghosting always seems to occur in the same places because that's where the screen has been "crushed". Now "crushed" is a bad word because the screen probably hasn't been compressed beyond an acceptable level but there might be some correlation between where the users normally places his/her hand when using the pen and where the phantom touches occur. Maybe when writing, some users are baring-down harder than they realize and prolonged pressure in the same arc-shaped area created by the side of a hand, causes some changes in the capacitive properties in that area which cause a "latch" condition -- where the digitizer gets stuck and won't unstick until power is removed.
I've noticed in the videos that I've seen that the presenter get the problem to appear when using the side of their hand in a rolling fashion -- probably the same motion that they use when they just start to write. I also believe that devices that have this problem "get better" or less sensitive when not used for a while. This would follow the idea that the screen is compressed and given some time, the compression relaxes.
If the problem is limited to a certain area of the screen, I find it hard to believe that the problem could possibly have anything to do with ROM or firmware. The matrix of the digitizer in X-Y coordinates is addressed such that if there were a problem like this, the error would occur and repeat in either a straight vertical or horizontal direction instead of finite points spanning many rows and columns.
I guess one way of ruling this idea out would be to find someone who has never used the pen to write yet still has the problem.
I haven't ruled out that it is hardware related, but I have noted a significant improvement leaving stock ROMs for aosp. Maybe that's just a coincidence, I can't know for sure. I have noted something else that might help diagnose this problem.
If the period of turning on the screen, using the tablet then turning off the screen constitutes one session, there are two types of sessions. Sessions which suffer from this problem, which will be apparent in a relative short period of time. But there are also sessions where everything works as it should, regardless of how long the session is. So you will notice this problem within 10 min or not at all.
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
I know that this sounds ridiculous, yet I have observed this issue for the third year in a row.
My Neo 003 smartphone (Android 4.2, 2013) fails to read out its sensors (gravity, compass, location etc) during the summer months!
All apps reading the sensor data will 'freeze' or 'hang', or simply report 'waiting for event'.
The values for xyz are stuck at odd values, or change once or twice before hanging.
I can provide more details on the sensor hardware used, screen shots of these weird freezes if interested.
It took a while before I noticed this obvious dependency, as it is so odd and unexplainable.
After working flawlessly for several months the sensor readouts would start to hang more often in later spring of 2014.
The effect got worse over time; I suspected a hardware failure and was pissed when they got stuck for several months in the summer. I contacted the manufacturer and was brushed off - FU! So I kept trying.
To my surprise the sensors would start returning values more often in early fall, and would run perfect again around October, for the entire winter!
And then the SAME happened in 2015 again! And again this year!! Currently all sensors react flawlessly to motion, shaking, rotation. They had become flaky around April, hardly worked in May and failed during the summer, came back to life several weeks ago: I checked them almost daily to see this drift of functionality. Just WHAT is going on here?
I have tried to fool my phone by resetting the date and not going online to keep the wrong time - it did not affect the dependency. It failed to run in summer when set to winter dates.
I use the phone at home exclusively and always in the same rooms. There is no significant environmental change I can think of that could affect this (temperature, pressure, humidity). The problem occurs as well on the road anyways.
I am a phycist by trade, in fact I was quite involved in electronic measurement and data collection for many years.
This phone is driving me nuts, because I can not come up with a resasonable explanation for its odd behavior?
Android seems to use a quite thick layer of software drivers and event handles to manage the sensor readouts; it looked rather confusing to me and was not straight forward as I hoped for.
Since the failing mechanism is NOT hard but 'soft' (slowly shifting from working to failure over several weeks, and back to functionality in a similar way) it can not really be a software 'numbers' glitch, or?
Could other apps (about 600 are installed) interfere and block the readout? But why only in the summertime months??
I REALLY want to learn about this phenomenon, because it is about the weirdest problem I ever saw on an electronic device.
Who can shed some light on this, who can explain how Android initiates the sensor chips and reads them out?
Who has seen the same effect on other phones or devices?
What tests should I conduct to isolate this unique failure pattern (phone in the fridge, in a Faraday cage etc).
I do not want to break my Neo, despite its age it works quite well and runs stable, with its original ROM in place.
It took me THREE years to come forward with this issue, because I could not believe my own observations.
Now it is time to bring it up.
Please explain my spooky phone to me - thanks a lot!
m
mw210461 said:
I know that this sounds ridiculous, yet I have observed this issue for the third year in a row.
My Neo 003 smartphone (Android 4.2, 2013) fails to read out its sensors (gravity, compass, location etc) during the summer months!
All apps reading the sensor data will 'freeze' or 'hang', or simply report 'waiting for event'.
The values for xyz are stuck at odd values, or change once or twice before hanging.
I can provide more details on the sensor hardware used, screen shots of these weird freezes if interested.
It took a while before I noticed this obvious dependency, as it is so odd and unexplainable.
After working flawlessly for several months the sensor readouts would start to hang more often in later spring of 2014.
The effect got worse over time; I suspected a hardware failure and was pissed when they got stuck for several months in the summer. I contacted the manufacturer and was brushed off - FU! So I kept trying.
To my surprise the sensors would start returning values more often in early fall, and would run perfect again around October, for the entire winter!
And then the SAME happened in 2015 again! And again this year!! Currently all sensors react flawlessly to motion, shaking, rotation. They had become flaky around April, hardly worked in May and failed during the summer, came back to life several weeks ago: I checked them almost daily to see this drift of functionality. Just WHAT is going on here?
I have tried to fool my phone by resetting the date and not going online to keep the wrong time - it did not affect the dependency. It failed to run in summer when set to winter dates.
I use the phone at home exclusively and always in the same rooms. There is no significant environmental change I can think of that could affect this (temperature, pressure, humidity). The problem occurs as well on the road anyways.
I am a phycist by trade, in fact I was quite involved in electronic measurement and data collection for many years.
This phone is driving me nuts, because I can not come up with a resasonable explanation for its odd behavior?
Android seems to use a quite thick layer of software drivers and event handles to manage the sensor readouts; it looked rather confusing to me and was not straight forward as I hoped for.
Since the failing mechanism is NOT hard but 'soft' (slowly shifting from working to failure over several weeks, and back to functionality in a similar way) it can not really be a software 'numbers' glitch, or?
Could other apps (about 600 are installed) interfere and block the readout? But why only in the summertime months??
I REALLY want to learn about this phenomenon, because it is about the weirdest problem I ever saw on an electronic device.
Who can shed some light on this, who can explain how Android initiates the sensor chips and reads them out?
Who has seen the same effect on other phones or devices?
What tests should I conduct to isolate this unique failure pattern (phone in the fridge, in a Faraday cage etc).
I do not want to break my Neo, despite its age it works quite well and runs stable, with its original ROM in place.
It took me THREE years to come forward with this issue, because I could not believe my own observations.
Now it is time to bring it up.
Please explain my spooky phone to me - thanks a lot!
m
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like defective hardware and something that is pretty much out of scope. There are several sensor testing/calibrating apps you could try to test your sensors. That is all I can suggest really
Good Luck
Sawdoctor
Thanks for looking!
It has NOTHING to do with calibration.
If the sensors do not react during the summer, they can not be accessed anyway.
I installed and tried a dozen or so sensor apps, all show the problem, if in different ways (frozen, 'waiting for event' etc).
Noticable is that the orientation readout is consistently showing the same '(fixed) value 0.0130 for x, while y and z show flat 0, every time the error occurs. The compass is entirely frozen during these times as well.
The Neo uses different sensors for magnetic, gyroscopic and gravitation measurements.
I would not have asked here, if I had ANY clue about this causality.
WHAT is throwing the orientation/gyro sensors off for several months and ONLY in the summer? Inside my own house, at fixed environmental conditions?..
mw210461 said:
Thanks for looking!
It has NOTHING to do with calibration.
If the sensors do not react during the summer, they can not be accessed anyway.
I installed and tried a dozen or so sensor apps, all show the problem, if in different ways (frozen, 'waiting for event' etc).
Noticable is that the orientation readout is consistently showing the same '(fixed) value 0.0130 for x, while y and z show flat 0, every time the error occurs. The compass is entirely frozen during these times as well.
The Neo uses different sensors for magnetic, gyroscopic and gravitation measurements.
I would not have asked here, if I had ANY clue about this causality.
WHAT is throwing the orientation/gyro sensors off for several months and ONLY in the summer? Inside my own house, at fixed environmental conditions?..
Click to expand...
Click to collapse
I'm out of ideas then all it can be is faulty hardware. Maybe try asking in android q&a to see if you can find any other Neo 003 users see if they have the same issue or not
I have raised this issue in the NEO 003 thread, without results. I read about other phones acting up on their sensors, but never due to DATE patterns; typically they fail entirely or due to firmware mods, driver issues etc.
I AM willing to believe that the temporary failure of my NEO 003 sensors is hardware related, BUT:
which miniscule environmental variable change could possibly let the sensors fail to respond to reading them during the summer months, inside a regular home?
What IS different in July compared to March? Neither gravity nor magnetic fields fluctuate in any reasonable range throughout the year.
Nor does temperature (which varies far more depending on other factors; the phone shows board temperatures of anything between 39C and 60C depending on CPU load).
Room humidity is lower in the summer than in the winter time (heating in Central Europe), but then the problem happens inside a home as well as outside on the road. And there humidity can be anything from 30-100% during the day.
I even thought of electro-magnetic interferences, but there is nothing in my home that would only disturb electronics in the summer. Plus the problem is not limited to my own home anyways.
As a physicist I AM at the end of my wits. For me this is downright 'spooky'.
Never would I have brought this up if I had the faintest reasonable explanation, yet I can prove that the observation is true. It took me THREE years (winters and summers) to notice the regular, season related, repeatability of the problem!!!
I have two more choices:
- entirely resetting the phone and rebuilding it; with 600 apps installed this may take months to get them all tweaked and running again
- conduct more thorough system time modifications (prohibiting date adjustments for several days in a row, while booting the phone frequently and using it offline), trying to enforce it to accept SUMMER as the current season. First tests failed to trigger the reported sensor failure.
The fact that failures do not occur 'black/white' but slowly (more and more often failing to return data, from 'alive' to 'dead' and vice versa, over several weeks) does NOT speak for the software dependency. A number glitch would kill the readout hard at a given date; yet it does NOT.
As you can see I AM pondering quite a bit, unwilling to accept a phenomenon that defies my understanding of this universe. This IS my 'Einstein moment': spooky behavior beyond my horizon, unknown entanglements, as mentioned earlier.
Maybe this is the fix? anyone had this before?https://forums.oneplus.com/threads/...-hint-it-was-never-a-software-problem.186235/
samuk190 said:
Maybe this is the fix? anyone had this before?https://forums.oneplus.com/threads/...-hint-it-was-never-a-software-problem.186235/
Click to expand...
Click to collapse
Possibly. Mine had a very slight issue like this when the phone got warm, but that is mainly for people with the TRUE ghost touch. That means you swipe and sometimes it swipes lazy whrn scrolling because it didn't catch the entire swipe, typing on the keyboard is terrible because it "touched" a different letter, and using an app to test the multitouch registers less than 10 fingers, or even putting a few fingers on the screen causes it to touch elsewhere or not detect a touch. I had a OnePlus One like this when they were still being sold and it was terrible. Then there was a nightly CyanogenMod build that fixed the problem but would drain battery about twice as fast.
Currently, we have custom roms that have updated drivers which vastly improve the screen performance on the ones that had very little issues. Me for example after flashing DotOS I no longer get the very slight issues. My issue mainly occured when swiping, where it would require a swipe perfectly straight up or down instead of the normal way we swipe with our thumbs which is usually slightly tilted. It wasn't something to ruin the experience for me, but sometimes unlocking my phone with the pattern was difficult because of this. There was another rom out there that specifically outlined that it had many updated drivers including the Synaptics drivers (touch), but I cannot recall the name.
Crossvxm said:
Possibly. Mine had a very slight issue like this when the phone got warm, but that is mainly for people with the TRUE ghost touch. That means you swipe and sometimes it swipes lazy whrn scrolling because it didn't catch the entire swipe, typing on the keyboard is terrible because it "touched" a different letter, and using an app to test the multitouch registers less than 10 fingers, or even putting a few fingers on the screen causes it to touch elsewhere or not detect a touch. I had a OnePlus One like this when they were still being sold and it was terrible. Then there was a nightly CyanogenMod build that fixed the problem but would drain battery about twice as fast.
Currently, we have custom roms that have updated drivers which vastly improve the screen performance on the ones that had very little issues. Me for example after flashing DotOS I no longer get the very slight issues. My issue mainly occured when swiping, where it would require a swipe perfectly straight up or down instead of the normal way we swipe with our thumbs which is usually slightly tilted. It wasn't something to ruin the experience for me, but sometimes unlocking my phone with the pattern was difficult because of this. There was another rom out there that specifically outlined that it had many updated drivers including the Synaptics drivers (touch), but I cannot recall the name.
Click to expand...
Click to collapse
my oneplus one was fine bro, I used every custom rom and it worked very well! but in the last month it start happening this ghost touch problem
and I'm sure its 100% hardware, even on TWRP it happens