Database Users

we need a bug fix update now

Don't you all agree?

not really. what bugs are you talking about?

I have had a G1, Mytouch, and now the Nexus - I see and have no bug issues with my Unit...
If you could explain what bugs (or problems) you are having ... Is this your first Andriod ???

zachthemaster said:
Don't you all agree?
Click to expand...
Click to collapse
100% disagree.
My phone is amazing. What bugs are you experiencing?

Be more specific? before or after the ota? Mine is still kicking a## after the ota!

I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........

ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
You don't have to reboot.
Just turn the screen off for 3 seconds and back on...
lol

Not everyone has this "touch screen accuracy" issue...
I haven't noticed any bugs that jump out at me. I would like them to improve the speech to text, and would love them to get the kernel with full RAM support out ASAP. I was sad this update did not have that. But, in a month when we get the next one I am confident and optimistic it will make it into it!

New RAM kernel.
Trackball/LED notification fix.
If its software the bottom row of buttons being difficult to register.
Those are all legit HW/SW issues that are unique to the N1 and need to be resolved.

New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error

Paul22000 said:
New RAM kernel - not a bug
Trackball/LED notification fix - what's the issue?
If its software the bottom row of buttons being difficult to register. - Not a bug. As I posted in the tips and tricks thread, aim for the top edge, where the screen meets the black border and you'll hit it every single time. Not many people know about this and that's why they always complain. This is just user error
Click to expand...
Click to collapse
Whether you label it as a "bug" or not its still an issue.
Half the available RAM not being used.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Those are 2 out of the box gimpings of available hardware.
And one either HW problem or design flaw. In which case can be chalked up to "it is what it is".

xManMythLegend said:
Whether you label it as a "bug" or not its still an issue.
Click to expand...
Click to collapse
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
Half the available RAM not being used.
Click to expand...
Click to collapse
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
The ability for Devs/Apps to customize the LED/Trackball is a feature removed.
Click to expand...
Click to collapse
I don't remember this ever being possible? When did they remove it?
And considering the Droid has the same panel and not the issues it is in fact a problem that the keys and "touch" area are not aligned. Thats a design flaw and nothing to do with user error.Its like asking the user to tap the Q to get a W.
Click to expand...
Click to collapse
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests

Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
How about the dots which indicate the screen you are on being off.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
The wifi is very buggy, bluetooth as well. There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not. E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...

gibosn6594 said:
How about the dots which indicate the screen you are on being off.
Click to expand...
Click to collapse
This is a bug yes. Introduced with this week's OTA.
You seem a little blinded by your love of Android. I like it too, but it is not without it's problems, just like any other software. You've convinced yourself that the the misaligned buttons are that way on purpose...really?
Click to expand...
Click to collapse
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
The wifi is very buggy, bluetooth as well.
There are also notification protocols that seems a bit buggy, sometimes they pop up, sometimes they don't, sometimes they vibrate, sometimes not.
Click to expand...
Click to collapse
Can you give specific instances of issues with these?
E-mail client inbox refresh doesn't reconcile with server with read/unread messages, even though data packets are received. To name a couple...
Click to expand...
Click to collapse
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me

Paul22000 said:
This is a bug yes. Introduced with this week's OTA.
Blinded? No. But if something is 95% good, and 5% bad, I'm going to focus on the 95%, not the 5%
And the buttons might be that way on purpose, yes.
Even if not, I've found a way to use them so they always work for me (aiming for the top) so it doesn't bother me. If I had not figured that out, then I could see how it could be frustrating.
Can you give specific instances of issues with these?
I haven't had issues with the email refreshing at all. In fact, when I'm sitting at my PC, my phone vibrates and makes a sound for new emails. I switch tabs in Firefox to Gmail and the email hasn't even shown up yet; I have to click inbox to refresh Gmail to make the email show up. My phone's email is faster than my PC's; that's how fast it is for me
Click to expand...
Click to collapse
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.

