I've read a lot of really good info on this site, but can't seem to find exactly what i'm looking for. i have a cheap Visual Land Connect table that runs ICS. It was dropped on the power/lock button and now the button has no resistance. It doesn't click anymore. I rigged my tablet so i can still use it but it isn't great. what i'm looking to do is disable the power button and us the Back button instead. is this possible. Using ES File Explorer, i've gone into the key layout files and tried a few things in there but nothing i do there seems to work. Each time i manipulate a file it creates a .bak file. i think this is normal. do i need to delete this? Also, there are a bunch of key layout files in there. not really sure which one to do. even if i can disable the power button once its turned on, and map a different button to do this, that would work. any suggestions?
Related
Hello,
Does someone know a solution for mapping the hardware buttton that normaly launch internet explorer? I would like to use it for X/closing cause I'm already tired to go on the upper side of the screen. i.e. when you put a new meeting with the keyboard, it is hard to go to the cross (up and right) for "saving" the new meeting.
I just bought this phone cause it has a good harware keyboard, but it's not important for me to have a direct access to internet explorer.
Thanks for your replies!!
juju66 said:
Hello,
Does someone know a solution for mapping the hardware buttton that normaly launch internet explorer? I would like to use it for X/closing cause I'm already tired to go on the upper side of the screen. i.e. when you put a new meeting with the keyboard, it is hard to go to the cross (up and right) for "saving" the new meeting.
I just bought this phone cause it has a good harware keyboard, but it's not important for me to have a direct access to internet explorer.
Thanks for your replies!!
Click to expand...
Click to collapse
Which button are you talking about?
I use AE Button to assign the Voice Recorder button to the OK/Close function and it works brilliantly. You can assign single press, long press and double press to different functions. It's a great little app that takes up very little system resources.
I'd still like to know which button is the Internet Explorer button because I didn't know we had that feature!
EDIT: Okay I just realised that you probably have the 16 key version whereas mine is the 20 key version
that's it, I've got the 16 key keypad. I really miss teh Ok/close button, caus I have to grip off my phone for going to the upper right corner of the screen and come back to the keypad....
AE button, doesn't work for this button, neither Vito button...
Anyone an other solution
juju66 said:
that's it, I've got the 16 key keypad. I really miss teh Ok/close button, caus I have to grip off my phone for going to the upper right corner of the screen and come back to the keypad....
AE button, doesn't work for this button, neither Vito button...
Anyone an other solution
Click to expand...
Click to collapse
Why doesn't AE Button Plus work?
I use it for OK/Close and it works perfectly well
So I must not have using it the good way.
But wich button are you talking about, cause with AE button, it only "see" the three external button (wich are on the side). I know that you can assign every button with AEbutton, but when I assign the internet key for ok/close, it close the app the first time I use it and then the key come back to its previous function (internet explorer). Someone a reg trick?
I have the 16 key version too and want the same, an ok button on the keyboard. button utilities only recognize the hardware buttons and not the keyboard buttons so there is no way to map these. hopefully someone will update their utility to include the keyboard buttons.
cheers,
cojones
"happy" to see that I'm not the only one who don't suceed by trying to change the function of the internet explorer button on a 16 keypad of a dual for using it with the ok/close button...
I found the camera button akwardly placed (kept launching the damn thing by accident) and dont use the camera much - so I remapped the cam button to OK/Close and have found this does the job for me. Not really a solution I know, but it wokrs for me.
Yes AE Button is great, but while you can map any key like Mail or IE, it will still launch the old app, we'd have to find a way to not launch the old app, in the registry possibly.
GpsPasSion said:
Yes AE Button is great, but while you can map any key like Mail or IE, it will still launch the old app, we'd have to find a way to not launch the old app, in the registry possibly.
Click to expand...
Click to collapse
I have found the same. Has anyone managed to map IE button succesfully? Also there is a pause/delay when using buttons handled by AE Button, has anyone else noticed this?
any updates!? i think it can be done in the registry though i don't know how. hope that someone can crack this.
Mapping IE button to Opera solution
cojones said:
I have found the same. Has anyone managed to map IE button succesfully? Also there is a pause/delay when using buttons handled by AE Button, has anyone else noticed this?
Click to expand...
Click to collapse
I have found a rudimentary solution. Add the IE key using AE Button Plus and run the following Mortscript (I am still a novice scripter) to close IE when it opens automatically and then run Opera Mini.
WaitFor("Internet Explorer",5)
Close("Internet Explorer")
Run("\Windows\jbed.exe", "-run s0_")
It works for me. If anyone has any suggestions on improving it, please let me know.
anythig new about this, pls?
thx
balviforever
Did anyone has a solution for this? Have been searching to change Ok/Enter and IE buttons. AEBPlus doesnt really work perfectly and eat into RAM..
Can we change registry? lnk? read somewhere about long_press_xxxx.ink but dont find it in our Nike.
Anybody found a solution for this? I've tried everything but couldn't map the IE button on my 16-key Nike to OK/Close.
I don't know about everyone else, but I've found that I instinctively want to push the home button on my phone when I want to end a call. It's burned me SOOOOO many times. I think it's funny how many Android devices seem to have their buttons mapped wrong! For example, I just bought a Coby Kyros 7015A tablet and it has a "rocker" style button on the top that just logically seems like it should be a volume up/down rocker, but for some odd reason they decided to assign "home" and "Menu" to the two sides of the rocker. In addition, the big silver button in the middle seems like it should logically be the Home button, but it is the back button instead.
After a little fiddling around with my Kyros tablet I discovered where the keymapping files are located:
Code:
/system/usr/keylayout/
there are two plain text files in this directory which need to be modified in order to make changes to keymapping, "qwerty.kl" and the other one is going to be named something to do with your particular device. You will need to edit them with a Unix compatible editor like Notepad++ on Window$, but Gedit or Kate will do just fine on Linux.
After successfully remapping the "back" button as "home" and the home/menu as volume up/down on my Kyros, I decided to tackle setting a button to hang up on my Optimus. Of course the first thing I did was make a backup in the recovery.
NOTE! This may not be a great idea for every ROM. Make sure that before you proceed, your ROM has "Spare Parts" and you can change the default behavior of the "end" button. The default behavior of the End button is to shut the screen off and it can not be changed on some ROMs.
This goes without saying, but you are editing files in /system/ so you will need to be rooted.
On the Optimus running CM7, the two files you need to edit are "qwerty.kl" and the other file is called "thunder_keypad.kl"
Code:
adb pull /system/usr/keylayout/
* make sure you put that last / at the end! it tells it to pull all of the files in the directory.
Editing these files is a pretty straightforward process. Basically, after you pull the files from your phone, you open the files and replace the instances of "HOME" with "ENDCALL". Save the files and push them back to the device, and then reboot. That's it!
Code:
adb push qwerty.kl /system/usr/keylayout/qwerty.kl
adb push thunder_keypad.kl /system/usr/keylayout/thunder_keypad.kl
adb reboot
Now you can hit the home button to hang up during a phone call instead of having to hit one of the hardware buttons to wake up the phone, which usually puts you at your homescreen or somewhere else just to have to get back into the phone call and hit the soft button hopefully before the screen goes black because of the proximity sensor (it's designed to do that!)
Like I had mentioned earlier, you're going to want to go into spare parts and change the default "End" button behavior to "Go to Home". Basically you remapped the end call button to where your home button is and then you're telling the Android OS that the end call button will emulate the normal behavior of the home button. Make sense? Didn't think so...
Works great on Mik's CM7. The only "bug" i've found so far is that when you're in the app drawer, hitting home doesn't take you back to your homescreen.
Here are my edited .kl files
Just in case you're really REALLY lazy and don't want to take the time to edit the files yourself (or if you don't have a Unix compatible editor)
Just remount and push them to /system/usr/keylayout/
Is there a way to have any hard key unlock the droid x2
I do remember reading about this in the developement section. There's something to change in one of the scripts, but I don't remember exactly where or what it was. Try the search or browse around a bit. It's there.
Sorry I wasn't much help.
If you flash CM7 you can have the home key and volume keys unlock the screen.
Settings--CyanogenMod settings--Input--check the box for "volume rocker wake."
I think "home key wake" might be on by default.
Read through this thread:
http://forum.xda-developers.com/showthread.php?t=1403013
I asked the same question in there. There is a file you can edit that can change the actions of the hard buttons. Just be sure to make a backup of the original file when you do it.
EDIT: Not sure if you have to have a certain amount of posts to see links. So heres a quick summary.
In a file explorer, go to /system/usr/keylayout. Open the tegra-kbc.kl file in a text editor (You have to give read/write permissions to edit and save this file on your phone) and you can change the menu, back, search and volume buttons from WAKE_DROPPED to WAKE. Notice how the home button is the only one set to "WAKE". This will make all the buttons wake from the screen being off like the home button does. Again, backup the file first in case something doesnt work right. Im not responsible if you mess something up. But this should work fine.
When I first did this, I did that to the volume buttons and it worked. So it should work with the other buttons as well.
They won't take until after a reboot. I edited the same file to make my search button open my camera.
Sent from my CM7 DEATHMACHINE!
Thanks everyone
I tried this b4 and did something wrong as the phone went dark and would not turn on. Somehow I got to factory reboot and brought it to VW and they replaced.
jsgraphicart said:
Read through this thread:
http://forum.xda-developers.com/showthread.php?t=1403013
I asked the same question in there. There is a file you can edit that can change the actions of the hard buttons. Just be sure to make a backup of the original file when you do it.
EDIT: Not sure if you have to have a certain amount of posts to see links. So heres a quick summary.
In a file explorer, go to /system/usr/keylayout. Open the tegra-kbc.kl file in a text editor (You have to give read/write permissions to edit and save this file on your phone) and you can change the menu, back, search and volume buttons from WAKE_DROPPED to WAKE. Notice how the home button is the only one set to "WAKE". This will make all the buttons wake from the screen being off like the home button does. Again, backup the file first in case something doesnt work right. Im not responsible if you mess something up. But this should work fine.
When I first did this, I did that to the volume buttons and it worked. So it should work with the other buttons as well.
Click to expand...
Click to collapse
Hello, I have just installed the latest NAND rom package (updated on 15-03-13) on my Telus RHOD500 and I'm having troubles with the power button (the button on top of the phone).
It's not mapped to anything once booted to Android. I mean I can access the recovery by pressing the Power button in miniPooploader so I know the key is not broken.
In android, quick pressing does not shut down the screen, long-pressing does no bring up the power menu and to wake the device up I have to use the End key.
A few times between boots when I would quick-press the power key it'll pop up the shutdown menu but now it's not doing anything.
I've installed Android Tuner, ES task manager and SetCPU on second reboot so these are the 2 application I installed that could come into problem before I noticed the problem. Uninstalling them doesn't do any good.
Also, where could I change the physical keyboard keymap? I got the underscore symbol mapped to letter "B" where it should be "P". It's not the only one of course but I don't find this too irritating so it's just a side-question like that.
Anyway thanks in advance!
psyko_chewbacca said:
Hello, I have just installed the latest NAND rom package (updated on 15-03-13) on my Telus RHOD500 and I'm having troubles with the power button (the button on top of the phone).
It's not mapped to anything once booted to Android. I mean I can access the recovery by pressing the Power button in miniPooploader so I know the key is not broken.
In android, quick pressing does not shut down the screen, long-pressing does no bring up the power menu and to wake the device up I have to use the End key.
A few times between boots when I would quick-press the power key it'll pop up the shutdown menu but now it's not doing anything.
I've installed Android Tuner, ES task manager and SetCPU on second reboot so these are the 2 application I installed that could come into problem before I noticed the problem. Uninstalling them doesn't do any good.
Also, where could I change the physical keyboard keymap? I got the underscore symbol mapped to letter "B" where it should be "P". It's not the only one of course but I don't find this too irritating so it's just a side-question like that.
Anyway thanks in advance!
Click to expand...
Click to collapse
You have to open the boot.img and edit the keyboard maps inside the ramdisk there to make them stick.
Look around post 47-50 for some ideas on what to edit.
http://forum.xda-developers.com/showthread.php?t=1965459
Good luck.
wizardknight said:
You have to open the boot.img and edit the keyboard maps inside the ramdisk there to make them stick.
Look around post 47-50 for some ideas on what to edit.
http://forum.xda-developers.com/showthread.php?t=1965459
Good luck.
Click to expand...
Click to collapse
Alright thank you. That will be good for the keyboard issue. Could it also fix the power button issue? Is the mapping of the keyboard is related to the mapping of other buttons?
So where can I find the boot.img file? Thanks!
So I've found for that I often want to easily go to the place I was before I pressed the back button. That or I have pressed it by accident. So a forward button is the first thing that comes to mind.
I don't think such a thing exists yet and there are very few discussions I have seen that touch on this idea. Mostly the idea was written off as being noob or just not being useful.
Now before you tell me that all I have to do is find and select the original place I was again, one word: convenience. And for the sake of innovation due to my own laziness, humor me.
The Forward Button would work similarly to how a forward button works on an internet browser, the difference being that it works throughout the Android UI just like Androids Back Button does.
When the Back Button is pressed, it triggers a feature that will record the path of the page you are leaving. So if you were to select the Forward Button after using the Back Button, the recorded path would be activated, taking you to the page you were on before you used the Back Button.
Although, the Forward Button directly relies on the use of the Back Button. So if you went somewhere else after using the Back Button, (instead of using the Forward Button) then all of those paths you came back from that were previously recorded would be erased. The Forward Button only works directly after using the Back Button with no other actions in between except using the Back or Forward Buttons again. Just like the internet browsers version.
Technically, because the feature of a Back Button is already included, the Forward Button just would be some sort of add on to that, right?
I should say that I am not a developer myself, and I have very little knowledge reguarding it. But if a concept is what it takes to get me learning so that I can create something, so be it.
So if some experienced developers or just anyone who has any input could give me insight into the possibility of this working and maybe even some logistics of how it could be done, please share.