Database Develop

Bluetooth controllers?

Are there any bluetooth controllers currently compatible with the SGS?
I know I can use the Wii controller, but I don't have a Wii, so that idea probably isn't best.
Thanks in advance.

not really an answer to your post, but...presumably either way you'd also have to buy a Bluetooth controller so it's probably just as easy to pick up a Wii one?

I would prefer something a little more portable and cheaper if at all possible

From what i've seen, the Wiimote is not working on the i9000 yet.
Correct me if i'm wrong please. (And seriously, this time i want to be wrong)

If you can get a Wii controller working, shout me - I've been trying since I got my Galaxy with every different firmware/update combination - it's a no go at the moment.
Ryan Frawley replied to an email I sent saying it's down to samsung's bluetooth drivers being modified as compared to the standard Android drivers.
As I was writing this post, I checked my mail to look up Ryan's reply, and found a reply from Samsung to a mail I sent a few days ago (last friday I think). I will post the conversation in it's entirety here, I hope the employees at Samsung do not mind, as I do quote this without permission:
Hello, and thank you for your time.
I have a question regarding connection of HID devices and, in particular, the WiiMote (Nintendo) to the phone, through applications available through Google Market.
Applications (such as 'Wii Controller IME' from Ryan Frawley) using bluetooth to cennect to certain HID devices appear to be unable to connect to the bluetooth drivers (the application fails to connect, and does not appear to be able to get as far as searching for the device).
Are there any plans to update/fix the bluetooth drivers to address this issue in upcoming firmware updates?
Does the upcoming Android 2.2 (FroYo) update address the issue, and should we so wait until the release of the 2.2 update?
Click to expand...
Click to collapse
Reply:
With regard to youremail, these are questions that need to be
redirected to Android, as we do not make the applications that connect
to the Wii-mote, and also have no information on the Froyo upgrade.
I hope this has been of someassistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-
reference number.
Kind Regards
Click to expand...
Click to collapse
My reply:
hank you for your reply to ref# XXXXXXXXXX.
I will try and contact Android customer service to expand on the query, but I have some more questions I would like to ask to clarify the situation:
- you state that Android is responsible for the applications which connect to the Wii remote. However, the Android version which is installed on the Galaxy will have been researched and developed by Samsung's own technicians.
The applications on the market are capable of connecting to the Wii remotes (and other bluetooth devices) on other Android devices - yet all applications have issues connecting through the bluetooth drivers on the Galaxy. Indeed, I have yet to find even a standard HID device which connects to the Galaxy successfully.
By it's very nature, Android is open sourced - anyone with technical know how should be able to view the internal workings of the operating system and (often in an attempt to fix problems like this) edit the underlying files.
It appears that the bluetooth drivers (along with all hardware drivers on the Galaxy), as supplied by Samsung are not open sourced. Nor do they adhere to the standards which applications on the Android market are able to connect to bluetooth.
This in turn points at problems with the Galaxy, and/or it's bluetooth drivers, which are, of course, designed and supplied by Samsung.
Please, if possible, can this issue be escalated to a technical team - I understand the issues of getting a problem raised within a multinational company; I work for one myself and deal with such issues on a daily basis.
I would greatly appreciate your help in dealiing with this issue, and getting help in raising it to the correct team/department to have the issue resolved, if it is at all possible.
Again, thank you for your time,
Click to expand...
Click to collapse
As usual, I don't expect much to come from this to be honest - my previous experience with this kind of query tells me that it'll get shoved under the carpet relatively quickly.
We'll probably be waiting until a proper Cyanogen ROM turns up, or someone gets either Ryan Frawley to patch up the application side (though I'd much rather the bluetooth drivers were standardised to begin with).
PS: Anyone tried a zeemote, mini bluetooth keyboard yet? I'm tempted to throw £30 or so on a keyboard/zeemote combo but I would like to know if it's something that will work out of the box or not.

I feel the need to bump this thread, since I'm so in need of this functionality.