gibosn6594 said:
As far as BT and wifi, it poorly handles the switchover. When disconnected, the attempt to reconnect does not always work, to put is simply.
The e-mail client issue is not with gmail, it is with the exchange integration on corporate accounts.
Click to expand...
Click to collapse
Ah yes, I have noticed that turning on wifi sometimes it just sits there and doesn't connect until I open up wifi settings. Definite bug.
Oh, exchange. Yeah, I have heard exchange is pretty bad on the N1 (or non-existant without the file from the dev forum?). I don't use it so I can't comment. But supposedly, there will be a Nexus One Enterprise edition with full Exchange support, and a physical keyboard So maybe this one is not aimed at people who rely on it.

Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.

Paul22000 said:
Well, the OP is asking for a bug fix update. A bug is something that is not working as intended.
For Example,
If the Android developers intended for there to be half, then it's not a bug. Having all of the available ram is more of a new feature.
I don't remember this ever being possible? When did they remove it?
It's hard to say without having a Droid and Nexus One together side by side. If they are exactly the same touch pads, and you can clearly prove that the same exact precision keypress on the Droid works 100% of the time on the Droid and not on the Nexus One, then I can agree it's a bug.
If they intended it to be so that you have to use your whole thumb (or aim for the top), then no bug. I find that if I use my entire thumb, it will always land 100% of the time no matter where I aim, so that's why I say it's hard to say it's a bug or not.
But again, this is the only one that I might agree is a bug. The other two are definitely feature requests
Click to expand...
Click to collapse
Ive had the Droid and N1 side by side which is when I realized its a design flaw or OS issue.
Both the RGB trackball and 512mb ram were both advertised as such. Including in the initial press conference. Those arent feature requests those are hardware limitations that have yet to be addressed.
The ram limitation has at least been acknowledged.
As for the LED/trackball. Its been a feature since the G1. Theres bunches of apps including the most popular messaging app that allow you to designate different colors and flash rates for LEDs for notifications.
N1 is great but before we can move forward I would like for Google to address these pretty significant things.
MT was a major feature add. But the 3g fix is still plaguing many users.
All in all N1/Android 2.1 are fantastic. Googles lack of communication frustrates too many people.
Maybe Im too used to games but good Devs are constantly in touch with users concerning bugs and issues and are pretty consistent with "update/bug fix" information and ETAs.
The fact that google is just getting phone support hiring going is pretty silly.
Im an early adaptor so I know the risks. But this really is a barely past Beta piece of hardware. I dont see the harm in other early adapters acknowledging that.
Frankly if it wasnt for users ((and haters)) *****ing and moaning non stop I dont think MT would have been put out and a 3g fix would have been put off.
The way Googles worked recently whining gets more results then sitting and waiting.

dbaboci said:
Cool thing about Android and this phone: all of the above mini-bugs can and IMO will be fixed. Something which you cannot say for most phones out there. That's why I love it - devs can do almost anything they want with it. Makes me go back to the list of smartphones behind this: If you had a problem you had to get used to it - so I think we all should give the guys working on the N1 a break - I mean we got an OTA upgrade LESS than a month after the phone went on the market which gave us multi-touch. So most of the bugs do exist but they are minor when compared to most of the mobile market and IMO Google is committed to fix them.
Click to expand...
Click to collapse
I agree.
Heres my primary issue.
The guys at google seem like a bunch of brilliant engineers but rely rounds of feedback to get things right.
There creative and quality control people are suspect IMO.
Engineers tend to be a snobbish anti-social bunch. You dont want that leaking into consumer products. The communication pitfalls of this month highly reflect that mentality. They need another layer. They seem to desire it though so thats good.

ratsoda said:
I Agree......
Even after the OTA update, the touch screen issue still exists.
the phone gets all buggy with registering touch (touching middle of screen activates haptic soft keys, at the bottom of screen), getting tired of constently rebooting...........
Click to expand...
Click to collapse
Same here,,,,,I encountered this problem once, after I had updated (never tired before update)..

Keyboard Issues...Just me?

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*

typing too fast; keystrokes not registering

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.

Nexus 7 not detecting presses accurately when pressing/typing too fast?

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).

Touchscreen issues solved after 05Q update

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?