Database Users

Which buttons can be assigend by AE Button Plus?

In AE Button Plus I only could assign the two phone buttons. What about the "Home Button", "Back Button", "Calendar" and "Contacts"?

The back button can be assigned. Assign things to the "OK-button" i AE Button Plus to assign it to the back button.

Great! Thank you very much.

Hi, here is a reply on AEB Plus compatibility with the HD direct from the developer:
---------------------------
Hello David,
Thanks, it is always nice to know if you find this utility interesting
As for your question: yes, BPlus is compatible with HD as well as any other PocketPC 2k3 / PocketPC 2k3SE / WM5/WM6/WM6.1 devices.
The problem I know on Touch HD:
- Home key may not be remapped due to driver implementation
- Long keypresses are not detected in BPlus for green/red keys and “back” button (button driver limitation).
- “Back” button corresponds to the “Ok” in button list so you will not need to add it via File->Add key but just re-define “Ok” button instead
- Backlight controlling will work in next BPlus release (should appear this week)
Anyway – just try and install BPlus to check if it will suit your needs before buying. It have very few “demo” mode limitations...
Regards,
Alexander
----------------------------

all keys except home key works great on mine

By "all keys" you mean:
- left phone key
- back key
- right phone key?

mirandolo said:
By "all keys" you mean:
- left phone key
- back key
- right phone key?
Click to expand...
Click to collapse
Don't forget the Volume Buttons (long-press DOES work for those two)

