Stock keyboard clearing field randomly - AT&T Samsung Galaxy Note II

Not sure if it's just my luck, but one thing I've noticed is when typing in a login field it clears randomly. Using stock keyboard and CleanRom currently. Happens in stock as well. Only thing that I can find to get around is getting my email added to the dictionary prediction field and swiping it in. Is it just me? Basically I type out s-h-a-m-p-o-o *bam, cleared*. Sometimes I get through a couple more letters, sometimes I don't. It's a bit frustrating.
Any one else or any ideas?

Related

Looking for a fix for the box you type in being cut off while texting

This happens to me very frequently and is fixed by just exiting the sms screen and opening it again. But it seems to have been happening much more often lately.
I tried searching but can't really think of the words to search for for this problem and came up with no results. so i'm sorry if this has been common.
Anyway, in case it is unfamiliar. When I go into the sms texting screen the portion that you type in on the bottom is cut off by more than half and this makes it very annoying to type. Any one know any fixes?
Thanks
Open the on-screen keyboard and close it - it will disappear.
I had the same problem a while back. I did what Genesis3 described and it would momentarily fix it, but it would show back up later. I have hard reset since then (for other reasons) and I haven't noticed the problem since.
i have done a hard reset recently and it still occurs :/ but thanks about opening the on screen keyboard, didn't know that. So there is no permanent fix?
Running a stock rom I also get that once in a while. I tap the onscreen keyboard then tap it off and it is fine. Pain in the ass though.

[Q] Random SMS glitch

The best I can describe it is when opening a text from the notification bar it brings me to the top of the SMS thread, which can be quite long sometimes and the only way around it is to back out and re-enter the thread to get to the most recent message.
I love how smooth this phone runs, I can deal when resource heavy applications freeze for a bit or have bugs. However when simple phone based applications do things like this I kind of twinge.
Any help on either what does this or how to fix it?
Is this stock? Never had that issue? Maybe try deleting some or all your txts? I know the stock app gets flaky when you have a ton of messages on your phone
sent from a phone
i get that same thing when i have 200+ messages in a thread. its somewhat annoying.
It's happened with stock and in skyraider now
Easy trick that works for new when that happens: hold menu so the keyboard pops up, bringing you to the text field at the bottom.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
I have not run into this problem since I have been using Handcent for SMS.
have this same issue, and this is with stock 2.2 from big V.
one thing i've found to get around it though is backing out of the thread and then re-entering will put you at the end normally and also if your typing and bounce between the 159 and 161 character count, not tapping back and just changing orientation a few times will set it straight again and you can continue editing the message.
Will say, i've got threads that are 2k messages long and even then its a hit or miss thing to the point where i cant get it to happen right when i'm in front of a big V tech. :/
i get that occasionaly and i get a glitch where even if i click on the sms notification it still shows it in the bar.

Swiftkey App - Intermittent problems

Hey - not sure if this is the right place to put this as I had the same issues with the Swiftkey app on my Galaxy s2. The problem I have is intermittent.
If i go into my messaging, or email app or WhatsApp - the keyboard appears as normal however when typing on it - nothing appears at all in the text field. I have to quit to homescreen 2 or 3 times and then go back into messaging and start typing for anything to appear.
Also sometimes what happens is that the keyboard will appear and will type as normal however the top line above the keyboard which contains the predictive words won;t appear - again the resolution is to quit the messaging app that i'm in and return to it. Really frustrating at times - esp when I can't type a message!
Does anyone else have this problem? I've updated to the latest swiftkey.
I'm running stock ROM however i've rooted the handset but the problem was happening before rooting too.
Any suggestions would be welcome - apart from that i'm loving the handset.

[Q] Keyboard Issues

Hey guys so im having some issues when typing text messages or when typing at all on the keyboard after recently doing something. So for example, I took a call and then ended the call and went to resume sending a text message. However, when I began typing the letters were not responding as fast as they usually do so I was making all kinds of errors. I have tried using the stock jelly bean keyboard which has the same issue and I am currently trying out swiftkey 3 and it is doing the same thing. It seems to only happen after I recently close another app or finish a task like a call. I am hoping there is some type of fix in settings or it may just be the outdated hardware however, when typing normally I can type quickly with little to no errors at all and the keyboard picks up every one of the letters I press. Any and all help is appreciated. I am also running stock jelly bean, nothing else, go the phone about two weeks ago, GSM nexus from google play. Loving it otherwise though, also loving the switch to prepaid thanks to a forum post here as well.

Freezing browser input

I am using Opera as my browser and the OS is 10.0.16.HD65AA. Often when I start typing a long post into an edit window of Opera the input frezzes. That is I am still typing on a GBord, it shows me suggestions for misspelled words, I can backspace and I see text changing in the keyboard's suggestion row, but... text in the text input field is not updating.
I have to wait around 10 seconds for it to unfreeze and update, often I have to click somewhere in the middle of the earlier writen text to force update within the same 10 seconds. I have already tried to switch off non-essential options of gboard like spell checking to no avail.
This is not new, I remember I had the same on my previous Pixel. It just stopped to happen at some point, I just don't remember what has triggered the change. Any leads maybe? Am I alone with the problem?
Does your whole phone freeze or only the browser?
I have a similar problem with Vivaldi, I normally just switch to the homescreen and back to the browser to unfreeze it immadietly.
It probably is problem with the app not the phone, you could try testing a different browser Firefox/Kiwi for example.
lilmonkehfellah said:
Does your whole phone freeze or only the browser?
I have a similar problem with Vivaldi, I normally just switch to the homescreen and back to the browser to unfreeze it immadietly.
It probably is problem with the app not the phone, you could try testing a different browser Firefox/Kiwi for example.
Click to expand...
Click to collapse
Not even a browser, I can still scroll the page. That is only input text field doesn't update.
You should test a different browser just to isolate the cause, you could also try to use a different keyboard app swiftkey for example and see if the issue persists.
lilmonkehfellah said:
You should test a different browser just to isolate the cause, you could also try to use a different keyboard app swiftkey for example and see if the issue persists.
Click to expand...
Click to collapse
This defeats both the purpose and the experiment. But I have tried it. Using any other browser is simply a nightmare obscuring the initial problem: all that panning and scrolling, random moving of input controls etc basically forces mistypes which is the way to unfreeze Opera in the first place. Honestly I don't know how people are using other browsers on Android if they have to write texts there.
Anyhow, the same problem exists in FF and Chrome. It is just not the biggest of their problems, so bothers less.
The main point here: I really had the same issue on Pixel and it has disappeared somehow, I don't remember how unfortunately. So I know it is possible to get rid of it. My question was: probably someone knows how.
Problem is solved with Android 11 FW.

Categories

Resources