I'm running wnc's lollipop 5.0.2 stock rom rooted with some basic xposed modules. My problem is that every so often when I go to an app to input text, the keyboard doesn't pop up, also, if I press the text box to enter text, the keyboard will not come up. This is usually fixed with a reboot but it is very frustrating to have to reboot almost every other day. This happens with Smartkeyboard Pro and the stock Sense Input. Any ideas?
I have had a similar experience with my keyboard and touch input freezing on 5.0.1. But I found that turning the screen off and then on using the power button usually puts things back to normal.
Thanks for the reply, I'll give that a try. Hope this issue is resolved soon.
Related
After installing VEGAn gingerbread on my brand new gTablet, when I press my gTablet home button I get the clock app, not the home screen. It also boots into the clock app, not the lock screen. Help!
I have seen other mentions of this in the xda forums, but no solution. Anyone have any help?
Thanks!
New information. I reset everything and started over. This time I installed another clock before rebooting the first time. Now, after I reboot and swipe the lock screen open, I am asked how to complete that action, using Clock or Alarm Clock Plus.
If I use the back arrow to get out of that, the Home button takes me to the Home screen for that session. If I reboot, then I get the "how to complete this, Clock/Alarm Clock Plus" option again the first time.
So, it seems that it wants to launch a clock. How do I stop it from wanting to launch the clock then?
Thank you!
This seems to be an existing problem, which has been discussed here, but I don't see a solution.
It is mentioned a bunch of times in this long thread for the release of VEGAn b5.1.1:
http://forum.xda-developers.com/archive/index.php/t-884103.html
(search for "clock " (with a space after it))
In that thread, gojimi thought it might be related to a specific run of the devices, but there didn't seem to be a resolution.
Here are a couple other posts which mention this problem, but not a solution:
http://forum.xda-developers.com/archive/index.php/t-1018754.html
http://forum.xda-developers.com/archive/index.php/t-963413.html
Others have reported it for Cyanogen. Any ideas?
Thanks in advance!
I am also experiencing this problem on Bottle of Smoke and also had it on Vega-Tab gingerbread. Even pressing soft home button goes to clock.
Also I am pretty sure that in both cases it was fine after the loading the Rom and only started after rebooting for the first or second time.
Has anybody found a solution to this rather annoying problem?
Update :-
Also on Flashback v 4.0 through to current... Definitely only starts after 1st reboot after installing rom.
Is everyone experiencing this problem or is it only some units as rumoured?
Am facing same problem on Honeycomb on my gTablet. Not sure how to reset the default for home button!
It's really unusable after this starts as we have to press Back button several times to reach the screen where we can select the apps
I've seen this on just about every ROM I've used.. Gingerbread and Honeycomb. It's real annoying.. I had having to press back a bunch of times just to get back.. UGH.
Quick reply - I've posted this elsewhere in other threads, but the problem is actually a misfiring dock indicator pin. The G Tablet thinks its docked and initiates docked behavior, of showing the clock when the home button is pressed. The solution is an app called Dock Nothingness from the Market! Thought this might help some people.
I got similar problem and brought my Galaxy W to Samsung. They said that my phone got screwed up due to wet 'usb' connector. Cleaning those pins also removed the occational fail to charge problems.
Hi all. Thanks for the site. Hope to help out here when I can. I just moved over from the "X" to Razr, and I have a couple of questions/problems.
When I have a new text message in the notification bar up to and try and open it, the screen goes back to the stock lock screen. What is even more weird about it is that I have Widget Locker installed and enabled. My second problem is that I have Swift Key X installed but every time I go to type something I have to go to input method and re-enable it every time otherwise it keeps returning to the stock keyboard. Any ideas? Thanks in advance.
For your first problem, it's normal. You have to disable the stock lockscreen itself. WL won't cancel the lockscreen. There are a few apps on the market that will do that, so just go search.
I'm not too sure about the second though. Try going under Settings -> Language and Keyboards, and change the input method?
Thanks. Found one called "no lock". Seems to be working so far. I don't really understand why I have to have that with the Razr, but never neded it with the X. Oh well. If it works who cares right?
Now I gotta figure out what's up with the keyboard.
Maybe this is an android thing. I'm using the stock keyboard on Skyraider 1.3 with no other mods. It behaved the same on stock and Froyo. I don't use any prediction at all, so the experience is as manual as can be. I have used swiftkey before but I don't remember it behavind better.
I cannot type as fast as I want because sometimes the letters overwrite as I type.
For example:
I type "gotcha"
It comes out as "gotca"
As far as I know it doesn't seem to happen more often with any combos of letter, but I'm not sure I'd notice if it did.
Sometimes the cursor will jump back a few spaces as I type. It's almost like a reverse TAB.
Also, when I'm typing sometimes the keyboard loads and drags the screen far below where I'm working. So much so that I cannot see what I'm typing. So, I exit out of the keyboard, scroll back up, manually place the cursor, and as soon as I type...bam it goes to the bottom of the screen again. I think this happens most while using a browser or e-mail client. And tapatalk.
Lastly, with my SMS messages sometimes it'll completely wig out and bring up the message log of the person I'm typing to prompting me to delete what I have check boxed, which thankfully is nothing.
What's going on here? Is it user error?
Duely blundered from my thunderdolt.
I think your typing issue is from accidently moving the cursor while hitting keys on the top row. I do it frequently, its either that or accidently hitting word suggestions, which is why i turned mine off to, that is far more annoying.
I also have that problem with not being able to see what I'm typing in certain apps. I think its just an app problem, oversight by the developers.
Sent from my ADR6400L using xda app-developers app
Hello. I'm a long time lurker, first time thread creater.
I have an Evo V from VM that's rooted, s-off, hboot 1.50 that was running CM10.1
Randomly it seems out of nowhere, the bottom strip stopped working. In other words I couldn't hit the calls button, the app drawer button, or the other 3 buttons on the homescreen. The hardware buttons still worked, and directly above the line of the homescreen dock worked. When in an app like greenify I couldn't hit the button to allow an app access, or in messaging I couldn't hit the text box to bring up the keyboard and start typing. When I went to do something that automatically brought the keyboard up I couldn't hit the spacebar, etc. At first I figured it was a hardware problem but now I'm not sure. This is because I enabled the dev option that shows you the input the phone is receiving. The little white dot came up exactly where I was touching, I just wasn't getting a response and I can't figure why. Tried the DU rom and the same thing. Tried the pacman rom and had the same problem. Yet the phone says that there is input there, things just aren't happening. This is further validated with the fact that when in 4ext, anything at the bottom of the screen where the dead zone would be, still works. Restored my CM backup when nothing else worked and for now the dead zone seems to be actually gone. But Idk how long that will last. Any ideas?
I'm guessing it's the pie controls getting in the way.
Go to settings>system>pie settings>trigger area>none
See if that fixes the problem.
Hello,
I bet that I'm not the only one who has that problem and I could bet that there is somewhere already a thread about it but all I can find (here and in generall over google) is the opposite case (keyboard disappearing when it shouldn't) or tips for developers to let a keyboard disappear when the user taps on an empty space, so I already appologize but I just can't find any solution.
I have this problem for a few years now, with Googles keyboard, Swiftkey and sometimes Swype. I have it now on my Galaxy Note 4 running stock TW, I had it on my G2 (at least in ParanoidAndroid and SlimROM but I think already in stock LG ROM) and I could even bet that I had it also on my Nexus 4, so that's why I'm asking in the general android forum for help.
Sometimes, I just can't close the keyboard when I don't need it anymore. Pressing back, home or recent apps or opening the notification shade (which should be in the foreground of all for all I know) the keyboard just stays where it is. It isn't frozen, I can still use it. But it really likes to hide buttons I would need e.g. to send the text I just wrote or the buttons in the power menu so I could only press "trun off" but not "reboot" to get rid of it. I even have my back key as "kill foreground app" when double tapping on it, but it kills everything but the keyboard. It takes time and constantly pressing the different navigation keys to finally close the keyboard.
I think you can imagine how annoying that is and I'm really sick of it. It happens randomly so it's not really possible to record any log, it might be possible that XPosed could be the reason for that but I think I already had that problem already befor I installed it the first time but I'm not sure.
Does annyone has that problem too and knows how to handle it?