[Aug-20] CobaltController - PS3/Wii Controller Driver for Windows Mobile

Search This thread

Cobaltikus

Senior Member
CobaltController

Use your Sony Playstation 3 Controller (Sixaxis/Dual Shock 3) or Nintendo Wii Remote (Wiimote) as a Bluetooth Game Controller on your Windows Phone.

It's perfect for game system emulators.

Play PlaystationOne games with FpseCE, Super Nintendo games (and more) with MorphGear (HD2 version), Nintendo, Genesis, GameBoy, GameGear games (and more) with SmartGear - There are many other emulators out there and this program/driver will work for anything that accepts keyboard input.

Compatibility
Post your results and I will update this list
Code:
DEVICE                    PS3  Wii  Confirmed By
------------------------- ---  ---  -------------
Acer beTouch E200         ?    Yes  pmprog
Acer Neotouch S200        Yes  Yes  Fenrir84 (PS3) / Snowball2010 (Wii)
HTC HD2                   Yes  Yes  Cobaltikus
HTC Touch Diamond         Yes  No   koert17 (PS3) / nightly_shadow (Wii)
HTC Touch HD (Blackstone) Yes  Yes  RDilus
HTC Touch Pro             Yes  No   Cobaltikus
HTC Touch Pro2            Yes  Yes  Cobaltikus
HTC Touch2 Mega           Yes  ?    RipNWO
HTC Vogue                 No   No   Mycle78
HTC Wizard                No   ?    shorty66
LG Expo                   Yes  Yes  dalb3 (PS3) / trueg (Wii)
Samsung SCH-i730          No   No   Cobaltikus
Samsung i780              Yes  ?    ShadowswordPL
Samsung SCH-i830          No   No   Cobaltikus
Samsung Omnia I900        Yes  No   Manny-77
Samsung Omnia II i8000    Yes  No   cyber-junkie
Sony Xperia               Yes  No   sashapont (PS3) / stratis10 (Wii)
Toshiba TG01              No   No   Cobaltikus
...                       ...  ...  ...
Your Device               ?    ?    You
You Tube Videos
http://www.youtube.com/watch?v=mH_NBKtj0R8 (Thanks i900frenchaddict)
http://www.youtube.com/watch?v=3dH9J1y0G-8 (Thanks ahmedsaid)
http://www.youtube.com/watch?v=Qo-_nMmYq1Y (Thanks dijay_94)
http://www.youtube.com/watch?v=HauZQWYZxmQ (Thanks ShadowswordPL)

Prerequisites:
  • PS3 Controller
    • A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post.
    • A PS3 Controller (I don't know if non-Sony 3rd party controllers work - maybe they do, maybe they don't).
    • A desktop or laptop computer with a USB port to set the controller's master address.
      • Linux - Use sixpair - directions in this thread somewhere, search for "Ubuntu"
      • Windows - Use Motion in Joy, but please note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, when I run CobaltController on my Touch Pro2 it displays "BT ADDR: 00:23:76:70:6B:4D" so I enter it into Motion in Joy as 4d.6b.70.76.23.00
  • Wii Controller
    • A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post. Devices with the Microsoft Bluetooth Stack can't use the Wiimote yet.
    • A Wii Controller.
  • XBOX 360 Controller
    Not Going To Happen
    In order to get the XBOX 360 controller to work in windows you need to purchase a wireless receiver - it doesn't use bluetooth. It needs additional hardware. So if a full desktop Windows PC can't even do it without additional hardware, I seriously doubt it will ever work for our phones. Some company could come up with an xbox 360 wireless receiver for Windows Mobile, but again, very doubtful. And since I don't even have an XBOX of any kind, I know I'm not going to be motivated enough to even try.

