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:
Related
I'm running Black 2.5 as my ROM, but it's happened on all ROM's, including the Cingular stock WM5 rom. The keyboard just stops working. It comes back sometimes on it's own a few minutes later, and always after a soft reset, but what causes it?
Does this happen to anyone else, and is it a hardware issue, or a software issue?
Does happen to me sometimes. Had one this morning. Not only k/b, but the scroll wheel as well.
Keyborad not responding
Hello,
Have same problem after flashing rom.
I thought that maybe I did it wrongly but also my friend discover this issue.
From time to time external keyboard not responding and on-screen keyboard is working but DEL key is also dead.
Also other buttons like green/red phone keys not respondig.
Sometimes problem disapper automaticaly sometimes I have to reset phone.
Any solution?
Has anyone found information on this problem? I have had my 8525 for about 6 months now and this has happened to me on the original shipped ROM as well as both Black 2.5 and 3.0.1.
It happens usually during texting, and like stated previously, sometimes it comes back on its own, and sometimes it takes a soft-reset to get it working again. I am able to finish the typing using the SIP before soft-resetting.
I haven't paid attention to whether or not the scroll wheel stops working or not. I'll keep an eye out for that. Also I can't figure out what's triggering this problem. It seems very random.
I would start to think it's a hardware problem since I have seen it on 3 different ROMs, but so many of us are experiencing the same issue.
Happens on my Vario 2 sometimes. I've put it down to me using the keyboard whilst the CPU is bogged down too much, and it just doesn't 'see' the interrupts coming from the keyboard I/O controller, and then it loses its sync.
I usually just soft reset at that point, because I can't be bothered to wait and see if it comes back
I have it sometimes when using IM and PIE. Closing PIE and waiting a couple of minutes usually brings it back.
Lately I've had problems with my QWERTY keyboard not always working. It will work fine, then one time I will pull it out and stop typing and text doesn't appear. I have to reset the device in order to get it working again. Usually when it is not working, I can use the on-screen keyboard, but this is such a hassle and much slower. There have been a couple times when that wouldn't work either.
Has anyone else noticed this issue? I've been using CRCs ROM (the first ROM I installed). If it sounds like it might be a ROM issue and not a device or WM6 issue, does anyone have any ROM recommendations? I do not need a lot of features - just the basics will do as I intend to install SPB Mobile Shell and a couple other programs anyways, but I do desire something very stable.
I have the same problem occasionally... two different ways
Sometimes the program will stop taking text input. For example while typing a text mesage the keyboard will stop working, but if I hit the windows key the start menu will still appear. I have to kill the text messaging program and re launch to regain functionality. Also happens occasionally in IE.
Other times the keyboard itself will stop working, all of the buttons. In this case I have to close the phone, power the screen off for a couple seconds, power back on, and begin typing again.
It's very strange, and very unpredictable.
<edit> I have a Cingular 8525 (1.5 years old) running Schap's 4.31 WM6 </edit>
ifiweresolucky said:
I have the same problem occasionally... two different ways
Sometimes the program will stop taking text input. For example while typing a text mesage the keyboard will stop working, but if I hit the windows key the start menu will still appear. I have to kill the text messaging program and re launch to regain functionality. Also happens occasionally in IE.
Other times the keyboard itself will stop working, all of the buttons. In this case I have to close the phone, power the screen off for a couple seconds, power back on, and begin typing again.
It's very strange, and very unpredictable.
<edit> I have a Cingular 8525 (1.5 years old) running Schap's 4.31 WM6 </edit>
Click to expand...
Click to collapse
I don't send very many text messages so I'm not sure about those, but I usually notice using IE (that is the main place where I type anything) or inputting a new contact or something like that. I'm not sure about the windows key, although I think I tested a bunch of buttons and none of them worked.
Think it is a bug in the phone or a bug in the ROM? I have no idea...I've only used one ROM so far on 8525 (I tested a bunch out on the 8125 when I had one). I'm thinking about installing Binkys11 since I hear it is fast and stable. Maybe it won't be as big of a problem then.
Note: I also have a case with a magnetic strap. I thought maybe that was messing with it since I hear the magnet could do funny things to the phone...I'm not sure though....
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.
Hey people,
This is an odd one for me. I'm finding that periodically, and I'm not even sure how often, my keyboard seems to get (the only way I can describe it) sticky. So when I'm tap tap tapping through a message, I'll notice that some keys will start displaying the character that occurs when you long press the base character. So on the Google keyboard which I'm using at the moment, if I try to tap "QWERTYUIOP" for example, sometimes I may get "QW3TY7OP" because the "E" acted as if I was doing a long press, and by the time I was tapping "R" it was entering "3" before catching up. Etc.
This also seems to happen on other keyboards I have tried for long enough. I say "long enough" because it probably takes weeks from it's last restart to do this. And when it's doing it, it's not constant. It's not enough to make me throw the phone through a window. It just happens for a bit, then goes. It will happen more and more if I don't reboot the phone, but it's a very gradual process.
Other tap targets, icons and widgets, never seem to act like I'm long pressing during periods when this is happening with the keyboard. I think I had seen this on my Nexus 5 but had assumed it was they Swype keyboard as other people had been having some problems too.
Any ideas???
do you ever restart your device?
I use the SwiftKey keyboard.
As soulfly3 asked 'do you ever restart your device?'
I find that if I leave the app running for long periods of time with a lot of typing it will start to lag and/or stick as you call it. I have fixed this a few times just by closing the SwiftKey app and restarting it, but I normally go for a full restart of the device as I have no idea how many other apps have been open for too long. Plus it's generally a good idea to give your battery a rest every once in a while
I do reboot the device, but not because of the keyboard. I don't often have much cause to reboot unless I'm updating, flashing stock images, rooting, or something similar. So by that nature, the phone is rebooted at least once a month (to apply monthly security updates from Google).
once a month!? jesus.
Longest Ive gone without rebooting is 2 days. Do I need to do it? No. But Ill tell you what.... I dont get any of the issues those most report, and im certain it's because of this.
honestly, for something that takes 10seconds to do, I dont know why everyone doesnt do it. really flushes out those bugs many complain of
Soulfly3 said:
once a month!? jesus.
Longest Ive gone without rebooting is 2 days. Do I need to do it? No. But Ill tell you what.... I dont get any of the issues those most report, and im certain it's because of this.
honestly, for something that takes 10seconds to do, I dont know why everyone doesnt do it. really flushes out those bugs many complain of
Click to expand...
Click to collapse
On the other side, it's arguable that if you have a device that needs to be rebooted or refreshed every two days, it's broken.
Soulfulgrey said:
On the other side, it's arguable that if you have a device that needs to be rebooted or refreshed every two days, it's broken.
Click to expand...
Click to collapse
it doesnt "need" it, I just do it as a preventative measure.
Soulfulgrey said:
Hey people,
This is an odd one for me. I'm finding that periodically, and I'm not even sure how often, my keyboard seems to get (the only way I can describe it) sticky. So when I'm tap tap tapping through a message, I'll notice that some keys will start displaying the character that occurs when you long press the base character. So on the Google keyboard which I'm using at the moment, if I try to tap "QWERTYUIOP" for example, sometimes I may get "QW3TY7OP" because the "E" acted as if I was doing a long press, and by the time I was tapping "R" it was entering "3" before catching up. Etc.
This also seems to happen on other keyboards I have tried for long enough. I say "long enough" because it probably takes weeks from it's last restart to do this. And when it's doing it, it's not constant. It's not enough to make me throw the phone through a window. It just happens for a bit, then goes. It will happen more and more if I don't reboot the phone, but it's a very gradual process.
Other tap targets, icons and widgets, never seem to act like I'm long pressing during periods when this is happening with the keyboard. I think I had seen this on my Nexus 5 but had assumed it was they Swype keyboard as other people had been having some problems too.
Any ideas???
Click to expand...
Click to collapse
I have the same issue, I do believe it started after the 6.0.1 upgrade. Occurs regardless of reboots. It is pretty annoying.
Sent from my Nexus 6P using Tapatalk
Same issue
I've got exactly the same issue and have tried custom keyboards, ROMs and kernels to no avail!
I've seen google asking for people to try safemode but who can run their phone in safemode for a week waiting for it to happen!
Same here. I'm sad to see that there's no fix other than a reboot.
this!! it happens to me every day.. very frustrating!!
tried a couple of keyboards.. same...
i restart daily so its not the issue..
i saw in some page it can be the vibrating function... (try disabling it and see if this dissapears ) i just did but i dont know if it will happen as i just did
Hi to all from a 99% highly satisfied v20 user!
I have run into an intermittent issue with my Verizon v 20 (VS99513A).
ONLY when I initially power-up the phone, do I sometimes (often enough to be a nuisance but far from consistent) get a significant lag on the "Secure start-up" page of the keyboard appearing where I enter my passcode. There have been a small handful of times that, no matter what I did in terms of waiting or tapping, the keyboard would not appear causing me to do a power-off/restart which always cleared the issue.
Most of the time I wait until the screen flashes a brighter light before tapping ( just a few seconds) and (most of the time) the keyboard appears. It will also appear frequently on its own if you just wait long enough.
The problem is the inconsistency of the keyboard not appearing reasonably quickly so I can enter my passcode and go on with my life's journey at that point!
I have chosen NOT to use the fingerprint entry system for a number of reasons and prefer using the above system.
My one desire is to have the keyboard appear as quickly as is reasonably possible and do so consistently.
Other that that specific issue, I love this phone!
I did search for this issue and did not see anything approximating it. If I missed then please accept my humble apology for any duplication with this query.
Bootup times can vary. And with Verizon bloat I'm sure it is wildly more inconsistent. I rarely.run into this issue, but I also rarely reboot my phone. Perhaps a cache clear might help? Don't know what else to do besides factory reset but sure you don't want to do that. I just rooted my phone and haven't noticed any performance issues aside from battery life seeming worse. Not related to root though as i updated to 10j Sunday, rooted last night and hoping battery life goes back to what it was on 10d.
Just for some clarification, what do you mean by power up? Is it turning the phone off completely and restarting it or just clicking the power button ( or double tap the screen).
If its a boot up, then its usual normal to have the keyboard take a moment to pop up due to everything loading
If its the second then try using a different keyboard or factor resetting the phone
Robdudem said:
Just for some clarification, what do you mean by power up? Is it turning the phone off completely and restarting it or just clicking the power button ( or double tap the screen).
If its a boot up, then its usual normal to have the keyboard take a moment to pop up due to everything loading
If its the second then try using a different keyboard or factor resetting the phone
Click to expand...
Click to collapse
"Is it turning the phone off completely and restarting it..." Yes, that is the only time(s) it happens.
I grasp the idea of "loading" but cannot (equally) grasp the inconsistent amount of time that it takes for the keyboard to materialize. The few times where no keyboard appearing leading to a reboot deepens the mystery for me.
If the extended loading time is due (largely) to verizon bloat, is there a safe way to rid oneself of as much of it as possible?
harryzee said:
"Is it turning the phone off completely and restarting it..." Yes, that is the only time(s) it happens.
I grasp the idea of "loading" but cannot (equally) grasp the inconsistent amount of time that it takes for the keyboard to materialize. The few times where no keyboard appearing leading to a reboot deepens the mystery for me.
If the extended loading time is due (largely) to verizon bloat, is there a safe way to rid oneself of as much of it as possible?
Click to expand...
Click to collapse
Of course, you can disable the apps by going into Setting>General tab>Apps. From there you just find the Verizon apps and disable as much of them as possible. Which stops them from booting when you restart.
One thing to keep in mind when powering up the device is a few programs want to start up at the same time (like your wallpaper, getting signal from service provider, loading the apps on your screen, loading widgets, etc). Which causes the keyboard to be pushed but back in a queue. Happens to me all the time, but I only restart my phone once every week and I give it a moment for everything to be settled in.
Robdudem said:
Of course, you can disable the apps by going into Setting>General tab>Apps. From there you just find the Verizon apps and disable as much of them as possible. Which stops them from booting when you restart.
One thing to keep in mind when powering up the device is a few programs want to start up at the same time (like your wallpaper, getting signal from service provider, loading the apps on your screen, loading widgets, etc). Which causes the keyboard to be pushed but back in a queue. Happens to me all the time, but I only restart my phone once every week and I give it a moment for everything to be settled in.
Click to expand...
Click to collapse
This^^^^
Sent from my LG V20 using XDA Labs
To All,
My issue appears to have resolved itself if I restrict my tapping to the vertical blinking cursor on the left end of the entry line.
Tapping ONLY here consistently brings up the number pad.
Previously, tapping just about anywhere on the screen would bring it up.
Problem solved.
Thanks.