yashsingh1/xdaforums huggingface dataset:
[Android General] sir_earl:
I believe this is left over fluff from the AOSP bluetooth stack. In many cases the property is left blank and a default address is used instead. The error doesn't imply the app won't work though, as a similar error occurs on the SGS2. In your case, you probably also get the output 'Can't set line discpline', which is the real show stopper.

I would be interested in seeing what happens if you run the following command, then try the app again (don't reboot in between):

su

setprop ro.bt.bdaddr_path /sys/module/board_spade/parameters/bdaddress
[Android General] Elloco305:
Nothing changes same output before and after command
[Android General] scukoemo:
It seems like the property's value doesn't change, even with superuser rights. So, no change in output.
[Android General] Brandotgreat:
Has there been any exploration into assigning the controller through the use of just the device and say a usb host cable? so that the controller could be assigned a mac through the android device. It seems like a kind of run around at first (connect controller with usb to be able to play through bluetooth) but there have been occasions where I may only have access to my xoom or evo but want to switch the controller to pair with the other device. or pair a friend's controller if he forgot to before he left a computer.
[Android General] sir_earl:
Doh - Yes, it's a read only property (hence the 'ro.' bit). You could edit the file '/system/build.prop' and update the value there, then reboot the phone. Just be careful (and back up the file).
[Android General] sir_earl:
There is actually an app in the market to do that (I think it actually costs more than my app though!). I believe it will only work on Android 3.0 devices (tablets). It is on my list to add this functionality, but in the meantime, I guess you could grab that app.
[Android General] bronevaya:
I have this exact same problem. same controller, works on pc perfectly using motionjoy, but wont connect to my HD2 running CM7. Would LOVE to get it working
[Android General] abo_mara7:
No plan to support LG Optimus 3D?
[Android General] sir_earl:
I don't have time to work on it at the moment - perhaps once CyanogenMod becomes available on this device I can take a look at how they are initialising bluetooth and port the changes over.
[Android General] akaruna:
well i just got to say it works flawlessly with my stock or cm7 droid x... the only thong ibcant figure out is how to get it to work with gameboy. works perfect for nes/snes/atari/ps1/genesis. thx OP u f'n rock!!!

Sent from my DROIDX using the XDA mobile application powered by Tapatalk
[Android General] virusx_43:
I can confirm it works with humble 4.5, once 5.0 is out I'll post a reply.
[Android General] rllr:
not 100% sucess! sixaxis controller

Don't know if anyone can help.....

Just bought sixaxis controller app, i can use PS3 control to play emuloter at my samsung galaxy tab(7"). I used my friend controller, it's work!

However, I use mine, it can't work! I sure the procedure of connection should be right since i can make a connect with other PS3 controller.

I used Sixaxis Compatibility Checker for checking it showed it should work, but the 4 lights of control is still blinking, can't connect. Only different is my control is not SONY original.

My question is, is this app only for SONY original controller??
[Android General] Elloco305:
Sadly yes, many have established this pages back.
[Android General] locibin:
I have the same problem. sixaxis app runs successfully but I can't connect with a brandnew original sony PS3 controller. (with SGS2, KF3, 2.3.3, rooted)

when I run the sixaxis app, I'm able to connect with a wiimote controller with NES emu. Without sixaxis it doesn't work. So it looks like my PS3 controller is not working. Maybe sixaxis app has problems with brandnew PS3 controller? or my controller is fake, although it should be an original.

(I changed the bluetooth adress succesfully on the PS3 controller with sixaxis pair tool)
[Android General] KurdX:
sir_earl:

I can understand that you have a lot of phones to support atm but just want to let you know that apart from many phones the Optimus 3D has HDMI out which would make it a great phone to support and also making your app bigger on the market.

I will test your compatibility checker app every changes made and give you the result you need to make it work.

Btw, you mentioned that a cyanogenmod release would work?

I tried the SelfKang2 release for Optimus 3D and the Compatibility Checker works great, giving a bluetooth address.

You can download it here:

http://cyanogenmod.googlecode.com/files/update-cm-7.1.0-SelfKANG2-Optimus3D-signed.zip

Problem though is Cyanogenmods lack of HDMI out support for the O3D atm.

The kernel:

https://github.com/CyanogenMod/lge-kernel-cosmo

Which files do you need to take a look at?

As someone mentioned, the phones does reboot after attempt 2 on stock rom.
[Android General] sir_earl:
Can you send me all the init.*.rc files in the root directory (from the cyanogenmod kang). I'll check it out.
[Android General] KurdX:
Thanks for looking into it.

http://www.megaupload.com/?d=RX3C6HEF

I included all the 6 .rc files from the root just in case.
[Android General] sir_earl:
It seems to be using a different method to initialise bluetooth that I haven't seen before.

Try copying the file /system/bin/uim-sysfs from the cyanogenmod build into your stock rom, chmod 744 it, then try to run it - what output does it produce? If it says that it cannot insert a module, see if you can locate that module in the cyanogenmod build and copy it across also. Good luck!
[Android General] KurdX:
Didn't work. Like before the output looks like:

attempting connection type 1..
driver starting..
error: failed to configure bluetooth
deleting device pipe
attempting connection type 2
driver starting..
error: failed to configure bluetooth
deleting device pipe
attempting to close server..
disconnected

And then the phone reboots.

I tested a old version you posted here on the forum with a different result.

http://xdaforums.com/showthread.php?p=18169962#post18169962

The apk for that result is the one above my post.

I'm ready to copy whole files from the selfkang to the stock version.

The selfkang is 2.3.4 and my stock is 2.3.5 so the files shouldn't be that different.

Do you have any idea which files that are involved with the bluetooth driver or just the bluetooth files?
[Android General] sir_earl:
Sorry - I should have been more clear. Once you've copied the file /system/bin/uim-sysfs and run chmod 744 on it, I'm interested in the output when you try to run the uim-sysfs executable from the command line. This won't fix the app, but it will help me to understand how bluetooth works with your device.
[Android General] sir_earl:
Any testers with an Android 3.1+ device willing to test a version of the app with built in pairing, please take the following steps:

1. Download and install the attached apk.

2. Using the Sixaxis Pair Tool, change the master address of your controller to something random.

3. Run the apk on your device and connect the controller to the device with a usb cable, then tap 'Pair controller'.

4. Report the output, and then verify whether the master address was correctly changed to match your device by using the Sixaxis Pair Tool on your PC again.

5. Also try pressing the 'Pair Controller' button without the controller attached and report the output.

This code is completely untested, so I'm not confident it will work! If it fails, could you also attach your logcat output. This feature will only work with android devices running 3.1 or newer.

Thanks!
[Android General] KurdX:
I must be lost here.

I copied the file, ran chmod 744 on it but i can't execute the file since it's not executable. What command do you want me to use to run uim-sysfs? And should i run it through adb or a terminal app?

Tried running it as a script but nothing happened if not a output file is created somewhere.
[Android General] sir_earl:
The steps should be roughly like so:

adb remount

adb push uim-sysfs /system/bin/uim-sysfs

adb shell

su

chmod 744 /system/bin/uim-sysfs

/system/bin/uim-sysfs

What output is produced at the end?
[Android General] Riebart:
I tested this on a rooted (but otherwise unmodified) Samsung Galaxy S II LTE and received the following output:

Attempting connection type 1...
Driver Starting...
Error: Failed to configure bluetooth
Deleting device pipe
Attempting connection type 2...
Driver Starting...
Done setting line discipline
Error: Failed to configure bluetooth
Deleting device pipe
Attempting to close server...
Disconnected

As far as I know, the master MAC was changed successfully on the controller, and the controller is an official Sony one.

This project is close to my heart, so if you have any suggestions or things you want to test on this phone (since it uses a different collection of hardware than most other of the S II series phones), mine is available.

Mike
[Android General] KurdX:
I tried that before but since I didn't get a result, I thought I did something wrong.

C:\adb>adb shell
$ su
su
# chmod 744 /system/bin/uim-sysfs
chmod 744 /system/bin/uim-sysfs
# /system/bin/uim-sysfs
/system/bin/uim-sysfs
#

No result.
[Android General] ZhuraYuk:
sir_earl any news on aftermarket controllers support? Also it's interesting to know why they do not work, because with PS3 they work like originals.
[Android General] rllr:
Only support originals controller????

Hi there,

Just raised the question before, is this apps ONLY support SONY original controller? I tried other OEM sixaxis controller which's worked on PS3 but this apps! and there are also passed by "sixaxis compatibility checker" but "sixaxis controller"

However, I saw other fourm they can used other brand controller and work, any step or setting I missed?
[Android General] sir_earl:
There seem to be quite a few different after market controllers around, so it's difficult to say conclusively that none of them will work. But generally, yes, it seems that most or all of these controllers will not work with the app (or rather, the bluetooth stack / firmware in our phones).

I haven't given up all hope (still have a couple of things to try), but I have put it down the priority list until I get a couple of the other planned features out the door.

Can you point me to any of the posts you found about people using after market controllers successfully?
[Android General] ozkaya:
Are there any plans for supporting HTC devices? I have an EVO 3D and am more than ready to help with all tests :)
[Android General] Jax184:
I've been eagerly awaiting the day when this would run on my Samsung Sidekick 4G. So when I tried the new version of the compatibility checker and was told my phone was now supported, I was ecstatic. I purchased the full version from the store, paired my real PS3 controller, and spent the evening playing emulated games with only minor problems.

Then I went to try it again today. What had gone so smoothly the night before was now being a problem. It took several tries of starting, stopping, closing the app, then trying again before I got it to work correctly. Once it did pair it worked great again. Any thoughts?

This is usually the spot where it stopped:
[Android General] Jax184:
And here it is on the 5th try, when it finally worked. Notice that it doesn't say "Error, failed to configure bluetooth"
[Android General] sir_earl:
Hmmm - I wonder whether it's timing out before the chip has initialised. Can you roughly time how long it sits idle between the second 'Driver started...' and the 'Error: Failed to configure bluetooth', or is it almost instantaneous?
[Android General] Jax184:
There's a 6 second delay before it errors out. And when it gets to the last line in the first screenshot it'll sit there until I press stop.
[Android General] sir_earl:
Can you try replacing the .hcd file in /system/etc/firmware/ with the file in the attached archive and then run the latest compatibility checker from the market. You might want to back up your old .hcd file before removing it!
[Android General] sir_earl:
Try this version of the compatibility checker and see if it helps. It waits twice as long before timing out.
[Android General] ozkaya:
I replaced the file with the one you posted and installed checker from the market. it gives an error. (screenshot included)
[Android General] Jax184:
I installed it and fired it up. The first try started correctly, though it's got the additional error of "Can't open HIDP control socket" now. The second time however it got stuck even sooner. This time before it even got to "Attempting connection type 1" it said "Cannot overwrite file brcm_patchram_plus" and caused the phone to stop responding.

I rebooted the phone and tried again, with precisely the same behavior. First try worked, second went very wrong.
[Android General] sir_earl:
Sorry - I had some test code in there that your phone obviously doesn't like!

Try this one.
[Android General] Jax184:
It seems to be starting better than before. BTW, the checker pops up the IMPORTANT dialog box every time I rotate my phone. Kinda annoying.
[Android General] sir_earl:
Does 'working better than before' mean 'works every time' or 'works more of the time'? If the latter, how much more of the time?

The rotation issue is annoying, I agree. People don't usually use the compatibility app long enough to notice!...
[Android General] Jax184:
It has worked every time I tried it. If you can update the main app with the timeout change, I'll let you know how it holds up over the coming days of use.
[Android General] lambstone:
I think I bought an aftermarket phoney "Sony" dualshock 3 controller. It looks like original sony controller and even comes in sony packaging, however I am unable to connect it to both my galaxy tab (running miui) or galaxy s 2 (running stock). However, using the same controller I am able to connect it to my PC using motioninjoy. Any ideas why this happens?
[Android General] sir_earl:
Still investigating, but seems the firmware or bluetooth stack are somehow incompatible with the one used in Android devices.
[Android General] sir_earl:
Is the output from the debug version of the compatibility checker app you tried before the same or different to the first screenshot you provided?
[Android General] lambstone:
Would the stuff from motioninjoy be of any use?
[Android General] onthebridge:
Do you know if this is going to be any different in Ice Cream Sandwich?
[Android General] ozkaya:
it is totally same. any more advice? I was also wondering if it is possible to inject a kernel module to open up L2CAP sockets or would it be very device dependent?
[Android General] DannyBiker:
This might sound silly but:

Can we test the compatibility without a PS3 controller ?

I want to buy a sixaxis to play on my Tab 10.1v (and HD2 why not) but want to be sure it'll work first...

Does the compatibility app need the controller to determine compatibility ?
[Android General] DesignDecay:
Hi I had this problem also, the patched version seems to work will this be implemented into the actual app?
[Android General] ozkaya:
You don't need the controller as long as you will buy a genuine one. Checker app is good enough to find if your phone has necessary bluetooth stack.
[Android General] sir_earl:
Probably not, though you reminded me that I've been meaning to contact them to see if they have come across such a problem or can provide any tips. I'll let you know what their response is.
[Android General] sir_earl:
Excellent. What phone are you using? Yes - I'll be releasing an update within the next week or so.
[Android General] sir_earl:
It's hard to say, but it will most likely depend whether a newer version of bluez is being used (I haven't checked this yes).
[Android General] DesignDecay:
Samsung Galaxy SII T989, do you have a beta version of the software that I can test for you?
[Android General] sir_earl:
I'll be releasing a new version in a week or so, as I'm in the middle of adding a major new feature to the main app. ;)
[Android General] presslab:
I did not have hciconfig, so I copied it over. Here are the results:

