My Xoom is running Tiamat ROM "hammerhead". I used the basic install from their post. That gives you some idea of what my software looks like.
I bought the Motorola Xoom camera kit to use a ps3 controller with my xoom. I used sixaxis controller for a while. Unfortunately that application does not support analog sticks. It will use them as the Dpad but it's a no go for certain games requiring both analog sticks. My hope was that this method DID prove fruitful with those games; However after plugging the ps3 controller in i noticed that the lights blink, but im unable to use the controller. It doesn't work with any of my emulators when trying to map the keys for playing.
The last thing i can think is that it's the ROM im using and I need to go back to stock, but i htoiught i'd try here first before spending a few hours reflashing stock roms and loading MicroSD card scripts.
Nv1dia said:
My Xoom is running Tiamat ROM "hammerhead". I used the basic install from their post. That gives you some idea of what my software looks like.
I bought the Motorola Xoom camera kit to use a ps3 controller with my xoom. I used sixaxis controller for a while. Unfortunately that application does not support analog sticks. It will use them as the Dpad but it's a no go for certain games requiring both analog sticks. My hope was that this method DID prove fruitful with those games; However after plugging the ps3 controller in i noticed that the lights blink, but im unable to use the controller. It doesn't work with any of my emulators when trying to map the keys for playing.
The last thing i can think is that it's the ROM im using and I need to go back to stock, but i htoiught i'd try here first before spending a few hours reflashing stock roms and loading MicroSD card scripts.
Click to expand...
Click to collapse
I can't help you with this but you could make your post title more descriptive of your issue to attract attention from gamers.
I appreciate the reply, though I wanted more Input than a gamer could possibly provide. The issue has been resolved though. I don't quite know what I did but hitting buttons on the desktop made it work. So I'm happy.
Nv1dia said:
I appreciate the reply, though I wanted more Input than a gamer could possibly provide. The issue has been resolved though. I don't quite know what I did but hitting buttons on the desktop made it work. So I'm happy.
Click to expand...
Click to collapse
I'm glad you resolved it. I doubt the problem had anything to do with the rom, but I had hoped someone that used those emulators would be able to assist.
Related
has anyone got it to work yet? if so did you have to root for whatever reason? i'm asking because I don't want to go buy a wii mote without knowing for sure i can use it.
It doesn't work on mine...
From what I've read, there is no support for HID in Samsungs bluetooth stack, meaning no keyboards, mice, wiimotes, etc. until someone (possibly Samsung themselves) rectifies this problem.
I'm hoping Froyo will fix this problem...
macsmister said:
I'm hoping Froyo will fix this problem...
Click to expand...
Click to collapse
Or a good ROM
I'm just curious as to why and what you would use a Wiimote for?
using an app from the market you can use the wiimote as a bluetooth game controller. the only reason i used it on my D1 was to play emulators. it was loads of fun to put it in the dock on my desk at work and play nes games using the wiimote as a controler. and you can even connect a nunchuck or classic controller to play snesoid or psx4droid. technically you can map it to any keyboard key, so you could use it for any application that allows for keyboard or softkey input.
Is there a solution to this yet?
Solution
Sorry no solution until Froyo comes out. Froyo supports HID thus the same reason why Cyanogen Mod 6.1 also supports it. I hope now that the Epic has had Froyo released Verizon will get competitive and get it out of the door, I'm excited to attach my apple blue tooth keyboard to it for note taking in class.
Can use a Zeemote ZS1 with our phones though. Need to use the MMG GamePro driver. Works in emulators though. Kind of a ***** to setup. Haven't tried any ZeeMote native games yet.
Zeemote Option
I can personally attest to the Zeemote working. After paying $17.45USB (10.78 British pounds) to purchase one off of Ebay and wait for shipping, I then paid Gamepro $9.95 for the registration code for my particular bluetooth profile. So, if having decent emulator gaming is worth $27.40, go for it!!
The wiimote is working great for me in Vanilla Froyo 0.9.3.
FYI: You use the wiimote controller app to pair, not the regular bluetooth settings.
EnigmaCurry said:
The wiimote is working great for me in Vanilla Froyo 0.9.3.
FYI: You use the wiimote controller app to pair, not the regular bluetooth settings.
Click to expand...
Click to collapse
How? What did you do?
Syn Ack said:
How? What did you do?
Click to expand...
Click to collapse
I installed Vanilla Froyo
I installed the Wiimote controller app
I connected my wiimote through the wiimote app NOT the bluetooth settings dialog (ie, no need to pair)
I installed nesoid, chose the wiimote input mode in the preferences, and mapped my key bindings.
profit!
will it work with any other Froyo release (EB01, EC10), or only source-built/AOSP?
exnihilo said:
will it work with any other Froyo release (EB01, EC10), or only source-built/AOSP?
Click to expand...
Click to collapse
From what I understand it's AOSP only because it's the bad samsung bluetooth stack that's the problem in the first place. Vanilla Froyo has really grown up though, it's a very stable and featureful rom now.
Could somebody who already has a Wiimote tell us if it works w/the 2.2 OTA update that was (finally) just released?
Nope doesn't work
You can use any aosp based rom such as vanilla, cyanogenmod, or MIUI. But anything with Touchwiz bluetooth stack won't work.
Apologies if this has already been asked, but I did do a search and didn't find much - I have both fpse and psx4droid, but I cannot get either of them to load a ROM.
I've tried ROMs I've created myself from old Playstation discs I still have lying around the house, and when those didn't work I downloaded a couple and couldn't get those to work either. psx4droid just won't load the ROMs, and fpse crashes all the time, sometimes when changing settings, mostly when trying to load ROMs.
Has anyone got either of these two programs to work on their Transformer yet? If so, what settings do you have?
Thanks a lot!
I guess it's a Honeycomb thing. FPSE works fine on my G Tablet.
EDIT: Then again maybe not:
http://technidroid.com/2011/04/08/fpse-working-great-on-honeycomb/
It might be a honeycomb thing, but both fpse and psx4droid are listed in the compatible honeycomb apps thread, so someone somewhere must have them working!
EDIT: I have posted a comment there asking, thanks. I guess the question is what Tablet they got fpse working on, and whether it was a Transformer! Fpse crashes like crazy on mine, often when just trying to do simple things, like open the settings.
EDIT2: Got this working. I completely uninstalled and reinstalled the app, and moved the bios file and roms to a folder on the a 16gb micro SD card. All works wonderfully now! I also have the first three graphics options selected, hope this helps anyone in the position I was in!
So sir_earl has done us all a great service by making it possible to use the Playstation 3 controller with Android phones. He posted about it in http://forum.xda-developers.com/showthread.php?t=1179929
But unfortunately for us, it's not compatible with the Sidekick 4G or several other recent Samsung phones. It sounds like our stock ROM doesn't give it the access it needs to the bluetooth hardware. What would it take to fix this? Is it something we can add with a custom kernel?
(BTW, I am the farthest thing from a software developer on the face of the earth, so sorry if I turn out to be Captain Oblivious.)
This is not an issue with access, but rather that certain protocols aren't built into our driver.
Think of it like this; you're trying to use an Xbox controller with a Playstation. They're both controllers, but they don't know how to talk to each other.
This would require either rewriting the bluetooth driver ( not feasible) or seeing if the driver is similar in our phones to that of one of the working phones.
EDIT: took a look in the kernel config, and found some bluetooth protocols that weren't enabled, that according to http://www.pabr.org/sixlinux/sixlinux.en.html are the same as the ones that the controller uses? not sure.
EDIT2: Tried enabling all the bluetooth options in the kernel config, couldn't get the compat checker to tell me anything good, still just says missing protocol, even though HID (what it should be) is enabled. I PM'd sir_earl to see what protocol is required and which phones it works on, perhaps I can see if their driver will build with our kernel, or if I can somehow mash together our sources to make it work.
That's a great start. I'd be really happy if we could make this work.
Our phone has all the power it needs to run things like N64 and PS1 emulators, and combined with the TV out cable, we've effectively got a dozen game consoles in our pockets. We just need a good way of controlling them.
Update: got a PM back from sir_earl, it's true that Samsung left out the BT protocol we need to use this, it's called "L2CAP via raw sockets" (from sir_earl). He suggested that using the AOSP/CM BT stack would be a good place to try, so I may give that a shot sometime later, as my list of projects is somewhat long right now.
Thanks for getting to the bottom of this. Here's hoping you get a chance to try it.
Did you have a chance to fiddle with this any more? I'd sure like to be able to use a proper gamepad with all the awesome emulators that run on these phones.
Tried looking at it, but the bluetooth stack that has proper support didn't work by just being added to our Kernel. I'm also kinda working on porting our kernel to be compatible with CM6/7, which would be easier to add the bluetooth stack to.
For anyone who plays FPSE with a Wii Controller + Classic Controller, could you send me your fpse.ini file? I am going to try to use it to map the buttons since hardware keys under input does not work for me. Wii remote connects to the Wii input app perfectly fine, and verified working, but will not work in FPSe. I have un-installed and reinstalled everything several times. The only thing I have not done is revert back to 2.2.3. I dont think that is worth it.
Data/Data/com.emulator.fpse/files/fpse.ini
PM or Email: [email protected]
Thanks in advance!
EDIT: I have come to the conclusion that when I updated to 2.3.3 (Pre-rooted GB)[Droid X2] It broke the ability for Bluetooth to communicate with emulators. Prior to update, I could play games on Wii controller no problem. Now I cannot. I fired up my old D1, installed apps in question, everything worked flawlessly (minus it's old and slow, spent a lot of time in Afghanistan) so I took the fpse.ini file that was created there, and transferred it over to manually map the buttons. Did not work.
If anyone has any suggestions, theories, fixes, a hammer or whatever may help, please do. Anyone know what was changed that may have broken this? Bluetooth stack 2.0?
Good afternoon all,
My first post here so I apologize if there is any existing thread on this, there wasn't as far as I could see.
My build is a GT-N8013 on Android 4.0.4.
I am running the latest Sixaxis Controller App and FPSE 0.11.75.
Rooted w/Chainfire's Exynos.
Basically, I did the setup on existing posts for getting the controller recognized by the Android Device (Running an original CECHZC2U Wireless Dualshock/Sixasis Controller).
I have spent a few hours trying to set up the controller for use with Breath of Fire 3.
No matter how which settings I try, I end up with either the Circle or the X Button failing. I have tried several setups but I am at a loss as to what could be causing the issue.
Would greatly appreciate any assistance on how to properly set up both the Sixaxis and FPSE area.
Thanks in advance,
Deb