Related
Is any useful way to remap the Green and Red Phone button and the volume slider button? I mean for launch application or any function. Thanx.
There are some such programs for volume slider.
The most simple I prefer is attached here.
Just put it to the \Windows\Startup folder. It just "unbind" slider but not remaps it to another buttons. This will allow to use slider as F6/F7 buttons in programs able to hook them e.g. Haali Reader...
Thanx
It seems to be ok but where did you attach it? On my MDA is no offered file to download at this time. ThankU.
I've got it
Ok. Now is the sheet with uploaded file appeared. I've got it and extracted it. After i run the *.exe file it does nothing. Why?
because it should do nothing
This utility just frees slider buttons from default binding to volume control.
If you have an application that understands F6/F7 hardware key pressings (slider up/slider down) you may bind these key in the program.
As for me - I use them to scroll text up and down in Haali Reader text reader program.
But (as I said above) there are another programs to use slider up/down control. Unfortunately I don't remeber where I saw these utilities - but they really exists
And, as far as I'm back to the Andes from (Blue Angel) - I think I will write another one specially for Himalaya/Andes.
Ok, let's wait some days. If there are any results - I'll post the report here
P.S.: BlueAngel is the best HW keys equipped device i've ever saw But...
Thanx once again
Thank you 4 ur help. Now i understand that. And what about the Phone buttons? Any ideas? Ex.I want to use red button as Ok/Close simulation. Any ideas how to do that? Thanks.
Nobody unmaps phone buttons. It is possible but unresonable because of HTC is a phone device also. But I'll implement this feature too.
OK
I will wait for it.
The very first (and buggy) try of HW remapping utility is done. The application setup is available HERE
After installing .CAB file go to Start -> Settings -> Buttons and see the changes...
DO NOT INSTALL THIS APPLICATION ON BLUE ANGEL!!!
It will hide four lower hardware buttons until hard reset!
1. This app was tested on Andes with WM2003se, but should work on Himalaya/Magican with WM2003 and above
2. You will lose the possibility to use hardware key mapping in other applications forl remapped buttons. I need to re-grab buttons from time to time because the system tries to thieve them from me
3. Currently I don't now how to emulate green and reed buttons functionality after unbinding them from the system.
4. I can count any number of button pressings (3,4,5...), but -
5. WinCE reserve codes for only 15 hardware buttons (40C1..40CF)
There are some ideas for future improvement. But it would be nice to know your thoughts.
Just to "stimulate": I can create settings screen during setup to allow flexible configuration where you will
- choose which buttons to handle and how many key pressings to detect;
- choose option to unbind and/or re-map volume and phone buttons
- ???
And let me take a time-brake for 2 days before next programming session
The utility is ready. It allows you to:
remap each standard hardware button to 2 or 3 "virtual", simulated via double or triple clicks;
use volume slider to simulate Up/Down direction keys or create additional "virtual" hardware buttons;
remap Red and Green phone buttons to 1,2 or 3 hardware buttons each.
In a result you may create up to 15 hardware buttons (system limit)
Just install program and check Start -> Settings -> Buttons.
Here is Oficial AEBPlus home page, full desktop-based setup (~27K) and Direct link to CAB file (~30K)
Well done!
Excellent software! Thank you once again for your work. Works very very well!
man this is great really like it
works perfect :lol:
Seems to work great. Haven't had it running long enough to see if the camera button will get stolen back (big problem for me on XDA IIi), but being able to map the volume is great.
In the next version any chance of adding an <enter> option like Vito Button Mapper which I think just sends a <carriage return> to select whatever is highlighted.
Is "<Ok/Close>" option in button settings applet not the same?
NO, <OK/Close> generally tends to close the current window rather than selecting whatever is highlighted.
Also whatever application keeps on stealing back the camera button is still doing it. I don't know if it is part of the UK O2 customisations or the core PocketPC Rom, but eventually whatever function is mapped to the Camera button gets re-mapped back to the camera. This also happened to me with the standard button mapper and Vito button manager. It's a little annoying since the camera button is the most usefully positioned, and it is also easily knocked, starting the camera at awkward times.
Ok, I'll add this option for camera button (a bit later, in a case other suggestions arrives).
As for the re-hooking button by camera application: AEBPlus initializes all of the buttons from time to time. Currently this take place every 30 seconds. So if you will wait a bit - all buttons should be re-grabbed again
This does not seem to help because whatever application that is resetting the camera does it in the same place as you are storing the button mappings. When I go into the Buttons Setup it will now say that the Camera button is mapped to the Camera.
Yes,I see... It looks like Camera application is a pushy application . The solution is to remap "normal" Camera HW button to 3 press instead of one, but I don't like this.
Anyway - utility was released.
New features: added option to emulate Enter key with Camera button.
Hi AE, your utility is great. It is very useful but SIMPLE and SMALL.
I used it instead of other button mapper software.
There're some issues need tobe improved:
1) Mapping "Green" and "Red" button:
Enable mapping when they're iddle only (phone function does not work).
E.g: I'd like using Red button to close running app. But in phone function, Red button is still used to hang-up the phone as original its function. Anytime I have a phone call, I can use Red button to cancel a outgoing/incoming call.
You can refer the program of mamaich in this web site.
2) Single press is too low:
I press a key one time and wait 5 secs or more until it works. It's too slow. Can you improve? Double-press is OK.
3) Press n hold:
Can you add "single press n hold" for all hardware-keys? I think "single press n hold (after 3-3.5 secs)" is more convenient than "double press" or "tribble press". Do you think so?
Hi AE, very usefull application! Is there any way that we can have an options screen, where we can change the key options we get after installing the app? That would be easier to edit our preferences if we want to make changes to our initial choices. Furthermore I added a Mortbutton to one of your simulated hard keys. Each Mortbutton can show a list of 12 apps for a buttonpress. That means That I can now bind more than 60 apps to the buttons in total! Very good for one-handed use of my Magician, thanks!
Is there a way to easily adjust the volume using the wheel? Or do we have to get the stylus out :?
Cheers
Just tried SPB pocket plus but it doesnt have a volume indicator, just a control which doesnt show what the volume is set to!
any clues?
What is it that you want to do?
If you move the jogwheel during a call, you can change the voulme of the speaker...
OK, But do you know how to adjust the volume when not in a call without tapping the screen? is there a way to do this please?
probably clumsier than tapping the screen, but if you have both Spb Pocket Plus and MS VoiceCommand, you can issue commands for Volume Up, Volume Down, Volume Loop, and Mute.
You can also tapp on the Comm Manager button and toggle the between (preset volume), (vibrate), and (silent).
Is there a good screen tap recorder which works with the tytn?
I tried Vitobuttonmapper which does this but it messed up all my other button assignments! I just want to be able to assign the voicedialler press and hold function to bring up the volume bubble!
Anyone found a prog which will turn a screen tap into an .exe which will be assignable to a button?
Vijay?
Anyone??????
with aebutton plus 2.4.3 beta (its now in 2.4.4 beta), if you remap the "ok" buttons after adding it, you can select it in such a way (under "\options\restore volume slider\" select "if today is active").
Now in the today screen, when you press the ok button, the volume slider will be activated. You can then use he left right up/down keys to select the volume of choice.
However, upon capturing the ok button, i have to map the ok button to close active apps when pressed twice. Pressing it once, regardless of the program in the foreground yields nothing.
To minimize, i have the use the red phone button.
I use the following mortscript:
Code:
MouseClick 160,0
Sleep 100
MouseClick 160,200
In portrait QVGA.
There's a neater way with VJKeyPress as well, but I can't remember the settings right now
If necessary it'll be easy to turn this into a seperate app.
V
vijay555 said:
If necessary it'll be easy to turn this into a seperate app.
V
Click to expand...
Click to collapse
That would be v. nice! would it be possible to make it landscape aware too?
(i'm to much of a thicky for mortscript..... )
The lack of hardware keys (without the keyboard attatched) on the x7501 was my biggest reservation while deciding to buy it. Now I'm having trouble with AEBPlus and HButton (would be perfect if I could use AEBPlus & assgn Hbuttons to the Long Press mode, but it doesn't work). I can't seem to get the flexibilty in button assignments like I had wiith my wizard, I think because a lot of the long keypresses are OS assigned and not UI available.
I don't want to start reg hacking in my random ways if someone has more experience, or better software ideas, and would be willing to share it.
(I keep my unit in the case without the buttons locked when it's in standby, so if I hit a hdwe key, I only have to do that once to get a specific Mortbutton menu up. 2 gestures to anything is my goal. Hbutton often can allow only 1, but I only get 2 keys out of it CommMgr/Record & Camera, my "IE" button longpress seems to be commandeered by VueFlo (cute but pretty useless). If I use that the AEBPlus doesn't seem to work on the other keys.)
UPDATE: I reinstalled AEBPlus, this time with the PC/Activesync installer instead of the cab. The cab installation I did didn't seem to change things. In any case, AEBPlus is working now.
Thanks!
Janis said:
The lack of hardware keys (without the keyboard attatched) on the x7501 was my biggest reservation while deciding to buy it. Now I'm having trouble with AEBPlus and HButton (would be perfect if I could use AEBPlus & assgn Hbuttons to the Long Press mode, but it doesn't work). I can't seem to get the flexibilty in button assignments like I had wiith my wizard, I think because a lot of the long keypresses are OS assigned and not UI available.
I don't want to start reg hacking in my random ways if someone has more experience, or better software ideas, and would be willing to share it.
(I keep my unit in the case without the buttons locked when it's in standby, so if I hit a hdwe key, I only have to do that once to get a specific Mortbutton menu up. 2 gestures to anything is my goal. Hbutton often can allow only 1, but I only get 2 keys out of it CommMgr/Record & Camera, my "IE" button longpress seems to be commandeered by VueFlo (cute but pretty useless). If I use that the AEBPlus doesn't seem to work on the other keys.)
Thanks!
Click to expand...
Click to collapse
AEButton will generally do long presses, double presses, and triple presses... if they are available. As you mention, this seems to be a hardware problem. Example, the "e" (internet) button uses the long press to activate/deactivate the motion sensor within your browser.
As a former Wizard owner, I know where you are coming from. Remapping the "e", "record", and "Win" buttons has given me about 9 quick launches, one of which is WkTask which gives another 12 on a pop-up panel--not to mention showing all open windows on the top bar. Also, the big screen makes iLauncher usable. And I still use good-ole SmallMenu. So I'm doing OK with opening things quickly. But I do miss having all those button launches from the Wizard.
Doing better
HButton and AEBPlus don't play well together at all.
I'm on AEBPlus, post flash, and don't get any long-presses, but I have 3 possiblilities on each of the buttons. Along with MortButtons and actually using the CommMgr instead of hdwe keys, I seem to be getting along well enough.
I had the basic edit commands (select all, copy, cut, paste) assigned to a key in AEBPlus, and turn on/off BT and WiFi. That's what I miss. I use MortButtons for it now, so it's a two-step process, but it works.
The problem with "long keypress'es" for many buttons like Ok/Win/VueFlo etc) is caused by keyboard driver implementation and may not be resolved on application level. The button driver returns both "key was pressed" and "keys was released" events simultaneously, right after button was phisically released. So application could not define time period button was in pressed state to decide if it was long or short keypress...
As for BPlus configuration for my Athena (I have no keyboard at al and use bplus only):
* Button 2 (40C2): (IE button)
1: Call default handler
2: "Messaging"
3: "Notes"
* Button 3 (40C3): (wireless manager)
1: Rotate Screen
2: Show Actions Menu
3: Switch Flashlight Off/On
* OK key (4075):
1: Press Green Button
2: "Contacts"
3: "Calendar"
* Windows key (405B):
1: "Notes"
2: "File Explorer"
3: Show Actions Menu
* Enter/Action (000D):
1: Call default handler
Long: Task Manager
* Volume Up (0075):
Change volume or...
1: Volume Up
2: Backlight Up
Long: Backlight Level 10
* Volume Down (0076):
Change volume or...
1: Volume Down
2: Backlight Down
Long: Backlight Level 1
Action menu items:
Rotate Screen
Switch BlueTooth off/on
Switch WiFi Off/On
Trigger Online
Disable "Power off if not used"...
Device Lock
Click to expand...
Click to collapse
P.S.: I reviewed this forum very occasionaly so you'd better to ask me via e-mail if any
AE, love the program but have one problem. The "ok/close" function is never "close", just always "ok".
The only way that I know of to map the OK button to really be "ok/close" is to configure an hbutton key to be "ok/close" and then use AEbplus to make that hbutton.lnk to the OK key. It's a bit convoluted and requires both programs being loaded and running (hbutton uses more memory than aebplus), but it's the only way to make it work.
Any way to fix the "ok/close" function in AEbplus? Even when there is an "X" in the upper right corner, AEbplus only minimizes the app, never closes.
Has anyone tried remapping or assigning the keyboard buttons to launch applications?
===
Is it possible to get the Half-Press-Function of the Camera-Button assigned for normal working(windows-mode, not camera-mode)??
greetz
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?
Hi!
I'd like to make some adjustments to my Xperia X2 configuration, so I'd be thankful for your help.
- Pressing End Call would close the current application.
- Pressing OK would minimize it.
- Assign Slideview button to something useful like lock/unlock screen.
- A rather exotic request, either:
-- Assign volume up/down to lock/unlock the screen if on the home screen.
-- Or Assign volume up/down to switch phone profiles (normal/vibrate/mute).
I'd even appreciate if you would point me to a right direction or tell me that something is definitely not possible.
Thanks