Well, I got an update from Samsung. This sounds very promising, I hope they follow through with what they've told me:
Thank you for contacting Samsung Electronics regarding your mobile phone.
Please accept our sincere apologies for the delay in responding to your enquiry.
With regard to your email, this issue has been passed to our development team and has been raised with Head
Office as well. There is a solution in development and will be forthcoming shortly.
Please keep checking the website for updates on this issue.
I hope this has been of some assistance to you.
Click to expand...
Click to collapse
Raised with Head Office? Hmmm...

What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.

AlexandreT said:
What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.
Click to expand...
Click to collapse
Did you try this? www.appbrain.com/app/com.mymobilegear

AlexandreT said:
What about connecting a PS3 official keypad (the one you attach to the PS3 controller) to the SGS? It would be useful to use in games like Quake 2 and 3, that need a physical keyboard to play. Has anyone done this? I have tried and have been unable to get it working.
The SGS can see the keypad, can pair, asks for the password but fails to connect.
Click to expand...
Click to collapse
That's the problem with most devices - the SGS will see the device and it's MAC address when scanning, but won't connect. Usually "0000" gives a very quick refusal, where anything else (the only way I've found to enter a blank PIN is to enter a digit then delete it) gives a rather long wait with "Connecting" then a message telling you it failed to connect.
Most 3rd party apps don't work either, though I've had success with the GamePro app NZTechFreak used - it's the only app I've found on the SGS up to now that does work with bluetooth. I'm pretty confident KeyPro from the same company would work, but I don't have a compatible keyboard to test.
Up to now, i've tried:
Wii remote/classic controller (original) - SGS sees controller, will not pair
Bluetooth "I-Tom" keyboard (ebay) - Despite coming with android drivers, does not work. Same symptoms as other controllers, third party app does not detect nor connect to controller.
Datel Wii Classic Controller - same as Wii controller
Zeemote - Works with GamePro drivers. Zeemote does not pair directly with SGS, it's all handled through the GamePro IME drivers/settings
I'd like to see if a PS3 controller pairs successfully, but from what you've said I doubt it very much
e: The app in the post above only has support for some very specific keyboards. By all means try it, I tried each one on my itom keyboard but nothing worked.

SquidgyB said:
Well, I got an update from Samsung. This sounds very promising, I hope they follow through with what they've told me:
Raised with Head Office? Hmmm...
Click to expand...
Click to collapse
Have you got any update on this?

I am also wondering. I have been trying to pair a bluetooth mouse with no luck.

ei0haro said:
Have you got any update on this?
Click to expand...
Click to collapse
Heh - nope. 'Fraid not.

[BUMP!]
Samsung has released 2.2 but still does not work.
Samsung has also released the source for many of their phones.
http ://opensource.samsung.com
It would be great to get this fixed.
Jim

jim0watters said:
[BUMP!]
Samsung has released 2.2 but still does not work.
Samsung has also released the source for many of their phones.
http ://opensource.samsung.com
It would be great to get this fixed.
Jim
Click to expand...
Click to collapse
Bumpity bump bump bump

apparantly latest cyanogenmod7 for SGS works with wiimote
I might start using it after the cameras are fully working and a few other bugs fixed.

oswade said:
apparantly latest cyanogenmod7 for SGS works with wiimote
I might start using it after the cameras are fully working and a few other bugs fixed.
Click to expand...
Click to collapse
Yahh it does work ;D I wonder if there's a way we can build a samsung kernel with the bluetooth modules from cyanogenmod? Hopefully the cameras are fixed soon this is a showstopper bug for me atm

[Q] Working bluetooth gamepad for TAB

Hi has anyone found a working Bluetooth gamepad for the TAB?
I know that the Zeemote works (I have one), but its not quite the gaming experience that Im looking for, Im looking for a gamepad for playing genesis/snes/nes etc emultors and for that the one hand zeemote does not really work.

I was on the hunt for something like this too to play emu games. The only thing I could find was the MSI BGP100 which doesn't appear to exist any longer, nor would it work all that well (IMO) with the SGT since it was designed for phones back in the day.

Ive got the msi bgp100 and have the app of the market and donated for full version and it works perfectly with snesoid, nesoid, psxdroid and genoid.
They are hard to find nowadays though lol.
Sent from my GT-P1000 using XDA App

Hey
you could try the WII controller I had it work but now I use the Zeemote I find that more easy to use but the WII controllers well work.
Ciao
Gigino