Initial One Time Setup for PS3 Controllers:
Setting the PS3 controller's master address to your phone's bluetooth mac address via Windows:

  1. Download and install Motion in Joy.
  2. Run DS3 Tool, installed in the previous step.
  3. Click the "About" tab in DS3 Tool to see the version. If DS3 Tool is less than 0.5.0003 you will need to update.
  4. Connect your PS3 Controller to your computer via the USB cable and wait while Windows recognizes the new device.
  5. Click on the "BluetoothPair" tab.
  6. In the DUALSHOCK 3 drop down list select your controller. If it says "Can't find connected(USB) Playstat":
    • Click "Driver Manager" directly above the drop down list
    • Click "Load" and wait for it to finish
    • Return to the "BluetoothPair" tab
  7. Run CobaltController on your Windows Mobile device to get its BT address.
  8. Enter that BT address into the text box directly above the DUALSHOCK 3 drop down list. Note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, a bluetooth address of "00:23:76:70:6B:4D" is entered it into Motion in Joy as "4d.6b.70.76.23.00"
  9. Click the radio button next to this textbox to make sure that it uses the one you entered and not the one above it which is to connect your controller to your PC
  10. Click "Pair Now"
  11. If all went well your controller is now configured to talk to your Windows Mobile device. Go to the "Quick Start" tab and click "Disconnect".
  12. Unplug your PS3 Controller.
  13. As long as you don't pair your controller with any other device (like your PS3) then you never have to do this again. If you do pair the controller with a another device and wish to re-pair it with your phone again, repeat the above steps.

Widcomm Stack Specifics:
  • Turn on bluetooth and set it to discoverable. Thanks to ryotgz, skilty, and gorelshv for this information. I believe it is only required the first time you use CobaltController. Once you have successfully connected, BT does not have to be in discoverable mode any longer so you can change it back to invisible to save battery life.
  • Make sure that the checkbox is not checked where it says "Allow only devices listed in 'My Devices' to connect".
  • If you have never tried to connect the PS3 controller to your phone before (or at least not since the last hard reset or rom flash) it will fail to connect at first and you'll get a bunch of pop ups with PLAYSTATION(R)3 Controller shown in bold asking for the pin. Keep tapping cancel as it pops up and wait for everything to stop trying to connect. After all that, try again and it should connect just fine and should always connect right away in the future without the pin prompts. There is no pin (that I know of at least) I'm bypassing security on both the PS3 and Wii connections (even though we do know the pin for the Wiimote is the host's mac backwards.)

Microsoft Stack Specifics:
  • TURN OFF BLUETOOTH The MS stack does not like the PS3 controller and will NOT pair with it. I ended up writing a modified version of this stack to get around this problem, but it will conflict with the real MS stack so they can't both be on at the same time.
  • Your phone will reboot when you disconnect the controller.

PS3 Controller Specifics:
  • Press the PS button to connect and then later to disconnect

Wii Controller Specifics:
  • Press the red Sync button to connect. Hold down the Power button to disconnect.

Common:
  • All 4 LEDs should flash a few times and then only the player one LED should remain lit showing it connected.
  • The driver stops running after you disconnect to save battery life. Run it again to reconnect. It's in Start Menu\Programs\Games
  • Registry Values are stored in HKEY_CURRENT_USER\Software\Cobaltikus\CobaltController
  • Currently only 1 controller can be active at a time but I am exploring the ability to add more.
  • Once you are connected you can tap Menu > Exit to close the configuration program and your controller will remain connected, and the driver will continue to run until your controller is disconnected.

To Do: (not necessarily in this order)
  • Get Wiimote working on devices with the Microsoft Bluetooth stack
  • Figure out why this doesn't work on the TG01 and HTC Vogue and fix it
  • 2 player support
  • Battery meter
  • Integrate LeSScro graphics
  • Clean up Microsoft stack code to eliminate the need to reboot
  • Add support for non-touch-screen devices

Attachments
  • CobaltController.vX.X.cab = Installs to \Program Files\CobaltController\ and a shortcut goes to \Windows\Start Menu\Programs\Games
  • NETCFv35.wm.armv4i.cab = Although the CobaltController driver is written in native C++, the UI is written in .Net 3.5, therefore you will need to have .NetCF 3.5 installed on your device to run the UI. You might already have this by default so try without this first, and come back if you get an error message about needing it.
  • NETCFv35.Messages.EN.wm.cab = Provides more details when .Net errors occur with any program written in .Net 3.5. This is optional and only needed if a .Net error occurs and you wish to see more details about that error.

Change Log
  • v0.7
    • Sorry - no actual driver enhancements yet - just bug fixes
    • IMPORTANT - Different Default Buttons - you may need to remap in your emulator settings
    • Updated instructions (Menu > Instructions)
    • Menu reorganized, some new menu items exist
    • More Bluetooth "stuff" working in the UI
    • UI Settings Bug Fixes (values not sticking etc)
  • v0.6
    • ANALOG STICKS WORKING!
    • Menu reorganized, some new menu items exist
    • More Bluetooth "stuff" in the UI - Mainly for devices with the M$ stack
    • Some other tweaks and changes but these are all the important ones.
  • v0.5
    • New Icon
    • UI Uses .Net 3.5, (driver is still c++)
    • Option to restore default keycodes
    • Bluetooth Address shown on screen so you don't have to search for it
    • 229 fix - it could cause you to not like how the SIP works in other programs but you can always restore, so no worries.
    • I might have forgotten about another change or two but these are all the important ones.
  • v0.4
    • Updated Instructions (Menu > Help > Instructions > [PS3|Wii])
    • Added Menu > Help > About to verify version
 

Attachments

  • CobaltController.v0.3.CAB
    187.5 KB · Views: 2,050
  • CobaltController.v0.4.CAB
    190.6 KB · Views: 1,140
  • CobaltController.v0.5.CAB
    373.5 KB · Views: 1,387
  • NETCFv35.Messages.EN.wm.cab
    136.3 KB · Views: 1,405
  • NETCFv35.wm.armv4i.cab
    2.6 MB · Views: 2,129
  • CobaltController.v0.6.CAB
    486.7 KB · Views: 1,736
  • CobaltController.v0.7.CAB
    536.7 KB · Views: 8,963
Last edited:
  • Like
Reactions: symbuzzer

Cobaltikus

Senior Member
Buttons - There are editable registry values to modify the button mappings - below are the defaults

Code:
Sixaxis Button   Keyboard Equivalent
--------------   -------------------
SELECT           A
LEFTCLICK        B
RIGHTCLICK       C
START            Enter
UP               Up
RIGHT            Right
DOWN             Down
LEFT             Left
L2               D
R2               E
L1               F
R1               G
TRIANGLE         Space
CIRCLE           O
X                X
SQUARE           Backspace

These are all the digital buttons - I will eventually implement the left analog stick to send Up, Right, Down, and Left. Not yet sure what to do with the right stick... window scrolling maybe?
 
Last edited:

Cobaltikus

Senior Member
dece. how did u manage to get the drifvers for hid support?

I didn't

I used Visual Studio 2008 + Windows Mobile 6 SDK + Widcomm SDK

I'm using L2CAP

Although the HID GUID is not defined, you can hard code the values for it and vwahlah - it works!

It runs great on my Sprint Touch Pro2 and also the HTC HD2 but should work for any Windows Mobile device with a Widcomm Bluetooth stack - again though I fully plan to tackle the M$ stack as well and also add support for the wiimote.
 

Cobaltikus

Senior Member
Request:

That would be really cool if someone would write a nice app to set the sixaxis master bluetooth address that doesn't require a pc with bluetooth and other apps. That would make my app even better - cuz I know the setup really sucks - but believe me it is worth it, especially if your phone also has TV Out.
 
Last edited:

Mase_Mase

Senior Member
May 6, 2008
91
1
I've been lurking on the other BT controller thread and I must say I was very anxious to see what you guys could pull off! Great, great work!!!
 

Hammerfest

Senior Member
Apr 3, 2008
1,659
279
San Antonio, TX
same here as above, lurking in the BT Controller thread (and even in the request thread for PS3 on PPC)

where the **** is the donation address I said I had $5 for a working PS3 and while I havent had the chance to test it yet I want to ****ing donate as soon as I have (yes the word **** was necessary to use, it conveys emotion and as is said, words are only as powerful as you make them)
 

Cobaltikus

Senior Member
It would be awsome if this could trigger some devs to make it vice versa, so that you can use your phone to control media stuff on the ps3 :)

