Related
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
drakester09 said:
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
Click to expand...
Click to collapse
It is different than ghost-touches.
I noticed there is a topic on xda about this problem already: Click
I hope this can be fixed with a software update.
joeyzbg said:
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Click to expand...
Click to collapse
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
DuckMcQUack said:
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
Click to expand...
Click to collapse
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
joeyzbg said:
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
Click to expand...
Click to collapse
It really may be...just get used to New display settings and you will be out of problem too then!
Inviato dal mio One utilizzando Tapatalk
I have the exact same issue with my OnePlus after 3 weeks of use. At first it was the swype issue where the phone wasn't picking up swypes properly on the middle left side of my screen. I use a pattern unlock so it's annoying when the dots don't connect.
The next thing was not picking up my touches properly so when ever I use SwiftKey and they recommend words, I could never properly select it because the touchscreen wasn't registering properly.
I did a factory reset and it solved the problem at first but it's now back after 2 days. It's not as bad as before but still persistent. There are tons of people on Redit, Cyanogen and the OnePlus forums that are reporting the same problem.
The good news is it seems like a software and not hardware issue, hopefully the permanent fix can come soon.
Possible solution to the supposed OnePlus One touch sensitivity problem
Settings→Developer Options→ Scroll About Half Way and UNcheck "block gesture touch events"
Also try and see if unchecking "Adaptive backlight" in Settings→Display & lights→ Adaptive backlight, helps.
Of course none of these are permanent solutions. And this problem is real. But maybe the "solutions" above help.
ive not had these issues just yet. but i do get annoyed by gesture control
This still needs to be addressed. It's almost as bad as an old capacitive touch screen!
I got my phone maybe a month after it was released. After exactly 4 months the touchscreen input died and lost all sensitivity. Typing became impossible. After going back and fourth with support for 2 months they finally sent me another one. The new one was excellent for EXACTLY FOUR MONTHS!! Almost to the DAY! My damn touch is broken again and I can't type. I'm furious! I'm also 1wk outside warranty.
With the first phone I tried every hack, crack, rom, reformat, anything I could find. Nothing would restore the touch. I assume it's a hardware issue. I've been looking around for a solution but haven't found anything. If there is anything, I would appreciate some direction.
Sorry for everyone that ever wasted their money on OnePlus, I won't be getting any more products from them...
When playing around with yamtt on this phone and another, I noticed this phone only had any bugs when:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
2. Whenever more than 4 or 5 touches were registered at one time, adding any more caused issues fairly often.
Since I have purchased one of the more recent units I'd assume that the so called grounding issue is not a fault but I can't confirm that since I'm not going to crack open my device. These also happen regardless or kernel I am using on 11s, Stock, Franco, and AK.
If anyone can use this info, help yourself. I don't know if it has been reported yet but I've been bored on my day off. Thanks.
bukithd said:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
Click to expand...
Click to collapse
Had this one too, but it didn't appear in an other touchtester (it should even fail with 3+ touches)
bukithd said:
When playing around with yamtt on this phone and another, I noticed this phone only had any bugs when:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
2. Whenever more than 4 or 5 touches were registered at one time, adding any more caused issues fairly often.
Since I have purchased one of the more recent units I'd assume that the so called grounding issue is not a fault but I can't confirm that since I'm not going to crack open my device. These also happen regardless or kernel I am using on 11s, Stock, Franco, and AK.
If anyone can use this info, help yourself. I don't know if it has been reported yet but I've been bored on my day off. Thanks.
Click to expand...
Click to collapse
I already reported it a while back but so far there hasn't been a response from cm
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
My fingerprint sensor will just stop working and I need to reboot it in order to make it work again. It doesn't detect my finger at all , it's like its dead. I have the Verizon s8+, pre ordered it and got it on 4/20. I don't suffer from the dqa issue but i have another s8 plus, also pre ordered that does suffer from the issue. Anyone know of a fix or know how we can bring this to light in order to get it fixed
Edit: I believe the fix is to go into lock screen and security, after which go to secure lock settings and select the lock automatically option, and set it to immediately. I tested it when my fingerprint sensor wasn't working, and it fixed it for me
Edit #2: That did not fix it forever , issue came back within 30 minutes, from my testing it appears that fidgeting with the following (1. Screen Timeout 2. The Automatic lock timer 3. Lock instantly with power key) causes the issue to disappear or appear. I have contacted Samsung about it and they suggested a factory reset, not giving 2 ****s about the issue, they couldn't even tell me if they were working on a fix.
Edit #3: wow, didn't expect this page to become so popular as I didn't think this was such a big issue, my final solution was turning off fingerprint gestures, haven't experienced the issue after that, I've tried to factory reset the phone multiple times.
P. S. I have been able to achieve better speeds with the Iris scanner, a key trick to getting it to unlock faster is to look right into the sensor, which is the smaller circle next to the camera in the top right corner
Should've clarified the dqa issue is not what i'm worried about, just wanted to point out the weirdness of these bugs, It's the fingerprint issue i'm worried about
Mine does the same thing....TMobile version....It works great, and then randomly won't work at all and I have to reboot
I have the same problem here.
Weird, I noticed this issue today
Posted in the other thread about the same problem. I noticed this today as well. Most of the time significantly moving the phone and scanning my finger again seems to work. I am yet to encounter this issue when the phone is actually unlocked authenticating to an app or something. So far it all seems to be limited to the lock screen in that the phone does not want to register a scan of the finger at all, as though the scanner is not there.
Same
GGgamer16 said:
My fingerprint sensor will just stop working and I need to reboot it in order to make it work again. It doesn't detect my finger at all , it's like its dead. I have the Verizon s8+, pre ordered it and got it on 4/20. I don't suffer from the dqa issue but i have another s8 plus, also pre ordered that does suffer from the issue. Anyone know of a fix or know how we can bring this to light in order to get it fixed
Click to expand...
Click to collapse
Same, I really dont want to get a new one. I need a answer and your the only post of source that has the same problem as me.
Same issues here, very annoying. T-Mobile version. We have two S8 and one of them is working fine, the other one it's having fingerprint issues. Any ideas on how to fix this? I hope is a software issue.
johnminea said:
Same issues here, very annoying. T-Mobile version. We have two S8 and one of them is working fine, the other one it's having fingerprint issues. Any ideas on how to fix this? I hope is a software issue.
Click to expand...
Click to collapse
I think it is software related. It seems to intermittent and in my case seems to be related to limited movement before scanning the finger as I only see this when trying to unlock. In other words, it seems the unlock needs an accelerator event before unlock event to work, and no movement such as a finger resting on the screen doesn't detect.
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Mine is doing the same thing. It's almost completey random as to when the fingerprint sensor works. It's not as if it isn't recognizing my fingerprint, it's as if the sensor is completely dead or inactive. I'm tempted to return the phone and re-order but I have a trip coming up that I would like the phone for but if I wait until I return I will be past my 20 days.
Very frustrating after having to return my Note 7 like 3 times.
Does this seem software related?
Not sure it is software related. I have another S8, same carrier (T-Mobile) same firmware same software updates, version etc. Both came on April 19. Mine is having issues since I got it, the other one 7 days later no issues at all. I called Samsung and they told me if a factory reset does not solve the issue, to go to the store and get a new one. I will get a replacement tomorrow. I am on the edge with Samsung coming from a Note 7 user....
johnminea said:
Not sure it is software related. I have another S8, same carrier (T-Mobile) same firmware same software updates, version etc. Both came on April 19. Mine is having issues since I got it, the other one 7 days later no issues at all. I called Samsung and they told me if a factory reset does not solve the issue, to go to the store and get a new one. I will get a replacement tomorrow. I am on the edge with Samsung coming from a Note 7 user....
Click to expand...
Click to collapse
That's good to know. I ordered mine online through T-Mobile and they require me to send it back through the mail. They won't let me exchange it in store. So dumb. They also won't send me out the replacement before I send the broken one back. Looks like I will be without a phone for a few days.
I'm getting real sick of this loss of quality control with Samsung.
'
Yeah same here, but. You can call customer service and ask them to send the replacement phone at a store near you. This is what they have done for me. I will go tomorrow to pick up the replacement phone and I will give them back the old one. Is stupid but it is what it is. I think because the stores are individual franchises, maybe. who the heck knows. If the second one does the same I am pretty much done with Samsung. I had enough with my Note 7, now this. grrr
So this morning I once again had the sensor shut down. It's not just on the lock screen. After unlocking with the pin I was unable to use the fingerprint sensor to bring the notification menu down either.
I'm going to go to Verizon after work today and get a replacement.
I had no time to go and get the replacement today. However, no issues in the last 48 hours. For some reason is just working. I might go tomorrow and get a new one just to be on the safe side, I hope.
johnminea said:
I had no time to go and get the replacement today. However, no issues in the last 48 hours. For some reason is just working. I might go tomorrow and get a new one just to be on the safe side, I hope.
Click to expand...
Click to collapse
Mine happened first on 4/20 and it had not done it again until today. So I'm just going to go in and exchange it.
Gary02468 said:
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Click to expand...
Click to collapse
Where is that setting
Well I took the phone into Verizon and they refused to exchange it. They said it's a software problem.
Gary02468 said:
Have you tried disabling Optimize Battery Usage for the Fingerprint system app?
Click to expand...
Click to collapse
I just did it, when Imade the thread I didn't know where to find the option, upon looking further I found it.
For anyone wondering, go to apps, then app manager, then in the upper right corner click on the option icon , then click on special access, then click on optimize battery usage, then click on "Apps not optimized" and then select "All apps", then scroll down and look for Fingerprint app(I don't know if this is the only app having to do with the fingerprint sensor) and untoggle it.
P.S. I dont know if this works or not, as I have not experienced the bug for over 36 hours
Edit: this did not work, I just experienced the bug again, the fix is to go to
lock screen and security, then to secure lock settings, and set the automatic lock to immediately.
Edit #2: This did not work , see OP for more info
Just like what I said in the title, I'm about to get a new screen replacement as I heard newer batches don't have any touch related issues. I'm a hardcore gamer and I think touch is very important for me when playing games.
Already 3 months and 'software fixes' regarding touches is not working great.
My phone is from september batch and running 8.12.27 beta and facing touch lags around edges.
Clean flashed 8.12.20 now more multi touches issues under notch.
Is there anyone else who already got a screen replacement?
Any issues like screen bleed/touch delay/multi touch and so on?
Under warranty??
Sent from my POCO F1 using Tapatalk
amitroutray said:
Under warranty??
Sent from my POCO F1 using Tapatalk
Click to expand...
Click to collapse
Yes
I also have the same problem but I'm on the stable Pie version of the ROM.
I still havent found any problem though. My screen does have a lil bit light bleed. Still,no touch issue yet.
buy a switch or something, you can consider yourself as ''hardcore gamer'' if you play un phone xD
I'm also facing touch lag around the edges.
The screen center is lag free though. Latest stable Pie didn't improve anything. I also have a little bit of screen bleeding around the notch.
Does the warranty cover this?
koax88 said:
I still havent found any problem though. My screen does have a lil bit light bleed. Still,no touch issue yet.
Click to expand...
Click to collapse
How about doing 'qi'test and see if it outputs iq on your Poco.
What ROM you using?
Any multi touch issues when playing tap intensive games like drums or MOBAs?
I think you might be wasting time because I'm pretty sure I've seen someone here or on Reddit say that they had their screen replaced and it did not fix the touch issue for them. Keep in mind after replacement that any of the beta releases from 8.11.23 on (except for the 8.12.27 update) have a new kernel which fixes the delay on the right and left edge and improves scrolling. So if you wish to test if the replaced screen did fix anything, use the stable ROM or the .27 beta to check that.
I must be one of the ones without the screen issue then.
Lel
What exactly is the touch issue?
I Got Armoured edition 128GB delivered yesterday itself. Updated it to MIUI 10.1.3.0 PIE and i am facing no issues as of now. No screen bleeding and no touch Issues.
I would like too to know how to detect those display issues.
mario123m said:
I think you might be wasting time because I'm pretty sure I've seen someone here or on Reddit say that they had their screen replaced and it did not fix the touch issue for them. Keep in mind after replacement that any of the beta releases from 8.11.23 on (except for the 8.12.27 update) have a new kernel which fixes the delay on the right and left edge and improves scrolling. So if you wish to test if the replaced screen did fix anything, use the stable ROM or the .27 beta to check that.
Click to expand...
Click to collapse
Ofcourse I'll use the Stable ROM to get a new screen instead using beta.
I can replicate those touch issues on Stable i.e touch delay on edges.
It'll be useless to ask for a screen replacement using a beta just to find out all the store did was just change it from Beta to Stable to 'fix' the touch issue lol.
Immortel.CZ said:
I would like too to know how to detect those display issues.
Click to expand...
Click to collapse
If you're on Stable pie, type 'qi' fast and most Pocos will output 'iq' even though pressed q first then i. This is touch delay issue.
If you're on 8.12.20 beta, theres screen freezes and multi touches under the notch if you tap and slide 2 finggers at the same button with a bit of force for it to occur. Screen freeeezes also happens where you cannot register ANY touches on the screen until you lock and unlock your phone
misleaded said:
If you're on Stable pie, type 'qi' fast and most Pocos will output 'iq' even though pressed q first then i. This is touch delay issue.
Click to expand...
Click to collapse
Well, I'm still not sure. Sometimes, I will do it quickly and output is "qi" but sometimes I do it quickly, output is "iq" but I'm not sure if I pressed "q" or "i" first, because of the speed. It's there any other way to prove it?
And if it have lags, who can feel those? Because I definitively not.
Immortel.CZ said:
Well, I'm still not sure. Sometimes, I will do it quickly and output is "qi" but sometimes I do it quickly, output is "iq" but I'm not sure if I pressed "q" or "i" first, because of the speed. It's there any other way to prove it?
And if it have lags, who can feel those? Because I definitively not.
Click to expand...
Click to collapse
'q' then 'i' super fast and make sure you know what you are pressing first.
Or you can try 'p' then 'e' quickly see if it comes as 'pe' or 'ep'
Every Poco have it. Forget about it and wait for the fix or just change to another device. If you're really hardcore, I'm assuming you a PUBG gamer, you should know that gyroscopic is the best way to aim on the game and the touch issue means nothing.
I can confirm by testing it, that switching from 8.12.27 to 8.12.10 touchscreen fw the delay is improved. At least, according to the maximum speed that I can type, performing the simple test of typing q and afterwards g or q and afterwards i, with the 8.12.10 is always printing on the screen the right order of the letters I ve typed, thus qg/qi, but on 8.12.27 always the outcome was gq/iq. My device is made on Oct.2018.
melodystyle2003 said:
I can confirm by testing it, that switching from 8.12.27 to 8.12.10 touchscreen fw the delay is improved. At least, according to the maximum speed that I can type, performing the simple test of typing q and afterwards g or q and afterwards i, with the 8.12.10 is always printing on the screen the right order of the letters I ve typed, thus qg/qi, but on 8.12.27 always the outcome was gq/iq. My device is made on Oct.2018.
Click to expand...
Click to collapse
Oh that's interesting. Some people here claim that newer batches don't have the touch problem yet you seem to have the exact same issue as my unit which was assembled in July 2018. Full four months and the issue still there... That is why I don't believe there are Poco users who don't have this problem.
mario123m said:
Oh that's interesting. Some people here claim that newer batches don't have the touch problem yet you seem to have the exact same issue as my unit which was assembled in July 2018. Full four months and the issue still there... That is why I don't believe there are Poco users who don't have this problem.
Click to expand...
Click to collapse
I just don't know.
It's just that maybe some units aren't affected.
I heard some random guy in the Poco reddit got a pocophone around September and bought another Poco for her little brother 2 months after that and what happened is his poco has touch issues while his little brother's doesn't have any.
That's why I thought I'm gonna get a new screen replacement
Pixel 6a. Just upgraded from Android 12 where the fingerprint reader worked decently. Now on A13 and although previously registered (on A12) fingerprints work, I cannot register any new fingerprints. Repeatedly get the "Couldn't process fingerprint. Please try again" error. This previously occurred on the most recent beta of A13 but once I rolled back to A12 fingerprints could be read.
You may have to factory reset unfortunately. That "fixed" it mostly on the beta.
ctfrommn said:
You may have to factory reset unfortunately. That "fixed" it mostly on the beta.
Click to expand...
Click to collapse
On the beta I did a factory reset and it didn't fix it. I then couldn't even register a single fingerprint so extremely reluctant to do another factory reset. At least right now I have one registered fingerprint that works.
Maybe try using Pixel Repair Tool to calibrate the fp reader
greatgoogly said:
On the beta I did a factory reset and it didn't fix it. I then couldn't even register a single fingerprint so extremely reluctant to do another factory reset. At least right now I have one registered fingerprint that works.
Click to expand...
Click to collapse
Thats a shame. Im not even going to mess with updating to A13 for a few days at least....maybe not till next week.
ctfrommn said:
Thats a shame. Im not even going to mess with updating to A13 for a few days at least....maybe not till next week.
Click to expand...
Click to collapse
Successfully just added another finger print. No problems whatsoever.
bobby janow said:
Successfully just added another finger print. No problems whatsoever.
Click to expand...
Click to collapse
Just tried a complete wipe and still can't add a fingerprint since the upgrade to A13
LOLCATpl said:
Maybe try using Pixel Repair Tool to calibrate the fp reader
Click to expand...
Click to collapse
Tried that. Still no luck registering a fingerprint.
Wow, didn't know a fingerprint sensor could be pooched. Sounds so vulgar
Well, I have complete different experience.
I was on A13 Beta where FP was most inconsistent..
After installing A13 Stable, it's better than A12..
No factory Reset, Nothing
Mine working okay. Doesn't seem any different 12 vs 13B vs 13S. Do you have the warranty? This could be an issue with the sensor itself.
Another user reporting FP issue after the upgrade. 12 was okay but 13 doesn't work with registered FPs nor letting me add new ones. Sigh.
I never had issues with 12 and don't have issues with 13. I do not use any screen protectors at this point but I have one coming.
You guys need to redo your fingers twice and increase sensitivity in settings.
msgfromside3 said:
Another user reporting FP issue after the upgrade. 12 was okay but 13 doesn't work with registered FPs nor letting me add new ones. Sigh.
Click to expand...
Click to collapse
So it turns out that FP reader with A13 does work well with dry skin now. I just washed my hand with water and it let me register. My hands are usually very dry so this is going to be a problem..
Edit: moisture doesn't help with recognizing fingerprint when I tried to use it. Instead, I found the spot on the sensor it works better (slight upper left part) . This is absurd but at least I figured out the way to use it.
Me too. Had a shower and it worked fine until my hands have now fully dried out and yes I have dry skin naturally.
This FP is just making me go crazy, almost slowly worked in 12, since 13, it's just not working at all, I succeed register 4 fingerprints (with only 2 thumbs...), it took me about 20 minutes... but after, it never recognizes me... The only change is that, since 13, this phone ask my password faster than 12. In fact, after 2 tries. Wow, really impressed by the Google hard work on Android 13. I'm starting to think to ask a refund, I'm starting to regret my good old xiaomi mi mix 2s with his back FP, fast and reliable.....
I had some user errors lol on the FP origninally but it was only in the way I was placing my finger on the sensor. It's a bit different with the screen having a "spot" to place your finger on, rather than a seperate part of the display like hte 3a. You kind of have to "push" into the screen for a split second to take. Once I figured that out I was able to use FP no problem.
superbellefleche said:
This FP is just making me go crazy, almost slowly worked in 12, since 13, it's just not working at all, I succeed register 4 fingerprints (with only 2 thumbs...), it took me about 20 minutes... but after, it never recognizes me... The only change is that, since 13, this phone ask my password faster than 12. In fact, after 2 tries. Wow, really impressed by the Google hard work on Android 13. I'm starting to think to ask a refund, I'm starting to regret my good old xiaomi mi mix 2s with his back FP, fast and reliable.....
Click to expand...
Click to collapse
I had the same issue as you on a13 (beta and stable) after about 1-2 days clean install but didn't seem to have any issues on a12. I was almost ready to downgrade back to a12. However, i later learned that it was due to my dry fingers.
Note: On a13, i do have issues with fingerprint sensor in bright sunlight. It won't recognize my fingerprint at all
Like earlier stated, a "firm" initial press seems to make it work most times, but they definitely need to keep working on this.
msgfromside3 said:
Another user reporting FP issue after the upgrade. 12 was okay but 13 doesn't work with registered FPs nor letting me add new ones. Sigh.
Click to expand...
Click to collapse
Exactly what happened to me after the upgrade.