gigino said:
Hey
you could try the WII controller I had it work but now I use the Zeemote I find that more easy to use but the WII controllers well work.
Ciao
Gigino
Click to expand...
Click to collapse
Wuh wuh what? When did the wiimotes all of the sudden started working! I'm gonna have to charge one up and find this out for myself.
What app did you install to get your wiimote working?
Sent from my GT-P1000 using XDA App

get the wiimote and the classic controller for wiimote to play like a bluetooth gamepad, also can be used to have two player one with the wiimote and the other one with the classic controller, both working

ellokomen said:
get the wiimote and the classic controller for wiimote to play like a bluetooth gamepad, also can be used to have two player one with the wiimote and the other one with the classic controller, both working
Click to expand...
Click to collapse
Which app did you install from the market if any to setup and pair the wiimote? I installed wiimotecontroller from the market but when i use the init function it never finds my wiimote. I also tried to pair it with using wireless settings and it finds my wiimote but always asks for a pass or pin? Just in case you were wondering, my bluetooth setting was on.
Sent from my GT-P1000 using XDA App

Lucky_Charms said:
Which app did you install from the market if any to setup and pair the wiimote? I installed wiimotecontroller from the market but when i use the init function it never finds my wiimote. I also tried to pair it with using wireless settings and it finds my wiimote but always asks for a pass or pin? Just in case you were wondering, my bluetooth setting was on.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Last I heard Wiimote does not work with the SGT on any firmware. Bluetooth issues.
Still waiting on a fix. Someone plz prove me wrong
-Tmo Tab

