Related
Hello guys!
Just got my Epic a few weeks ago to replace the old Moment.
Unfortunately.. I like everything about the phone except the main reason I got it over the Evo.. the keyboard. It seems to drop keys a lot, and I know for a fact I pressed them.
For example I can open up a text and type "lalalalalalalalalalalala" and it will drop a l or a or two. It's extremely annoying, the main reason I opted for the keyboard was for good accuracy when replying to emails for work..
As anyone else experienced this issue? Is this a software glitch or is hardware related? If this is a hardware problem.. I will be trading in for the Evo since I'm still within my 30 days.... not to mention the much better support Evo has for updates.. oh and my Network Based Location doesn't work.. wth really? So no location based app can find me with the real gps off. Why couldn't it of been HTC Epic 4g..
Anyways any input on the hardware keyboard would be greatly appreciated.
Sadly, this is a issue with the Epic's keyboard.
All of the Epic's i've played with have this problem, and I think its a combination of hardware and software.
Typing very quickly will cause it to lag and skip a few letters. You have to slow down about 2seconds and it will be fine.
Yeah, I was in the IRC talking to some people and it came off that its a known issue, happens in recovery to (although not quite as bad).. must be a hardware issue.. very disappointing considering the selling point to this phone over the evo is the keyboard mainly.
Does the keyboard have a buffer setting in the kernel somewhere? Maybe a seasoned developer would know haha, my gut tells me this is a buffer issue, you type to fast the buffer will fill up, and a letter or two will drop. Seems logical..
Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought
mikeschevelle said:
Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought
Click to expand...
Click to collapse
IF I hit the A and S key at the same time it properly puts in "as"..when I slide "asdfghjkl" it misses a few characters..its not too big of an issue for me as I don't type that fast but there is definitely something :/
Out of curiosity I also tested the same thing on an Samsung Intercept..and Intercept is not effected..
Seems like my keyboard has gotten worse over time. I can't type a word without missing a letter. Really annoying.
I have the same problem with mine. I figured it's a hardware issue and not really so much an issue with lag. I can hit a key and it just won't show up period so that's not lag.
I'm glad I don't type that fast.
It does it to me whether typing fast or not. Every time I send a text I allot myself time for corrections because I know every time it misses 1-2 letters. It's pretty annoying. Not only that but i'm constantly getting unsent txt errors with this phone...never had that problem before.
Ever since ditching Swype for Ultra keyboard I haven't had this problem. I have it enabled so that its auto correct system works for the physical keyboard as well.
I've also had this problem. Very annoying especially being a fast typer. I feel like it is mostly a software issue too. It would be nice to have one of the great developers here take a look into it. This is my biggest problem with the epic.
Yeah it is particularly sad, especially considering that phones like the G1, Motorolas Devour & Cliq (*Puke, my old phone*) as well as other mid-range phones could type flawlessly. Yet one of the best phones in the world IMHO and you can't even type as fast as you'd like.
I'd also like to start a bounty for this soon, I'd be glad to donate to any developer that tracked down the issue and abolished it. (Unless its a hardware issue, in which case were just screwed.)
I am starting to get it as well. Seems to be a known issue but very annoying. If it gets any worse I am just going to get a single piece phone case and say goodbye to the keyboard forever. Sucks to say it but there is no point in using a keyboard that is inaccurate to the point that I need to go back and correct things when I know I typed it correctly the first time
Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.
Yeah I noticed I need to slow down. I come from the touch pro 2s sick keyboard.
Sent from my SPH-D700 using XDA App
Gotta say I was having the same problem... then someone here said to try ultra keyboard... and for some reason it has stopped missing the keys.. so I do believe it is more of a software problem. I am on the 24 hour trial and so far it works.
Sent from my SPH-D700 using XDA App
I personally believe this is a software buffer issue with this particular keyboard.
Every physical keyboard needs a buffer, even on your PC. I think if we could increase the buffer on our Epic's keyboard driver which is built into the kernel we could alleviate this problem.
If a actual Dev would be willing to check it out that would be awesome! Not sure if Froyo still has this problem.
I agree with the disappointment... my Moment never missed a beat texting with the keyboard or writing an email, my Epic with all of its potential drops the ball in this department currently.
I hope it can be fixed. And no the solution is NOT to type slower..
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
muyoso said:
Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.
Click to expand...
Click to collapse
no its not the problem..I did a test by pressing both "a" and "s" key at same time and it registered as "as"..if that was the problem it wouldn't have registered that
Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
I just disabled swype and did the "asdfghjkl" test and it worked flawlessly...I then re-enabled swype and it still worked fine :/ (running the dj29 froyo rom)..we may need more testing into this I guess?
Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
Sometimes I use swype whenever I need to type a short message. It's the best of both worlds. Sad if you need to disable one of the features just to get the keyboard to work properly.
EDIT: Look at the fail rate when typing ab for a solid minute on my KB:
Abababababababababaababababababababababababaabababababababababababababababababababbaababaababababababababababababababababababaabababababababababbabababbababbabababababbabaababaabbababaababababababababababababababababababbaabababababababaababababaababababaabababababababaabababababababababababaabababababababaababababaababababababababaabababababababababababababbabababababababababababababababababaababababb
This is with swype disabled.
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?
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*
hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?
rp_guy said:
hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?
Click to expand...
Click to collapse
yeah I noticed this too, it seems like the multitouch doesn't work properly. What ROM are you using? I'm on WetDream 1.2 still. I don't know why it's this way but it makes me very sad. It's very annoying. Anyone else have this?
I have this problem as well. I went on a rampage downloading a million different keyboards, but to no avail.
I have the same problem. Could it be the digitizer?
Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA
TheMan0790 said:
Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.
Yes I believe the problem is poor implementation from Motorola.
IF you use the stock keyboard (the multittouch one) this problem goes away. Just figured this out this morning.
I am using a blur based stock rom (one of nottach's) so I still have that keyboard available. I think this will be enough to keep me on stock based roms or at least roms that will have that keyboard.
Atrix_Owner said:
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.
Click to expand...
Click to collapse
That is very weird. When I was using CM7, I never faced any keyboard issues. It kills me that the Atrix's worst keyboard, IMO, was when I was using stock GB. Absolutely the worst thing ever.
Sent from my MB860 using XDA
bump for more attention.
I've always had this issue on every ROM with every keyboard I've ever used including the stock Motorola one. I just chalked it up to the multitouch not working since it doesn't seem to work correctly for anything.
Sent from my MB860 using XDA
I've only ever had this problem with the stock ICS keyboard on a CM9/ICS Rom, the 'solution' was to disable either the keyboard's or android's spelling correction. Can't say I've know exactly what's causing it on anything else, I'm afraid.
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?