I did some searching to see if this was possible on android and couldn't find any good info.
I am still not used to onscreen keyboards and on the One S in particular I keep hitting the home button when I type (it has happened twice since I started writing this)
Am I the only one with this problem? Does anyone know of a way to disable the home button when the keyboard is up?
Thanks
Sent from my HTC One S using xda app-developers app
It seems like a good idea, but is probably very hard. The home button is kinda coded to work the same way always, regardless of what app is open
Yea I kinda pressed the home button too at first but just practice typing without trying to hit the home button and you should be all set, its not easy to type without pressing the home button but it takes some time to get used to...
Sent from HTC one s
It's damn near impossible! Been using touchscreen keyboard on different phones for years (how I miss my G1), and never had this problem...I feel like Homer trying to phone his children in that one episode of the Simpsons...."mash the keypad to continue"
Try SwiftKey keyboard, it detects where spaces go so you don't need to press space
Moved To Q&A
Please post all questions in the Q&A section
Related
Has anyone come up with working solution for mapping hw keys?
I found this thread on Diamond, but no help:
http://forum.xda-developers.com/showthread.php?t=398280
I am using AEKMap to enable both latin/cyrillic input on my TP's hw keyboard. You may google it and give it a try.
There is no need for additional software, just follow this post and you'll get the answer. Worked for me.
Try AE Button Plus.
B.
I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).
Taajuus said:
I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).
Click to expand...
Click to collapse
And that is EXACTLY what i also want to know....
The total lack of hardware-keys on this device is already disturbing enough, but being locked out of the option to remap any of them is truely horrid...
Anyone know of any reg-hacks maybe?
I've got Spb PocketPlus 4 installed btw, and it's got a button mapping function as well...
But when i go into the buttons map, some weird black icons appear with no name attached to it. Can anyone make anything of this? As you can see i've been able to map one thing only: the Spb close-button-contex-menu, which allows me to switch task KW-buttons only....
But this is not enough for me, i need ALT-TAB aswell and off course a VoiceCommand button.
And regrettably the Rapael doesn't have that many HW keys to start with...
I want also to use Home/Back buttons for different purposes,but I didn;t found a solution yet.
Gotten a step closer to what i really need over this weekend:
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
So far, this setup is to my satisfaction, and after two months of use this phone finaly behaves completely the way i want it to...
Hi, guys.
See my post here:
http://forum.xda-developers.com/showthread.php?p=2743845#post2743845
Hope this helps!
Cheers.
helped realy much !!! big thx for that nice instructions
You're very welcome, tk_berlin.
You be sure to let me know if anything in there doesn't make sense or you need any help with it.
Cheers from Canada!
ah cool to see a reply that fast ,)
hmm u got any further with finding out how to set the home button and the backwards button ?
Since the other htc user ,) wrote
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool
ah cool to see a reply that fast ,)
Click to expand...
Click to collapse
Lol. I was on my machine all morning and had XDA open in one of my tabs.
Yes, you can map practically any button in AEBPlus no problem.
hmm u got any further with finding out how to set the home button and the backwards button ?
Click to expand...
Click to collapse
AEBP will also *learn* any keys it doesn't have. So you could use the "Add Button" option, press your Home key, and away you go.
The way I have it set up, holding down the phone key will activate voice command (default behavior).
But remember, assigning commands to the Home or OK buttons (that "Back" button is actually an "OK" button) doesn't unmap what they normally do so you will always go home first and then it will perform <x>-function that you assign.
Personally, I don't like to program the Home or OK buttons because I find that they are "trickier" to press. What I mean is, if you tap the OK button near it's center or close to the left, it doesn't register a press. If you tap it sort of with the long part of your thumb (which is more natural when holding the device in one hand), it registers it. I've tried this with two TP's now and the button behaved the same way on both. Due to this, I find it unreliable to map anything to it.
In any case, as I mentioned earlier, the Volume buttons, Phone and End keys will be unmapped once you attach AEBP to them but the others will not.
Oh -- I forgot to mention, you can map the directional pad as well if that is your thing.
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool
Click to expand...
Click to collapse
It does work, but it sends an OK command first.
I wrote a little utility for hard-coded buttons such as these for another Pocket PC I had (an ASUS P527) called "DoNothing.exe" but we can't apply that work-around here. What I would do is replace the EXEs of apps the hardware keys called with my DoNothing.exe, but in the case of the TP, we definitely don't want to replace START.EXE (which I believe to be the likely EXE (haven't tested this)).
If I find a way to map those buttons reliably, I will let you know, tk_Berlin. So far tho, I've been quite pleased with just using the four buttons I mentioned. The more I use this device and the more I ponder my decision to stay with TFL3D instead of the normal WM interface, the more I realize that I don't need half the add-ons I used to use prior to having TF3D. I am accustomed to very, very, very *heavily* customizing my device, but the setup I have now works great and I really haven't lost nething from my old WM world. In fact, prolly gained a few CPU cycles and memory to boot.
I don't miss the Today Screen at all!!! Now that I think about it, I never really looked at it.
Cya!
I'm using Butler [ http://forum.xda-developers.com/showthread.php?t=464611 ] to use the extra functionality of the hardware keys ... the only thing missing for me now is the possibility to use the 2 top buttons of the touch pro [Home and Back] for the left and right softkey (that's the only thing I miss from the kaiser). Any ideas how to do it without AEB ?
And is there a program you can launch to go to the today screen?
I'd be interested in this also. Thus far Da_G's latest roms have been able to reprogram every button except volume, home, and back keys.
Unfortunately the Volume, Home, and Back keys give me the most trouble. I always keep my phone on vibrate and I never use the Home/Back buttons. Even a good way to simply disable these keys would be a start. I'd much rather be able to use my dpad without ending up at the today screen.
Although someone said they used AEB to remap the Home/Back buttons to ONLY function on a double tap.
i was just thinking about this. i noticed i could change long press for send and end as soft keys. not enough buttons on the device you know.
I also would love to be able to reprogram the home and back keys to be the left and right softkeys. There has to be some way to do it...
I did some more searching on this topic. Try DredSensor. It works for me so far.
drcursor said:
I'm using Butler [ http://forum.xda-developers.com/showthread.php?t=464611 ] to use the extra functionality of the hardware keys ... the only thing missing for me now is the possibility to use the 2 top buttons of the touch pro [Home and Back] for the left and right softkey (that's the only thing I miss from the kaiser). Any ideas how to do it without AEB ?
And is there a program you can launch to go to the today screen?
Click to expand...
Click to collapse
If we can get the home, back button, set as left and right softkeys as well as set pressing the center button in as OK button then i would have zero complaints about my att fuze. Sometimes i turn my tilt back on just to use programs such as opera mini, life is so much easier with softkeys!
DarrenUtd said:
I also would love to be able to reprogram the home and back keys to be the left and right softkeys. There has to be some way to do it...
Click to expand...
Click to collapse
Yes im sure everyone is aware of dredsensor which is what i have to use when running opera mini on my fuze. What we are talking about is setting the home and back button as softkeys for good for all apps by default and also having the center button as OK as well. Do we really need a home and back button anyways? I mean we have touch screen phones, i can drag my thumb to get to home screen and press the center button to go back if set to OK button.
No we don't need an Home and Back button. The home button works the exact same as the End key. The back button is iffy. While I don't use it much, I'm sure "some" people do. There are the occasional situations when the back button is useful.
If you make the Center button "Close/Ok", then you won't have a select button. What WOULD work is set the center button to default, but do an "Close/Ok" on Center Hold.
I wish we had all the buttons unlocked to do what we wish. Using Home/Back as softkeys aren't a big deal to me, BUT being able to at least disable them or remap them in games would be sweet. (yes I know about DredSensor... I'm talking about permanent).
Another thing I am aiming for is a "virtual D-pad" using the touch pad area around the center button. Allowing us to navigate simply by making contact to the "hotspots". This would at least fix the problem with using the Dpad in games without ending up at the today screen.
If we could offload the navigational functions to the touchpad... then we could remap the buttons up/down to launch programs or whatever (left and right too).
So Pressing the buttons on the touchpad could launch apps or be used as softkeys or whatever but touching the touchpad would navigate.
Here is the thread; http://forum.xda-developers.com/showthread.php?t=473023
The last couple of posts have been playing down my earlier suggestion to use dredsensor to remap the home and back buttons to be the left and right softkeys (the topic of this thread). I'm not affiliated with dredsensor in any way, but I wanted to clear up this issue.
Since version 1.1 was posted on 1/17, you can in fact remap the buttons as stated above. In your config.ini file, for the [Default] profile with WindowTitle=* and ClassName=*, you have the entries:
HardKey_Launch1=Key:SoftKey1and
HardKey_Launch3=Key:SoftKey2
I'm not sure what you guys mean by "permanent" or "for good for all apps by default", but with this configuration these rules should apply in any app, which would seem to be what you want. I've been using this for a few days now and it works for me in the applications I've used. Anyway, it's just a suggestion. Maybe give it a try and I hope it helps.
i followed your suggestion..but i find the behavior erratic..sometimes it looks like it just goes to sleep and the keys are back to normal, and then out of nowhere starts to run again :\
drcursor said:
i followed your suggestion..but i find the behavior erratic..sometimes it looks like it just goes to sleep and the keys are back to normal, and then out of nowhere starts to run again :\
Click to expand...
Click to collapse
From what I've read, there could be problems if you have G-Scroll installed, or maybe on some specific ROMs. Maybe post the issues you are having so that the developer can fix it in the next version.
http://forum.xda-developers.com/showthread.php?t=472280&page=2
Idk if someone already found this but i thought i would post it anyway you can get into the stock recovery by
1. pressing and holding the x key on the keyboard
2. without letting go of the x key turn on the phone
up to here its the same as the droid 1
3. you should get a yellow triangle and android logo to show up
simply press the search key on the keyboard srry
4. and your in
Seems to work ok but pressing the search button does nothing for me... just sits there and does nothing. Have to pull battery to reset. I must be missing something... ??
Sent from my DROID2 using XDA App
You may have done it this way but...
You have to hit the physical search button on the keyboard
Sent from my DROID2 using XDA App
vampireincubi said:
You may have done it this way but...
You have to hit the physical search button on the keyboard
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Wow, its always the simple things.
Yes, make sure you use the search button on the slide out keyboard, not the one on the bottom right of the screen. That was my problem now it works fine.
Thanks vampire
lol srry for got to say it was on the keyboard my bad
http://forum.xda-developers.com/showthread.php?t=769549
original post by me just so you know and it probably shouldn't be in development but rather General.
Please search before you post or at least skim the topics to save from having lots of double posts, thanks.
Was curious if any of you guys were working on, or know of a program that can act as a back button or menu button, on screen. My home row keys are taking a beating, and normally cause to much hand adjustment to use them.
Just a thought.
I was thinking maybe swype like actions for the back button, etc...
I've tried button saviour, but didn't like it too much.
Thanks for reading and replying.
"Softkeys for root users" might be what you're looking for.
Sent from my HTC Glacier using XDA App
Download Button Savior from the Market. Alot more friendly to the eyes and a heck of a lot easier to use than Softkeys. I use it on my Nook as well.
tried softkeys, wow, that is a difficult program to use, but looks great.
I will have to go back to button savior I guess, and make it work.
Thanks for the replies.
Hope this helps you.
lion766 said:
tried softkeys, wow, that is a difficult program to use, but looks great.
I will have to go back to button savior I guess, and make it work.
Thanks for the replies.
Click to expand...
Click to collapse
Its not hard to use. Its hard to configure properly.
When you install, hit the home button and choose softkeys as your default home. This will allow softkeys to intercept the home button call.
Then, in softkeys, program it so one push gives softkeys and 2 pushes gives you "home" (<--- specify which home app that you want softkeys to call upon double click)
I also put the back and menu buttons (on my Nook Color) in the notifications area to have easy access to them those as well.
Thanks! I just noticed I had a pm, and this is apparently where all the posts, I followed, made apparently get moved to!
I thought I was crazy.
So I came across this in the EVO 3D forums. How hard do you think it will be to port this to our device?
http://forum.xda-developers.com/showthread.php?t=1346760
It is in development already. See bricked kernel thread for more info.
Sent from my Sensation
Anyway to enable this?
http://forum.xda-developers.com/showthread.php?t=1269247
And gnex has it
Both Bricked and TamCore have this feature.
Bricked: http://forum.xda-developers.com/showthread.php?t=1269247
TamCore: http://files.tamcore.eu/android/?dir=tamcore-kernel
Bricked gives you an option to enable it during installation, while TamCore requires you to flash a zip to enable it, which you can get on the same page, under the name "sweep2wake_enable.zip".
A few kernels already have it.
I am already using it... :angel:
Already using it on bricked!
It's nice because you don't have to constantly use your power button to turn on device ! I really love it! It's so easy.
Sent from my HTC Sensation 4G using xda premium
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Sometimes it will pull up the power window, it will go back, back out of an app...instead of posting here...post in show-p threads.
It's a good feature, the bricked & faux kernels have it as far as I know!
Sent from my HTC Sensation Z710e using xda app-developers app
Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)
kgs1992 said:
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)
Click to expand...
Click to collapse
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.
Louer Adun said:
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.
Click to expand...
Click to collapse
There's a thanks button.
However, I don't see how this is practical much. I only lock using sweep because it's a good shortcut to exit current app, go to home & luck.