synplex said:
Last I heard Wiimote does not work with the SGT on any firmware. Bluetooth issues.
Still waiting on a fix. Someone plz prove me wrong
-Tmo Tab
Click to expand...
Click to collapse
I have both wiimoteController and other one that is excellent and more easy to use than wiimoteController that is called RWiimote (was removed from the market don't know why)
I will test it and come back to post result and if successful I will post the .apk

ellokomen said:
I have both wiimoteController and other one that is excellent and more easy to use than wiimoteController that is called RWiimote (was removed from the market don't know why)
I will test it and come back to post result and if successful I will post the .apk
Click to expand...
Click to collapse
Awesome. Looking forward to getting this to work for my emulators.
Edit: Found Rwiimote on the market and tried it out. Doesnt work for me. Tells me my device is not supported when i try to pair the controller.
Sent from my GT-P1000 using XDA App

As with the SGS the Wii remote does not work with the SGT with the original firmware. You can get the Wii Remote working on the SGS with Cyanogen CFW.
Is there a firmware build etc that would support the wiimote?

Is it just that Cyanogen has added a bluetooth profile that the SGS/T devices don't have? Do you know what that would be? It might be something as simple as modifying the bluez config files on the device. If I get a chance I'll mess with it tonight.

agentdr8 said:
Is it just that Cyanogen has added a bluetooth profile that the SGS/T devices don't have? Do you know what that would be? It might be something as simple as modifying the bluez config files on the device. If I get a chance I'll mess with it tonight.
Click to expand...
Click to collapse
Tell us what you find! would be appriciated

I have thought of the next best thing: http://www.dealextreme.com/details.dx/sku.45604
Im thinking of ordering one of those and customizing it to only contain the buttons that are needed for gaming. Since the TAB does have bluetooth profiles for BT-keyboards and mice. (My DiNovo mini works perfectly, but its a little bit too expensive to rip to atoms)

sts_fin said:
I have thought of the next best thing: http://www.dealextreme.com/details.dx/sku.45604
Im thinking of ordering one of those and customizing it to only contain the buttons that are needed for gaming. Since the TAB does have bluetooth profiles for BT-keyboards and mice. (My DiNovo mini works perfectly, but its a little bit too expensive to rip to atoms)
Click to expand...
Click to collapse
That's actually not a bad idea. I'm almost tempted now.....

agentdr8 said:
Is it just that Cyanogen has added a bluetooth profile that the SGS/T devices don't have? Do you know what that would be? It might be something as simple as modifying the bluez config files on the device. If I get a chance I'll mess with it tonight.
Click to expand...
Click to collapse
Did you test this?

Couldn't wrestle the wiimotes away from the kids, but I'll post up when I do have the opportunity.

agentdr8 said:
Couldn't wrestle the wiimotes away from the kids, but I'll post up when I do have the opportunity.
Click to expand...
Click to collapse
I got a wiimote today, tellme what to do. And I will test it.

I'm not sure that this issue is due to anything more then the Tab being hard coded to require a PIN and not being able to skip it...
When I try using WiiController (demo) it stops trying to search immediately, and I don't have Root so the RWiimote fails as well
when I go into Bluetooth settings and search I can see the wii-mote, I can connect to it however it is prompting me for a PIN which the Wii-mote doesn't support. There is no way around this pin code request so my connection fails everytime
If the Bluetooth software is designed to not allow connections without a PIN then I don't see how it can work with any software unless its designed to bypass the PIN requirement?
or I may just be missing something

Sorry to bring this one back to life again, but did anyone get the a wiimote working with the tab successfully?
I'm having the same problem Dredly, it just asks for the pin and you can't continue.

[Q] USB OTG Xbox wired controller support.

Has anybody managed to get there xbox controller to run on there One yet? I tried my wired controller with the OTG cable and had no luck. Worked fine on my One X. Cant remember if i installed something else to get it to work.

jcb1985 said:
Has anybody managed to get there xbox controller to run on there One yet? I tried my wired controller with the OTG cable and had no luck. Worked fine on my One X. Cant remember if i installed something else to get it to work.
Click to expand...
Click to collapse
No, i've tried both the xbox controller and the ps3 and none work, both with six axis app or usb bt center. I'm afraid it looks like everyone will have to wait until a custom kernel comes out that supports it.
This is an age old sense thing which has been happening since the days of the Hero, trust me i remember.
A vanilla rom and or a kernel that supports it. I think with sense it's only happened a few times where someone has been able to get it to work. I think on the Desire HD, but i might be wrong about that.
It's a real shame as it's one of the features that i was looking forward to, MHL out whilst playing tekken 3

[Q] ROM with /dev/uinput support for N900A AT&T Note 3

I'm looking for a Note 3 ROM that has /dev/uinput support so I can run apps like USB/BT Joystick Center. I want to be able to use my Xbox One Controller to play games and fly drones and use the Xbox controller instead of the touch screen. There seems to be issues with stock Samsung kernals.
- Samsung: "Can't access dev/uinput". This is a known Samsung KNOX Kernal issue. You have to use a custom rom with clean kernal. Or try this fix: hxxp://forum.xda-developers.com/showpost.php?p=53343683&postcount=105
I've done the troubleshooting suggested in the LINK, now I'm on Option 3: Find a rom with a different kernal.
hxxps://groups.google.com/forum/#!topic/pokes-android-apps/sME_vV9pPcE
Samsung has done something that has broken the /dev/uinput that is expected with other android manufacturer builds. I've tried AllianceROM, etc but since they are built off of the stock Note 3 firmware, they would have to fix this issue specifically like other roms have done in order to make this work. According to the above group post, non-at&t roms like 'Clean Rom' & FlexCat work, but unfortunately they do not have N900A revisions =/
Does anyone know of a ROM that does at least have a good possibility of working? I don't mind flashing a few, I just dont' want to blindly flash everything =/ Any help would be much appreciated.

If it helps I can use a ps4 controller no problem and a 360 controller as well. Have you tried pairing it like a normal Bluetooth device?

majortaylor said:
If it helps I can use a ps4 controller no problem and a 360 controller as well. Have you tried pairing it like a normal Bluetooth device?
Click to expand...
Click to collapse
No. I wanted to stick with the Xbox One controller because I have those on hand so it wouldn't be an extra expense. Did the 360 controller connection need to be wired, or does it work wirelessly with no extra hardware?

PaulzePirate said:
No. I wanted to stick with the Xbox One controller because I have those on hand so it wouldn't be an extra expense. Did the 360 controller connection need to be wired, or does it work wirelessly with no extra hardware?
Click to expand...
Click to collapse
360 was wired but ps4 was over Bluetooth.

So I'm guessing there isn't a solution other than changing my controller?

[Q] Moto G 2nd Gen. (2014, Dual SIM) PS3 controller doesn't work with USB OTG

I'm having a strange problem. I recently bought an USB OTG cable to use my PS3 controller on my Moto G.
The phone is rooted, but the stock 5.0.2 ROM (22.26.1.titan_retde.redeall.en.DE retde) hasn't been altered otherwise.
So, when I plug in the PS3 controller via the USB OTG cable, the controller immediately starts charging (slow blink of all 4 leds), but I can't do anything else. I though Android was supposed to support the PS3 controller out of the box?
I tested the cable, it works fine. I connected my Kingston 16GB flash drive, it was automatically mounted and I could access it with Root Explorer.
I also tried the PS3 controller and cable with my Samsung Galaxy S4 (stock android 4.4.2, unrooted) - the controller works perfectly. A Logitech RumblePad 2 which I had lying around also works like a charm on the S4, but doesn't do anything on the Moto G.
So the problem has to be either the Moto G itself or (probably) Android Lollipop.
Did anybody else have a similar problem? Can anybody help me?
P.S.: I don't want to use the PS3 controller over BT, reason for that see here: http://forum.xda-developers.com/android/help/bluetooth-vs-wifi-t3046293

drunken_m said:
I'm having a strange problem. I recently bought an USB OTG cable to use my PS3 controller on my Moto G.
The phone is rooted, but the stock 5.0.2 ROM (22.26.1.titan_retde.redeall.en.DE retde) hasn't been altered otherwise.
So, when I plug in the PS3 controller via the USB OTG cable, the controller immediately starts charging (slow blink of all 4 leds), but I can't do anything else. I though Android was supposed to support the PS3 controller out of the box?
I tested the cable, it works fine. I connected my Kingston 16GB flash drive, it was automatically mounted and I could access it with Root Explorer.
I also tried the PS3 controller and cable with my Samsung Galaxy S4 (stock android 4.4.2, unrooted) - the controller works perfectly. A Logitech RumblePad 2 which I had lying around also works like a charm on the S4, but doesn't do anything on the Moto G.
So the problem has to be either the Moto G itself or (probably) Android Lollipop.
Did anybody else have a similar problem? Can anybody help me?
P.S.: I don't want to use the PS3 controller over BT, reason for that see here: http://forum.xda-developers.com/android/help/bluetooth-vs-wifi-t3046293
Click to expand...
Click to collapse
I have the same problem you have buddy, except in my case it's a generic gamepad but the problem is the same: missing drivers, you could compile the driver easily but there seems to be a problem with lollipop kernel sources (in kitkat it worked fine). Anyways when the problem is solved i will compile the drivers, check out this thread btw, we are trying to solve this problem http://forum.xda-developers.com/moto-g-2014/help/gamepad-joystick-otg-support-t2995943

germanargentina said:
I have the same problem you have buddy, except in my case it's a generic gamepad but the problem is the same: missing drivers, you could compile the driver easily but there seems to be a problem with lollipop kernel sources (in kitkat it worked fine). Anyways when the problem is solved i will compile the drivers, check out this thread btw, we are trying to solve this problem http://forum.xda-developers.com/moto-g-2014/help/gamepad-joystick-otg-support-t2995943
Click to expand...
Click to collapse
Thank! After I posted this thread I found the one you linked, and already have it in my bookmarks. I hope somebody will find a solutions.
Unfortunately I'm bad at coding, so I can't really contribute. I'm just baffled, that Android gets "worse" with every new version (at least in my eyes). Why did they break something which was working perfectly before?

drunken_m said:
Thank! After I posted this thread I found the one you linked, and already have it in my bookmarks. I hope somebody will find a solutions.
Unfortunately I'm bad at coding, so I can't really contribute. I'm just baffled, that Android gets "worse" with every new version (at least in my eyes). Why did they break something which was working perfectly before?
Click to expand...
Click to collapse
It's not exactly like that, in fact motorola has never enabled those drivers on kitkat nor on lollipop. What i did was to compile those drivers and they worked (on kitkat) but now when i try to do the same it doesn't work on lollipop, my guess is that there's something wrong with lollipop kernel sources

Oh, I didn't know that. I thought this was something Android-related (like it is so basic, all Androids should have it), not something that each manufacturer has to integrate himself.