Is there any rom other than the CM7 alpha that'll fix bluetooth so that I can get my LG thrill to pair with sixaxis and / or wiimote?
thay is a good question
Doubtful... all these roms are based off stock firmware... and no stock roms support it.
Sent from my LG Thrill 4G...
Actually Im wondering the same thing. I have an iControlPad that wont play nice because HID isnt implemented in stock rom?!?
Plays nice with my iPhone and considering 3D converter now works very nicely with N64oid and FPse, then my dual analog stick iCP would make gaming on the Opti3D even sweeter!
iconttolpad should work fine with blues EMI app.
Pete
Sent from my LG-P920 using XDA App
I have tried iCP with Bluez IME app.... (in SPP and HID)
iCP will pair but not connect and once paired will always spit out a UUID error
The UUID error is usually related to the rom not supporting HID/keyboard functions?...
Others have the same problem - the LG Opti 3D/Thrill have stuff missing from their bluetooth modules... A custom rom will probably fix it.... Cyangenmod maybe?...
It did for HTC phones.....
Is the 3D convertor out in the recent firmware update?
Sent from my R800i using XDA App
yep...
3d converter works on n64oid.... Mario64 in 3D!
update 10j....
You should order a Phone Joy. They're backed up on pre-orders but they said they'll be getting a big shipment early next month.
I went to phonejoy.net and it looks like it still talks via bluezime?... if so the Opti3D will always get UUID errors due to poor bluetooth stack.... and please correct me if im wrong but froyo cant use the mini usb for a controller either?..
The O3D has issues with Bluez Ime? If so, then they say to create a new issue on their site if you want a device to be supported.
EDIT:
Apparently someone already made a thread about hte UUID issue.
http://forum.xda-developers.com/showthread.php?t=1239221
http://forum.xda-developers.com/showpost.php?p=17012717&postcount=10
Killer Bee said:
The O3D has issues with Bluez Ime? If so, then they say to create a new issue on their site if you want a device to be supported.
EDIT:
Apparently someone already made a thread about hte UUID issue.
Click to expand...
Click to collapse
I started that case,
I only have the bgp100 gamepad and wiimote to test
If you can please help with whatever you can. Maybe follow some of the steps listed and provide some feedback.
The more people trouble shooting this the faster we can play some games with our bt controllers.
Maybe the Zeemote can be used for a some hints since it seems to work as shown in the one post.
Just to let you all know, I plan on adding support in the Sixaxis controller app for this phone and many others within the next couple of weeks. Root access will still be required though.
sir_earl said:
Just to let you all know, I plan on adding support in the Sixaxis controller app for this phone and many others within the next couple of weeks. Root access will still be required though.
Click to expand...
Click to collapse
Fantastic, I wish you the success.
sir_earl said:
Just to let you all know, I plan on adding support in the Sixaxis controller app for this phone and many others within the next couple of weeks. Root access will still be required though.
Click to expand...
Click to collapse
I would love to see that and pay.
I will be next in line..... happy to pay if I can play games with b/tooth controller. (preferably iControlPad but I'll take sixaxis....) Its a shame the bluetooth stack is so screwy..... I love everything else about the O3D...
There are some blacklist in /etc/bluetooth/blacklist.conf in the P990 :
// Do NOT change this file format without updating the parsing logic in
// BluetoothService.java
// This file contains information to prevent auto pairing with Bluetooth devices.
// Blacklisting by vendor prefix address:
// The following companies are included in the list below:
// ALPS (lexus), Murata (Prius 2007, Nokia 616), TEMIC SDS (Porsche, Audi),
// Parrot, Zhongshan General K-mate Electronics, Great Well
// Electronics, Flaircomm Electronics, Jatty Electronics, Delphi,
// Clarion, Novero, Denso (Lexus, Toyota), Johnson Controls (Acura),
// Continental Automotive, Harman/Becker, Panasonic/Kyushu Ten,
// BMW (Motorola PCS), Visteon
AddressBlacklist=00:02:C7,00:16:FE,00:19:C1,00:1B:FB,00:1E:3D,00:21:4F,00:23:06,00:24:33,00:A0:79,00:0E:6D,00:13:E0,00:21:E8,00:60:57,00:0E:9F,00:12:1C,00:18:91,00:18:96,00:13:04,00:16:FD,00:22:A0,00:0B:4C,00:60:6F,00:23:3D,00:C0:59,00:0A:30,00:1E:AE,00:1C7,00:80:F0,00:12:8A,00:09:93
// Blacklisting by Exact Name:
ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3
// Blacklisting by Partial Name (if name starts with)
PartialNameBlacklist=BMW,Audi
// Blacklisting by addition of the address during usage
Click to expand...
Click to collapse
Hope can help you.
Hey Guys... now after the GB-Update is out are there some News about using the Sixaxis app???... I tried it with the Thiaz rom 2.1. But the Phone Reboot... *cry*..
I can confirm that GB stock cannot talk to Bluetooth controllers properly. O3D still refuses to connect to iControlpad, sixaxis and bgp. Hid profiles stil not properly integrated into the Bluetooth stack.
Only almost cyanogenmod works - I believe that the standard Bluetooth stack is integrated in framework - yet another LG fail - hardware is capable and software is still lacking.
I would use cyanogenmod but without 3d it just isn't the same phone. Anyone know how to dual-boot on an O3D?
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.
This thread should be used to provide feedback and troubleshooting for the Sixaxis Controller and Compatibility Checker apps.
If you have a device that you would like to see supported, and you're happy to step few a bit of debugging to help me determine the issue then please let me know, and preferably provide a screenshot of any error messages.
I'm doing my best to add support for new devices (especially HTC and Samsung), but it seems that it might not always be possible to add compatibility. In this case, the only option for running the app on said device is with an AOSP based rom such as CyanogenMod.
Also, throughout the thread I will occasionally be posting beta versions of the app that include new experimental features. I would be most appreciative of any feedback from those willing to test these new features.
For those looking for help with touch profiles, mythek88 has put together a master list here with a growing list of games. Hopefully at some stage I will add the ability to share profiles directly through the app.
Regards,
Earl
Both Nexus phones. I'd volunteer for testing, but I don't own a sixaxis.
Out of curiosity, why does this need root access whereas Wii doesn't? Is there a difference between the way the controllers pair or something?
Sent from my Nexus S 4G using XDA App
Out of curiosity, why does this need root access whereas Wii doesn't? Is there a difference between the way the controllers pair or something?
Click to expand...
Click to collapse
Yes unfortunately, although the Sixaxis basically communicates via the HID protocol, there are a couple of minor differences that would require a kernel patch to make the controller start talking over HID. The only solution I have found for this so far is to bypass HID and communicate directly over L2CAP (both of which require root access).
I'd love to volunteer for testing! I have access to several androids and 8 dualshock and sixaxis controllers
If you wish to test on an Galaxy S II then I am available to help out if required. I too have both DualShock and SixAxis controllers.
I can join to you guys too! I have Desire HD with sense or without it and dualshock3/sixaxis controller.
I have three phones that I'm willing to beta test.
I have dualshock 3 controllers.
LG Optimus S
HTC Hero (rooted w/o Sense)
HTC Evo 3D (soon to be rooted)
I definitely think you should release a free version that lets people test basic compatibility. 15 minute return window doesn't seem like enough to test an app like this.
Very excited to see this app!
Ok, what I'll do initially is release a standalone compatibility test app on here in the next couple of days that basically allows me to get some initial feedback and if required have anyone who is willing with an incompatible phone to run a few tests that might enable me to get them working.
Again, this application will only work on rooted devices, sorry!
Stay tuned.
I'd suggest you to put an free version for like 2 weeks for the time its a beta stage then when everything is finalised make it 1$ which i think is reasonably fair ! And i own an sony ericsson xperia x10 it has to work ! Since sony > sony ericsson is the same company i think ? Lol
Sent from my X10i using XDA Premium App
shahkam said:
i own an sony ericsson xperia x10 it has to work ! Since sony > sony ericsson is the same company i think ? Lol
Click to expand...
Click to collapse
I don't think that's how this sort of thing works.
Sent from my Nexus S 4G using XDA App
do want so much
G2x I'm in
Sent from my LG-P999 using XDA App
Here is the (very basic) windows utility I created today for pairing the controllers to a specific MAC address. Once installed, you should be able to plug a controller in to your PC via Mini-USB and the 'Current Master' should change from 'Searching...' to the last MAC address the controller was paired with (probably your PS3). You can then change the master by entering a new MAC address in the format of xx:xx:xx:xx:xx:xx. This address will ultimately be the bluetooth address of the phone you wish to use the controller with. The Android app will give you the correct address when run on your phone.
Make sense?
If anyone wants to try it out and let me know if it works on your PC's, that would be lovely. Just enter any old MAC address 00:00:00:00:00:00 will do.
Linux users (and apple mac?) should be able to use the utility called 'sixpair' that is floating around the net.
Just an update that I'm hoping to get a bit of feedback on...
This app allows you to test whether your device will be compatible with the app. Once I have enough feedback about which devices / OS versions it will run on (and potentially improve compatibility with some assistance from testers on the forum), then I will make a release on the market that enables IME.
If you would like to help out, you will need to download the attached apk, as well as the SixaxisPairTool in my previous post. You will then need to extract and install the apk on your phone using adb or something like 'app installer' from the market. Run the app and follow the instructions (you will need to use SixaxisPairTool to pair the controller with the phone (using the bluetooth address displayed at the bottom of the app after tapping 'start').
Please could anyone who tries the app report back here any devices and OS's they have tried, and the success they have. Feel free to ask for help if anything is unclear.
Cheers,
Earl
I ran Sixaxis Compatability Checker on my Asus Transformer running Prime 1.6 (Android 3.1). When I clicked "Start" the program said "Connection Initiated..." and then "Connection Failed." At this point I have not paired my controller because the Checker program does not give me the MAC address. When I click "Stop" my Transformer locks up and nothing works, and while I can turn it off with the power button it does not turn back on until I hard reset it.
oKay i run the Server on Android.. they show me the MAC.. ..
i type the mac address in the Windows App .. the show me the same address in the Server and Controller .. but if i press start at the controller hey only blinking.. -.-
Connection Initiated...
Connection Established..
Samsung Galaxy S Miui Galnet v6
@presslab - Can you try running the command 'hciconfig' on the phone in a terminal emulator as root user and tell me the result.
@Witalka 15 - When you paired the controller using 'SixaxisPairTool', did the 'Current Master' show the same address as the one you typed in after clicking 'Update', or was it still showing 'Searching...'?
I have a Droid X running Liberty Gingerbread ROM 0.9. First off I'd just like to say that I constantly have problems with it, including with Bluetooth, so this may not apply to all Droid X users, but I do receive the "Connection Failed" message, and was just wondering what I can do about it since I've been dying to use my Dualshock with my phone for the longest time. Thanks
Anyone getting a 'Connection Failed' message can help me out by trying the following commands in a terminal window and reporting the results:
su
echo 1 > /sys/class/rfkill/rfkill0/state
start hciattach
hciconfig -a hci0 up
hciconfig -a hci0 pscan
hciconfig
If you get a 'not found' error when calling hciconfig, you could try copying the executable (from say here) to your /system/xbin folder and making it executable with 'chmod 744 /system/xbin/hciconfig'. Then try running the above commands again.
sir_earl said:
@presslab - Can you try running the command 'hciconfig' on the phone in a terminal emulator as root user and tell me the result.
@Witalka 15 - When you paired the controller using 'SixaxisPairTool', did the 'Current Master' show the same address as the one you typed in after clicking 'Update', or was it still showing 'Searching...'?
Click to expand...
Click to collapse
Yes i see the same address... In sixaxispairtool and the server..
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.
Has anyone tried a HID keyboard? i have read in many places that Android phones support only SPP. But someone told that it was only till Froyo. I dunno whether HID is hardware specific feature or just a part of the driver. If its just the driver, then gb and ics should have it.
Also theres this app to make bluetooth keyboards work https://play.google.com/store/apps/details?id=net.mybesttools.btkbservice
quote from description:
Android has support for HID devices but is not able to connect bluetooth keyboard devices correctly (yet).
This service automates the connection to your keyboard.
Click to expand...
Click to collapse
I'll be without a laptop for almost 10 months (until affordable win 8 touchscreen laptops are released here). So, i need to do some serious typing, like long emails, chat and blogging (and posting on XDA) from my phone. Swype is the best virtual keyboard for me, but that is nothing compared to a physical one. On Omegle, the other person will disconnect even before u have finished typing "hi".
If our phone can support HID keyboards, can u suggest me one?
O1 supports HID bought a external from Walmart works BT says HID device connected worth the buy.
Sent from my LG-P500 using xda app-developers app
Which os are u using? And did it connect straightaway or u had to install some app?
The user ukdutypaid request me and
LNEt - I don't found the profile yet
Robbie P
qazzi76
sergiocabraljr
With some words:
So can anybody tell me either a) why is BT HID so 'rubbish' on Android, ie why is it so rare that anybody seems to have got it to work e.g "Look. It's a massive problem, nobody really knows how to do it. Count yourself lucky that you've got found a GB build where it does work at all. Put the problem down and walk away"; or b) what a solution might be?
I've tried rooting round in builds, until I'm blue in the face but unless the *.so file either has a BT and or an HID in the file name, then I'm in the dark.
qazzi76 ; GregórioAxiaMagno and sergiocabraljr have found various solutions for GB builds I think and I know Samsung seems to have solved the problem. (I've seen videos of the Galaxy Nexus and it worked with no problems on an SII a friend of mine has).
Could it simply be a case of isolating and extracting the magic HID file and putting it into any/all custom roms, or it's a case (for some just to make it harder reason) that the BT files have to be recompiled for each and every build; as GregórioAxiaMagno has kindly pointed out with some of his work.
The holy grail I suppose is a set of files that can be uploaded to any build by apt, that resolve the lack of BT keyboard with every/any build.
Click to expand...
Click to collapse
:good:
The point here is, as always I say, the bluetooth stack on Android is a issue like call recording. And with this cenario, I think we can join people to help on this thread to post information about mods, replacements, hacking, apps and more. Until we find the optimal solution for the largest number of phones what we can. :fingers-crossed:
All is valid: kernels, modules, CWM, apps, tips, :angel: pray... any way of help.
I will ask for you people to post solutions here, and along of the time I will quote it in the second post of this thread.
Also, I want discuss with you about an optimal solution.
So keep this thread clean and focused only about bluetooth.
No, I and nobody thinks what the bluetooth is the world conquest, I want only use the totally potential of this "old" tecnology.
I know we have other tecnologies like OTG, but this thread must be only about how to deal with bluetooth in our daily use and experiences.
Lets start! :highfive: I have your help?
Please, press thanks instead to manifest your support with posts.
Current solutions
[app][beta][2.1+] myblucon v1.0 & mybluime v1.0 - bluetooth kit to hid devices
so you buy a bluetooth mouse but your ginger won't connect it?
Or you have an bluetooth keyboard and can't write at your ice cream?
Solution for:
* ST15a/i - GB/ICS
* Others
Click to expand...
Click to collapse
Bluetooth Keyboard problem resolved
Infamous "paired but not connected."
Solution for:
* Galaxy Note GT-N7000
Click to expand...
Click to collapse
[APP]Bluetooth Keyboard Easy Connect
A service which connects your bluetooth keyboard device.
Android 2.3 has support for HID devices but is not able to connect bluetooth keyboard devices correctly (yet).
This service automates the connection to your keyboard.
Solution for:
* Many Androids
Click to expand...
Click to collapse
Solving Bluetooth connecting problems
My Desire's bluetooth allways worked like a charme untill rooting REDUX 1,2
Connecting to any previously known device, or any new once for that matter, did not work.
Some grey hairs, upgrading to Redux 2.0 and many tries later I concluded some data must be corrupted somewhere.
Deleting the content, not the files, just the content of the following files did the trick, much to my relief.
Solution for:
* HTC - Redux
Click to expand...
Click to collapse
HID Bluetooth Device FIX for 2.3.5 and 2.3.6!!
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
Solution for:
* Many Androids
Click to expand...
Click to collapse
resv 2
:good::good::good:
Congratz... keep going
Looking here:
/data/misc/bluetoothd/<A BLUETOOTH ADDRES>
I was thinking one of this files have a value to set for make an device manually connectable. Like disabling/enabling auto connect. So the market apps to HID devies will work better.
What do you think?
I was messing into the system and looking at this path
system\etc\bluetooth
Inside, we can found some confs, so I was editing and guessing about input.conf.
So I made some mods and I will test today, but if anyone know something more about or want to test, please a hand will be cool xP.
Regards.
EDIT: yeah nothing changes... haha