Hi guys,
I played around with AE Buttons for a couple of hous last night and here's my experience:
- Volume up/down - Work like a charm.
- Home buttom - Can't be mapped.
- Back key - Didn't realize it was mapped to the Ok button. I tried it out tonight. Works fine, but I'm not sure what action should I put in the single press configuration to preserve it's normal function. "Ok/Close" a suppose. Can someone confirm, please ?
- Green/Red phone - work fine in single, double and triple press
- Green phone long press is mapped by the driver to a virtual button called "Button 1(Hold)" (It's just at the top of the AE Buttons list) and by default launches the voice dial program (this is defined in the Settings/Personal/Buttons/Program Buttons)
- Red phone long press - This is a tough one. This button can't be captured unless you set "Lock device" in Settings/Personal/Buttons/End key. In this case it generates a key code and you can record it as a new key in AE Buttons. There's a catch though. When you map an action to single press, Lock program is no longer executed. Your selected action is executed, but immediately after that the device goes to the today screen as if you have pressed the Home button.
- Power button - Can't be mapped at all. I wish this was possible. I wanted to make long pressing the power button to soft reset the device directly.
Hope this info is useful. It took me a couple of hours and A LOT of soft resets to try all the possible combinations

triffonovm said
[- Back key - Didn't realize it was mapped to the Ok button. I tried it out tonight. Works fine, but I'm not sure what action should I put in the single press configuration to preserve it's normal function. "Ok/Close" a suppose. Can someone confirm, please ?]
Confirmed.
John R

triffonovm said:
Hi guys,
I played around with AE Buttons for a couple of hous last night and here's my experience:
- Volume up/down - Work like a charm.
- Home buttom - Can't be mapped.
- Back key - Didn't realize it was mapped to the Ok button. I tried it out tonight. Works fine, but I'm not sure what action should I put in the single press configuration to preserve it's normal function. "Ok/Close" a suppose. Can someone confirm, please ?
- Green/Red phone - work fine in single, double and triple press
- Green phone long press is mapped by the driver to a virtual button called "Button 1(Hold)" (It's just at the top of the AE Buttons list) and by default launches the voice dial program (this is defined in the Settings/Personal/Buttons/Program Buttons)
- Red phone long press - This is a tough one. This button can't be captured unless you set "Lock device" in Settings/Personal/Buttons/End key. In this case it generates a key code and you can record it as a new key in AE Buttons. There's a catch though. When you map an action to single press, Lock program is no longer executed. Your selected action is executed, but immediately after that the device goes to the today screen as if you have pressed the Home button.
- Power button - Can't be mapped at all. I wish this was possible. I wanted to make long pressing the power button to soft reset the device directly.
Hope this info is useful. It took me a couple of hours and A LOT of soft resets to try all the possible combinations
Click to expand...
Click to collapse
I encountered the below problem.
After receiving or making a phone call, the button did not work for around 5 minutes. Instead of move the arrow up or down, it turn the volume up/down. After that the button work again as what I had configured.
Anyone having the same problem?

Regarding the back key. I have this not mapped for one touch, i.e., normal OK operation, and for double press I have it rotate the screen.
I don't like gsen and the gyrator - great apps but I just don't need them always there.

dannyng said:
I encountered the below problem.
After receiving or making a phone call, the button did not work for around 5 minutes. Instead of move the arrow up or down, it turn the volume up/down. After that the button work again as what I had configured.
Anyone having the same problem?
Click to expand...
Click to collapse
I have this problem too! Any solution to share?

That's weird - I have just tested and all the AEB Plus assignments worked before a call.
After a call the volume assignments I have (1 press = arrow up/down, 2 press = volume up/down, long press up = flash lamp, long press down = resco audio) don't work. All the volume presses just revert to the volume operation.
I also have the back/OK key assigned to screen rotate for double press. This works fine after the call.
So, status now is not working right - I'll wait and see if it fixes itself (!!) with a few minutes.

Cheesy Dave said:
That's weird - I have just tested and all the AEB Plus assignments worked before a call.
After a call the volume assignments I have (1 press = arrow up/down, 2 press = volume up/down, long press up = flash lamp, long press down = resco audio) don't work. All the volume presses just revert to the volume operation.
I also have the back/OK key assigned to screen rotate for double press. This works fine after the call.
So, status now is not working right - I'll wait and see if it fixes itself (!!) with a few minutes.
Click to expand...
Click to collapse
I found the fix. In AEB + there is a set of options. One of these is the "restore volume slider" - by default this restores volume control to the phone app. It appears not to reset it back after.
I have just turned all these "restore volume slider" options off and now AEB Plus works as it should (or as I expect).

Thanks for the fix!
I shall try it tonite!

Cheesy Dave said:
I found the fix. In AEB + there is a set of options. One of these is the "restore volume slider" - by default this restores volume control to the phone app. It appears not to reset it back after.
I have just turned all these "restore volume slider" options off and now AEB Plus works as it should (or as I expect).
Click to expand...
Click to collapse
I just tried it and it doesn't work. I guess it's a bug and need to be fixed by the developer. Hmmmm, just suprised that no one really notice this bug.

Same bug on volume up. I assigned 1P for standard function and 2P for WiFi toggle. Well after the first or second use, it looses mapping. To have it to work again a soft reset is needed...

Cheesy Dave said:
I found the fix. In AEB + there is a set of options. One of these is the "restore volume slider" - by default this restores volume control to the phone app. It appears not to reset it back after.
I have just turned all these "restore volume slider" options off and now AEB Plus works as it should (or as I expect).
Click to expand...
Click to collapse
Thanks a lot mate! Works purrfect! had the same problem going on.

Insane Devil said:
Thanks a lot mate! Works purrfect! had the same problem going on.
Click to expand...
Click to collapse
I'm glad this is working for some.
But, I got an email from the developer (who is very quick to respond to emails) that said he is aware of a fault with the phone interaction and has not been able to replicate it.
Removing the volume slider option for the phone might work (as it did for me) but it seems that the intermittent fault probably will remain.

Cheesy Dave said:
I'm glad this is working for some.
But, I got an email from the developer (who is very quick to respond to emails) that said he is aware of a fault with the phone interaction and has not been able to replicate it.
Removing the volume slider option for the phone might work (as it did for me) but it seems that the intermittent fault probably will remain.
Click to expand...
Click to collapse
Glad that it work for you (so envy, hehehehe) and thanks for the email to the developer.
Wondering why some HTC HD working (removing the volume slider option) and some not (like my case )

Remapped vogue buttons - DONE

Update: http://rapidshare.com/files/265248702/zImage-08-08-09-custom
No changes on my end, just updated to today's kernel source and repatched.
Here is the better version:
After trying a variety of combinations of keys, shifting, etc...I've come up with what *I* like best. There are plenty of better ways, if I could get them to work, but I've ended up with some severe limitations:
- Can't use shift with call, end, power or camera buttons
- Can't detect long vs short keypress
So, I've disabled shifting entirely. Yes, I loose a couple keys (home and left rotate...home can be done with end if setup to do so, and I don't care about rotation that much).
Everything is the same as the default builds except:
- Power is menu instead of home
- Volume keys do volume control
- Camera is back
Included in the file is the two source files I've changed, which go in kernel/arch/arm/mach-msm
Anyone else who knows how to compile the kernel should be able to change the layout...if you need help, let me know and I'll do what I can.
----- Original post -----
I've slightly remapped the vogue's buttons.
Before we start, I want to be clear: This is a dirty hack. The buttons are not customizable. But IMHO it's better than what we have.
Just download (see above for new link) and replace your existing zImage.
All I did was swap the GPIO settings in vogue-board.h
Add this to the bottom of the file, and comment out the original #define lines near the top.
Code:
#define GPIO_VOLDN 29
#define GPIO_POWER 41
#define GPIO_VOLUP (VOGUE_GPIO_MISC5_BASE+7)
#define VOGUE_GPIO_CAM_BUTTON 42
Power and volume down switched.
Camera and volume up switched.
Power = Menu
Camera = Back
To rotate screen, use vol up + left.
To change volume, use vol up + power or camera.
For me, this will result in much less use of the volume keys, saving some wear and tear.
Hope you like it!
Edit: Seems volume down is the only key that will turn the screen back on now...will look into fixing that.

I think I'll pass. I'm sure some people will like it better, but I like the idea of my volume keys being associated with the audio volume, even if I have to use a shift-key to do it.

craig0r said:
I think I'll pass. I'm sure some people will like it better, but I like the idea of my volume keys being associated with the audio volume, even if I have to use a shift-key to do it.
Click to expand...
Click to collapse
Hopefully that will happen eventually.

This is definitely a step in the right direction though, my volume slider is starting to get pretty shaky. Its got lots of side to side movement.

grantemsley - finally something i wanted to get done for a long time, can u pls explain how you did it - this is the combination i like, seeing that i dont use the d-pad much (with a nice touch screen and all.... )
i like the d-pad - down : menu
d-pad - up : back
volume up : volume up
volume down : volume down
power : power
camera : rotate screen
pls help me customize my zImage. what do I need to package the zImage already available..

myshinynewtouch said:
grantemsley - finally something i wanted to get done for a long time, can u pls explain how you did it - this is the combination i like, seeing that i dont use the d-pad much (with a nice touch screen and all.... )
i like the d-pad - down : menu
d-pad - up : back
volume up : volume up
volume down : volume down
power : power
camera : rotate screen
pls help me customize my zImage. what do I need to package the zImage already available..
Click to expand...
Click to collapse
I like this idea, although I occasionally use the d-pad. No way to add a shift to make the d-pad still the d-pad, or use a long press or something? Or is that too complicated for the fix atm?
I should start reading about android coding.

myshinynewtouch said:
grantemsley - finally something i wanted to get done for a long time, can u pls explain how you did it - this is the combination i like, seeing that i dont use the d-pad much (with a nice touch screen and all.... )
i like the d-pad - down : menu
d-pad - up : back
volume up : volume up
volume down : volume down
power : power
camera : rotate screen
pls help me customize my zImage. what do I need to package the zImage already available..
Click to expand...
Click to collapse
This control scheme looks very appealing to me as well...+1
Grantemsley, could you post another zImage with this config?

I'm currently at work at my real job, but playing with the code a bit in between things. I'm working on rewriting this the proper way, so that I can add additional shift keys.
There are two things I need to know:
- Where is the code that controls which button(s) will turn the phone on from standby. If I remap the power button, I end up with no buttons able to turn the phone on...I basically can't continue without finding this.
- Assuming we have any 1 key as a "shift" key, and every other key is remappable, what do you think the ideal layout would be?
Note: This will never be user configurable unless someone else figures that part out...but we can compile our own kernels with our preferred layout.

myshinynewtouch said:
i like the d-pad - down : menu
d-pad - up : back
volume up : volume up
volume down : volume down
power : power
camera : rotate screen
..
Click to expand...
Click to collapse
I would vote this layout - keeping the power button as it currently is, but change the camera butto9n back to being the [alt] key for rotating, etc... just so that there were a few more options.
The d-pad up and down for back and menu respectively is what I am REALLY looking forward to.... and the volume switch back to controlling volume.

grantemsley said:
I'm currently at work at my real job, but playing with the code a bit in between things. I'm working on rewriting this the proper way, so that I can add additional shift keys.
There are two things I need to know:
- Where is the code that controls which button(s) will turn the phone on from standby. If I remap the power button, I end up with no buttons able to turn the phone on...I basically can't continue without finding this.
- Assuming we have any 1 key as a "shift" key, and every other key is remappable, what do you think the ideal layout would be?
Note: This will never be user configurable unless someone else figures that part out...but we can compile our own kernels with our preferred layout.
Click to expand...
Click to collapse
Power: Power
End: End/Power Off
D-Pad Up: Back
D-Pad Down: Menu
D-Pad Left: Rotate
D-Pad Right: ?
Camera: Shift
Shift + D-Pad: Standard D-Pad
That's how I see it being ideal.

grantemsley said:
I'm currently at work at my real job, but playing with the code a bit in between things. I'm working on rewriting this the proper way, so that I can add additional shift keys.
There are two things I need to know:
- Where is the code that controls which button(s) will turn the phone on from standby. If I remap the power button, I end up with no buttons able to turn the phone on...I basically can't continue without finding this.
- Assuming we have any 1 key as a "shift" key, and every other key is remappable, what do you think the ideal layout would be?
Note: This will never be user configurable unless someone else figures that part out...but we can compile our own kernels with our preferred layout.
Click to expand...
Click to collapse
K, I dunno where the code is, so I can't answer that... but as for my ideal layout:
- Keep Camera button as shift
- Volume key does volume (non-shifted)
- Power button is Home
- Shift-Left is "back"
- As for suspend... I dunno, maybe double-tap the power button? Or just leave it as the Red key.
As far as never being user configurable... I'm not too certain how this all fits into the kernel, but if it could be incorporated as a module rather than built into the kernel, then that could be overcome. It wouldn't be simple. We'd need a UI front-end, which would be easy enough, but the back-end would essentially have to edit the kernel source, rebuild then reload the module. And even that probably isn't possible, as I'm quite sure android doesn't include gcc.

You guys really use the dpad that little? I use it all the time while web browsing.

TheKartus said:
Power: Power
End: End/Power Off
D-Pad Up: Back
D-Pad Down: Menu
D-Pad Left: Rotate
D-Pad Right: ?
Camera: Shift
Shift + D-Pad: Standard D-Pad
That's how I see it being ideal.
Click to expand...
Click to collapse
I see a few people want to map functions to the non-shifted D-Pad. This makes no sense to me. I like having the D-Pad as a D-Pad. My ideal configuration would make my phone usable to anyone I hand it to. My biggest beef with the current key layout has nothing to do with me using the phone, as I'm used to it... but I like to show off android to people, and it's kinda lame when they can't figure out what the buttons do without me explaining. I'd like it to be simple for someone to pick up an Android Vogue and just use it. Of course, there's no button physically labeled "Menu," so the lock screen will always be confusing to them.

grantemsley said:
You guys really use the dpad that little? I use it all the time while web browsing.
Click to expand...
Click to collapse
Yeah, I used the D-Pad all the time in WinMO, but since switching to Android, I don't touch it, unless I'm playing a game or something. If it doesn't make sense to re-map the d-pad, I'm good with that. Using the camera button for back kind of makes sense, or even the shift-left combo...
If my volume rocker gets less use than currently, it's all good.
Edit: I browse using the touch screen only and it is very accurate, even zoomed out...
Also, I don't ever hand the phone over to someone else anymore, because it NEVER seems to make sense to them, but I can see Craig0rs point...

TheKartus said:
Power: Power
End: End/Power Off
D-Pad Up: Back
D-Pad Down: Menu
D-Pad Left: Rotate
D-Pad Right: ?
Camera: Shift
Shift + D-Pad: Standard D-Pad
That's how I see it being ideal.
Click to expand...
Click to collapse
I like this layout best, so that's a +1 from me. That volume toggler wasn't made for industrial use like the d-pad and I really don't use the d-pad to select items very often since I can just touch what I want.
Also, I'm glad you guys started talking about the shift key...because in all the frigging reading I've done on android over the last week, I have somehow managed to miss that the camera button is the shift key for volume toggle ["head banging on wall"].

rhorton said:
Yeah, I used the D-Pad all the time in WinMO, but since switching to Android, I don't touch it, unless I'm playing a game or something. If it doesn't make sense to re-map the d-pad, I'm good with that. Using the camera button for back kind of makes sense, or even the shift-left combo...
If my volume rockjer gets less use than currently, it's all good.
Click to expand...
Click to collapse
Going back though is a function used very commonly, it would be a pain to have to hold a shift/alt button in order to go back.
I understand people not wanting to remap the dpad, and craigOr has a point about usability.
How about something like this:
Volume Up: Up
Volume Down: Down
Power: Wake, Home
End: Suspend, End
Camera: Back, Shift?
Camera + Left: Rotate
D Pad: D Pad
Is it even possible to make the camera function as back if pressed, and a shift if held?

My ideal layout would be:
Power: single press for suspend/resume.....long press for power off menu.
Volume slider: volume
Send: single press for phone dialer.......long press for home
End: single press for end call....long press for menu
Camera: single press for back.......long press for rotate:
Dpad: dpad
Center button: single press for select.....Long press recent programs

zenulator said:
My ideal layout would be:
Power: single press for suspend/resume.....long press for power off menu.
Volume slider: volume
Send: single press for phone dialer.......long press for home
End: single press for end call....long press for menu
Camera: single press for back.......long press for rotate:
Dpad: dpad
Center button: single press for select.....Long press recent programs
Click to expand...
Click to collapse
I was under the impression that the Red key's function gets changed by android depending on whether it's in a call or not. This would cause a huge problem with your layout, as it would take a lot more work to get the menu up during a phone call.

Thus far, I do not know how to do long keypress vs short keypress.
Also, there has to be at least 1 button that is not shiftable...which will be the button used to wake up from standby (since I still haven't gotten the dev tools working right, I can't tell why shiftable keys aren't waking the device up...)

zenulator said:
My ideal layout would be:
Power: single press for suspend/resume.....long press for power off menu.
Volume slider: volume
Send: single press for phone dialer.......long press for home
End: single press for end call....long press for menu
Camera: single press for back.......long press for rotate:
Dpad: dpad
Center button: single press for select.....Long press recent programs
Click to expand...
Click to collapse
When thinking about layouts I was under the impression that we had to keep the same functions, just move them to different keys. If the power button could suspend and wake the phone, that would be ideal... but is it possible to change all the different functions around like that?

[APP] AE Button Plus to reassign EVERY physical button

Hello everyone, I'm sure many people will be interested to know that AE Button Plus is working perfectly with LEO and support english, french (which I use), spanish, deutsch and ten other languages. BTW, this is my first post, so every comments are welcome
The HD2 may be a touch device, it still has 7 buttons and I use them for variaty of functions, including switching on/off BLUETOOTH, WIFI or TORCH. You can even assign any button to run an application. The program is VERY stable and VERY convenient.
This exceptional app has the ability to reassign function to (almost) every physical button of your device, including the volume button. Moreover, it has the ability to assign different functions whether you press the button ONCE, TWICE or LONG PRESS. It very simple to use and work wonderfully with my HTC HD2 (as wall as many other Windows Mobile Device). I've used it for more than a week and I can't report any bug, even though I installed many other apps, tweak and so on.
I'm using the evaluation version (you have pay 7.99$) by the fact that it shows a splash screen when device starts up. But you can believe I will pay the damn Russian guy who created the app, many even donate more!!!
I wanted to share my experience with using this app, since it's not very known in this (great) HD2 forum. Also, I want to show you the way I've been remapping the buttons, to show how useful it can get. Feel free to comment!!! Once you install the program, softreset and assign the AEBPlus to a shortcut and you're ready to rock! By the way, the icon is quite ugly, but that's just a minor issue .
THIS IS THE WAY I REMAPPED HD2 BUTTONS (in brackets, the way AEPlus "calls" the button)
Volume up.
Single press: volume up
Long press Backlight up
Volume down.
Single press: volume down
Long press Backlight down
Hang up (green phone button)
Single press: switch vibration mode on/off (and shut down the volume)
Double press: switch torch on/off (run application "TorchButton v2.3")
Home button (button #00ED), added manually
Single press: unchanged, impossible to remap ??
Double press: switch bluetooth on/off (impossible to make it different than the "Home button"...)
Long press: impossible to remap ??
Windows button (windows key)
Single press: ok/close (close the window, but not the program still runs)
Double press: windows file explorer (you can choose to run another explorer, for example Total Commander)
Long press: close active application ("really" close the application)
Return button (also button #00ED, added manually, see ISSUE below)
Single press: unchanged (actually I chose no action, but the original function remains)
Double press: switch bluetooth on/off
Long press: switch wifi on/off
Power button (red phone button)
Single press: unchanged (shuts down backlight)
Double press: unchanged
Long press: unchanged (actually, I use it with "Touch X LEO Power 12 icons actionscreen v1.1")
KNOWN ISSUES AND SOLUTIONS
- Absolutely no bug !
- Bluetooth. The function included with this program doesn't work (apparently because HD2 uses Widcomm bluetooth, unlike its predecessors). To solve this, I simply assign the desired button with the application "ToggleBTh.exe" (credit to Dextrosan http://forum.xda-developers.com/showthread.php?t=587493). I copied the file to the folder "Program Files" and created a shortcut in the "windows/start menu/programs" to be able to make it appear in the program list.
- Backlight level. To adjust the backlight, you have to access the settings of the program. Click options -> backlight settings (scroll down !). There you can adjust the darkest level you wish (0 = minimum backlight) and the brightest level (10 = 100% = maximum backlight , less if you want to save battery life) and backlight step (2 = 20% is fine with me). Beware, when you assign a button with function backlight level, you have to choose in the subsequent menu if you want "backlight down", "backlight up" or even "backlight level" 0, 2 (= 20%), 4 (= 40%) and so on.
- Manually add Home button. Home button is not listed in the program, so you have to add it manually. Choose "File -> Add button" and follow instructions. Actually, there's a trick... If you press the Home button, it will close the window and go back to your home page. You'll have to go back in the program using the task manager.
- Home and Return button cannot be remapped individual. For some reason, when you manually add Home button, it's called #00ED and when you assign actions, these actions also work with the Return button... Actually, these actions even work BETTER on Return button than Home button. Single press and Long press actions will not work with Home button, but they work with Return button. Weird, huh? Even if you manually add Home button (then called #405C) and assign actions for the button, it won't work at all, and the Return will still execute actions listed with the button #00ED. All in all, it's a minor issue. Just remember that I can't remap single or long press for teh Home Button.
EDIT: Dec, 20 I also use the function "control volume directly" so that the volume buttons control SYSTEM volume directly and not the ring volume. Also, this nice function disable the ugly pop-up volume window that appears and have the annoying tendency to change ring volume first !!! This function is located in the menu "Options -> Other options -> Control volume directly". You can check or uncheck it.
That all folks, hope this little work will be useful for many.
Much help is appreciated to try to solve the Home/Return button issue.
SIGNATURE
- Device: HTC HD2 codemane "Leo"
- Rom: 1.48.406.1 (7 1294) FRE
- Manila: 2.5.192 116 19.0
- Radio: 2.05.51.05_2
INSTALLED SOFTWARES & TWEAKS
- Net 3.7 Compact Framework
- AE Button Plus 2.6.6.1
- BsB Tweaks v1.5
- TorchButton v2.3 (use your flashlight as torch, SOS etc...)
- Total Commander 2.51
- WMLongLife-0.60.205 (fine connexion manager)
- Touch X LEO Power 12 icons actionscreen v1.1

is their a way to config the take picture on screen button a hardware button

DAMIEN123_666 said:
is their a way to config the take picture on screen button a hardware button
Click to expand...
Click to collapse
Of course, as long as you find an exe which does that automatically whenever invoked. You can do pretty much anything as long as you can associate it with a specific utility. I use the program with my ipaq 210 and am very pleased with it, with a resistive screen it's even more useful.
Now, if only I wasn't dead-dumb enough to let slip from my hands this leo for 430EU on ebay... who knows how long will I have to wait to find another one at that price.

theemed said:
Of course, as long as you find an exe which does that automatically whenever invoked. You can do pretty much anything as long as you can associate it with a specific utility. I use the program with my ipaq 210 and am very pleased with it, with a resistive screen it's even more useful.
Now, if only I wasn't dead-dumb enough to let slip from my hands this leo for 430EU on ebay... who knows how long will I have to wait to find another one at that price.
Click to expand...
Click to collapse
ok ive can boot the camera app but cant take picture, any ideas

I'm using this program also for a while.
I'm used to use the power/hangup red button to go back to the today screen but can't find a way to get that working.
It takes me a while to figure out the working posibilities but it's useful anyway.
Great post! Thanks for sharing with us.

Disable the volume window !
I also use the function "control volume directly" so that the volume buttons control SYSTEM volume directly and not the ring volume. Also, this nice function disable the ugly pop-up volume window that appears and have the annoying tendency to change ring volume first !!! This function is located in the menu "Options -> Other options -> Control volume directly". You can check or uncheck it.

Thx for all.
It works very well

DAMIEN123_666 said:
ok ive can boot the camera app but cant take picture, any ideas
Click to expand...
Click to collapse
uhm, sorry no idea you still need to associate that hardware buttom combo through AE with an executable file which takes the shot, it's up to you to find a exe trigger for that

rzasharp said:
Hello everyone, I'm sure many people will be interested to know that AE Button Plus is working perfectly with LEO and support english, french (which I use), spanish, deutsch and ten other languages. BTW, this is my first post, so every comments are welcome
...
Click to expand...
Click to collapse
can you share you aebutton config file? i don't install it, i just copy it from my old device (eten) but there not enough default buttons

rzasharp said:
Hello everyone, I'm sure many people will be interested to know that AE Button Plus is working perfectly with LEO and support english, french (which I use), spanish, deutsch and ten other languages. BTW, this is my first post, so every comments are welcome
...
Click to expand...
Click to collapse
your first post is excellent. this realy helped me.
i've almost forgot about aebutton on my used blackstone. hd has no true hard keys. now i have a leo and aebutton came back with me. i can confirm that aebutton works perfectly on my leo. even more than i need.
rzasharp said:
...
- Bluetooth. The function included with this program doesn't work (apparently because HD2 uses Widcomm bluetooth, unlike its predecessors). To solve this, I simply assign the desired button with the application "ToggleBTh.exe" (credit to Dextrosan http://forum.xda-developers.com/showthread.php?t=587493). I copied the file to the folder "Program Files" and created a shortcut in the "windows/start menu/programs" to be able to make it appear in the program list.
...
Click to expand...
Click to collapse
if you already have Touch X LEO Power 12 icons actionscreen then no need for you to use togglebth. touch x leo power 12 icons have wifi and bluetooth toggles working well on leo.
rzasharp said:
- Home and Return button cannot be remapped individual. For some reason, when you manually add Home button, it's called #00ED and when you assign actions, these actions also work with the Return button... Actually, these actions even work BETTER on Return button than Home button. Single press and Long press actions will not work with Home button, but they work with Return button. Weird, huh? Even if you manually add Home button (then called #405C) and assign actions for the button, it won't work at all, and the Return will still execute actions listed with the button #00ED. All in all, it's a minor issue. Just remember that I can't remap single or long press for teh Home Button.
...
Much help is appreciated to try to solve the Home/Return button issue.[/B]
...
Click to expand...
Click to collapse
ok. so we have something special on our leos.
- htc sense.
- green button - send key.
- red button - end key.
- home button. this key is stucked with htc sense.
- back button.
1. green button.
i can do any thing with this key. but i leave long press unchanged beacause my vangrieg_incall_lock_ita had added long_send.lnk that link to phone on my \windows and i don't want to interfere into it. now long press on send key = phone. this is a vital function, right? so let it be.
2. red button.
i can't do any thing, but "Touch X LEO Power 12 icons actionscreen" can.
so for me end key has single press as normal and long press by "Touch X LEO Power 12 icons actionscreen". that is more than enough. power off is a vital function also.
3. home button.
as said, this key is stucked with htc sense. so you can not change single press anyway. you can do somethings with double, triple and even long press but firstly it takes you to home screen then do your commands. for long press see next item.
4. back button.
this is exactly "ok key" on aebutton. you even don't need to add it manually. you can do everything with this key except long press. long press works only when you are on a certain program interface. this does not work when you are on htc sence interface. to get this long press work on anything, anywhere and anytime you have to assign the same action you want to do to HOME KEY LONG PRESS. and voilà !!! this works 4u.

Thanks for your appreciation of my thread.
Still, If you are really "hardcore hardware fan" you can use AEBPlus to assign even the double tap and triple tap of the keys
To oainot. About the bluetooth toggle, If find it quicker and simpler, to double tap on one button, turn on my headphones and get going out in the snow. I use it literally everytime If get out of my apartment. Just think: would you prefer to switch the light off your apartment with a long-click (+ click in a menu) or with a simple double-click? Just a matter of taste I guess. The best is to have to choice!
To satoo. Here's my configuration file. I should tell you that my system is in french. I managed to put "english" as language in the program, but you can still get some french word (calculatrice = calculator i think; Explorateur de fichiers = file explorer; ). See attached file.
Merry Christmas!

oainot said:
if you already have Touch X LEO Power 12 icons actionscreen then no need for you to use togglebth. touch x leo power 12 icons have wifi and bluetooth toggles working well on leo.
Click to expand...
Click to collapse
I am in entire agreement with you.
one key like hold red key ,we can switcher wifi on/off, bt on/off.
So，in an identical manner，
I set one key (ex:hold vol up) to active phoneweaver ,with which i set some usefull profiles :
mute mode: switch vibration mode
day mode: loudly volume
night mode: max or min backlight level as you like
.......
each mode we can define (backlight level,vol lvl,differents rings,wifi on/off,bt on off)
here is phoneweaver 2.0 with XXXX，sorry for my english

oainot said:
your first post is excellent. this realy helped me.
Click to expand...
Click to collapse
same from me
oainot said:
2. red button.
i can't do any thing, but "Touch X LEO Power 12 icons actionscreen" can.
so for me end key has single press as normal and long press by "Touch X LEO Power 12 icons actionscreen". that is more than enough. power off is a vital function also.
Click to expand...
Click to collapse
i would like to switch the action of the red button the other way round.
i would like long press red button to lock the phone and turn off backlight and single press red button to launch the Touch X Power 12 icons actionscreen. I cant seem to achieve this does anyone have any ideas?

rzasharp said:
Thanks for your appreciation of my thread.
Still, If you are really "hardcore hardware fan" you can use AEBPlus to assign even the double tap and triple tap of the keys
To oainot. About the bluetooth toggle, If find it quicker and simpler, to double tap on one button, turn on my headphones and get going out in the snow. I use it literally everytime If get out of my apartment. Just think: would you prefer to switch the light off your apartment with a long-click (+ click in a menu) or with a simple double-click? Just a matter of taste I guess. The best is to have to choice!
...
Merry Christmas!
Click to expand...
Click to collapse
ok. i've get it. you are absolutely right.

Audio Oblivion said:
same from me
i would like to switch the action of the red button the other way round.
i would like long press red button to lock the phone and turn off backlight and single press red button to launch the Touch X Power 12 icons actionscreen. I cant seem to achieve this does anyone have any ideas?
Click to expand...
Click to collapse
i'm afraid it is not possible.
single press of red key may controled by basic input output system, not the operating system (windows mobile), not the htc sense or not any other resident program.
may be this should be that for power on the phone by single press while operating system is still not running.
may be someone could hack the key someway. i dunno. if aebutton had a button assume called "power key", it could be possible to try.

Assign Softkeys Functions
I changed the setting to reassign functions of softkeys. AE Button shows the setting properly, but it does not work.
any suggestion?
thanks

msrox said:
I changed the setting to reassign functions of softkeys. AE Button shows the setting properly, but it does not work.
any suggestion?
thanks
Click to expand...
Click to collapse
yeah.
i forgot softkeys is not controled by aebutton.

I want to remap left softkey (single click) to HTC Message.
But when I do it the left softkey is still "phone" and the caption is not changed!

msrox said:
I want to remap left softkey (single click) to HTC Message.
But when I do it the left softkey is still "phone" and the caption is not changed!
Click to expand...
Click to collapse
Yes, I noticed that the left softkey cannot be remapped by AEB. You'll have to use the newer BsBTweak which works just fine with the left softkey. Find it here

msrox said:
I want to remap left softkey (single click) to HTC Message.
But when I do it the left softkey is still "phone" and the caption is not changed!
Click to expand...
Click to collapse
this feature is for devices with physical soft keys. Leo doesn't have them. search the forums for softkey remapper (Today and/or Manila).

[Q] Key to go directly to home screen

Hey guys
the android versions for blackstone are very well, u did a good job.
But why you don't use the "Hang up" button to go directly back to the home screen?
The prob is when i use the browser the only way to go back to the home screen is pressing the backward-button. that means it browses all the visited pages back before minimize the browser and show the home screen.
so why u don't used the turn off button to turn off the display and you the hang up button to minimize the running app and go directly to the home screen?
greetz.

I got similar question.
Why Android can't have same buttons behavior like WM?
Is something wrong with this?

Geek12 said:
Hey guys
the android versions for blackstone are very well, u did a good job.
But why you don't use the "Hang up" button to go directly back to the home screen?
The prob is when i use the browser the only way to go back to the home screen is pressing the backward-button. that means it browses all the visited pages back before minimize the browser and show the home screen.
so why u don't used the turn off button to turn off the display and you the hang up button to minimize the running app and go directly to the home screen?
greetz.
Click to expand...
Click to collapse
It's because most devs have a different device.
But dude, check my signature...
next time a little searching might help you on your way a lot faster

could someone edit rootfs.img file like this:
remove "sleep" from End call button
and assign:
to Volume + button on hold => Home screen
to Volume - button on hold => Recent apps
is it possible? as I never hold volume key to increase/decrease volume, i always press it step by step..
do you think it would be ok like this ?

crnogorac081 said:
could someone edit rootfs.img file like this:
remove "sleep" from End call button
and assign:
to Volume + button on hold => Home screen
to Volume - button on hold => Recent apps
is it possible? as I never hold volume key to increase/decrease volume, i always press it step by step..
do you think it would be ok like this ?
Click to expand...
Click to collapse
Altering button behavior is impossible. We can swap them around but HOME will always show Recent Apps when long pressed no matter to which button it is assigned (except for power). Sorry

oh.. I thought it is possible as I found this code for desire(http://forum.xda-developers.com/showthread.php?t=683902) :
Code:
key 102 HOME
key 139 MENU
key 158 BACK
key 217 SEARCH
key 107 ENDCALL WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
and thought if it was possible to locate this code for blackstone and alter it..

crnogorac081 said:
oh.. I thought it is possible as I found this code for desire(http://forum.xda-developers.com/showthread.php?t=683902) :
[CUT]
and thought if it was possible to locate this code for blackstone and alter it..
Click to expand...
Click to collapse
That's what we're doing here - modifying that table. I think I didn't make myself clear enough: we can swap keys but we can't change what long press does. Check this link: http://forum.xda-developers.com/showpost.php?p=12066475&postcount=24
This is the rootfs I've made. Button assignment looks like this:
Code:
[FONT="Lucida Console"]
Button / Android function / Android long press
------------------------------------------------------
Power / Sleep / Power Menu
Volume Up / Volume Up +1 / Volume Up Continuous
Volume Down / Volume Down +1 / Volume Down Continuous
Call / Dial - Answer / Voice Dial
Home / Menu / Menu
Back / Back / Back
End Call / Home / Recent Apps
[/FONT]

You were clear I just thought it was possible

Disabled n button from waking up device?

Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App

ramiss said:
Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
I don't know that you can stop one of the 4 inputs from waking up the hardware, but...
You can define the 'n' button to do something that doesn't offend you and set your screen to sleep after a very brief moment (15 seconds).
Why do you want to change the hardward button behavior?

byronczimmer said:
Why do you want to change the hardward button behavior?
Click to expand...
Click to collapse
Hi, thanks for answering. The reason for this request is because the screen keeps waking up as it moves around in my bag. Just lightly pushing on the case/cover I use will activate the button and leave the screen on until the timeout. I am surprised this isn't an issue for more people (or perhaps people aren't noticing their nook turning on.)
Lowering the timeout is not going to work since I do a lot of reading and having to tap the screen every 15 seconds would be a pain. Unless anyone has figured out how to get screebl to work??

You can completely disable the "N" button by editing the keyboard layout file. Using Root Explorer (paid app - but WELL worth it!) or equivalent, navigate to SYSTEM>USR>KEYLAYOUT then click the button at the top to "Mount R/W", now long-press the file "qwerty.kl" and choose "Open in Text Editor". Then find the following line:
Code:
key 102 HOME WAKE
and simply add a # to the beginning of that line so that it looks like this:
Code:
#key 102 HOME WAKE
Now press your MENU button and choose "Save & Exit". You'll need to reboot the Nook for the change to take effect.
Now your N button should be completely disabled. Just make sure you have the soft keys set up with a home button so you'll have a way to use that functionality when needed.
If you want to maintain the functionality of the "N" button but just prevent it from waking the Nook, simply remove the word WAKE from that line and don't insert the # character. I haven't tried this implementation, but it should work fine.

If you did what jason suggest, make sure you not hide the status bar.

You can change the "unhide" button to something else in Tablet Tweaks or you can use the long-press Power menu option which is also in Tablet Tweaks.

911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
Simply removed WAKE from the home button as suggested.
Works beautifully. Doesn't wake the device, yet does all the other stuff it's supposed to.
Score one victory for increased battery life for shared knowledge.
I have a soft case and it gets turned on in my pocket.
I went ahead and also removed WAKE from the volume up and down buttons.
Now the only way to wake the screen is the power button. The way my case is, that's the one button that won't get pressed in daily travel.
(don't know if reboot is necessary, but i'd assume so, and did after each change before testing)
Thanks!

TCAndroid said:
911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
[ ... ]
I went ahead and also removed WAKE from the volume up and down buttons.
Click to expand...
Click to collapse
I also took WAKE off the volume keys, because I tend to reach into my bag and adjust the volume while walking or waiting for the train. My buttons don't tend to get pressed, since my bag is for a netbook and my uncased NC doesn't rattle around. However, after adjusting the volume, the screen was live and the bag and its contents sometimes made random touches all over the screen...
The volume buttons now work exactly the way I want! Thanks for the very clueful answer to this question!
Of course, now I have another thing to do every time I update my ROM. I should learn how to make update scripts!
I am curious why HOME has WAKE and not WAKE_DROPPED, when it appears to behave like WAKE_DROPPED.

From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.

911jason said:
From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.
Click to expand...
Click to collapse
Exactly so. HOME acts like WAKE_DROPPED, doesn't it? But it's marked WAKE.

Actually, yes, you're right... just realized that. Not sure why it's behaving that way.