Related
OK, so apparently the OTA update is going to fix issues with the fingerprint reader - except I didn't have any issues - until the 4.1.57 update was installed - now it takes 3-9 swipes vs. 1-3 before the update. Anyone else seeing this ?
Second, only found in the last hour, certain key combinations in Swiftkey cause it to crash now - was 100% stable before the update.
Phone had been rooted with ARoot - and yes I stupidly accepted the update without thinking about it - but both of the above aren't really affected by root, su, etc. As Swiftkeys came via the Amazon Marketplace which appears to still be working fine.
Anyone else noticed any other breakages. Deciding whether to flash back now and hold off update.
Not sure I needed another hobby - but I do love this phone, and Android in general (first Android device - should not have held off so long).
This update is not what i have expected. I have 2 problems:
1. The screen is now slightly less sensitive.
2. GPS takes longer to lock satellite.
Im not sure if its a mental thing but my screen and the default keyboard seems less responsive
Sent from my Atrix using XDA App
I don't see any changes in screen responsiveness on my device after update.
Sent from my MB860 using XDA App
After update I redid the fingerprint lock. When I do mine I hold the phone in a natural position then swipe my finger as well in a natural way I never go straight down with my finger perfectly parallel to the reader try that and see if it helps I never have to swipe it more that once. Swiftkey crashed on me before update so I stopped using it. Also you can flash back to stock then run the script in the revs thread in order to keep your root
Sent from my MB860 using XDA Premium App
The screen seems overly sensitive for me now
Sent from my MB860 using XDA App
I have been having issues with the screen turning in when I receive a phone call or press the power button, after the update the issue got worth, the only way to get my phone functional again is to remove and reinstall the battery. I called Att they claimed ut could be a charger issue!!!
Sent from my MB860 using XDA App
My opinion of the update is it was an attempt to quickly patch the "root exploits". I was part of the beta update release Motorola had and myself along with many others tried feverishly to warn Motorola of all the issues we were having but they successfully ignored us and pushed the update out to the public. The ONLY consistent "effect" the update had was it disabled root, from what I had read over in the Moto forums.
I've been having a helluvatime bluetooth pairing after the update. I don't remember having these issues the first time around, but pairing my in-car stereo (Pioneer AVIC F700BT) and 2 bluetooth mice for Webtop (Lapdock) has been a pain in the arse, especially the mice that do not require PINs.
MAJOR touch screen issues since the update
Since the update, I am having major touch screen issues. If I set the phone down (i.e. on the table, desk, couch, bed), the touch screen does not work (especially scrolling or swiping). Sometimes it tries to work, but is so erratic it is unusable. Try it for yourself. If I hold the phone in my hand, the touch screen works normally, but if I set the phone down on any surface (other than my body), the touch screen will not work (can't scroll or swipe). This used to work fine before the update and I often used the phone with one finger while it was sitting on my desk or table. Now I cannot do that. Unfortunately, we have the same behavior on all three of our Atrix phones (mine, wife's, and son's) -- all three phones have been updated.
I cannot believe more people are not complaining about this issue.
JLHumbert said:
Since the update, I am having major touch screen issues. If I set the phone down (i.e. on the table, desk, couch, bed), the touch screen does not work (especially scrolling or swiping). Sometimes it tries to work, but is so erratic it is unusable. Try it for yourself...
Click to expand...
Click to collapse
I have the newest update as well, although with root, I still get perfect touchscreen functionality. Granted, to get root, I had to downgrade using the SBF file on the forums, and upgrade again, but that shouldn't matter. Maybe your Atricies (multiple Atrix?) came from a faulty batch or something.
JLHumbert said:
Since the update, I am having major touch screen issues. If I set the phone down (i.e. on the table, desk, couch, bed), the touch screen does not work (especially scrolling or swiping). Sometimes it tries to work, but is so erratic it is unusable. Try it for yourself. If I hold the phone in my hand, the touch screen works normally, but if I set the phone down on any surface (other than my body), the touch screen will not work (can't scroll or swipe). This used to work fine before the update and I often used the phone with one finger while it was sitting on my desk or table. Now I cannot do that. Unfortunately, we have the same behavior on all three of our Atrix phones (mine, wife's, and son's) -- all three phones have been updated.
I cannot believe more people are not complaining about this issue.
Click to expand...
Click to collapse
I have my phone on my desk for 8 hours a day, brah. No problems here whatsoever. My buddy at work is reading this over my shoulder and swiping the heck out of his Atrix with no problems either.
I have an AT&T and he has a Bell. Rooted another friend's Bell Atrix and confirmed no issues either because I did a ton of mods with it on a wood desk, glass coffee table, etc.
JLHumbert said:
Since the update, I am having major touch screen issues. If I set the phone down (i.e. on the table, desk, couch, bed), the touch screen does not work (especially scrolling or swiping). Sometimes it tries to work, but is so erratic it is unusable. Try it for yourself. If I hold the phone in my hand, the touch screen works normally, but if I set the phone down on any surface (other than my body), the touch screen will not work (can't scroll or swipe)....
Click to expand...
Click to collapse
Maybe I do have defective phones (bought on launch day). I installed GB about a week ago and still have the same issue.
Sent from my MB860 using Tapatalk
bongd said:
I have my phone on my desk for 8 hours a day, brah. No problems here whatsoever. My buddy at work is reading this over my shoulder and swiping the heck out of his Atrix with no problems either.
I have an AT&T and he has a Bell. Rooted another friend's Bell Atrix and confirmed no issues either because I did a ton of mods with it on a wood desk, glass coffee table, etc.
Click to expand...
Click to collapse
Can we PLEASE stop with the term "brah"?
IMHO It's way too "4Chan" and "distant" for the XDA "community".
I know the "Atrix" part of XDA is a different animal, but we are (supposed to be) family here...
Sent from my MB860 using XDA Premium App
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Mine always put full stops outta nowhere its.like.its gone nuts or something..
Sent from my R800i using XDA Premium App
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Frogybloop said:
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Click to expand...
Click to collapse
already done that
I too have had this problem twice now.
The first fix was to install Gingerbread Keyboard and it seemed to fix.
Then i had the same problem again (If i pressed "p" it would also press "t" and pressing "delete" would also press "c") and fixed it by cleaning the screen with a wet wipe.
The problem for me when it happens is basically when you press the right hand side of the screen in landscape mode, it also think you are pressing the middle of the screen at the same time.
Its only happened twice so im not all that bothered.
Try cleaning the screen with wet wipe and see if it fixes.
I've been using swype...and as cool and innovative as it is...I'm always having to double our triple check my text msgs and posts...lately I've been having to correct my corrections..its a bit ridiculous so I'm trying to get into the habit if reading what I type every few words..
Sent from my R800x using XDA App
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
OK. I've just cleaned the screen with a wet wipe. I'm going to post this message and leave it if it makes any incorrect entries.
Seems to have worked. I will now try landscape orientation.
OK, so portrait seems to have worked well enough. I'm trying out the landscape input now. Seems to be working. I was kinda worried about this problem, but cleaning the screen seems to have sorted it out.
Also, I have installed swype, but I do not really like it. Its awkward. I used to love it on my WinMo 6.1 phone (Omnia) however, I do not feel that i should be restricted to what keyboard I can use because of the phone not responding to input properly.
Back to portrait, OK. Seems to have worked. Nope, its doing it again now. Dunno why?
Stress
Sent from my R800i using XDA App
I have a question.
Is this problem consistent like it happens every single time or does it come and go?
I personally use swype and I love it. I have not had this problem yet.
It's not a software problem, it is hardware.
When mine has had the problem, it does it on stock keyboard, chinese keyboard and gingerbread keyboard.
Basically, for me, when i touch the furthermost right hand side of the screen in landscape mode, it also registers as touching in the middle of the screen too.
Well it only started happening in the past few days. I'm gonna reflash back to 2.3.3 stock and see does that fix the issues. If not what's everyone's suggestions?
Sent from my R800i using XDA App
RacecarBMW said:
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
Click to expand...
Click to collapse
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
So i'm not the only one who is having this problem?
dsswoosh said:
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
Click to expand...
Click to collapse
Well that was just my theory to the OP. The multitouch problem does exist but I thought the problems with the OP's keyboard was related to this. Turns out its not.
I flashed CM7 and haven't experienced this problem yet, but I'm sure I will at some stage... *sigh*
Hi everyone,
I recently bought the Nexus 7, and honestly, for $200 I couldn't be happier. However, there is one minor issue with the Nexus 7. Randomly, touches will stop registering, and sometimes things like the power button will cease to function as well. After a while, everything will start working again as if nothing had happened earlier. However, recently, I've been seeing a force close in random apps (sometimes launcher, sometimes settings) as soon as it starts working again. Although I am rooted right now, I've experienced the same issues on a purely stock OS as well. Is anyone else experiencing the same issues? Can anyone offer any advice?
Thanks so much.
mohitrocks said:
Hi everyone,
I recently bought the Nexus 7, and honestly, for $200 I couldn't be happier. However, there is one minor issue with the Nexus 7. Randomly, touches will stop registering, and sometimes things like the power button will cease to function as well. After a while, everything will start working again as if nothing had happened earlier. However, recently, I've been seeing a force close in random apps (sometimes launcher, sometimes settings) as soon as it starts working again. Although I am rooted right now, I've experienced the same issues on a purely stock OS as well. Is anyone else experiencing the same issues? Can anyone offer any advice?
Thanks so much.
Click to expand...
Click to collapse
i am in the same boat. i am NOT rooted (yet) and i am wondering if this might be a warranty issue. the screen just stops responding all of a sudden and takes multiply presses to make it move. it comes back but keeps missing touches. a restart certainly fixes that but it will happen again.
Same issue here with random unresponsiveness calling both Google and Gamestop to see what option is best for me.
Sent from my Nexus 7 using xda premium
Same here. A GPlay rep said a factory reset should correct it.
Havent done it yet
Having the same issue. A hard reboot fixes it temporarily but it happens again after a few hours.
Saw a YouTube video on this a couple of days ago. There are a ton of them there now. Here's just an example: http://www.youtube.com/watch?v=1BOTU75DBUA. Some other guy had done more elaborate testing, but can't find that one right now. It seems like a widespread problem. Do you notice this happens when the unit gets hot perhaps? Just curious... The guy in the other video said that it'd go away each time by simply turning off the screen and turning it back on... but that's not normal obviously.
Sent from my SCH-I535 using xda app-developers app
Few other threads on here regarding this I suggest you follow.
cliffgardner said:
Having the same issue. A hard reboot fixes it temporarily but it happens again after a few hours.
Click to expand...
Click to collapse
Just turning off the screen and waking it back up usually "fixes" it for me...its happened about 3 times already...
I get it sometimes but it feels more like it's lag related then the screen.
Grims said:
Few other threads on here regarding this I suggest you follow.
Click to expand...
Click to collapse
2 different issues
Sent from my Nexus 7 using xda premium
.. No same issue. I'd search for you but I don't care to on a mobile device.
Sent from my Nexus 7 using xda app-developers app
The issue(s) that I'm experiencing is random touch screen unresponsiveness/ lagg. So I repeat this is not about dead spots or multi touch issues.
Feel free to link other threads with similar issues to this, I've searched but only find dead spots, multi touch issue, screen crackling and dead screens.
Sent from my Nexus 7 using xda premium
I think that the touch srceen firmware was broken, just wait the OTA next time, and ASUS will fix it.
Sent from my MI-ONE Plus using xda premium
I think the two issues being described here are the same issue, just being described in different words
Sent from my Xoom using Tapatalk 2
Same Screen Issue
The screen on my Nexus 7 is randomly becoming unresponsive and I have to restart the tablet. It is usually happening after using apps that are video memory intensive (Google Earth, Google+). I hope Google or Asus will fix this issue because I love the tablet and I would hate to send it back.
I have the same issue. Usually it happens when a resource hog is running in the background. It is annoying but I can deal if its infrequent.
Sent from one of my devices, you nosey bastards.
I think it may be hardware related. My first N7 had this issue and I exchanged it (albeit for other reasons). My new unit has had zero problems, even when running the same apps. Draw something and chrome were the biggest culprits before.
+1. When it becomes unresponsive, I briefly press the power button to shut the screen off, then turn the screen back on and for me that solves it 90% of the time. The remaining 10% of the time, well, it's just frozen so I long-press the power button to reboot the tablet.
mohitrocks said:
Hi everyone,
I recently bought the Nexus 7, and honestly, for $200 I couldn't be happier. However, there is one minor issue with the Nexus 7. Randomly, touches will stop registering, and sometimes things like the power button will cease to function as well. After a while, everything will start working again as if nothing had happened earlier. However, recently, I've been seeing a force close in random apps (sometimes launcher, sometimes settings) as soon as it starts working again. Although I am rooted right now, I've experienced the same issues on a purely stock OS as well. Is anyone else experiencing the same issues? Can anyone offer any advice?
Click to expand...
Click to collapse
My son and I have experienced this too. It seems to happen most frequently with games. However, sometimes when I go to Settings->Apps, it will go to its "Happy Place" and freeze up for a while. Letting it sit will eventually cause a dialog to pop up asking if I want to close it because it is not responding. I'm thinking that it's a software issue because even when I've been playing games, the Nexus isn't very hot. Is there a way to file a bug report with Google?
I had this issue when I received my replacement 7.
After I did a system update and the issue has not returned. I received my replacement on 07-27.
I would suggest trying to do a system update and see if that may help.
Edit:
Removed the Build Number, as I can not remember which BN shipped with the replacement.
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Drapetomania said:
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Click to expand...
Click to collapse
I think I've figured out part of my problem--the touch screen is so sensitive, it will register my touch even if my finger is close enough but isn't actually touching it! Wow! Anyone know of a fix for this?
Drapetomania said:
I think I've figured out part of my problem--the touch screen is so sensitive, it will register my touch even if my finger is close enough but isn't actually touching it! Wow! Anyone know of a fix for this?
Click to expand...
Click to collapse
I have screenshots showing the dev mode options demonstrating what is going on but the forum won't let me post links.
Just tried typing college with zero issues. Elephantitus of the thumbs?
Sent from my Nexus 7
You may want to try locking the device and then unlocking it. One unconfirmed theory is that the touchscreen calibrates capacitance when it is turned on. More than once it has helped me when the display either seems to be missing touch points or if it is is too sensitive.
Sent from my Nexus 7 using xda app-developers app
Sent from my GT-I9100G using xda app-developers app
BTW, SwiftKey received an update yesterday and it is now much, much, MUCH better. No more bugs.
b34tn1k said:
Just tried typing college with zero issues. Elephantitus of the thumbs?
Sent from my Nexus 7
Click to expand...
Click to collapse
I obviously considered that. The device seems to be too sensitive, if my thumbs are something like a millimeter away from the screen so some very very short gap it'll still read it as there being finger contact. I'm rather amazed at that level of sensitivity, but that clearly is no good for typing where your fingers may hover a very small distance over the keyboard when typing going over to different keys.
Don't just type it once. Keep typing it ("coming" gets better results for me") over and over again and you'll notice that most specifically the o gets omitted because it's reading it as a swipe down towards "m"; the stock keyboard not registering keypresses if you slide off the key.(swype does obviously which is why this issue gets even worse, and swiftkey is just pure magic and corrects for this to some extent).
When I get enough posts I'll post the screen shots. It's clear by the fact that the dev console is showing a lot of the swipe line to be dark purple, which I think means that very very little pressure is being put on it, or something (maybe one of you will understand it better than I will). Additionally some of the line geometry may seem suspect and may indicate other problems, I'm not sure.
eager27 said:
BTW, SwiftKey received an update yesterday and it is now much, much, MUCH better. No more bugs.
Click to expand...
Click to collapse
if it has corrected the bugs for stuff like facebook where I can't submit responses and the weird backspace bug I was getting then I'm definitely going back to that. It's not perfect but it does the job better than the other two keyboards I've tried due to this odd issue.
IS there a way to turn sensitivity down? I want to see if that helps. This tablet is, in theory, very very nice for the price, but due to all the odd issues...
I may end up RMAing it as I get the touchscreen connection bug anyway, but I'm waiting a few months for that because I don't want to risk getting a tablet with worse issues; this one doesn't have any left-side glass issues for example.
I was going to create the same thread.. same issue here. I KNOW for sure my typing is accurate. Unless I type slow, there are letters not getting displayed. Kind of annoying. Wish I had a bluetooth keyboard to try out.
I have similar issues.
I am using a favorite, Thumb keyboard.
Rob
Rob has sent this from his Nexus 7 using Tapatalk 2
Drapetomania said:
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Click to expand...
Click to collapse
Totally understand what you're talking about.
Tying in portrait mode using the standard keyboard was driving me absolutely bonkers.
I turned off typing sounds, and it seems to have made the situation slightly more bearable. Typing "college" is fine, still struggling with "coming". Space key sometimes doesn't register between words.
Yep, landed on this thread cause I was also searching if others had this problem. I'm on CM10, which I think has the same keyboard as stock?
I've been using Swype for a while on my phone, and it used to behave like this, but Swype is for swiping. The latest version (regressed version numbers back to 1.xx) fixes this, but screws up other things (which are OT for this thread, but check the Swype forums for many complaints).
I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?
Nothing's changed for me :c
Sent via Telnet
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!
I m also facing same issue
Any solutions to resolve this issue?
Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk
I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.
anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch
Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app
Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/
Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..
Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.
I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?