Database Info

"Select" Hardware Button

I'm using Des' slider hack to get the slider to function as an up/down slider on a plain XDA II. I wish to map the record button to "Select", (not OK/Close), but the settings/hardware buttons panel won't let me. Is there any program, or way to get hardware buttons to act like the center of the joystick to select things?

Me Too
I have the same setup and would really like to have a "select" function mapped to another button.
Is there a solution to this? Any help would really be appreciated.
Thanks

No OK button

The Cruise doesnt have an OK button. I find it frustrating to use the DPAD for scrolling, but then have to reach to the top to tap the OK button in the upper right hand window of the window. Is it possible to remap a hardware button to this task?
I tried AE Button, but it doesnt seem like AE button behaves properly for me on the Cruise.

Does the red phone button not act like an ok button on your phone?

AE Button does work. I use it on my Cruise and have mapped the IE button to become the OK button. One thing I have noticed is that depending on which ROM you are using, sometimes you have to select the "OK/Close" action and other times you have to choose the "Close active application" action.
I Hope this helps

The red phone button does exaclty that.
Why do you map this action also on another button?!
TDO

TDO said:
The red phone button does exaclty that.
Why do you map this action also on another button?!
TDO
Click to expand...
Click to collapse
No, the red button will only minimise the application but it doesn't act like an OK button. In any screen or dialog where you need to press OK, pressing the red button will only take you back to the Today screen and will not press OK. By mapping a hardware button to have the OK feature, the button searches for the OK button on the screen and presses it.

mkhattab said:
No, the red button will only minimise the application but it doesn't act like an OK button. In any screen or dialog where you need to press OK, pressing the red button will only take you back to the Today screen and will not press OK. By mapping a hardware button to have the OK feature, the button searches for the OK button on the screen and presses it.
Click to expand...
Click to collapse
I have Dinarsoft's Handyswitcher for task management. I use the following key mappings to supplement for lack of an OK/Windows Button(s):
Long Press Phone start - HandySwitcher Menu
Messaging Button - Launch QuickMenu
Long Press End button - Suspend
IE button - Close app (using Handyswitcher)

Update: Use AE Button
Thanks for all the suggestions. After reading your thoughts I re-attacked the problem. It turns out AE Button will work. You can set the IE key to be your OK button. Actually AE works great!
The conflict was between AE and S2u2. I did not realize S2U2 has a conflict with AE.
Issue resolved.
I really love the Cruise. I have owned the 3300, 3600, TYTN II and I like the 3300 and cruise the best. Why? The are feature packed and very light. If you dont need a keyboard (and trust me, its overrated to have a keyboard) the cruise is great.

kunicki said:
The conflict was between AE and S2u2. I did not realize S2U2 has a conflict with AE.
Click to expand...
Click to collapse
If you still want to use S2U2, you can use a setup like I posted above. No conflicts using S2U2 and I have the functions that I need without the use of a button mapper application.

Maybe I'm not understanding your problem here, but just map it using the Buttons icon in Settings. There's a choice in there for <Ok>/<Close>. I have the ok button mapped and it works great.

hambola said:
Maybe I'm not understanding your problem here, but just map it using the Buttons icon in Settings. There's a choice in there for <Ok>/<Close>. I have the ok button mapped and it works great.
Click to expand...
Click to collapse
same thing for me, except the O2 Orbit 2 variant actually shows a "Windows" logo button on the left and the "OK" button on the right. i have to map them as such because I'm using a custom ROM.

hambola said:
Maybe I'm not understanding your problem here, but just map it using the Buttons icon in Settings. There's a choice in there for <Ok>/<Close>. I have the ok button mapped and it works great.
Click to expand...
Click to collapse
Let me rephrase that, I mapped the ok "action" to a hardware button. It can be mapped to any button, in my case I just used the top left one (for Voice).

The best for me was to map the left messaging button to win-start, double to messaging, and long press to rotate fo tomtom, the right one to ok, doubleklick to opera, long press to vibratemode.. ... i had the same on my old tytn... works perfekt with aeb-plus.
greets
voxid

Button Mappings - So Far So Good!

