I've had this problem on every iteration of CM7 thus far where occasionally after entering my message, whether in a text message or search engine, the keyboard will stay maximized rather than disappearing as it normally would. The only way I can get rid of it is to press back and reenter my search or exit by pressing the home key and then navigate back. Anyone else encountered this?
Sent from my Evo using XDA App
try pressing t and then swiping down. you need to press for about half a second before swiping. also try holding the menu key.
dkdude36 said:
try pressing t and then swiping down. you need to press for about half a second before swiping. also try holding the menu key.
Click to expand...
Click to collapse
Well at that point he'd have to press back, because long pressing the key brings up the keyboard; unless I interpreted it incorrectly.
teh roxxorz said:
Well at that point he'd have to press back, because long pressing the key brings up the keyboard; unless I interpreted it incorrectly.
Click to expand...
Click to collapse
not a long press. about half a second. then swipe your finger down to the spacebar. the keyboard will disappear on stock gb kb. or just hold the menu button. it will also disappear.
Related
Hi,
im using the i927 with OsiMood-Rom.
Today its the second time, that my hardware keyboard behaves a bit strange:
- When I press "e" the Email App opens
- When I press "b" the browser opens
First time I got it "repaired" with a reboot, for now a re-open of the keyboard helped.
What is going on there?
That is not a weird behaviour but a feature. It's called "Quick Launch" and is started by pressing and holding the search button on hw keyboard plus any key in the hw keyboard. the "E" key is the default for email (press "Search" + "E" = Email), you can modify this in settings > applications > quick launch
Thanks, I mentioned that it's something like this but I didn't know what other button activates the shortcut or where to disable it
Roeni said:
Thanks, I mentioned that it's something like this but I didn't know what other button activates the shortcut or where to disable it
Click to expand...
Click to collapse
Like me, you might be using the "Search" button (either soft/hardware keys) to launch apps a lot.....most of the time, I end up pressing search plus the first character of an app i want to launch that results in pressing the two keys almost at the same time. That is how I accidentally discovered it....
I was like searching the "Email app" then I accidentally pressed the "E" key while the "Search" key is pressed then I went "How did this thing know that I want to launch Email?"
Press your search key again on your keyboard it is stuck. Happened to me once or twice. Quick launch is launching your short cuts that are programmed because it thinks you are hitting a 2 key combination. (Search and E)
I don't use any lock screen and I always use the home button to wake my phone up.
Since official JB, the home button not only wakes the phone up but it closes the app I'm in. Example : I'm browsing something on chrome, the screen turns off bc of timeout, I wake the phone using the home button and I see chrome back but immediatly it closes down like if I had pressed the home button again (but I didn't). The same behavior does not happen when a lock screen is enabled.
I tried searching for an answer and tried the solution of editing the .kl files in system/usr/keylayout by adding WAKE_DROPPED or replacing WAKE with WAKE_DROPPED for every occurence of the home key (key 172) without luck. I tried fixing the permissions in CWM and I made sure the permissions are rw-r-r.
Running stock rooted with CWM.
Any other ideas? Thx!
I'm also curious about this. My temporary fix was to unfreeze S Voice in Titanium and then enable the double press of the home button to start S Voice.
I'd rather keep S Voice frozen and still keep the same behaviour of the home button in ICS.
pappcam said:
I'm also curious about this. My temporary fix was to unfreeze S Voice in Titanium and then enable the double press of the home button to start S Voice.
I'd rather keep S Voice frozen and still keep the same behaviour of the home button in ICS.
Click to expand...
Click to collapse
Yes that does work indeed. However, it brings back the lag when pressing the home button. I'm also using home2 shortcut for some shortcuts and it completely breaks them!
The same problem arises also when you long press the home button to get to recent apps, if you have an app open in the background at that moment and you press the home button to get out of the recent app screen, it closes the app!
So heres my problem in a nutshell:
When I press the home button, my phone unlocks (I have no lockscreen), however it takes me to the home screen. Whereas if I hit the power button, the screen turns on where I left off. This is the expected behavior.
If I go into S-Voice, and select "Open via the home key", the home key unlocks the phone correctly, but I have to deal with the home button lag issue.
So, how do I get the best of both worlds? No lockscreen, no home button lag, and no issue with using the home button to wake the phone.
I could do without S-Voice all together so if thats an option Im OK with it.
jackher0r said:
So heres my problem in a nutshell:
When I press the home button, my phone unlocks (I have no lockscreen), however it takes me to the home screen. Whereas if I hit the power button, the screen turns on where I left off. This is the expected behavior.
If I go into S-Voice, and select "Open via the home key", the home key unlocks the phone correctly, but I have to deal with the home button lag issue.
So, how do I get the best of both worlds? No lockscreen, no home button lag, and no issue with using the home button to wake the phone.
I could do without S-Voice all together so if thats an option Im OK with it.
Click to expand...
Click to collapse
I wasn't happy with the speed of the home button, I took off the double tap for svoice and I'm much happier not sure if that helps you
This issues has been solved!
Anyone have the issue where when you use the home key after you release the press their is a audible clicking noise, nearly like something is lose in the home key.
Edit, I now realise that I was use a little bit too much force with my press, this maybe why. Now I wonder if this home key is prone to breaking
Ming Wu said:
Anyone have the issue where when you use the home key after you release the press their is a audible clicking noise, nearly like something is lose in the home key.
Edit, I now realise that I was use a little bit too much force with my press, this maybe why. Now I wonder if this home key is prone to breaking
Click to expand...
Click to collapse
You understand that the home key is not a button right? It just a capacitive key.
Dont press it, just tap it.
Of course it will break, if u press something that wasnt supposed to be pressed, LoL
otonieru said:
You understand that the home key is not a button right? It just a capacitive key.
Dont press it, just tap it.
Of course it will break, if u press something that wasnt supposed to be pressed, LoL
Click to expand...
Click to collapse
Turns out I have a screen protector that's causing issues as it has a raised ring around the homekey. The clicking noise is the screen protector.
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
DonnyR said:
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
Click to expand...
Click to collapse
Unless the back button is programmed to kill an app, the app should stay in memory. So check the options for the back button and change it.
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
DonnyR said:
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
Click to expand...
Click to collapse
Check the long press duration and if possible lengthen it. Or assign double tap for kill and none for long press as an experiment and check.