I was looking into that a little bit and it seems completely possible - it's just a matter of devoting the time. If no one else does it first I'll probably end up doing it eventually - after this program grows more

My main goal right now as far as this is concerned is to get it working on all windows mobile phones.
 

itoYo

Senior Member
Apr 4, 2007
350
4
ASDA
good job, lets hope we can get it working with FPSECE, if thats the case i am willing to donate £5. you better get your paypal address sorted!

thanks
 

braindoc

Member
Feb 4, 2008
33
0
It would be awsome if this could trigger some devs to make it vice versa, so that you can use your phone to control media stuff on the ps3 :)

I agree. I use my PS2 to watch a lot of movies and it would be great if I could use my phone as the remote control instead of using the standard controller.
 

frmariam

Senior Member
Oct 21, 2008
550
3
How about Morphgear?

I'm all for OSS apps so this seems only natural :D

Morphgear is very similar with Smartgear with the difference of being free and open for development (you can get the sources at SourceForge). And it surely could use a boost and more attention.
 

Cobaltikus

Senior Member
good job, lets hope we can get it working with FPSECE, if thats the case i am willing to donate £5. you better get your paypal address sorted!

thanks

I don't see why it wouldn't work with FPSECE - it works with anything that accepts keyboard input - you can even text with it so long as you don't need more letters than A, B, C, D, E, F, G, O, and X, maybe I should use letters like WTFLMAO instead...