Guys, this is what I have done with my button mappings and so far it seems to be working reasonably well. Well, reasonably enough that I am happy with it/can live with it.
Now I am very nit-picky and am coming from a heavily customized WisBar world. But in my quest to be stylus-free (and loving the WOW-factor of TF3D), I am able to live with the device by making the changes listed below.
-+-+-+-+-+
1. AEBPLUS - Volume Buttons
o Remapped volume buttons to provide Up/Down scrolling
o HOLD volume up or down - normal volume control
I did this because the TP was rejecting calls on its own whilst in my holster -- you know, the "press any volume button to mute the ringer" feature.
Note that if you do this, don't forget to look at the "Restore Volume Slider" option in AEBPlus (that guy thought of everything). I have all of mine unticked. Also take a look at: Options|Other Options|Control Volume Directly.
Screenshot: http://auxiliary.razer7.com/aevolume.png
··········
2. AEBPLUS - Phone Key ("Green Phone Button" in AEBP)
o Press once = Phone Button
o Press twice = Task List (Swipe left shows Programs)
o Press three times = Action List <-Note the Cut/Copy/Paste here!
Screenshots:
Task List: http://auxiliary.razer7.com/tasklist.png
Task List - Swipe Left: http://auxiliary.razer7.com/programs.png
Action List: http://auxiliary.razer7.com/actionlist.png
ABOUT THE TASK LIST: The Task List (and Programs list) is all touchable. AEBPlus provides its own task list as well but it isn't as nice as the one that I am using nor is it fingerable. The one that I am using is a freeware program called "MortButtons".
Download MortButtons here:
http://www.sto-helit.de/index.php?module=download&action=list&category=13
NOTE: Don't forget to also download the "ClickLED" skin on the same page. This skin closely matches the TF3D colour scheme.
During my testing, I've noted that MortButton uses about 250K (if you decide to leave it resident (recommended!)) and zero CPU since it is being called by AEBPlus.
ABOUT THE ACTION LIST: The "Action List" (as pictured above) is part of AEBPlus and can be custom-catered to your liking. I like to keep it simple and simply have cut, copy and paste in there, as well as toggle Wi-Fi (which works on the TP).
··········
3. AEBPLUS - End Call Button ("Red Phone Button" in AEBP)
o Press once = End Call
o Press twice = Last Task (ALT-Tab)
o Press thrice = Call DinarSoft TapText*
* "TapText" is a little utility that allows you to create a menu with clippings in it. I used it for email addy's and more. Check it out. I find it very useful and worth the ten bucks to register.
Screenshot of TapText in action: http://auxiliary.razer7.com/taptext.png
-+-+-+-+-+
4. About the Home and OK Buttons...
Now these two buttons *can* be mapped using AEBPlus, however, they can't be *re-mapped*.
In other words, if you map something to these buttons, they will also perform their inherent functions (i.e. the Home button will always go home first; the OK button will always send an OK message to the system, etc.)
Personally, I have left these two alone.
-+-+-+-+-+
CLOSING COMMENTS:
Now there is MUCH MORE you can do with the above two apps in the configuration I've described. Customize it to your delight.
I hope that this post helps some of you guys out. I need to give back to this community!
This community R0X.

Thanks for sharing. Will try this out as soon as possible.

You're very welcome!
I was playing around with this setup earlier today and so far, it has been working really well.
Take care.

I have AEBPlus and it is working great. My home key is mapped to be the start menu on a single press and torch on a long press, the back button closes active applications on a single press. My soft keys are mapped to lock the device and contacts. Works perfectly for me.

I'd already re-mapped the volume buttons as you did, though for a different reason. I use MS Readern often, and find the circular direction button on the TP pretty useless - I try to press arrow down and get the centre keypress instead more often than not. The volume buttons are a perfect substitute.
On tip though - when mapping the volume buttons it works best if you map double click and triple click to none. Doing otherwise gives confusing results.

Excellent post Minus-1, AEBPlus is a program I'd been looking for since getting my touch pro and the Mortbuttons program is proving to be a very useful program itself. one q though on the button options list in AEBPlus which ones cover the touch pros 'home' button and '<-' button

grezz said:
On tip though - when mapping the volume buttons it works best if you map double click and triple click to none. Doing otherwise gives confusing results.
Click to expand...
Click to collapse
Absolutely. I have only single click (directional up or down) and press-and-hold (volume control).
I often double-click the volume button to move up two elements, etc.
Excellent tip. Something definitely worth noting!
P.S. One quick note about the smartwheel: I used to HATE it but now I LOVE it. U have to get used to it and memorize the length of your stroke, etc. Once you do, tho, honestly, doing things become a breeze (especially whilst reading RSS).

yan2k said:
Excellent post Minus-1, AEBPlus is a program I'd been looking for since getting my touch pro and the Mortbuttons program is proving to be a very useful program itself. one q though on the button options list in AEBPlus which ones cover the touch pros 'home' button and '<-' button
Click to expand...
Click to collapse
Hiya, Yan2K!
I'm glad that you're enjoing AEBPlus and MortButtons.
In AEBP, the '<-' is mapped as the "OK Button" (which is precisely what that button means; some people like to call it the "back button" but it actually send a WM_OK message to the system).
As for the HOME button, you will have to map it...
In AEBPlus, go to the FILE|ADD BUTTON menu entry and press your HOME button. The TP will go back to the home screen but don't worry -- AEB is still running. Just click on your Quick Menu in the home screen (upper right corner of your task bar) and switch back to the AEB task.
Now remember: if you map these two buttons, they will NOT unmap their original functions... I generally leave these two buttons alone m'self.
Cheers!

thanks for the quick reply. I've created the 'home' button as you instructed, ended up with 'button #00ED' but cant get it to do anything either on 1-2-3 or long button press nor can i get the 'ok/<-' button to do anything either. prob doing something stupid can you help? ideally i want to be able to run a program on a long 'home' key press

Well mine is working, but not when TF3D is the active application. I remaped the (Long press) Home butoon to Second Today, and when I press it (long) it opens Second Today. Again, only when the TF3D is *not* the active program.
Hope that makes sence...
Cheers,
Cacti
yan2k said:
thanks for the quick reply. I've created the 'home' button as you instructed, ended up with 'button #00ED' but cant get it to do anything either on 1-2-3 or long button press nor can i get the 'ok/<-' button to do anything either. prob doing something stupid can you help? ideally i want to be able to run a program on a long 'home' key press
Click to expand...
Click to collapse

Mapped the volume buttons as you did. Just what I was looking for. Also set 'back' to proper 'ok/close'.
Cheers.

I think,the original functions are hardcoded somewhere(dll or something else). We need to find the file and modify it to disable these functionalities.

I remapped the "green" button the following way:
1 press) Phone application
2 presses) Alt+Tab
However, now when there is an incoming call I can't use it to answer. Which is quite logical.
Is there a way around this?

le_cactus said:
Well mine is working, but not when TF3D is the active application. I remaped the (Long press) Home butoon to Second Today, and when I press it (long) it opens Second Today. Again, only when the TF3D is *not* the active program.
Hope that makes sence...
Cheers,
Cacti
Click to expand...
Click to collapse
played around with it and found purely by chance that just like you said you cant use the home button or '<-/ok' button to do anything when you've actually got the TF3D home screen showing. hopefully someone will come up with a workaround for this as although i can make use of the '<-/ok' button it pretty much makes the 'home' button redundant for anything else but its original purpose

yan2k said:
played around with it and found purely by chance that just like you said you cant use the home button or '<-/ok' button to do anything when you've actually got the TF3D home screen showing. hopefully someone will come up with a workaround for this as although i can make use of the '<-/ok' button it pretty much makes the 'home' button redundant for anything else but its original purpose
Click to expand...
Click to collapse
Oh man, the OK button is one of the buttons I miss the most.
Specially while texting and such.
I hope I can remap some of the full keypad buttons as well.
I noticed that it sometimes doesnt' start up well, but oh well.
I re-maped the volume down to Ok/Close and Volume up to Start Menu
Then changed the volume settings to long hold, Which half the time when i press the buttons the volume comes up. haha.

hello!
I want to remap some buttons and I've tried with AE button Plus without success. Can you help me?
What I have is the call button configured for a long press to cyberon voice dial.
The disconnect button long press is for vibrate / ring.
what I want is to turn home and back buttons long press to wifi and bluetooth on/off and.
is it possible?
can I do this without AE button +? like a registry change? would be even better... or another program suggestion is also a good help!
Please help!
deiota

Is it able to remap the PTT button? That would be AWESOME.

dumb question, but where can I download AEB Plus?
I can't find a direct link or site to get the program!
Thanks...

http://ae.inc.ru or ask directly the author AE(here on XDA-Alexander Eltsyn).

So, is there any way to change the mapping on my keyboard? Like the hot button keys really get in my way, and I'd rather have a TAB key than a CAPS key, and stuff. So is this possible yet?

[Q] HTC TD2 Button mapping?

Hey everyone! Im new in smartphone world, so i need your help.
Problem is that I dl-ed a game (tomb raider) and it requires arrow keys to move, but TD2 doesn't have arrow keys. I tought maybe its possible to assign left and right keys on volume buttons and up and down keys on call button and home button.
Except that they should only be like that in games.
So if you know how this can be done, then I would be grateful for your replies.
Thank you!

Your take on the perfect (Android) button placement?

