Related
Hey guys,
is there a way to reassign the hardkeys home and back?
I also have an item "Buttons" in the settings but there is only one key defined: "Key 1 (Hold), Voicedial settings".
However, I can't find this button, where is it?
It's the first button i.e phone pickup, hold it and it will give you the voice dial
Key 1 is the dial key (far left).
You can reassign the back key with AE Button Plus. I'm not sure that you can remap home.
use AE Button Plus to reassign the keys, words great on my touch hd. I read somewhere that Home button is not supported due to different driver implemented by HTC
Thanks for your replies.
I'm aware of AE Button Plus but the interesting thing is the reassignment of the home key.
I wanna keep the back key as it is and assign an ok/close task to the home key because the end call button actually does the same thing as the home button namely go back to the today screen when you have a running application in foreground.
In AEB+ I have the following:
Button 1 (hold)
Windows Key
Enter/Action
Volume Up
Volume Down
Green Phone Button
Red Phone Button
Left Softkey
Right Softkey
Up Arrow
Down Arrow
Left Arrow
Right Arrow
I can access the volume up and down keys but which key is the back key?
I assume the green and red phone button is pickup and hangup key respectively?
Is there a way to access the power key at the top?
ez2remember said:
...but which key is the back key?
Click to expand...
Click to collapse
The back key is "Enter/Action".
It seems that the home key as well as the power key cannot be reassigned.
Back and home key can be reassigned on a window by window basis in the registry. Not particularly useful, but better than nothing.
V
What exactly needs to be done in the registry to reassign the home key?
Even if I have to enter a new registry key for any program window I might use it is worth the effort (at least for me).
gacowarlock said:
The back key is "Enter/Action".
It seems that the home key as well as the power key cannot be reassigned.
Click to expand...
Click to collapse
I just want to update:
the back key is not the "Enter/Action" key. i have tried to edit this button and it didn't remap to the Back key.
If you go to File -> Add Button, and tap the Back key, it will recognize the key as button #405C. I have remapped it to "Close Active Application" and it worked.
i don't think u can reassign the Home key as AE Button Plus cannot access the Home key.
I was also unable to change the Home key in AEBplus.
Concerning the back key assignment with AEBplus, I was trying to assign something to the long press but unable to get it working. No problem for single press and double press.
Anyone has better luck?
vijay555 said:
Back and home key can be reassigned on a window by window basis in the registry. Not particularly useful, but better than nothing.
V
Click to expand...
Click to collapse
So how do we go about doing that vijay555?
Power Key
Here's the modified power key from Diamond but it can be used on HD.
When Power key on long-pressed, it will display the menu for choice. Tested.
Regards,
KCJ
just tested on Aeplus 2.6.6.1, the Back key = the Ok key, it can be remapped.
I have it set to:
Single press="Ok/Close"
Double press = S2U2
Long press=close active app
EDIT: Long press doesn't work... might try another method.
don't know if this works, but it is worth a try:
if you copy a shortcut to \Windows and name it "Short_Power.lnk" you can intercept the short power key press. at least that worked for me on my diamond.
you could try s.th. like "Short_Home.lnk" but that would intercept the "other home key" (which manages the cursor's position like end, up down, left, right, etc).
the magic would be to find the correct name of the key.
longpress back key (405C)
I know this is an old thread, but I haven't found yet a solution.
I'd like to be able to add longpress back key (405C) to the key menu on the windows config.
I've found the registry key that HTC uses to provide longpress send key, but I copied with no luck.
Anyone knows how to do it? vijay555 has said it's possible but never indicated how...
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 )
hi i want to assing the back button "<--" on the bottom with the OK button. i dont need the back functionality, what i want is to avoid trouble hitting OK on the top every time. someone suggested me AEbutton, that solved my problem assigning the volume button for up down navigation, but i want to assing back button to act as OK.
pl. help
Well, I've got good news. The Back button IS OK. Try it in a Settings dialog, pressing Back *will* save your changes.
You can assign actions to OK with AEBPlus.
This surprised the hell out of me - I only realized this after owning my HD for a month.
It also means that there is no PPC/HD equivalent to the Back button on smartphone devices. I had a Vox before, and was used to the Back button meaning "cancel".
JUst to add a little to that.
Is it possible in any way to disable the volume keys?
I cant stop pressing them by mistake
Bengaz said:
JUst to add a little to that.
Is it possible in any way to disable the volume keys?
I cant stop pressing them by mistake
Click to expand...
Click to collapse
AE Button plus
then just remap them so they dont work as volume keys on a single press ( i use the long press to make them go up and down, but in rreality i use the slider to actually move change volume so i dont need to even map them to the volume at all)
Ehm.... what is the slider? I read about that also in TouchLockPro and I couldn't realize what it was.
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?
/edit: this guide is now obsolete because Xposed Additions now has button remapping with some advanced options, which also seem to enable volume wake on my HTC One
If you hate locking and unlocking your HTC One with the Power button, you can change that quite easily int for example Volume Down.
ButtonRemapper would be the easiest method, but it doesn't work with the HTC One. It doesn't load the correct file.
The solution: simply edit the correct file
Code:
keypad_8960.kl
found in
Code:
/system/urs/keylayout/
by hand (I used Fx File Explorer with the paid Root plugin) and reboot your phone. My edited file is attached on this post.
Original:
Code:
key 116 POWER WAKE_DROPPED
key 114 VOLUME_DOWN WAKE
key 115 VOLUME_UP WAKE
key 107 ENDCALL WAKE_DROPPED
My current file that switches the Volume Down and Power button:
Code:
key 116 VOLUME_DOWN WAKE
key 114 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 107 ENDCALL WAKE_DROPPED
I don't know if the same file is used on different ROMs. I tested this on the P.A.C. Man ROM.
Now waking my One is a breeze! :laugh:
P.S. You may need the following workaround to fix the 'volume wake not working' bug present in some (or all?) JB ROMs, which strangely also affects this tweak (symptom: volume down won't wake phone sometimes).
1. Install Xposed Framework (which you should anyway, it's awesome)
2. Install MoDaCo Toolkit
3. Wait for the annoying ad (Paul, tsk, tsk) and enable the option 'HTC One > Enable Volume Wake'
4. Enable MoDaCo Toolkit in Xposed
5. Reboot
6. Profit ^_^
Is there a way to remap volume keys to change song when double clicked or something?
dare2k said:
Is there a way to remap volume keys to change song when double clicked or something?
Click to expand...
Click to collapse
I'm not sure, but when there is, I think it's not done with this or another .kl file but with a 'ROM tweak', like AOKP settings.
But remapping it that way does it mean if you want to lower the volume you press the power button?
Sent from my HTC One using Tapatalk 2
baste07 said:
But remapping it that way does it mean if you want to lower the volume you press the power button?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Correct. I'm currently having the issue that my phone won't always wake using the remapped Power button, or only after 4 seconds holding it. I think it's a conflict with my ROM settings though.
While locking the phone with volume down would be nice, it prevents you from turning the volume down/vibrate/off. Which is pretty important.
Although you could alternatively hit Volume Up and then drag the slider via the touchscreen.
BTW I tried this on TrickDroid 4.2.2 and it works.
Syn Ack said:
While locking the phone with volume down would be nice, it prevents you from turning the volume down/vibrate/off. Which is pretty important.
Although you could alternatively hit Volume Up and then drag the slider via the touchscreen.
Click to expand...
Click to collapse
Actually, the adjustment only swaps the buttons, so the physical Power button acts as Volume Down
I'm still having issues with the adjustment though, has anyone tried it and got it working correctly all the time? I also edited Generic.kl and qwerty.kl, but that didn't help. Pacman ROM 2.9.
Is there any way to use his once you're in the camera . Since we don't have a dedicated camera button it would be great to set up the volume key to take pictures ?
Sent from my HTC One using xda app-developers app
Volume wake bug workaround added to OP.
Problem...
jelbo said:
Volume wake bug workaround added to OP.
Click to expand...
Click to collapse
I have multiple problems guys:
Rooted...double checked if it's rooted (htc one) - then installed Xposed...mods...guess what? it worked for a few hours then all of the sudden...Framework disabled...pushed Install again...and then one of 2 things happen:
1 - phone reboots
2 - Installed and notification for SU....but when restarting my phone the framework it's NOT installed....wtf?!?
Solutions errybody
jelbo said:
Correct. I'm currently having the issue that my phone won't always wake using the remapped Power button, or only after 4 seconds holding it. I think it's a conflict with my ROM settings though.
Click to expand...
Click to collapse
PERMANENT FIX: This problem is caused when the phone enters Deep Sleep mode, the processor stops listening to the .kl files and is pre-programmed to listen on the power button. --On mine, I was completely unable to turn the phone on, I figured out thought that I could turn it on is by holding the power button and the configured volume button at the same time, like a screenshot, hope this helps somebody.-- To permanently fix this download "Wake My Android Pro (free)" from the Play Store, this app is specifically designed to keep your phone in the "Sleep" mode and preventing it from entering the "Deep Sleep" mode. **This does not drain your battery.** Just make sure to set "Low Wake" in the settings, and set the time to 9 seconds and auto-start. Hope this helps some people, those who do not want to fiddle around with Xposed.
dare2k said:
Is there a way to remap volume keys to change song when double clicked or something?
Click to expand...
Click to collapse
This you can do via Tasker. Just create a profile: Event, Variable Set: Volume - Media. This will pick up the volume presses, from there you can restore the volume to what it was (via stored variable) and detect double-presses or gestures between the vol-up and vol-down buttons. I recommend running Javascript to detect that, to be more streamlined. Once detected, use the Media Control action to skip/restart/pause songs in OEM, or if you use Spotify or Pandora, you will have to use a shell "input keyevent 87" Use Root: Yes--87 to skip, swap it with 88 for previous, 85 to play/pause.
rollsrd said:
Is there any way to use his once you're in the camera . Since we don't have a dedicated camera button it would be great to set up the volume key to take pictures ?
Click to expand...
Click to collapse
This can be achieved with Tasker as well. Use a profile "Application," select Camera, and combine with an Event (by long-pressing profile and "Add...") Variable Set: Volume - Ringer. For the action, select Input>Button>Camera. You must be rooted.
If we combine this button swapping idea with Tasker, we can do a lot of cool things guys. An easy way to pick up an easy button gesture with Tasker is with the power button (which always works from sleep, the volume buttons can only be detected when music is playing). I use Tasker to do a certain action when the power button is double-clicked (Display On>Display Off within, say, 1 or 2 seconds).
Hope all was a help, I am new to XDA (*NOT* a noob!) and actually, this is my first post, so a thumbs up or a "thank you" or whatever you guys call it would be great. Thanks! :good: