Hi!
I am developing an application which connects a Wiimote to a bluetooth enabled android phone/device.
I did this by interfacing with the native bluez bluetooth library directly, rather than via the Android API. The reason for this is that Android API doesn't support HID devices, which a Wiimote is.
A problem now is that on some devices, mostly those sold by HTC, my app simply doesn't work. After calling the hci_get_route(NULL), this function should return an id of the first bluetooth device available (most likely 0), but instead returns ERNODEV (-1) as if no bluetooth device is available.
I suspect it has something to do with our beloved HTC grossly modifying something in the libbluetooth library to make this fail to work.
Has anyone ever done this kind of bluetooth interfacing?
How could I make this work?
Rooting the phone and replacing a library or two would be fine too.
For a list of working and non-working devices, check out the 2nd post of this thread.
HTC support
I just sent a customer service message to HTC about this issue. I hope they can get back to me with a "we'll work on it" message, or something. I really want this on my incredible. I'm new to coding like this, but could you disguise the Wiimote as another kind of device?
Just a response from someone equally interested in a solution. I'm trying to set up a bluetooth keyboard (Freedom Pro) with my gsm Hero running the 1.5 based MCR 3.2. Available drivers (Freedom's own, BlueInput & KeyPro) should work with 1.5, but HTC devices, especially the Hero, seem to be lacking something that is present in most 1.5 builds.
Investigating, I find the same issue of no route to device, because there is no known device. AIUI when bluetooth is turned on hciattach is used to establish a link to the hardware. At that point an hciconfig should list the hci0 device as present but down. However I find this list remains empty at all times.
I found this for keyboards.
Since I can't post the link, it's called "KeyPro for Android"
Google "keypro android" and click the first link.
Maybe that could help. It says it works with any android device above 1.5, however, I did read that some keyboards use a different type of bluetooth profile, SPP rather than HID.
I haven't heard back form HTC yet either.
EDIT: Upon reading your post again, you have tried this. Sorry, my bad.
Thanks for looking though The Freedom Pro is switchable between spp & hid profiles, so I figured I was safe, lol. Not with HTC's butchered 1.5 bt it seems.
Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid
Edit: Double post
tobren said:
Did you ever try to use the most likely id 0 on an HTC device? Even though the call to get the id fails?
Maybe you could use also the Android API to synchronize if a device is present and then use the id that Android API gives you?
Just some thoughts since I would love to see that App running on my Desire with Snesoid
Click to expand...
Click to collapse
Believe it or not, I actually tried this. Unfortunately, the next command (to bind the bluetooth adapter) also fails, and of course every command after that one because the adapter is not bound.
Thanks for the idea anyway.
usb
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth? one advantage of this would be increased battery life and probably better compatibility across models.
i'm sure some people would prefer bluetooth, but i figure i'll always be using it very close to my phone so i can see the screen, so the wired option is actually a bit more attractive (considering battery performance).
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).
rubber soul said:
does the wii remote have usb connectivity? could it be possible to have the communication pass through that connection rather than bluetooth?
[snip]
i know ps3 has usb connectivity as well, you just might need an adapter (mini to micro).
Click to expand...
Click to collapse
I'm pretty sure the first answer is no - our wii is round at a friend's atm. However even if it was yes, you'd need more than an adapter. USB operates with one device as master & the other as slave. To allow you to connect slave devices to your phone it would need to be in host mode. Some mobile phone hardware implementations support this, however I don't know of any mainstream Android kernels which do. Even if you workaround that, you're left with the huge issue that slave devices can assume it's safe to draw power from the USB bus which could do nasty things (tm) to a lower power device like a mobile. This can be worked around via a powered hub, but it all gets very messy.
I looked into this a few months ago, hoping I'd be able to use a usb keyboard with my Hero. I ended up with a BT keyboard instead. Of course that doesn't work either but for completely different reasons, as hinted at by this thread. Hopefully a 2.1 ROM will solve that, but that's the subject of numerous other threads.
Uh, just throwing stuff out, what if you have a pc with two bluetooth adapters, it connects to the wii mote, and then broadcasts that in someway the android api can understand?
Also please actually try working on something with a rooted phone, the HTC EVO 4g is rootable, and I will make man love(no homo) if you get it working.
Either one works lol.
Using a PC as a proxy is kind of useless. If you have a wiimote connected to a PC, you might as well play games on the PC itself (there are nes/snes/sega/etc emulators for PCs too).
At this moment, rooting doesn't help with the problem either.
@1 True
@2 That sucks.
Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.
well if you send the null pairing code to the wiimote from the default bluetooth pairing screen.. it will fail to communicate with the wiimote too
waffles004 said:
Do we think that this will/could be fixed in HTC's Froyo update for 2010 devices? Not looking for definite answers, just a ponderin'.
Click to expand...
Click to collapse
Doesn't it work in stock/vanilla Eclair? I thought the main problem was with Cupcake, though HTC seem to have done weird things to every stock firmware. I read that removing Sense from a 2.1 HTC ROM breaks bluetooth. Go figure. And there was I thinking Sense was a gui enhancement
I contacted HTC about their bluetooth issues and just received this response
My name is Courtney, and I would be glad to assist you today. I understand that you are unhappy with the Bluetooth connectivity on your HTC EVO. HTC is aware of the problems occurring with the EVO and Bluetooth. We are currently investigating this issue and are working on a solution. As soon as we have an update, we will inform our customers. Thank you for contacting HTC America Technical Support. If you need further assistance, please feel free to contact us via email or at 1-866-449-8358. We are open 7 days a week from 6 a.m.-1 a.m. EST. You can also check out our Community and Support pages at htc.com/us and our pages on Facebook and Twitter.
Click to expand...
Click to collapse
I contacted HTC about this issue with my incredible and I basically got the same answer except the guy was more knowledgeable and said that other people were complaining about certain bluetooth issues. I think they know what they did and are waiting to fix it in Froyo to be easy for them. No worries though, should be comin' in a few weeks. I can't freakin' wait. I have soooooooooo much Pokemon and Mario to play.
does anyone know if this works on samsung galaxy s, i dont have my phone yet to test, but as soon as it arrives (sometime next week) i will test this.
All I can say is that my wii controller is working really well on cyanogen on my evolution now!
So my YoCam camera arrived, and excited to receive my new kickstarter toy, I tried to connect it to my phone following the basic instructions.
Phone sees and connects to the device via wireless, but the app refuses to connect. However using other android phones will allow me to connect to the camera, using exactly the same process., so it does not appear at least at a basic level, an android or an app issue.
Just wondering if anyone has any suggestions, or can suggest some troubleshooting tools so i can get a better view of what is going on.
Thanks
Hi, Not that this helps: I have exactly the same but on a Samsung Note 3 running cyanogenmod 6.0.1. When connecting to my Samsung tab S2 with standard Android no problem.
Are you running a alternative rom on your phone or standard?
Edit: see also Faq at getyocam.com
Hello there.
I'm having an issue with my Nokia 6 TA-1039 where I can connect pretty much anything through OTG with an adaptor EXCEPT for my Dualshock 4.
I've been looking for information for the past 2 days, testing different cables and testing different devices, but only the DS4 is causing me trouble. It connects and charges, the light in the back turns on, but beyond that, it does nothing. Pressing the buttons does nothing, emulators don't recognize them, hell, even my Razer Panthera works.
Has anyone had this problem before and found a way to solve it? Is it some firmware compatibility issue or I'm just having super bad luck with my cables?
Thanks beforehand~
Hello everyone. I tried to pair my dualshock 4 via bluetooth to my s10+ and i had no luck making it work. Then i tried with cabel and it worked but there is a mapping issue. Pressing O is recognized as X. X as Square and square as L1. Does antone have an idea how to fix it without root?
Need root to change key bindings. You can change the buttons within some apps, but many still won't work well.
Thank you Ace. Do you think this is a problem from googles end given the fact they just included the files with pie. Or it might be a wrong implementation from samsung? I dont have another pie device to test. If its samsung i can try reporting the bug and hopefully have it fixed with future updates
peshetoman said:
Thank you Ace. Do you think this is a problem from googles end given the fact they just included the files with pie. Or it might be a wrong implementation from samsung? I dont have another pie device to test. If its samsung i can try reporting the bug and hopefully have it fixed with future updates
Click to expand...
Click to collapse
There are two PS4 controllers. V1 and V2. The former relies on x input, whereas Android seems to side with d input (XB1 controller) like Windows.
With the controller and OS supporting different APIs natively, key presses aren't interpreted well on every phone. Some devices have everything assigned correctly, but the S10 isn't one of em. I'm not sure Samsung is concerned with compatibility. Ofc feel free to submit feedback or email them.
For what it's worth, this is the only Pie phone I've had luck with. Neither my Pro 3 nor z2F acknowledge the DS4 over OTG. Haven't tried it on my Note yet.
Thank you very much. I hope they do, as i got dex station as well with the hope of playing some games on the screen(rayman!) ))