Back button on the far left? Second from the right?
Power button on the top? On the side?
Softkeys or real buttons? On-screen (a la Honeycomb) or off-screen?
Do we need a search button at all?
A lot of sweat, blood, and saliva has been spilled over it. [citation needed]
Now it's *your* turn to join the fray!
If you were to design *the* perfect Android phone, what buttons would you give it? And where? And what would it be like?
Or maybe you don't even care about how the buttons are placed, as long as the manufacturers could just agree and they all make devices with similarly-placed buttons?
Me? I'd personally place the buttons sorted by their frequency of use, starting from the leftmost to the rightmost (from the most natural to the most awkward for my thumb to press). Back button - Home - Menu - Search, from left to right.
But I see how this would be an issue to left-handed people, so I'd settle for Back and Home button in the center, and Menu and Search flanking them. That's fair enough I think.
I would love to experiment with placing the back button on the top of the left side of the phone (indexable for right-handed people, and thumbable for left-handed), but I can see how this is not for everyone I'm not even sure I'd like it.
However, if manufacturers could just agree on the placement of the buttons, that would be good enough for me.
Whether it's hardware buttons or touchscreen buttons ain't an issue to me.
I'd place the power button top center (index-fingerable).
I find volume buttons useful only during calls, so I'd like to have them function as volume buttons only during calls. During idle/homescreen/any other scenario, they would become two (customizable!) shortcut buttons (a la Blackberry). <-- if only one thing from my dream phone is manifested, I hope it's this one. Two wasted (and often pressed by accident) buttons, turned into something more useful.
If I wanna be detailed about it, I guess the volume buttons should be on the center of the right side of the phone, so one of them can be customized as shutter/camera button (although I wont use it as such, preferring to tap the screen instead).
How's yours?

I think power button on top right side, lock button under, or like you mentioned having them function as volume buttons during call. Do completely away with search button, add in maybe a camera button where my search is, but make it where you have to hold it for a second so you do not enable it accidently. Have a designated capture button for the camera, that also functions as a silent/vibrate setting out of the camera.
Sent from my SCH-I500 using XDA App

Different people, different preference. Perhaps a default Home key, + 2 customizable keys where the user can choose their preferred key to be assigned.
I'd have the Search Key and Back Key always on the screen.
Menu key shouldn't even be on the phone. That should force app developer to design and create user interface with menu function incorporated in their app for consistency purpose.

I would love to have buttons on the back of the device

Now that I'm getting used to honeycomb (and apps developed for it), i can assure you that the search and menu buttons are not really necessary. i'd want a device with a back button on the left, the home button in the middle and a end call / power button on the right. that's it. oh i actually forgot a volume rocker at the usual spot at the side of the device.

Dustin.Dwayne said:
I think power button on top right side, lock button under, or like you mentioned having them function as volume buttons during call. Do completely away with search button, add in maybe a camera button where my search is, but make it where you have to hold it for a second so you do not enable it accidently. Have a designated capture button for the camera, that also functions as a silent/vibrate setting out of the camera.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hmm.. No search button.. Interesting.
I find it useful to search things from the homescreen without having to open a particular app first (be it Market, Springpad, Contacts, Evernote, etc.), but I can surely live without it
albling said:
Different people, different preference. Perhaps a default Home key, + 2 customizable keys where the user can choose their preferred key to be assigned.
I'd have the Search Key and Back Key always on the screen.
Menu key shouldn't even be on the phone. That should force app developer to design and create user interface with menu function incorporated in their app for consistency purpose.
Click to expand...
Click to collapse
Customizable keys FTW!!
JuanDeaux said:
I would love to have buttons on the back of the device
Click to expand...
Click to collapse
Wouldn't that be awkward, Mr. Doe?
fabsn said:
Now that I'm getting used to honeycomb (and apps developed for it), i can assure you that the search and menu buttons are not really necessary. i'd want a device with a back button on the left, the home button in the middle and a end call / power button on the right. that's it. oh i actually forgot a volume rocker at the usual spot at the side of the device.
Click to expand...
Click to collapse
Oh, you even made the pic!
Your opinion is interesting. I can easily see why the search button isn't really necessary, but the menu button? Substituted by long-press, I presume? (I never tried Honeycomb for any longer than 2 minutes )
I'm beginning to get glimpses of what ICS is gonna be like Keep it coming, guys! Let's crowdsource this!
Thanks to the moderator who moved my thread. I was hesitant on where to put my thread, but finally decided on the "General" forum, even though my OP contains questions, because I thought it was more of a "discussion" thread instead of a particular question trying to uncover a particular answer (which is what Q&A usually is)