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..... )
After a call, you get a status screen which stays on for approx 10sec. I find it very annoying and would like to change that.
thank you
Please help on this issue
Hi, anyone knows of a tweak to reduce the time the "phonecall" screen stays up ? it is very annoying when switching calls or to quickly do something after a call.
many thanks for the help
I reprogrammed the buttons on my Polaris to work as "Startmenu" (left) and "OK/Close" right.
This way I can quickly access the startmenu without having to stretch my thumb across the whole screen and I can quickly make the call windows dissapear by pressing "Red/End" and "OK/Close" which is the same key Alternatively you can double press "Red/End" to end up on the Today screen.
Unfortunately I think there is no such thing as a registry edit to tweak that setting.
ok, thanks a lot for the tip
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?
Guys,
does anybody know if and how can I make my dialer not dial the person when I single tap on the row but only highlight it and then use either the hardware dial button or the big green "talk" button ... or double tapping the highlighted row?
I find it very annoying when I tap an adjacent row by mistake and have to search again. This happens pretty often when I drive and have my HD2 on a stand but it also happens from time to time when hold the phone in one hand I try to select/dial the topmost row in the result list.
The last part brings another question - is there a way to add two arrow buttons at the bottom of the dialer which will go trough up/down through the list? These will be very helpful in such "car" situations and also in the case where the search criteria results in large list (more than 3-4 items) which requires a scroll (flip scroll) and/or hiding the dialing pad to see the full list. Currently I've mapped the Vol Up/Down keys for up/down directions with AEButtons but it's not very convenient / comfortable.
I'll try to make some kind of screen shot to show what exactly I mean but I believe you get the point.
Here are the screen shots - the original and the modified (using paint)
It would be great if somebody can make such a dialer ... or explain what I need to make it myself. (the arrow buttons should stay visible when one hides the dialer ... or when the user presses them to start moving the "focused" contact just as if hardware arrows are pressed).
pankov said:
Here are the screen shots - the original and the modified (using paint)
It would be great if somebody can make such a dialer ... or explain what I need to make it myself. (the arrow buttons should stay visible when one hides the dialer ... or when the user presses them to start moving the "focused" contact just as if hardware arrows are pressed).
Click to expand...
Click to collapse
I'm not sure but I don't think I can do it. I'm not to good at editing those resource dll files.
Someone like RyanMogul6800, or Fards, would know about this. Maybe senf one of them a PM.
I am trying to design a game that has multiple buttons in rows. I want the user to be able to press a button, hole it and move it to a button on the side, top, or bottom of it and the two buttons will change places. Were do I start the programing to make this possible. I am new to programing so any help would be appreciated thanks.
You can try implement an ontouchlistener for your buttons, and when event is move do the movement via setting margin on the button.
Take a look there also:
stackoverflow.com/questions/17464428/property-animation-of-a-moving-button-android
To identify when the button is above the other button or near it, to perform the swap (you may need to animate this as the above link, too) try to get all the buttons position via view.getTop and view.getLeft ( as described there) and store them. When you move a button you have the coordinates of your finger dragging the button, so by extension you have also the coordinates of the button being moved. So then you check inside the ontouch event move again, when, after the set margin, your button is close enough to any button and perform the swap between them
See here for getting positions of buttons.
( stackoverflow.com/questions/7203740/retrieve-the-x-y-coordinates-of-a-button-in-android )