I put a link to donate in the first post http://www.cobaltikus.com

If you donate - that would be awesome - I've never received any donations before.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Good News!

    GOOD NEWS EVERYONE!!!

    My divorce is final, and my girlfriend dumped me.

    Therefore, I am taking advantage of this massive influx of extra time to work on the Android port of CobaltController.

    I'm getting the HTC Arrive on March 20th so expect a Windows Phone 7 port eventually as well. Unless of course another hottie snatches me up and drains the rest of my life out of me.

    Going to Poe's Pub for some drinks and bar food alone with my laptop and free wi-fi. Side note: It's Open Mic night, just fyi, in case anyone cares to stop by and play a tune.
    1
    CobaltController

    Use your Sony Playstation 3 Controller (Sixaxis/Dual Shock 3) or Nintendo Wii Remote (Wiimote) as a Bluetooth Game Controller on your Windows Phone.

    It's perfect for game system emulators.

    Play PlaystationOne games with FpseCE, Super Nintendo games (and more) with MorphGear (HD2 version), Nintendo, Genesis, GameBoy, GameGear games (and more) with SmartGear - There are many other emulators out there and this program/driver will work for anything that accepts keyboard input.

    Compatibility
    Post your results and I will update this list
    Code:
    DEVICE                    PS3  Wii  Confirmed By
    ------------------------- ---  ---  -------------
    Acer beTouch E200         ?    Yes  pmprog
    Acer Neotouch S200        Yes  Yes  Fenrir84 (PS3) / Snowball2010 (Wii)
    HTC HD2                   Yes  Yes  Cobaltikus
    HTC Touch Diamond         Yes  No   koert17 (PS3) / nightly_shadow (Wii)
    HTC Touch HD (Blackstone) Yes  Yes  RDilus
    HTC Touch Pro             Yes  No   Cobaltikus
    HTC Touch Pro2            Yes  Yes  Cobaltikus
    HTC Touch2 Mega           Yes  ?    RipNWO
    HTC Vogue                 No   No   Mycle78
    HTC Wizard                No   ?    shorty66
    LG Expo                   Yes  Yes  dalb3 (PS3) / trueg (Wii)
    Samsung SCH-i730          No   No   Cobaltikus
    Samsung i780              Yes  ?    ShadowswordPL
    Samsung SCH-i830          No   No   Cobaltikus
    Samsung Omnia I900        Yes  No   Manny-77
    Samsung Omnia II i8000    Yes  No   cyber-junkie
    Sony Xperia               Yes  No   sashapont (PS3) / stratis10 (Wii)
    Toshiba TG01              No   No   Cobaltikus
    ...                       ...  ...  ...
    Your Device               ?    ?    You
    You Tube Videos
    http://www.youtube.com/watch?v=mH_NBKtj0R8 (Thanks i900frenchaddict)
    http://www.youtube.com/watch?v=3dH9J1y0G-8 (Thanks ahmedsaid)
    http://www.youtube.com/watch?v=Qo-_nMmYq1Y (Thanks dijay_94)
    http://www.youtube.com/watch?v=HauZQWYZxmQ (Thanks ShadowswordPL)

    Prerequisites:
    • PS3 Controller
      • A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post.
      • A PS3 Controller (I don't know if non-Sony 3rd party controllers work - maybe they do, maybe they don't).
      • A desktop or laptop computer with a USB port to set the controller's master address.
        • Linux - Use sixpair - directions in this thread somewhere, search for "Ubuntu"
        • Windows - Use Motion in Joy, but please note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, when I run CobaltController on my Touch Pro2 it displays "BT ADDR: 00:23:76:70:6B:4D" so I enter it into Motion in Joy as 4d.6b.70.76.23.00
    • Wii Controller
      • A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post. Devices with the Microsoft Bluetooth Stack can't use the Wiimote yet.
      • A Wii Controller.
    • XBOX 360 Controller
      Not Going To Happen
      In order to get the XBOX 360 controller to work in windows you need to purchase a wireless receiver - it doesn't use bluetooth. It needs additional hardware. So if a full desktop Windows PC can't even do it without additional hardware, I seriously doubt it will ever work for our phones. Some company could come up with an xbox 360 wireless receiver for Windows Mobile, but again, very doubtful. And since I don't even have an XBOX of any kind, I know I'm not going to be motivated enough to even try.

    Initial One Time Setup for PS3 Controllers:
    Setting the PS3 controller's master address to your phone's bluetooth mac address via Windows:

    1. Download and install Motion in Joy.
    2. Run DS3 Tool, installed in the previous step.
    3. Click the "About" tab in DS3 Tool to see the version. If DS3 Tool is less than 0.5.0003 you will need to update.
    4. Connect your PS3 Controller to your computer via the USB cable and wait while Windows recognizes the new device.
    5. Click on the "BluetoothPair" tab.
    6. In the DUALSHOCK 3 drop down list select your controller. If it says "Can't find connected(USB) Playstat":
      • Click "Driver Manager" directly above the drop down list
      • Click "Load" and wait for it to finish
      • Return to the "BluetoothPair" tab
    7. Run CobaltController on your Windows Mobile device to get its BT address.
    8. Enter that BT address into the text box directly above the DUALSHOCK 3 drop down list. Note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, a bluetooth address of "00:23:76:70:6B:4D" is entered it into Motion in Joy as "4d.6b.70.76.23.00"
    9. Click the radio button next to this textbox to make sure that it uses the one you entered and not the one above it which is to connect your controller to your PC
    10. Click "Pair Now"
    11. If all went well your controller is now configured to talk to your Windows Mobile device. Go to the "Quick Start" tab and click "Disconnect".
    12. Unplug your PS3 Controller.
    13. As long as you don't pair your controller with any other device (like your PS3) then you never have to do this again. If you do pair the controller with a another device and wish to re-pair it with your phone again, repeat the above steps.

    Widcomm Stack Specifics:
    • Turn on bluetooth and set it to discoverable. Thanks to ryotgz, skilty, and gorelshv for this information. I believe it is only required the first time you use CobaltController. Once you have successfully connected, BT does not have to be in discoverable mode any longer so you can change it back to invisible to save battery life.
    • Make sure that the checkbox is not checked where it says "Allow only devices listed in 'My Devices' to connect".
    • If you have never tried to connect the PS3 controller to your phone before (or at least not since the last hard reset or rom flash) it will fail to connect at first and you'll get a bunch of pop ups with PLAYSTATION(R)3 Controller shown in bold asking for the pin. Keep tapping cancel as it pops up and wait for everything to stop trying to connect. After all that, try again and it should connect just fine and should always connect right away in the future without the pin prompts. There is no pin (that I know of at least) I'm bypassing security on both the PS3 and Wii connections (even though we do know the pin for the Wiimote is the host's mac backwards.)

    Microsoft Stack Specifics:
    • TURN OFF BLUETOOTH The MS stack does not like the PS3 controller and will NOT pair with it. I ended up writing a modified version of this stack to get around this problem, but it will conflict with the real MS stack so they can't both be on at the same time.
    • Your phone will reboot when you disconnect the controller.

    PS3 Controller Specifics:
    • Press the PS button to connect and then later to disconnect

    Wii Controller Specifics:
    • Press the red Sync button to connect. Hold down the Power button to disconnect.

    Common:
    • All 4 LEDs should flash a few times and then only the player one LED should remain lit showing it connected.
    • The driver stops running after you disconnect to save battery life. Run it again to reconnect. It's in Start Menu\Programs\Games
    • Registry Values are stored in HKEY_CURRENT_USER\Software\Cobaltikus\CobaltController
    • Currently only 1 controller can be active at a time but I am exploring the ability to add more.
    • Once you are connected you can tap Menu > Exit to close the configuration program and your controller will remain connected, and the driver will continue to run until your controller is disconnected.

    To Do: (not necessarily in this order)
    • Get Wiimote working on devices with the Microsoft Bluetooth stack
    • Figure out why this doesn't work on the TG01 and HTC Vogue and fix it
    • 2 player support
    • Battery meter
    • Integrate LeSScro graphics
    • Clean up Microsoft stack code to eliminate the need to reboot
    • Add support for non-touch-screen devices

    Attachments
    • CobaltController.vX.X.cab = Installs to \Program Files\CobaltController\ and a shortcut goes to \Windows\Start Menu\Programs\Games
    • NETCFv35.wm.armv4i.cab = Although the CobaltController driver is written in native C++, the UI is written in .Net 3.5, therefore you will need to have .NetCF 3.5 installed on your device to run the UI. You might already have this by default so try without this first, and come back if you get an error message about needing it.
    • NETCFv35.Messages.EN.wm.cab = Provides more details when .Net errors occur with any program written in .Net 3.5. This is optional and only needed if a .Net error occurs and you wish to see more details about that error.

    Change Log
    • v0.7
      • Sorry - no actual driver enhancements yet - just bug fixes
      • IMPORTANT - Different Default Buttons - you may need to remap in your emulator settings
      • Updated instructions (Menu > Instructions)
      • Menu reorganized, some new menu items exist
      • More Bluetooth "stuff" working in the UI
      • UI Settings Bug Fixes (values not sticking etc)
    • v0.6
      • ANALOG STICKS WORKING!
      • Menu reorganized, some new menu items exist
      • More Bluetooth "stuff" in the UI - Mainly for devices with the M$ stack
      • Some other tweaks and changes but these are all the important ones.
    • v0.5
      • New Icon
      • UI Uses .Net 3.5, (driver is still c++)
      • Option to restore default keycodes
      • Bluetooth Address shown on screen so you don't have to search for it
      • 229 fix - it could cause you to not like how the SIP works in other programs but you can always restore, so no worries.
      • I might have forgotten about another change or two but these are all the important ones.
    • v0.4
      • Updated Instructions (Menu > Help > Instructions > [PS3|Wii])
      • Added Menu > Help > About to verify version
    1
    Great App. Flawless Victory!

    I've been using this on my HD2, and must say, you've outdone yourself Kobaltikus.

    I <3 you!!!​

    Just donated $5 - I think everyone here who uses your app should follow suit. It takes work to code, and guts to release working programs for free. Cobaltikus deserves it :D

    I now have a PS3 controller to play my NES, SNES, Sega Genesis, PSOne, and GameBoy color games. I'm getting virtually flawless emulation out of all these systems after some good research.

    Using Cobalt Controller for Emulators

    The following is how I got my new PS3 Cobalt Controller working on my HD2 alongside virtually flawless emulation of my games. I was dreadfully frustrated in finding the best emulators, AND getting them working with my new PS3 controller, but I now have it all figured out to a 'T'. I'm posting this because I was hoping someone would do the same for me. Enjoy!

    NES: I use PocketNester. The only problem with PocketNester, is it doesn't support soft-keys, and thus no Cobalt Controller.
    Fix: Install PocketNesterPlus (soft-key support), then go back to using PocketNester. The mappings now work flawlessly, and the emulation is near perfect.

    SNES: Morphgear is a really decent SNES emulator. Problem: when mapping keys, the mappings only show up as '229' in the settings.
    Fix: Find and install KforTP, made by ShinRa. Switch to M$.
    Also, mappings still won't work in-game.
    Fix: Go to 'Global Settings', enable 'Polling Method'.

    Sega Genesis: SmartGear is nearly perfect for this. Go to the main page, and look under the Latest News for " ... new fixes/features and give it a try here." - click 'here'. Scroll down to the download link for the beta version. Might need KforTP - I forget if I needed it for this one.

    PSOne: Use FPSECE. Select the controller icon, and press on the buttons you want to map on your screen (yes, press on the buttons that are on the controller image on your screen), then press the respective button on the controller.
    Bug: I noticed that if R1 is pressed while FPSECE is open, FPSECE thinks it's stuck down and when you go to map any other buttons, it sets those buttons to the R1 key. Have to reset to get rid of this. Use an analogue stick button for this instead.
    Edit: This is an old bug - it has been fixed with the newer version of Cobalt Controller. *where have I been?! - gasps*
    Thanks Cobalt!

    Gameboy Color
    : I use MorphGear for this - it works great. No issues so far.
    1
    Ya, I discuss the sad state of Emulators for Windows Mobile on my site (http://www.computerabuser.com/?p=876). Anyway, from there you can link to a roundup I did for WVGA compatible emulators on a different forum. It's not all bad, especially if you are willing to shell out $10 for SmartGear which is pretty awesome.
    1
    pls do it for andorid

    That's the plan. I still have a lot to learn tho.