I've been fighting this on and off since the MF9 update. Originally I thought I just had bad reception where I was at the time but now, even with wifi and 4g network I still get this.
Basically I'll be typing...could be Galaxy keyboard OR SWYPE and suddenly the keyboard will stop responding. Even if I hit the "home" button to get out the app (usually I notice this in web browser but it doesn't appear to be app-related) the keyboard overlay will persist and can't be killed. I can make it go away by pulling down the notification bar where the "select input method" icon is still displaying and select whichever input method wasn't in use when it hung, but I still won't be able to type anything until the keyboard catches up....sometimes that takes several minutes, sometimes I have to reboot the phone. I noticed that some words or phrases are more likely to cause this lockup than others. Ironically, "galaxy s4" will do it almost every time.
The only way I've found to prevent this from happening is to turn off all predictive features on the keyboard including predictive text and swiftkey. I've tried updating my language and pretty much everything else but nothing works permanently. I can get it to work temporarily by clearing data on the keyboard service too, but it always comes back when it's least convenient (like when I'm trying to enter an address into GPS and in a hurry). This started after the MF9 update. At one point I even did an ODIN wipe and reinstalled from a stock image....still does it.
anyone else getting this?
Yeah, I've been noticing this happening to me lately too. I use the Swype keyboard though. It's quite frustrating.
I've gotten used to the Google keyboard and haven't switched to something else since. Yes, it's not perfect, but it suits my needs.
Related
I noticed this today (although it may have happened after installing some peice of software over the last couple of days. When I click on the keyboard it shows right away... but if I click on the arrow next to the keyboard to choose my input method it takes about 10 seconds before that little window pops up. I don't remember it being like this from a fresh OS with nothing installed.
I actually notice this after installing "nullkb.ARM4.CAB" which is a program that adds itself to that list of input methods. You can then choose it and the auto keyboard won't pop up all the time when you don't want to enter data. Works great.. but I'd sometimes like to be able to use that keyboard. I'd like to be able to open the options, change it from nullkb to keyboard, type, then reverse it back to nullkb.
Anyways, I uninstalled and soft reset the phone and the problem still persists. I reinstalled and it's still there as well. Any ideas? Anyone else have this problem?
Yep, it's a known (and common) problem. From what I can tell from reading around the 'net is that as soon as the SIP menu is modified in any sort of way, the menu becomes slow to display. Mine takes up to 17-20 secs to display. I did a hard reset last week and the menu became quick to respond. However, when I restored from my backup, the menu became slow again. I didn't want to re-configure and re-install again so I kept my restore.
Hi,
Ive searched but cant find an answer or that it even happens to anyone else.
Recently reformatted my phone, running out of RAM to clean it up.
It now runs great except now after about 5-10 sms's being received when i go to reply, no keyboard appears. The symbol is below but normally when you tap to type, nothing happens.
This is for Swype, Touchpal and even the standard keyboard. This applies for sms's or anything that requires to type.
Only resolution for me at the moment is having to soft reset all the time then its good for a few more sms's.
Only occured since i reloaded everything after a hard reset but the phone runs great, only installed what i had previously so no new software.
Any ideas?
Guess im alone on this one. Well if anyone else ever has the same prob, i discovered it was Swype v3.9. Never had problems before but now ive hard reset the phone to clean things up, fresh install things, it is causing problems.
According to other forums, v3.9 is very buggy so reverted back to v2.0 from the Omnia and its working great.
I have same problem.
I have installed: Resco Keyboard, Swype, and TouchPal. I usually use Resco; I can have sessions since a soft boot using ONLY Resco, then eventually the keyboard will refuse to appear after tapping the icon. Thus, the problem was not triggered by either of the other two keyboard apps.
Like you, my only remedy has been to soft boot. This is usually good for a few days before the keyboard is forever hidden.
(Still no permanent solution ...)
I was in the AT&T store earlier today hoping I could do a side by side comparison of the Captivate and the Aria but, of course, AT&T didnt have out the Captivate yet so I just spent time with the Aria.
I loved it. Very smooth and quick with everything. Comfortable keyboard for the size that it is.
One thing I noticed before I was done experimenting with the keyboard and texting is that when I was typing a message landscape, the words weren't showing up, but appeared when I turned to portrait...and then disappeared again when turned landscape.
It only happened at the end of the 15 or 20 mins I was playing with it...but is this a problem others are having with the phone or was the in-store phone just being defective?
That is a problem that i also use to experience, if i text in landscape mode at a fast pace it caused the app to force close. When it auto restarted i couldn't see the text i was typing in landscape mode but when switched to portrait mode the text would appear. I have since stopped texting in landscape mode since texting in portrait mode is just as fast as long as you hit the first letter of the word correctly.
I have not had the issue since flashing the liberated B003 rom though. Also I do not know if it was something running in the background causing this to crash before i flashed but for me the problem no longer exist.
But thats just one of the few problems you will discover with this phone
Thundervore said:
That is a problem that i also use to experience, if i text in landscape mode at a fast pace it caused the app to force close. When it auto restarted i couldn't see the text i was typing in landscape mode but when switched to portrait mode the text would appear. I have since stopped texting in landscape mode since texting in portrait mode is just as fast as long as you hit the first letter of the word correctly.
I have not had the issue since flashing the liberated B003 rom though. Also I do not know if it was something running in the background causing this to crash before i flashed but for me the problem no longer exist.
But thats just one of the few problems you will discover with this phone
Click to expand...
Click to collapse
Thanks! Hopefully going to pick up a Captivate as long as it performs like I hope. Otherwise I will be joining all of you here in the Aria forums!
Kind of a dead thread but I'm bringing it back to ask...
How many of you have also experienced this problem with the phone? Is it a large majority?
MendedEagle said:
Kind of a dead thread but I'm bringing it back to ask...
How many of you have also experienced this problem with the phone? Is it a large majority?
Click to expand...
Click to collapse
i've never noticed this issue
ryan92084 said:
i've never noticed this issue
Click to expand...
Click to collapse
Thank you. Hope some more people respond so that I can see how many people experience this problem so I can try to decide between this and the captivate
I spoke too soon, the issue is happening again, seems to happen after typing long texts.
I get the error "the application Touch Input (process com.htc.android.htcime) has stopped unexpectedly. Please try again." [Force close]
do you use the stock keyboard as opposed to swype, swiftkey, or the droidx?
stock keyboard.
That might be the silence then. You might want to see if the problem persists with a different keyboard. For landscape I suggest the droidx multitouch.
Sent from my HTC Liberty using XDA App
I too have the same issue - many times. Stock ROM, non rooted.
I'm going to mosey on over here for the Nexus forum to vouch this issue for my sister. She just got the Aria about 2 weeks ago and her keyboard freezes on her in landscape mode constantly. If she goes into Settings/Applications/Manage Applications/ and selects the keyboard then chooses 'Clear Data' it seems to bring it back up without her having to restart her phone. Another option I've found while scouring the internet has been that if you disable predictive text on the keyboard (Under Settings/Language and Keyboard/Touch Input/Text Input/Prediction) it seems to fix the issue... but you of course lose predictive text. Which, if you ask me, is a huge issue given the cramped keyboard on the Aria. I can't confirm if removing the predictive text option works yet or not, but if she lets me know, I'll be sure to let you folks know.
[edit]I should probably state that shes on Stock AT&T Rom with non-root and she plans to stay that way... unless I convince her to hand the phone to me for a few hours)[/edit]
I should also probably state that this issue does not occur using the swiftkey keyboard from the market. One could argue just using that instead, but I personally don't like swiftkey and frankly the default keyboard should work! Lol.
So far turning off predictive text has fixed it. My sister has gone all day without a freeze up. And it was occurring almost every time she texted.
Day 3 and her keyboard still hasn't froze since she turned off predictive text. I think the may be a solution. But now HTC needs to release a fix for this lol. Hopefully the aria gets a 2.2 update and this is resolved. Wishful thinking I guess.
lately my keyboard has been randomly disappearing while using it. The keyboard will just be not there at all or it will just be a big black box. It is still usable when it is the black box, but not usable while it is transparent / not there.
Has anyone else been having anything like this happening to them?
Or does anyone have any suggestions for this issue?
I tried a reboot...nothing...I will try to uninstall some of the latest apps I installed.
-BTW I am not rooted and have not done so yet...
Have not had this issue...although...
...I have had several instances where I will be typing away (feel the haptic feedback and hear the key click) only to look up and find that nothing I typed is registering in the input field. Once it does this, it continues in all applications and even after changing input types (default, dragon, or better keyboard)
The only way I can get it to work again is to reboot the phone entirely.
In an off topic rant...last night I was 10 feet from my router and my phone kept saying I was out of range, even after a reboot. Every other device could connect though..I ended up taking out my SIM card and throwing it in my HD2. My MT4G is now in time-out in the closet for a couple days while it thinks about what it did.
I have had that issue as well with the keyboard...(that is - in addition to the current issue discussed...)...
now in order to keep this thread on topic, I will PM you about your other issue...I have a suggestion for it
I'm just wondering if anyone else has this problem. So, for a long time now, my phone will randomly act funny when trying to longpress things on the keyboard when typing. It is random and does not always occur. It has happened in Swiftkey X, Swiftkey 3 Beta, Swiftkey 3, Froyo stock keyboard, ICS stock keyboard, and now Jellybean stock keyboard. I am currently running the Toasted Marshmellow rom. It started happening around the time ICS came out (in custom roms) and has continued on many, many different roms.
So it will occasionally bug out when trying to long press things and here is what happens:
-The longpress character briefly shows up but then disappears as if I stopped touching the screen, but the character is not inserted.
-It will repeat the above 3-4 times
-It will no longer register the touch on that character of the keyboard (but it will for all surrounding keys)
-After exiting the keyboard, and re-entering it, it will function normally.
This has been an ongoing problem throughout multiple roms and multiple keyboards. It is incredible frustrating because it tends to happen about one time every time I send out a text. It is so time consuming to have to exit the app and reload it.
Any help? Thanks. :good: