Is there possible to assign volume control buttons as up/down scrolling?
There can be options
- better is if on home screen they works as volume control, for applications as scrolling
- always scrolling
- scrolling only in certain applications
?
Also, is there possible device tilt for scrolling?
maybe you check "AE Button Plus". a lot of discusiion around here
Is is possible?
Yes it is possible - I use it.
I have set it up do do exactly as you as you ask where a "short press" of the up/down volume buttons will scroll up and down and a "long press" will change the volume as normal.
You can download it here http://ae.inc.ru/aebplus.php
Thank you!
AE Button Plus is good application and it works, but it's not free.
Now I try HButton 2.3
http://www.freewarepocketpc.net/ppc-download-hbutton-v2-2.html
Question guys,
How do I map the call button to long press (like the smallest long press ever) to get the Start menu?
Thanks
peeters said:
Thank you!
AE Button Plus is good application and it works, but it's not free.
Now I try HButton 2.3
http://www.freewarepocketpc.net/ppc-download-hbutton-v2-2.html
Click to expand...
Click to collapse
The unregistered function is almost fully functioning.
I recommend it.
I bought the app as I use it all the time and thought it fair to the developer even though I don't actually use the additional functions in the reg version.
CorruptedSanity said:
Question guys,
How do I map the call button to long press (like the smallest long press ever) to get the Start menu?
Thanks
Click to expand...
Click to collapse
You should be able to map long press send, long press end and long press power. It should work like the Fuze. Check out this articles but I bet it's identical:
http://www.fuzemobility.com/?p=1751
Here's one on making it the start menu: http://www.fuzemobility.com/?p=1249
The mapped long press buttons take 3 seconds or so...not sure it's great for that unless you try DredSensor but then you'd lose a physical button (short press) to something else...
Is the long press timeout option in the settings the time one has to "long press" in order to trigger what he sets? Coz you can set it from 200ms to 900ms. I am guessing this is the time required to trigger a long-press response/activation.
I would suggest you send an email to the AEB developer. I did once and he responded in the same day.
He could probably guide you much (v. much) better than I on all the options in AEB+ (including "long-key press mode")
thanks Dave.
For a temporary fix,(or perhaps a preferred alternative?) I have set up volume to scroll up and long press (which is barely a second) to start menu (shows quick menu not original start menu) and volume down to scroll down and long press of it to ok/action. This way I can pull down the start menu with a little press, scroll up/down and then select an item or enter the submenu using the down button.
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?
Hi,
Im trying to play a game on my phone, which requires me to push "Yes" or "No" to "Do you want sound?".
You have to actually push the hardware left or right nav key button to proceed, which the Topaz/Td2 does not have.
So i thought simple, go into the Buttons configuration settings, and set "Call (hold)" as left soft key, and "Hangup (Long hold)" as right soft key... but this doesnt work.
Anyone have an idea of how i can mimic the nav buttons?
Cheers,
Blake
There is a program called "TopazKbdControl_GSM" that allows mapping of all your hardware keys, even Volume keys, Home, and back. It is actually pretty slick, allowing you to map Volume keys as Up and Down with a single press... and VolUp-VolDown on a hold.
Same with the bottom buttons.
http://forum.xda-developers.com/showthread.php?t=555821
Thanks!
That program is exactly what i wanted.
Unfortunately it doesn't let me get pass the screen in the game :S
Its Line Rider 1.0.5 if everyone knows how to get it working.
Hi All
I've just got a S5 today. Overall I like it a lot however the bloody button res-assignments is soooooooo annoying!
Is there any to re-map the button layout back to the older galaxy versions? I.E.
Press the left button and the menu will activate (I know if I hold it down it will work but I keep forgetting and it brings up the tasker)
Hold the home button to bring up the tasker.
Frustrating yours
Paul
jokerni said:
Hi All
I've just got a S5 today. Overall I like it a lot however the bloody button res-assignments is soooooooo annoying!
Is there any to re-map the button layout back to the older galaxy versions? I.E.
Press the left button and the menu will activate (I know if I hold it down it will work but I keep forgetting and it brings up the tasker)
Hold the home button to bring up the tasker.
Frustrating yours
Paul
Click to expand...
Click to collapse
Root it -> Install Xposed -> Install GravityBox
Thanks, I had thought about it but its a new fone and you know what Samsung are like... I'm leaving towards re-mapping the key.
/system/usr/keylayout/Generic.kl
Anyone know the key number for the left button (Is it 138), what would I need to change to make the default option a menu. I suppose thinking out loud I want to swap the commands over. I.e. I press the key once I get the menu, press and hold I get the tasker.
Thanks
P.
Just long press the left button and the options come up
Sent from my SM-G900F using XDA Premium 4 mobile app
jokerni said:
Thanks, I had thought about it but its a new fone and you know what Samsung are like... I'm leaving towards re-mapping the key.
/system/usr/keylayout/Generic.kl
Anyone know the key number for the left button (Is it 138), what would I need to change to make the default option a menu. I suppose thinking out loud I want to swap the commands over. I.e. I press the key once I get the menu, press and hold I get the tasker.
Thanks
P.
Click to expand...
Click to collapse
Your best bet is to use gravity box, as suggested above. You can only change the recents function to menu via the file you mentioned. I believe the rest of the options you want are smali edits.