/ $ su
/ # echo 1 > /sys/class/rfkill/rfkill0/state
/ # start hciattach
/ # hciconfig -a hci0 up
/ # hciconfig -a hci0 pscan
/ # hciconfig
hci0: Type: UART
BD Address: F4:6D:04:4C:90:E7 ACL MTU: 1021:6 SCO MTU: 64:
UP RUNNING PSCAN
RX bytes:366 acl:0 sco:0 events:11 errors:0
TX bytes:50 acl:0 sco:0 commands:11 errors:0

/ #
[Android General] sir_earl:
@Witalka 15 - Just to double check, when you run SixaxisPairTool and plug the controller in to the USB port, does the text change from 'Searching...' to the address you typed in previously?

@presslab - That looks promising. With that file in place, try running the compatibility tester again and see if it gets any further. You may need to reboot the phone so bluetooth is turned off before running the app though.
[Android General] presslab:
Yes, it works now! So now I tried to pair on the PC. When I run the software it says "<snip> libusb0.dll is missing from your computer." I see "HID-compliant game device" in device manager with the same VID & PID as the ps3.inf driver. I guess the driver is not installing correctly. I try to manually select the ps3.inf file, but it says "The folder you specified doesn't contain a compatible software driver <snip>".

I am using amd64 Windows 7. It looks like there is a libusb driver for that, but perhaps the INF file is not correct?
[Android General] sir_earl:
With the controller plugged in to the PC, try uninstalling the 'HID-compliant game device' via device manager, then re-installing the SixaxisPairTool and seeing if that makes any difference.
[Android General] Witalka 15:
Yes it change to my address from phone , after typing the address and plug out than plug in.. I see the same address but only with small Letters..
[Android General] sir_earl:
Can I get you to run the same commands I posted earlier and let me know the output.
[Android General] GazaIan:
That's not how it works... It has to do with how the kernel does Bluetooth. AOSP ROMs and the Nexus One / S should always work with things like this. If, for some reason, if you flash a Sense kernel on an AOSP ROM, it wouldn't work, you'd get the same results as you would on Sense ROM. a failure in Bluetooth. Sense ROMs them selves wouldn't work. HTC Desire HD and HTC Inspire 4G users that dual boot between a Sense and AOSP ROM won't work, since both ROMs are powered but the Sense kernel.
[Android General] Witalka 15:
Yes no problem.. But you need to wait... Im at work... ;-)

