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
Hi guys,
My digitizer has died, and till the new one comes I was thinking of how I could use my T7272, I can write the SMS fine, but I can't send them out, cause the button is on the screen itself... is there a rom I could use freely w/o using the touchscreen?
P.S.
Is the digitizer hard to replace?
You could check out AE Button; it has some options like button presses that will activate soft buttons. I suspect you could send sms's using it. You could also try using mortscripts with AE button that will do stuff you need. There are some pretty simple scripts that will simulate screen taps, and you could assign them to a button push. I'd rather have a working touchscreen, though.
Here are some of the commands:
# 91: startmenu (on some devices it might be home button)
# 92: back key (not the backspace key but back key for closing applications which is available on some devices such as diamnd or blackstone)
# 93: menu key
#112: left softkey
#113: right softkey
#114: accept call (green button)
#115: hang up (red button)
#117: volume up
#118: volume down
#126: data disconnect
#127: toggle speaker
#133: devicelock
#223: power off
I use one to lock the device. Basically, you just put this:
Code:
sendspecial(133)
in a .txt file, and change the extension to .mscr. I call it Lock.mscr, and I have it assigned to a few different actions (like when a call comes in, a script locks the phone). So, sendspecial(112) and sendspecial(113) might help you out. There's also one for hitting 'Ok' in popups, which would probably work for you. I can't find it, though (google 'sendspecial' and you'll find it, it's all on msdn).
Anyway, if you install mortscript (maybe you already have it) as well as AE Button, you could assign button pushes to carry out those actions. Just stick the scripts somewhere easy, like the start menu, and it will be easy to set up.
If you want to get more complicated, there are also mortscript commands that simulate button pushes on the screen. You could set one up that would do just about anything. Also, SK Schema does similar stuff. You can write fairly simple sequences of button pushes that will do just about anything. This is one that I use that runs SK Tools Pim backup (I have it scheduled to run every night in the middle of the night).
#r(\windows\sktstart.exe) #p(STH:20)
#tap(146;602) #sleep(15000)
#tap(110;533) #sleep(500)
#tap(339;455) #sleep(500)
#tap(126;604) #sleep(500)
#tap(114;84) #sleep(500)
#tap(146;99) #sleep(5000)
#tap(310;254) #sleep(90000)
#tap(433;602) #sleep(10000)
#pwr() #sleep(10000)
Click to expand...
Click to collapse
Basically, the backup tool gets launched in line 1, then there are a bunch of screen taps (w/ delays, to make sure everything is ready) in the menus to get the right options selected, followed by turning the device off.
I`m not sure... But i saw somewhere app that emulate a mouse (cursor) and you will be able to control this mouse with your D-pad... But I can be wrong...
I can't install that mortscript w/o the touchscreen though..damn it..: )..
Get MyMobiler, and use it to run your device off of a pc. You should be able to get that working.
Hi, i was wondering if you guys can help me remap my home touch buttons to work how they used to (on some devices). Ive tried to get used to how it is now but i just cant get comfortable. I checked another thread thats similar to what i want done but not quite exactly what i was looking for.
I use the back button, home button, and recent apps button. My goal is to long press the home button and have recent apps open and use the recent apps button as a general settings button (instead of having to long press the recent apps to get there). Im basically trying to acheive the LG Optimus G setup. Its a minor tweak and i'd enjoy the phone even more this way.
Any help would be greatly appreciated! If theres a thread that I missed that fits my needs plzz direct me to it! Thanks!
Hello all,
Recently the power button on my Nexus 5 has been acting really weird. Sometimes it works flawlessly, others it requires pressing it really hard to work. In order to prevent it to stop working indefinetely, I am looking for a way to remap my volume-up button so it can work as a power button. I don't need it to turn my phone on or to work in the recovery mode (from what I read, it seems to be impossible), only when Android is running.
I've already tried some workarounds:
1) Volume Unlock Power Button Fix app: I tried it, but it just allowed me to turn on my phone with volume but not turning off. Also, it drains a LOT of power.
2) Buttonremapper app: It would theoretically do exactly what I wanted, but did not work at all.
3) Editing generic.kl: I tried switching volume-up and power buttons codes in generic.kl, but also did not work. Maybe I need to modify another file?
3) Xposed Framework + Additions: The installation of Xposed went Ok, but after installing Additions module I got stucked in bootloop. I am running Android 5.1 stock, maybe this module is not yet compatible.
So, can anyone help me? Do I need to install a custom ROM?
PS: I live outside US, so no warranty for me. Otherwise I would just use it
Thanks in advance for any help!
Cheers,
Humberto
Hi folks,
Just a heads up for anyone who might be facing the same issue. I decided to change from stock to Cataclysm ROM due to some specific features (listed below). After the installation, here's what I did to work around this problem:
1) Enabled "Volume wake" and "Sleep button on status bar" in "Cataclysm Settings / Miscellaneous".
2) Enabled "Swipe to sleep" and resized NavBar to 115% in "Cataclysm Settings / Navigation bar options". -> This way I can swipe in NavBar at any time (except lockscreen) to turn off screen. I raised it a little to facilitate the swipe gesture.
3) Changed Lockscreen Dialer shortcut to ""Turn off Screen" app shortcut (just search for it in the play store) in "Cataclysm Settings / Lockscreen options" -> This allows me to just swipe right and turn off the screen when my security settings are disabled (which accounts for most of the time). I found it way faster than pressing sleep button in status bar, especially when I'm driving and I can't look at the screen. Plus, I don't really use the dialer function of my phone so often since the invention of Whatsapp ;P
I realize this is not the perfect solution, but I don't see a better way to deal with this power button malfunction problem (except from a hardware fix).
Hope this helps!
Cheers,
Humberto
PS: I am really enjoying Cataclysm. It's a very nice ROM, completely stable and with a lot of other interesting features aside from the ones mentioned above. I strongly encourage anyone to give it a try!
I'm facing the exact same problem but I really need to eliminate the power button or I will need a power button fix soon.
The solutions you found hthiengo are good if not needing to turn off (or worst: running out of battery, something that happens me sometimes). I'm in the situation that next time I hit power button I will need to replace the button, or throw the nexus away
I did installed the xposed additions for lollipop but it is not working, and the Cataclysm trick is not enough in this case
Ok, after some research I've found a temporary solution:
For the power button you can remap modifying the file gpio-keys.kl under system/usr/keylaout (i wonder why anyone could figure out thise before, no that difficult). I would like to map power button leeaving it useless but I've found it impossible to remap the power button (probably because the key number is not 116). I would have liked to see xposed additions to help me map the keys but is not functional at least for me.
If the phone runs out of battery I've found that if I plug the power cable by pressing both volume buttons at the same time, eventually it starts up with the bootloader so I can plug the pc cable and it will reboot sucessfully.
So despite the phone know is pretty disfunctional (not the best phone for a hurry without battery), I can still use it for some weeks before I plan buying a new one or something (or I find a place for reparing). Its a shame I could not find a better solution for example, ADT when powered off so I could just reboot it by using ADT reboot command while powered off.
And It would be really amazing if the volume up button could also power it on from the powered off state.
In my case the power button is broken, but sometimes it gets stuck and puts the phone in a reboot loop: To avoid pressing the power button accidentally I've made a hole in the protective case so its pretty difficult to access it.
That's all for now. If anyone can make it better I will be glad to hear him/her