Database Info

[Q] New Google Maps flickers on CM10.1

Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.

emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?

PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.

emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.

interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..

Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.

PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.

Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.

Bump for update, anyone else experiences with new maps?

PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!

greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story

j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.

I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app

Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?

Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.

anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.

It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2

possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.

Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.

same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..

oneplus one touch screen problem?

touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?

Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.

ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess

sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD

ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too

sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.

I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.

Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.

http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html

Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you

I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'

i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.

I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One

Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com

DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?

alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.

DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.

alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...

[Q] HELP! touchscreen issues

hi everyone - not a new issue, but seems like most ppls phone has this figured out now after 44s.
Getting ghost touches and very slow/laggy scroll/swipe response...basically have to press and drag the finger to get anything working.
Currently running stock CM11s 44s with a locked bootloader, completely flashed back to stock using the zip file from cyanogens website. but i have tried CM, Omni, paranoid, and have tried diff kernels including franco, but it doesnt seem to wanna work.
here is a link to my screencast - kinda hard to see but i tried to record what happns when i imitate typing.
https://drive.google.com/file/d/0B1quWiDbFcajdkdTaGhwZzc4M1k/view?usp=sharing
any help would be appreciated! i have seen other posts on this, but nothing seems to be working! what am i missing!?!? :crying:

I have seen other people complain about this and it seems to be a bug, there is no fix at the moment. Wipe the screen clean with a microfiber/lint free cloth while the phone is off. If you think it's hardware damage then use your warranty and send it in.

hmm. I have contacted one plus and have submitted a ticket a while ago, but they are extremely slow in responding. its been over 20days now. Since the touchscreen works fine for the first 15 20mins, i thought it would be a software issue that i could somehow fix....

There will be a new Touchscreen firmware soon

nice!! where did u hear/read this? any ideas when?

hassan3216 said:
nice!! where did u hear/read this? any ideas when?
Click to expand...
Click to collapse
it's a known problem. I have it too. I don't think a firmware update is going to fix it.
http://gadgets.ndtv.com/mobiles/new...defect-affecting-touchscreen-digitiser-625211
https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/

Problem with my OnePlus One's Screen!

Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!

I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.

welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases

I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?

Try going back to cm11s and then check...
Sent from Android (a google product)

Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.

Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!

One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?

naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?

Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.

donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/

vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.

I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.

donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..

vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.

Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!

Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk

anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.

donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk

Sometimes touch is unresponsive

When I press something quickly and not so hard, touch doesn't get recognized. For example when I type in 4 PIN on a lockscreen 1 or even 2 out of 4 touches may not be recognized.
Apps, keyboard - everything has this issue.
Im now trying through different ROMs, official releases and etc to find most stable version of MIUI.
I really hope this is not hardware issue :/ Is there any way to calibrate touchscreen tho?
Does anyone experience same problem? It takes place only when I press not to hard on screen and quickly.

I haven't seen this problem, but I remember having an issue with a recent Motorola phone I tried for work. Removing the screen protector fixed it in that case.
Sent from my Mi MIX 3 using Tapatalk

PWn3R said:
I haven't seen this problem, but I remember having an issue with a recent Motorola phone I tried for work. Removing the screen protector fixed it in that case.
Sent from my Mi MIX 3 using Tapatalk
Click to expand...
Click to collapse
I dont use screen protector yet, stores in my country still don't have them :d
SO I just noticed that problems are gone while I'm in TWRP. Keyboard is dream-like responsive, no random un-responses when I press to quickly and softly. It still recognizes a touch like a charm.
I guess its MIUI than?

They probably means it's kernel/touch driver related. If you have unlocked bootloader you could try the custom kernel. As always be sure it works for the rom version you are on and that you follow directions.
Sent from my Mi MIX 3 using Tapatalk

I have the opposite problem to this! If anything my screen is too sensitive, I have to be really careful lifting it or putting it down with the screen on, despite it not being a totally edge-to-edge display (which is one of the reasons I didn't buy a Mate 20 Pro, edge-to-edge looks great, but it's a pain in day-to-day use).

Well this is getting deal breaker for me. Touch is annoyingly unresponsive on latest stable build. Also on latest Beta build.
Does anyone experience same problem? please respond.

Dathrex said:
Well this is getting deal breaker for me. Touch is annoyingly unresponsive on latest stable build. Also on latest Beta build.
Does anyone experience same problem? please respond.
Click to expand...
Click to collapse
You got a lemon, this thing is one of the most responsive screens I've ever used. I have an essential phone so I know how bad it must be for you, the touch response on those is the worst I've ever experienced by far.

Dathrex said:
Well this is getting deal breaker for me. Touch is annoyingly unresponsive on latest stable build. Also on latest Beta build.
Does anyone experience same problem? please respond.
Click to expand...
Click to collapse
Depending where you bought it and what ROM you have I'd advise to download a ROM and purge the ROM now because if you are saying that the touch problem is in MIUI something is not right. Just wipe the phone and fastboot new ROM. If this does not fix problem RETURN IT FOR NEW ONE.

Can this happen because of unlocked bootloader?

Dathrex said:
Can this happen because of unlocked bootloader?
Click to expand...
Click to collapse
No.

You are not crazy dude.
Same here.
bought today the European version and, in the first Google wizard, touch was unresponsive for, for example, the next button.
Now I don't have any issue.
So, you are not crazy.
Ps
And no: I'm locked.

Same problem here...
Mine was totally fine, really responsive and nice, up until I installed the MIUI 10.2 Global and now it's ****. Seems to be especially bad in the lower right corner. Seems to be software triggered...

My CN version running Xiaomi.EU rom has no problems with the touch screen or touch sensitivity, been running fine for the past 2 months or so. Also have tried on multiple roms (stock CN rom, CN developer rom, global rom).
Sounds like an issue with the EU/Global version?

I'm on Global ROM and facing same issue.

Same issue here with 256/8GB CN device, I unlocked the phone as soon as I got it and installed Global 10.0.11.0 on it. The touch issue happened when I updated the phone to 10.2 first via the updater. Then i thought it was an issue with dirty flash so I wiped everything via TWRP and did a clean flash. Still the same issue, i even tried the 10.2 EU rom. For now I went back to 10.0.11.0 and there's 0 touch issue.

I have the same issue, is it a software or a hardware issue ??

Was this solved by now or is it still an issue? I'm planning on buying a Mix 3 and this would be deal breaker for me.

Calmasis said:
Was this solved by now or is it still an issue? I'm planning on buying a Mix 3 and this would be deal breaker for me.
Click to expand...
Click to collapse
I think it was extremely rare if you read all the posts I don't think many members experienced the issue

954wrecker said:
I think it was extremely rare if you read all the posts I don't think many members experienced the issue
Click to expand...
Click to collapse
Well I was kinda worried because I saw 2 topics about this, this is the other one: https://forum.xda-developers.com/mi-mix-3/help/touchscreen-sensitivity-t3896796
Thank you for your reply.