I just wanted to get a poll going regarding "ghost touches" on CM11s 33r release. When I first updated to 33r, the touch screen was great and it seemed like the firmware update fixed the issue. However, after using my device, the touch panel once again became stubborn and the "ghost touches" appeared once again.
This issue reminds me of the 2013 Nexus 7 which to this day still hasn't been resolved. It is weird how the phone will work fine and then all of a sudden become unresponsive. I notice this especially when typing, sometimes the keyboard will show a swipe gesture even though I am physically typing.
nope, never had this problem.
I had this problem 1-2 times in a month of usage. Not a great issue but it definitely existed. With 33r i experienced no more ghost touches, just some occasional touchscreen freeze (unlocking phone was impossible until the system reboot).
Issues that are making me angry are others: touchscreen responsivity and precision, for example. Typing with my 1+1 is a total pain.
working smooth & fast no problems...
had ghost swipes ever since I got CM11S and had it for every update. Didn't really get better each time.
was on stock kernal now with ak, just a BIT better but still experience it every 6-7 words.
Hope they completely fix this soon.
Never had ghost touches on stock rom
Sent from my A0001 using XDA Free mobile app
I had ghosting everywhere
I am so far surprised on the results. I have two friends with the opo and both of them also have the touch screen issue. Is there any info we can compare to see if there is a different touchpanel used for those who are experiencing the problem vs those who are not?
For sure. Mine still have. For me the biggest problem is the poor latency performance, the worst that i experience. Coming from a HTC one, M7. Running nightlies actually.
Have ghost touches since update to 33R, never before. Is this sw or hw related?
Especially when typing moderately fast, the screen does not seem to be able to distinguish between two touches. It kind of "swallows" the symbols I have pressed on the keyboard resulting in a disastrous typing experience. Before I had a Nexus 5 and it that respect it was definitely more precise (and sensitive) to touches. Typing without any hiccups. Just the way it should be.
Also sometimes my opo, while surfing through websites; when I try to touch a small hyperlink, it doesn't seem to recognize the interaction. I have to touch the link several times to get the screen to recognize it.
This, paired with the typing issues makes using the opo awfully complicated touch-wise. I have to artificially slow down my typing speed to lessen the erratic behaviour of the screen. A no go in my opinion and I am thinking about returning my opo and insist on a refund for the stated reasons.
This is a major problem and OnePlus better get their asses up, admit the faults and solve the problems.
GalaxyFan88 said:
Especially when typing moderately fast, the screen does not seem to be able to distinguish between two touches. It kind of "swallows" the symbols I have pressed on the keyboard resulting in a disastrous typing experience. Before I had a Nexus 5 and it that respect it was definitely more precise (and sensitive) to touches. Typing without any hiccups. Just the way it should be.
Also sometimes my opo, while surfing through websites; when I try to touch a small hyperlink, it doesn't seem to recognize the interaction. I have to touch the link several times to get the screen to recognize it.
This, paired with the typing issues makes using the opo awfully complicated touch-wise. I have to artificially slow down my typing speed to lessen the erratic behaviour of the screen. A no go in my opinion and I am thinking about returning my opo and insist on a refund for the stated reasons.
This is a major problem and OnePlus better get their asses up, admit the faults and solve the problems.
Click to expand...
Click to collapse
Same here. I love this one plus one, but the typing issue is a huge problem for me. If they don't fix it I'll have to jump ship when I can get something new.
tpierce89 said:
Same here. I love this one plus one, but the typing issue is a huge problem for me. If they don't fix it I'll have to jump ship when I can get something new.
Click to expand...
Click to collapse
Agree. It's a love-hate relationship; the specs and furthermore the price-performance ratio are absolutely great but that one issue really keeps me off staying with the opo.
I will wait a bit and see how well the problem-analysis goes. Considering how the alleged touchscreen driver fix didn't fix anything at all (at least for me) makes me seriously doubt that there will be a final fix for this issue, ever.
no typing issues or lag its way faster than note3 on par with nexus 7 if not slightly smoother in total experience. since i got used to sony's xperia keyboard i'm using the kk emoji keyboard from playstore on ONO which is faster.
I used to have them all the time, to the point I couldn't get pass the lock screen.
I even though of doing an RMA, while hesitating. I decided to do a full wipe and install crdroid ( i knew the developer had them to and was trying to fix them ) now it's a thing from the past I never get them anymore.
I'm not saying crdroid is miracle fix, I'm just stating what happened to me.
If your rooted and occasionally flash ROMs it may be worth a try.
Also a friend of mine just received his today. If he has ghost touches will try crdroid again and if it works will report here.
Nope, nemas problems on my phone.
Had it for the first time couple of days ago. After rebooting the device, everything went normal.
bradm23 said:
I just wanted to get a poll going regarding "ghost touches" on CM11s 33r release. When I first updated to 33r, the touch screen was great and it seemed like the firmware update fixed the issue. However, after using my device, the touch panel once again became stubborn and the "ghost touches" appeared once again.
This issue reminds me of the 2013 Nexus 7 which to this day still hasn't been resolved. It is weird how the phone will work fine and then all of a sudden become unresponsive. I notice this especially when typing, sometimes the keyboard will show a swipe gesture even though I am physically typing.
Click to expand...
Click to collapse
After initial flashing I had the ghost touch issues but after a few days they went away...my 2013 Nexus 7 does the same thing and it pisses me off cause I'm rebooting the thing every couple of days to fix it.
Having some touch issues, 33r update, i don't know how toy call them ghost touch it whatever it's very annoying when i try to pull notification bar it pulls back down, and i get more typos thought it was me typing bad =)
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
Well probably my issue is touchscreen latency, anyway that is not a catastrophic, they will fix it, so brace yourselves update is on the way [emoji6]
Previously i have no ghost touch at all.. But suddenly, i got ghost touch after the update.. I dun know why man.
Any1 suffering this issue ?
Related
Hey guys, I was wondering if anyone may know if the new 4.4 Kit Kat will fix all of the Nexus 7 2013 touch screen problems.
Maybe Asus and Google knows it fixes the issue. That's why they didn't rush to help us in the last few months.
Cross your fingers people and hope this fixes all of our issues. That would be sweet.
Oct 28 4.4 I'm thinking.
I hope that... it's been a headache, and that's the only flaw mine has, the fix here fixes it just temporally.
Can't say whether it will or won't but I can say I really doubt they have the fix already in hand and are holding it back waiting for kit kat.
They've never been shy about putting out releases to fix things and a touchscreen fix is very contained and isolated, not something that touches many areas requiring long code reviews.
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
I don't know, maybe I use the device too much? But I can definitely say ghost touchs and some multi-touch issues are there and persistent. In fact right now as I was writting this the keyboard went crazy, it's really annoying and I don't even want to start with the horrible experience I'm getting with PS Touch(which I use a lot) thanks to this problem. Sometimes I have to reboot the device when it goes crazy zooming while navigating the internet.
For you guys that your tablet is "perfect", fascinating, good for you, but that doesn't mean the problem doesn't exists anymore, you just got lucky.
I personally have no more touchscreen issues since JSS15Q, but if there is another touchscreen fix in KitKat that would be good to the few unlucky ones still having issue with theirs..
neo5468 said:
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
Click to expand...
Click to collapse
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Google will have to detect each variance and patch accordingly. Probably why it hasn't been released yet because it probably will take a larger testing period then previously mentioned. Even using the XDA fix, some versions can cause several FCs and bugs. Similar to the specific pattern freakout.
With 4.4 on the horizon, it would be best to include it in that. Google probably isn't going to create an OTA and then another one in a few weeks.
Just cross your fingers and hope for an official fix.
GPS was fixed though. I'm not sure about the kernel reboots though. I haven't used the stock kernel nor had reboots since I flashed CM Kanged.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
player911 said:
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Click to expand...
Click to collapse
Any source for that 75% number? Without a proper source it is hard to not consider that as a case of the loud minority.
If it were that serve of a problem we would hear the tech press clamoring about it by now. But nothing was said about N7 touchscreen by the tech press since JSS15Q.
I can't tell you what the real percentages are, but the touchscreen issue is definitely a much bigger problem than your standard problems.
Standard run-of-the-mill issues get a thread with maybe 20 posts. Touchscreen is producing 1000 post threads. So relative to normal problems it is a big problem, but whether that is a 5% vs 1% problem or a 75% vs 1% problem I could not tell you.
There are at least 3 huge threads on Google support forums about this problem:
Multi-touch - reports of improvement, no improvement, and some worse
Multi-touch (continued) - more reports of fixed / not fixed for JSS15R
Multi-touch (continued 2) - more reports of touchscreen issues
BTW I created the xda fix for touchscreen so I'm very familiar with the fixes Google put out and whether they have fixed the issue. JSS15R fixed it for some screens but made it much worse for others.
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
NekroWolfen said:
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Well, actually it is hardware related, but you can't tell if your hardware is one type or another without using Sfhub's process.
Well, thanks for confirming
I personally don't think that all of the touchscreen issues will be fixed with Kit Kat. I feel that Google will he focusing more on a fully operational OS, and that we'll need a dedicated fix to solve our problems.
But I surely hope that I'm wrong.
______________________________
HTC Evo 4G LTE
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Lockeskidney said:
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Click to expand...
Click to collapse
At this point, questions to me are almost meaningless to ask. We night as well wait for tomorrow. It took long enough to arrive.
It just sucks that I don't have my tablet. I went back to Radio Shack and ordered the 32gb through them, since none of their stores had that version on their shelves, and 16gb was not working out for me. At least I'll get to download it as soon as I get my new device!
______________________________
HTC Evo 4G LTE
GPS isn't solved to me.
diogobuique said:
GPS isn't solved to me.
Click to expand...
Click to collapse
That's a hardware issue, I suggest you to send it back to Google.
Kitkat gave me phantom touch issues, have none before kitkat. :-\
Sent from my SM-N900P via TapaTalk PRO
Elite Tester
This process doesn’t wipe the tablet, so your settings, apps and everything else should stay in tact whenever you get back to the system. Remember that you will have lost root at this point, but it’s easy enough to get that back.. Cool resource!
But before kitkat my GPS worked very well
So I updated to 4.4 yesterday with adb sideload. Since that I was using my Nexus 7 "heavily" and I always had "buttons stucked" on keyboard, but now it's gone and I havent experienced any other touchscreen bug.
I don't think I have had any buttons sticking since I updated as well. That was my only issue with my Nexus 7 when in was still running 4.3. It would usually have a keystroke stick several times while typing things and I haven't experienced it once while typing this entire post, which is also why it keeps going because I'm trying to keep typing to see if it'll happen, and instead I just keep making spelling mistakes.
It did not fix the touch issues that may be related to grounding. In a case or stand, both Nexus 7 devices I have still fail to see any touch on numerous occasions, even single finger touch events. Manufacturing issue I guess, but we all know how G & Asus deal with those.
Let's hope it lasts... some issues are fixed temporally.
touchscreen is definitely improved for me too.
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
bokoy said:
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
Click to expand...
Click to collapse
Never had multitouch issues, only single touch problems like quad touches innstead of one etc. (As u can see it happened again lol)
They poped up after the R update, and im waiting for CM11
I had single touch issues even after sending my tablet in for service. I had called yesterday to send it back again when I noticed the update was available for side loading.
After the update my screen is behaving!
I'm going to hold off on claiming that my issues are completely resolved but it is looking promising.
Sent from my Nexus 7 using Tapatalk 4
I was going to make a thread about this same thing my keyboard is good now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
So i am about 3 weeks into my LG G2 i went custom AOSP from the very start. never even touched stock. I had weird graphical glitches which i chalked up to the AOSP stuff. I also had weird touch screen issues. like double clicks when i was dragging my finger. I also had odd shaking. like if i would drag from one screen to the next and stop in the middle instead of the panes being static they would shake way way worse then i have even seen on a phone. after about 3 weeks it got to much. i went back to stock to see how it felt. i have the same graphics issues. and i think some of the same touch screen issues. Although i didn't stay long enough to really test, but the graphical glitches are there. I can reproduce anytime i want on AOSP or Stock.
Did i get a lemon?
I can post a video if anyone wants to see any of the symptoms.
JustusIV said:
So i am about 3 weeks into my LG G2 i went custom AOSP from the very start. never even touched stock. I had weird graphical glitches which i chalked up to the AOSP stuff. I also had weird touch screen issues. like double clicks when i was dragging my finger. I also had odd shaking. like if i would drag from one screen to the next and stop in the middle instead of the panes being static they would shake way way worse then i have even seen on a phone. after about 3 weeks it got to much. i went back to stock to see how it felt. i have the same graphics issues. and i think some of the same touch screen issues. Although i didn't stay long enough to really test, but the graphical glitches are there. I can reproduce anytime i want on AOSP or Stock.
Did i get a lemon?
I can post a video if anyone wants to see any of the symptoms.
Click to expand...
Click to collapse
What are the graphics and touch screen issues? Care to elaborate? I've had 3 g2s in about 2 weeks and have experienced the high pitched buzzing in the ear piece when making a call and the touch screen issues when the phone is used playing video or games after 45 minutes or so the touchscreen becomes erratic and the scrolling goes crazy. There's a couple videos on here showing the touchscreen issues when writing in a quick memo (looks like an EKG). Maybe a little more info on your part will give us a better idea on your problems though.
Sent from my VS980 4G using Tapatalk
Why did you wait 3 weeks before you came to the conclusion you have a lemon? And with all those issues why you even asking that stupid question?
Sent from my LG-D801 using xda app-developers app
Sounds like 4.4 issues with the graphical stuff. Its common because we don't have a proper port yet.
I suggest you ALWAYS use your phone stock for a week or else you have no idea if its software or hardware when things go wrong.
I suggest you flash back to stock and waiting it out and see for yourself.
-sent from my LG G2 using XDA Premium 4
I will see if I can make some videos to show of what I mean.
Sent from my LG-VS980
The touch screen issues are present in all G2s, it's whether or not a user "triggers" it that's the question. I've seen it in both AOSP and stock. So your touch screen is "fine." The other issues are not normal though.
Sent from my LG-G2 using Tapatalk
To conclude if anything is normal or no...you need to have your phone completely stock...What player911 said is the right thing to do.
So i swung by verizon and sure enough the demo model showed no signs of what my phone is doing...
btw i did say i went back to stock to test it and both the graphic issues and the touch screen issues have been present. I cant always reproduce the touch issues but the graphic glitches is some sore of faulty unit. I will try to get the to replace it on monday.
Koopa777 said:
The touch screen issues are present in all G2s, it's whether or not a user "triggers" it that's the question. I've seen it in both AOSP and stock. So your touch screen is "fine." The other issues are not normal though.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
This is not true! I have the Verizon variant and I have no issues with the tough screen at all...ever?? In fact, for whatever reason (maybe because Verizon is more closed/careful/anal/controlling) I read of more issues with other carriers than I do with Verizon. So either it's Verizon, or maybe Verizon's version got a better batch of hardware while the others got a bad batch??? :crying:
Return it and get a new one. If you were at the store, I would have already done this. Its under warranty regardless.
Touchscreen is very responsive on mine. Maybe too sensitive. Sometimes I don't even feel my fingers touching the screen.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Edit: here you have the prove (bad scrolling and multitouch problem) i think i am going to RMA
Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Edit:
Suddenly the issue has been gone for a week, no problems at all since 15 October... I am so confused
Edit 2:
The sensibility issue is back on 24/10/2014 without changing anything
QuBeX said:
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Click to expand...
Click to collapse
Yes, I also still have troubles with it. I especially notice it when typing.
gr4nchio said:
Yes, I also still have troubles with it. I especially notice it when typing.
Click to expand...
Click to collapse
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
gr4nchio said:
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
Click to expand...
Click to collapse
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
QuBeX said:
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
Click to expand...
Click to collapse
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Touch screen is still going to be an issue. You can check the original bug which was reported here (still says in progress) https://jira.cyanogenmod.org/browse/BACON-55
gr4nchio said:
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Click to expand...
Click to collapse
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
QuBeX said:
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Click to expand...
Click to collapse
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
jlevy73 said:
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
Click to expand...
Click to collapse
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
Not sure since I just requested a new phone.
dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
They will, at least, replace your phone. I did and am waiting for my new one to arrive. If multitouch issues remain (and most likely will) i'll ask for a refund. I don't really care if the phone is "cheap for specs", this flaw is unacceptable.
My S3 is much worse hardware wise and feels SO much better while typing or anything else touch related. I did have to open a ticket and later show up a few videos of multitouch malfunctioning to oneplus. They decided it was a malfunctioning unit and i was eligible for a replacement. They never mentioned bacon 55 or a "known issue" common to every phone that would be solved at some point later on.
It's taking forever too. It's been over a month and it's mainly their fault because they take so long to reply to every single email. They did ask my VAT number before hand so they could send an invoice with it to my customs that would facilitate the returning process. Despite that, my phone got stuck on my country's customs precisely because they sent them an invoice without it and was up to me to ask it to oneplus. I waited about a week for what seems an poorly excel made document (compared to my country's invoices this is a joke of a document ). I sent it to the courier who picked up and they forwarded it to customs. Stuff went smooth from that point on. Oh yea, i'm from Portugal and even though my phone was sent to me from the UK the first time, to return a phone, you're going to send it to Hong Kong. All free of charge. I did have to print loads of pre made documents (about 10 pages?), because apparently sending anything with a battery is a big deal safety wise.
Even though they are, like someone said, polite, they do take a good while to reply to anything and aren't very keen to answer to anything that falls a bit out of their "process". For example, I've asked them several times if they would send me a new phone before or after a return mine. They never really cared enough to answer. Their English also seems translated by google sometimes. Several different people may take care of the same case. I've had about 5 or 6 different names reply to me and they all just use their first name like "Wilona". It made me stop to think i was sending my already paid phone to some place across the world because this randomly named guy told me so by email - in any other different scenario this would scream of a scam. But I've placed my RMA through an official ticket on their website, they actually made a new order request from their store on their website, they use very well known couriers with tracking numbers and it's the only way i'm ever getting a chance of having a properly working phone.
I did warn them before sending my "faulty" unit back they can expect me asking for a full refund if this new one isn't working any better.
I have been on liquidsmooth rom since I got the phone, no problems with touchscreen whatsoever, Installed new 38 CMS today and started to experience that problem. Also, cms lags compare to AOSP, this is pretty weird
QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
Flashing ColorOS for me gave a much better touchscreen experience, things worked flawlessly in all apps for me(Amazon is my biggest issue, any scrolling over a description/review would select it and move you to that section to read it, does not happen at all in ColorOS), so im thinking its software
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
What is the touchscreen issue that people are referring to? Mine seems perfect? The only issue is the slight yellow at the bottom but you only notice it if you actually go looking for it.
jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Not really. It's bothersome.
Sent from my OnePlus One using Tapatalk
Mines slightly yellow at the bottom, appears to be getting a bit better though, unless thats just my eyes playing tricks on me. I haven't noticed touchscreen issues except i can't seem to press the spacebar properly
My touchscreen seems to be very picky as to where I touch. Sometimes it takes a few attempts. Since 38 I have had random reboots. I m stock rooted without anything else flashed.
jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If you can say that you're a lucky one. It can render your phone completely unusable. Imagine your phone randomly assuming touches when you're not even touching it, non stop (stuff opening, key input, etc). You can't do anything else while it happens and the only way to stop is by rebooting. 5 to 10 times a day, everyday. Also, just about anything multitouch like simply zooming on a webpage has a 50% chance of working or send your phone spazing on a zooming in/out frenzy. So I'd say it isn't exaggerating, you just aren't experiencing the worse of it.
Got my Z1 two days ago and this annoys me like hell:
Sometimes I have to rather touch the display with more pressure so the digitizer reacts to my input.
I installed a touch test app and when putting my finger slowly and gentle at the display I get no app output.
If I intensify the touch it reacts. Cuz of this sometimes when going through the UI I have to press an UI element two times or a bit harder.
This is the first time that a device I got has such a problem. The problem is there with tempered glass and with a hybrid display protect layer (plastic glass hybrid).
Never using any device without display protection.
Faulty hardware? Please no. I ordered at efox shop which really is a pain in the **s when it comes to warranty and RMA.
My Mi4 (RIP) even reacted when just hovering above the display, and had a very accurate touch input system.
So this is why this annoys me like hell. The ZUK touch input is not precise and the sensitivity sucks.
Did any of you experience something like that with your Z1?
Update:
I was very pissed first, installed a test tool for the touch.
It could be seen totally clear that the touch was not very precise. I could touch the screen very very softly, then giving more pressure and nothing happened. Pressing more harder the tocu test app gave output.
I thought; well I'll have to send it back because the digitizer is faulty.
I flashed unrooted stock cm-12.1-YOG4PAS3OH-ham-signed.zip from the Cyaonogen OS website then after making a full wipe (keeping my SD-memory untouched).
Same problem again, the touch sucked, even lag was less and the fresh flash got me a more fluid experience. I was wondering though; trebuchet and music FX FC'd various times.
I guess cOS YOG4PAS3OH is just buggy...
I flashed cm-12.1-20151211-NIGHTLY-ham.zip from the CM site then, because I did not want to give up.
Clean install of the newest nightly and voilà... touch is working very precisely, even the softest touch input gives output with the touch test app.
Sadly no audio at all is working for me with cm-12.1-20151211-NIGHTLY-ham.zip. No output, no recording... nothing.
But the CM build is more fluid than the cOS build, it feels really smooth.
So now I am stuck with a good device and two buggy ROMs which I both do or can not want to use as daily driver.
Aaaargh!
Reboot the device. The audio issue most likely originates from twrp.
MrColdbird said:
Reboot the device. The audio issue most likely originates from twrp.
Click to expand...
Click to collapse
Sir, you were right.
So now I will test this build. Hope there will be a stable soon.
I was not into CM for quite some time now. Heard stuff about battery drain on the ZUK Z1.
I'm not happy with the touch. Sometimes it's oversensitive, most of the time unresponsive first time and occasionally works fine. I'd love a stock Marshmallow rom. This is way too buggy. I've rooted every Nexus and others like the note 1.People laughed at the size of it May give this away at Christmas and stick to my fast, reliable nexus 5 while I save for a 5x.I did want an Asus zenphone 2 but they were sold out ( Bought this for 1 storage 2 battery 3price. Buy cheap buy twice they say.....
With CM (not COS) it is better.
Did notice the touch screen issues but not the screen issues people report yet.
Yes Dude Same Problem With Me But I Have Got A Solution Just now You Have To Increase the Pointer Speed To A 80% And You Can Feel That Smoothness That You Wanted And One More Thing Disable Swift Key Like Apps Too