I'm trying to set up Duke Nukem 3D on the Wizard and can't find the key names or codes for various keys, like the camera, call, hang up, backlight etc...
Any ideas?
I think most of the hardware keys are in the normal range of F1, F2 etc.
Eg I think the hangup key is like F4.
Check here:
http://www.vijay555.com/index.php?Releases:VJKeyPress:Key_List
V
Aren't the pickup and hangup keys hard-bound in Windows Mobile to the phone options, and the nagup key is always set to hangup the phone call, or kill the current app? I've always found that I can minimise ANY running app by hitting the hangup key. Which has its uses, but is wholly impractical for mapping keys to functions in games and stuff.
christopherwoods: no the hard keys aren't mapped to the phone. Well, in a way they are, but not internally. Basically, if the phone app, cprog.exe, is working, it will intercept keys F3 and F4 and interpret those as dial/hangup keys. So using my program VJKeyPress you can simulate red and green with VJKeyPress 114 or 115
However, if you redefine the function of those keys, eg using a program like AE Button Plus, if you then simulate pressing F3 or F4, then it will perform the function chosen in AEButtonPlus. So, the keys can be overriden. Using VJKeyPress 114 will not simulate the phone key etc.
I've always found that I can minimise ANY running app by hitting the hangup key. Which has its uses, but is wholly impractical for mapping keys to functions in games and stuff
Click to expand...
Click to collapse
In normal use the red button doesn't minimse windows, it just jumps to the today screen I think. It certainly doesn't close windows. To close windows with the hangup key, check out my program VJOkButt.
Most programs written with GAPI will override the hardware key settings. However, if your game doesn't, use AE Button Plus to remap it to any other key press (perhaps by using my VJKeyPress). Then your game won't have fits when you press it.
V
Yeah, when I said minimise I meant that it shows the Today screen, and apps behave in the same way as if they're closed using the X - they don't really close, I know that for certain because... Well, that's how Windows Mobile (stupidly) behaves, and Switch shows them as still open.
I'd forgotten about your programs which can intercept keypresses and remap stuff... I must check those out sometime.
Does anyone know what I actually put into the config file, as in, the number or the words from that list or what?
mrsnoopy: I've never tried your game. Quote a few of the settings here and it should be easy to guess. I'd imagine the number though, not the words. Eg escape should always be 27 (or 1B if it's in hex).
V
awesome game in its day
used to play it on my 486 with 1 meg vga ram , yea !
Does it still have the taunts when u used to press an F key (in LAN multiplayer) come get some 2: who wants some 3:what are you some bottm beating scum sucking alge eater 4:it hurts to be you 5: your going to pay for that 6: wasted
cant think of any more .
much better in multiplayer , that work on the phone?
Is there a way to disable the shortcut of pressing the middle of the DPAD and the messaging button? When i play emulator games, it always pops up.
Ha, same thing here! At least now I know why it was coming up ...
Yeah, that would be q nice registry fix! Very annoying while playing action games, not so bad on rpg's though....
yea!! i cant play street fighter alpha without concentrating on not hitting the centre button. not easy i tell u..
For my snes i reassigned the buttons to be the pie button one of the buttons and the volume up another button (makes it easy to run and jump in super mario). Also, i reassigned my start to be volume down and it's perfect.
I'd like to be able to hold a button (other than Button 5) and have it execute a command/program. Can it be done?
ie. Hold OK button to launch X program? I've googled with no luck.
Search the forums. There is a thread by Sleuth255 (?) with the title PTT Function Hacked or something similar.
I found that thread. But it's doing what my TyTN does anyways... allows you to hold the button 5 and launch. I need that function for the other buttons as well.... unless I'm missing something.
i use ae button plus for this.
its free on a trial with a popup on phone phone startup, or $7 to unlock.
its FANTASTIC. interface isn't overly intuative to setup, but basicly you can have
1 click, 2 click, 3 clicks and press to hold on *all* the hardware buttons do different things.
its also got a reasonalbe app switcher built in, and way to turn the screen off and lock the keys if you want your media to keep playing when the phone in in a lower power state. *(not sure how much this saves in terms of power, but the key lock is why i use it)
For example,
my internet button (up and right of screen) is now set to
1 click - Load IE,
2 click - Load MusicID (listens to any song being played and then tells you the artist and track)
3 click - Load tomtom (usfull so i can switch between messages/phone calls and tomtom when driving quickly.
press and hold - turn off screen and lock keys for media playback.
Wish it was more popular i think its a fantastic application! you should give it ago.
as an aside note, i think there is a reg hack to do the press and hold on other buttons, but honestly do your self a favour and try
http://ae.inc.ru/aebplus.php
(website looks Naff!!! but good app)
Thank you. Exactly what I need. Cheers.
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.
Is there any way to do this?
Apparently Call of Duty: Mobile requires a Dual Shock 4 or Xbox One controller in order to work. This defeats the purpose of playing it on a Switch. Which I'm ashamed to say, is a big reason I bought and installed Android on my Switch. To play CoD:M on it during down-time at work (I work night-shifts).
I was wondering, since this is a custom FW anyway, is there any way to trick it into thinking the Joy-Con controllers are actually Xbox One controllers? So it would be registered as such in Android as a whole? The Screenshot-button could be the Xbox-button. Many, if not most/all games with controller support, support Xbox One controllers. I see no downside to that.
If not, is there any working overlay program out there? I tried Mantis Gamepad Pro. l connected it to my PC and activated it. It found the Joy-Cons. I added CoD:M as a game. Started it.
Game started, I went into Practice Room in order to set up my overlay.
There's a semi-transparent green overlay-button in the top left corner, so I press it and try and add a button, and get told to "Press a Button". So I physically press a button on my Joy-Con, and that button pops up as a Virtual Button. I drag the VB over the icon on the screen indicating the action it does (let's say, physical button = RT, VB = dragged over Shoot-icon). Now this is working great, I'm placing the analog sticks, pushing all the buttons and placing them where I want them. It registers my buttons.
But when I close the settings by pressing the semi-transparent icon in the top left corner of my screen (the green icon is still there, but the button layout disappears) and actually try and PLAY the game, none of the buttons are registered when I press them. Nothing happens.
It's like.. so close, yet so far!
I think I have all the settings correct, and I've enabled the app to be on top of other applications or whatever.
If anyone has ANY idea how I can get CoD:M working on my Switch with lineage-17.1-20210510-UNOFFICIAL-foster_tab-signed, that would be awesome!
Thanks for ANY response! Anything helps!