edit:

Okay.. i have put the hciconfig in my xbin folder and making it executable with 'chmod 744 /system/xbin/hciconfig' ..

than .. (i hope thats right)

$ export PATH=/data/local/bin:$PATH
$su
# chmod 744 /system/xbin/hciconfig
# echo 1 > /sys/class/rfkill/rfkill0/state
# start hciattach
# hciconfig -a hci0 up
hciCan't init device hci0: Connection timed out (110)
#

edit2:

after uninstall the Six ... Tool (+ driver) .. and reinstall they find my controller no more.. -.- ..

but in the device manager they show me thats all is installed .. strange
[Android General] presslab:
Yes, that worked. I can now see in the debug window on the Compatability Checker the button up/down presses, so it looks like it is all working.

Can't wait to get the full version and try it out with N64oid!

My tablet has USB ports, is it possible to do the pairing right from the Android tablet?
[Android General] sir_earl:
@presslab - Good to know. Expect a full release in the market within the next couple of weeks, depending on how feedback goes. I will put automatic USB pairing on tablets on my 'To do' list, but it may be difficult without actually owning one.

@Witalka 15 - Can you try rebooting your phone, turning off bluetooth (if not already), then enter the following in a terminal and let me know the output:

echo 1 > /sys/class/rfkill/rfkill0/state

start hciattach

hciconfig

There seems to be a problem with the drivers only installing to the usb port that the controller was originally plugged in to. Can you try plugging the controller into the original port, otherwise re-installing SixaxisPairTool with the controller plugged in. I will take a look at this tonight.
[Android General] flex59:
got it , working with a rooted Nexus s now for some games to play???

if anything else needs testing please pass it across and i will try it out for you
[Android General] mcimo88:
I will be trying this out. I'd be glad to pay for this app once it is out. If this works you will be the hero of android gaming.
[Android General] flex59:
what do i need to/ need to do to make it control my snesroid games?? i'm so excited. mario kart without covering half the screen with my thumbs
[Android General] sir_earl:
@flex59 - Can you confirm it's working on your Nexus s. i.e. Do you get the debug key presses show up once you connect the controller?

In a week or so I will be releasing the app on the market that will actually allow you to select the controller as an input method. This will allow emulators and other games to use the controller. Until then, check back here for updates!
[Android General] flex59:
yup working fine put my about phone stats up also
[Android General] flex59:
did that work???? https://lh3.googleusercontent.com/-...AAAAAAIA/4Gmqb-RT8us/s512/CAP201107290331.png

this should be a screen shot
[Android General] sir_earl:
Anyone able to try it with their rooted stock rom? I'm fairly confident that CM7 will work across all / most devices.
[Android General] Witalka 15:
After fresh Reboot and Bluetooth off.. This comes after typing the commands..

