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
Related
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
GPS fubared?
No notification when charging usb
Hey guys i recently started having a problem with the back button.it will pick up half the time and then its unresponsive the time any ideas on what i can do?
Probably just lag. Which way did you flash dk28?
Btw, I came up with some other things.
1. Notfications are delayed (ex. Handcents icons in the top bar are sometimes delayed)
2. Keyboard delayed (its actually a bit worse than before)
Sent from my SPH-D700 using XDA App
*Keyboard/touchscreen/captivate button lag/failure to register action/press
*Streaming music skips (last.fm) while doing anything else; like browsing the web.
*Slow orientation change
*No lineout on multimedia dock yet
*None of the unicorns and rainbows flying out of the screen that were promised by the legion of unrelenting froyo fanboys littering this forum for the past month.
Sent from my SPH-D700 using Tapatalk
acer1096xxx said:
Even though its certain this isn't the official release, I thought we should condense the topics and just post the your thoughts about the good and bad features this update provides.
Ill start..dk28 isn't that awful for me like others. The only problems I've noted was samsung widgets disappearing sometimes, home screen rotation lag, and a few checkers showing up in the browser when zooming in and out.
However, on the bright side, flash is very smooth, and there are better icons
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, I guess a few of us got lucky. Just very small things such as checker boarding. I don't have homescreen lagg though, or widgets that disappear.
Sent from my SPH-D700 using XDA App
hardrock121 said:
GPS fubared?
Click to expand...
Click to collapse
GPS actually finally works for me with the update, I'm getting signal indoors in places I hadn't previously and it has yet to time out and require me to reflush the agps data or reboot the phone (used it all day today for work).
dannyzen said:
No notification when charging usb
Click to expand...
Click to collapse
Not seeing this one either, lets me know right away though the notification bar as per usual.
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
That's odd...maybe your phone is actually damaged then
Sent from my SPH-D700 using XDA App
I personally went back to 2.1, rock solid and stable.
On 2.2, Screen rotation is slow as molasses, GPS is stuck on my work location and would not work at all in updating. Browser was a bit slower compared to 2.1. Hated the scattered, non-alphabetical applications folder, wtf?!!
I enjoyed the 2.2 leak but the little niggles weren't enough to stay on it.
I did like the coloured menus, and the ability to turn off 3G when holding the power button for a few secs.
I keep getting errors when connecting to Wifi. I will look down at the phone and wifi will be off even though i never turned it off, and then the notification toggle wont do anything, and when I go into settings to enable it, it says "error" underneath the Wifi entry. Then it takes a few tries to get it connected again.
I do like where Froyo is headed, but this is absolutely no where near polished enough for final release.
Edit: Having a fully working GPS is awesome though. 2 meter accuracy = Awesome.
Does anyone else have lag when trying to adjust brightness on the notification bar?
LordLugard said:
Hated the scattered, non-alphabetical applications folder, wtf?!!
Click to expand...
Click to collapse
If you press menu > edit > menu again, there's an option for A-Z order.
Guess it doesn't matter now since you downgraded, but just thought id let you know.
Edit: lilxflip, yes. I'm getting the same problem but didn't notice that until now
Sent from my SPH-D700 using XDA App
I've noticed since 2.2 that when a caller hangs up, I get a single beep in my bluetooth earpiece confirming that the call has ended, which I like...didn't have any sound before that.
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
I must be one of the lucky few, everything works great, and not only that it fixed all the issues I had with the previous 2.1 build. I've tried out just about everything I can think of wifi, gps, 4g, pandora, etc.
edit: Should add, I did a factory reset after I installed it, wiped everything the only bit I loaded back in was contacts.
muyoso said:
Anyone else having trouble hanging up during a phone call? I hit the damn End button at least 3-4 times before it decides to hang up.
Click to expand...
Click to collapse
Give the phone a few secs after the screen comes back on then press it. Works fine; if you immediately press it.. it doesn't hangup. Seems intentional..
Umm.. aside from no GPS now which I plan to fix by reflashing di18 then 2.2... I don't find any major problems. The keyboard does have a bit of a registration flaw but not too major..
The leds do light up whenever the screen is off.
And I don't think the brightness sensor likes my room light because it enjoys changing itself a bit.
Sent from my SPH-D700 using XDA App
I'm always weary about doing wipes, so to test if this is true, mid anyone else testing out this also to see if he's right? =P
punzada said:
However I am experiencing one very odd piece of behavior, If I open the phone to show the keyboard, turn off the screen and leave it sitting ... the keyboard LED blinks constantly. I'm not sure if it's an app of mine conflicting or froyo itself but it's fairly annoying.
Click to expand...
Click to collapse
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
kenvan19 said:
I have noticed the Sammy widget thing and the slow screen rotations but I was intrigued by your bug. So I tried it. Definitely happened. I wouldn't say 'blinks constantly' though. At least not in my case. It flashed on for about 2-3 seconds every 30 or so seconds. Maybe even as long as a minute. Caught me off guard. I watched it for a bit then went back to reading this thread only to have it happen out of the corner of my eye.
Click to expand...
Click to collapse
Woah, just tried it. I had similar results. However, I opened the keyboard, let the flash disappear, then 2-3 seconds later it came back. And stayed there too, for about a minute or so!
Not really a big deal in my opinion; I honestly don't use the keyboard often due to its laginess..
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
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've had my G2 for little more than a week now, and while it doesn't happen often, every now and then the digitizer seems to spas out a little. it mostly always happens when im typing in the stock messaging app. i think it mostly always happened when using the LG Keyboard as well. but keyboard strokes would type multiple letters, and words would come out like tttthhhhhhisss, then touch selection became sporadic rendering any text input or navigation impossible. this is quickly fixed by simply locking and unlocking the screen. like i said, its quite rare, but it has happened a few times, including shortly after i got home from the store. enough to concern me a little.
it reminds me of my old Atrix 2 i bought from a friend a few months ago, the digitizer had a thin strip running from the top to the bottom that went "bad" somehow. when it was touched the digitizer would spaz out, typing and selecting things on its own (including google searching and calling people, but then not letting me hang up). obviously my issue isn't nearly as bad with my G2 but it seems like something could be wrong with my digitizer.
has anyone else experienced similar issues?
EDIT
bump, no one?
It has been happening slightly more often...happened twice today, once in messaging and once in XDA app. Also LG keyboard likes to crash every now and then when im in the stock messaging app.
Sent from my LG-D800 using xda app-developers app
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?