Hi all, been lurking for a while but thought I would finally post up.
Having an issue with my Nexus S on stock ROM v2.3.3. It isn't the same issues with the keyboard disappearing etc but it is an issue with the keyboard not inputting text when I type.
If I am typing a SMS reply to someone on my phone and I pause for a few seconds (to talk to someone for example) then I try to continue typing, the keyboard acts like its typing but does not actually type anything else into the message. The only fix I have managed to discover is exit the SMS so that a draft gets saved then once I go back into the message it works again.
Don't know if that is a clear enough description but if anyone else has any suggestions or even a fix for it then it would be greatly appreciated
Thanks
Yeah I have that too sometimes. What also happens to me about every week is, that the smiley sections' and the (particularly important for me since I'm from Austria and using the German keyboard ü-ö-ä) special buttons and symbols' pop up extension (hard to describe, but I mean the thing that pops up when you put your finger on the expandable tile for like 2 second and which let's you select the unusual symbols from a list) simply will not pop up. So it would make it impossible for me to choose from the pre-created smileys etc.
I have found out that changing your input method to another keyboard (I use SwiftKey in these cases) and then changing it back Android keyboard make the problems disappear. But they seem to come back regularly and I haven't found out what causes them to appear...
Any help?
One works fine. The other, when I type in the destination I can type in a word then it auto adds (repeats) the word. Almost never could get my email account set up.
Identical builds of copilot live. Identical transformers, both with 3.1. Just received this 2nd one.
What possible explanation if not hardware differences???
I had the exact problem. Try using a different keyboard. The keyboard was trying to predict what I was typing and was deleting the letter before where the cursor was every time I tried to choose a predicted word. Almost any keyboard should do the trick. I used one of the alternate keyboards that came installed.
On a side note: I bought Thumb Keyboard for .99 on the Amazon App store and will never go back
I had the same problem early on. Go into the settings for your keyboard entry and turn off the auto complete and correct. It appears that copilot does not handle this correctly and rather than auto completing, it duplicates the entry. Once turned off no issues.
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
Hey guys first of all I'm going to apologize because I usually come on here only each time I get a new phone and I often forget where I found stuff before, and each time I come back the site seems to have been redesigned.
Anyway, I have a Pixel and I have Verizon Unlimited data. I came on here and found the workaround to root and slipstream some package in, and boom I can use my phone as a hotspot. Good to go.
But I notice that whenever the hotspot is turned on, the phone acts really weird. I notice it more in some apps than others, but the one that's affected most is WhatsApp. When I type, the phone misinterprets my input and types stuff that I didn't type. I don't use swype, but blue lines will appear on the keyboard, characters get entered into the text box, etc. Voice recognition is not affected the same way.
It's most apparent when there is an onscreen keyboard because that's usually the most precise stuff I do with the touchscreen. But sometimes it will launch another app instead of the one I clicked on, etc. It's always a fidelity thing; it never does something completely autonomously or interprets a touch as being on the other side of the screen. It basically feels like I'm drunk! But I can always make it go away by turning off the hotspot.
Any suggestions on what to do? Is there a new method that's cleaner and leaves less side effects? I rooted the phone about 4 months ago.
Thanks!
Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.
I just added videos of the issue to the OP.
That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.
I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.