$ su
# echo 1 > sys/class/rfkill/rfkill0/state
# start hciattach
# hciconfig hci0: Type: UART BD Address: 00:00:00:00:00:00
ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0

#

Yesterday i tryed all my usb ports.. I cant find the controller more.. And the original port few times..
[Android General] sir_earl:
@Witalka 15 - That looks right, so now can you try the following again (also after reboot with bluetooth off, to be certain):

su

echo 1 > sys/class/rfkill/rfkill0/state

start hciattach

hciconfig -a hci0 up

hciconfig -a hci0 pscan

Now wait 10 seconds for bluetooth to come up and then type:

hciconfig

Also, if you haven't tried the compatibility checker since a fresh reboot, could be worth trying that again.
[Android General] Witalka 15:
Okay after fresh Reboot..

$su
# echo 1 > /sys/class/rfkill/rfkill0/state
# start hciattach
# hciconfig -a hci0 up hciconfigCan't init device hci0: Connection timed out (110)
# hciconfig -a hci0 pscan Can't set scan mode on hci0: Network is down (100)
# hciconfig hci0: Type: UART BD Address: 00:00:00:00:00:00
ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:4 acl:0 sco:0 commands:1 errors:0

#

And after fresh Reboot i tryed few times compatiblity checker.. They start the server. But dont connect
[Android General] sir_earl:
Try grabbing the build from this link:

http://xdaforums.com/showthread.php?p=17470062

Be sure to do a nandroid backup before trying any of this!

Have a look in /system/etc/firmware. First try replacing the .hcd file on your phone with the one in the zip. If that still doesn't work, you could start replacing the firmware files (fw_bcm4329.bin, etc). You could also try extracting the kernel driver modules from boot.img (look for the bcm4329 module) and using insmod to load them (or flash them through CWM if you know how). I have no idea whether the kernel modules will be compatible with the stock kernel... For info on extracting the boot.img, check this link - http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Feel free to ask for assistance if you get stuck!
[Android General] GazaIan:
Does my computer need to be Bluetooth enabled for this to work? I'd search if the search didn't keep telling me to try again later.
[Android General] lambstone:
No it doesn't. The instructions are quite clear on the sixaxis controller site. Plug in the controller via usb to pair.

Sent from a Galaxy S 2 Far Away
[Android General] Autocrossn:
I would like to test ive got a htc evo 4g and a sixaxis controller.