Does the wiimote work with the EVO 3d stock rom(rooted or not rooted)?
Does the PS3 remote work?
Please, I don't can about the first Evo so if you own one good for you. It is a different phone. I just need a simple proven answer. It has been months since it was brought up and the phone has had updates since then.
Also, if it does work, what apps are you using to run it?
No, it doesn't work.
Via My HTC Evo 3D On The Now Network From Sprint.
It will work if you're running cyanogen or miui the aosp based roms. It has to do with the Bluetooth stack that's used in sense.
Sent from my PG86100 using xda premium
Gotta be on an aosp ROM. They work for me on cm7.
Whooo! (Cole Voice...)
THANKS
It was a pain trying to find that answer. Maybe it will work with the next update...
or I will try it once CM7.1 fixes all the bugs. And hopefully others who are wondering will see this answer and know once and for all.
"This new update means Android tablets will also be able to act as a USB hub and you'll be to hook up devices such as mice and keyboards and game controllers to tablets and smartphones."
http://www.techradar.com/news/mobil...m-sandwich-everything-you-need-to-know-954464
Not sure how trustworthy this is, but it sounds good...
Just wanted to update anyone who read this post!!!
It appears someone has figured it out. Here is a link to a youtube video of the guy who made the app wiimotecontroller.
http://www.youtube.com/watch?v=OS4h1Z2nKHw
Here is something else I found. Not sure what to make of it or what this app does. There is an app called "Bluez IME". It is specifically for a few HTC and Samsung phones with stock rom. I don't think it works on the 3d but I will keep you posted if it does. You can connect multiple controllers and some wiimotes(I guess they made diffent ones).
Anyone no more about the Bluez app?
***Just tested it, it doesn't work. It finds the wiimote but it won't connect. Sucks!!!*** For what its worth it might work with other controllers.
Related
Hey guys,
I've spent a lot of time here on XDA and around the internet and I can't seem to find an answer to my problem. I've been looking for a week or so, on and off.
I really would like to use my Vibrant for some mobile gaming, including some of the emulators that are available on the Market. What I would like to do is use the Wiimote Controller application alongside the emulators, because I never feel very comfortable using a touch-screen game pad.
The trouble is that for some reason, Samsungs Galaxy S line of phones will not sync up with the Wii Remote via Bluetooth. Most if not all HTC devices have been able to sync up, so I know the Wii Remote is capable of it. I spoke to the developer of the application and he said that for some reason the SGS line of devices just won't do it. He suggested a while back that flashing a stock-Android ROM should solve that problem.
My question, then, would be is there a Vanilla ROM based on 2.2 or do you guys know of a ROM that will accomplish what I'm going for? Right now I am using Frankin-TWIZ by Eugene and I love the ROM but the Wii Remote problem is still there.
So, I appreciate any advice and suggestions that you guys can offer and I do apologize if a similar thread has been started elsewhere, I really couldn't find anything.
Thanks so much,
Nate
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
T313C0mun1s7 said:
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
Click to expand...
Click to collapse
So, I'm assuming there is no way for a Samsung Galaxy S device to use an older implementation of Bluetooth?
Thank you for your help, I really do appreciate it, this has been bugging me for a while haha
You should be able to gleam more information from this thread:
http://forum.xda-developers.com/showthread.php?t=746489
I am not saying that it is not possible, just that the ROM is not the issue, but rather the Bluetooth implementation is. It almost feels as if Samsung did this intentionality.
As far as I am aware all the ROMs here are based off either Samsung source or Samsung leaks. A TRULY vanilla ROM to get the original Bluetooth implementation would mean building it from Google source, which would be sans drivers and you would need to make everything work with your hardware by building your own drivers. I don't think you are going to find this just yet.
You could try CM 6.1, but it is not stable or final yet on the vibrant and I don't really know if it fixes the Bluetooth issue.
Everything works great with my MotoROKR S305 Stereo Bluetooth Headset, and that is all I really care about.
T313C0mun1s7 said:
Vanilla 2.2 will not help you here. The problem is in the Samsung implementation of Bluetooth. Bluetooth v3.0 + HS is on the virge of existence, but is not yet a fully ratified standard. Samsung used this fact to be able to release a device they call Bluetooth 3.0, but since there is no standard yet they can do whatever they want with. Apparently what they wanted was to not support Bluetooth game controllers.
Click to expand...
Click to collapse
T313C0mun1s7 said:
You should be able to gleam more information from this thread:
http://forum.xda-developers.com/showthread.php?t=746489
I am not saying that it is not possible, just that the ROM is not the issue, but rather the Bluetooth implementation is. It almost feels as if Samsung did this intentionality.
As far as I am aware all the ROMs here are based off either Samsung source or Samsung leaks. A TRULY vanilla ROM to get the original Bluetooth implementation would mean building it from Google source, which would be sans drivers and you would need to make everything work with your hardware by building your own drivers. I don't think you are going to find this just yet.
You could try CM 6.1, but it is not stable or final yet on the vibrant and I don't really know if it fixes the Bluetooth issue.
Everything works great with my MotoROKR S305 Stereo Bluetooth Headset, and that is all I really care about.
Click to expand...
Click to collapse
I'll take a look at that thread, and I just wanted to say that I really appreciate you taking the time to help me out here.
If there's anything I can do for you to return the favor, please don't hesitate to ask. Thanks again
It sounds like the bluetooth stack on most Vibrant ROMs including stock will not work with apps like WiimoteController. The only one that I've seen that is advertised to do so is Cyanogen's. Does anyone know of any other ROMs that use the older, or UK Bluetooth stack that will allow this app to function? I'm currently using Nero3 and wouldn't give it up for anything.... accept maybe the ability to play River City Ransom with a physical controller.
willmatic said:
It sounds like the bluetooth stack on most Vibrant ROMs including stock will not work with apps like WiimoteController. The only one that I've seen that is advertised to do so is Cyanogen's. Does anyone know of any other ROMs that use the older, or UK Bluetooth stack that will allow this app to function? I'm currently using Nero3 and wouldn't give it up for anything.... accept maybe the ability to play River City Ransom with a physical controller.
Click to expand...
Click to collapse
No one is gonna answer this yet because the scene is too wild with gingerbread and all being out from the nexus s, The problem is that the nexus s uses bluetooth 2.1 hardware, so we wont be seeing anybody adding another one to it like cyanogen has. I waited patiently for the last 5-6 months and nothing has changed. and nothing will unless other manufacturers start using the same stack, or some developer re-writes ours, we will see.
I bought a small bluetooth keyboard specifically for use with my ThunderBolt. Using CyanogenMod 7, it will work fine. However, if I use any rom that is based on sense, the bluetooth keyboard will not sync correctly. I've read that sense uses an outdated version of the bluetooth stack. Is there any way to get the bluetooth stack that CyanogenMod uses and put it into a sense based rom?
This is something people have been after for a long time my friend. Complain to htc
On a side note, this really should have been posted in Q&A, or better yet googled.
Edit: just realized I did not technically answer you. If out is possible, no one has done out on any sense rom that I'm aware.
My bad about posting in the wrong place. I have googled it and found nothing that solved the problem. Since there are a lot of smart people here, I thought I would ask it here.
Sent from my ThunderBolt running INJ3CT3DTH3ORY V6.01
What was the solution?
The title says it all...
I am currently typing this on a bluetooth keyboard. I am running an AOSP based rom now and loving it. Link is in my signature if anyone wants to check it out.
Sent from my ThunderBolt using XDA Premium App
I havent tried it yet, but using my old blackberry keyboard via bluetooth would be kind of cool if I could get it to interface.
i had this: http://www.geeks.com/details.asp?invtid=PA-BK03-PB&cat=KYB
it worked on my old Incredible 2 and my gf's iphone.
keyword being 'had'... it started having issues connecting. would have to try 2 - 3 times occassionally before it connected. rather then exchange i just got a refund.
voxigenboy said:
i had this: http://www.geeks.com/details.asp?invtid=PA-BK03-PB&cat=KYB
it worked on my old Incredible 2 and my gf's iphone.
keyword being 'had'... it started having issues connecting. would have to try 2 - 3 times occassionally before it connected. rather then exchange i just got a refund.
Click to expand...
Click to collapse
I have one just like that somewhere. I need to find it and give it a try.
Sent from my ThunderBolt using XDA Premium App
I just downloaded n64oid and I have a PS3 controller that I was hoping to pair via bluetooth to play. Im not sure how to do this, though. Does it require root? I've looked and I can't seem to find any answers for the flyer. Any help is appreciated.
Also, is this possible with a wiimote as well?
If the flyer is anything like other HTC devices, the sixaxis will not work because HTC uses strange bluetooth kernals on their builds. You can try the https://market.android.com/details?...patibilitychecker&feature=more_from_developer once you have root to check if it will work.
Changing to a different ROM based on Cyanogen would fix the issue, but I don't know if it's build available for the flyer and you'd probably lose some features like the stylus.
So far Sense 3.0 will not allow connectivity. It's deep within and I hope someone can figure it out.
Sent from my HTC Flyer P510e using xda premium
So after many people telling me that the only way to accomplish what I want is to root...I did. For the first time ever, in over 5 years of Android ownership. So will itemize the issues at at hand and ask relevant questions and state what I have done within each one. But first, you should know I rooted using this method http://forum.xda-developers.com/showthread.php?t=2026938 and I have SuperSU version 1.25, and still running stock ROM and I am S-On.
Issue 1: Wifi tether.
I have downloaded Wifi Tether version 3.2 Beta 2 and I got it to work. The issue is, is there a better performing app or a way to get this one to perform faster? I get about 2mbps on speedtest.net on my phone while the tethered devices get 0.72mbps..I want to get the same on both. Anybody know how?
Issue 2: LTE connectivity.
Many know the LTE connectivity on LTE Evo sucks the big one. So now that I am rooted, what can I do to improve it? Specific ROM? Specific App? custom radio drivers?
Issue 3: Bluetooth
Within my 3 questions here, I am obviously also asking for ROM recommendations, but I have heard certain ROMs break bluetooth and I wanna avoid that at all costs. But the real issue is not the latter. My concern is AVRCP bluetooth profile. I need it to be version 1.3 or higher in order for my phone to send track/album art info to my car's Display Audio/Navigation screen. This is something I have been trying to figure out for years, I posted many threads on this here http://forum.xda-developers.com/showthread.php?t=1728786 and here http://forum.xda-developers.com/showthread.php?t=1702047 and also here http://forum.xda-developers.com/showthread.php?t=1553950
The difference is that back then, I was not willing to root, but now, I'm already rooted.
So shoot me some solutions, and forever change my life! O well respected community of android tinkerers!
Now for issue 3 (bluetooth), if you guys know a way to get this issue http://forum.xda-developers.com/showthread.php?t=1702047 to work, that would also help me. Here is the OP post quoted
darkleafar said:
So I just recently upgraded from an Evo 3D to the Evo 4g LTE, and the phone is gorgeous and all, but I've lost a major feature and it is scaring the hell out of me, I hope you guys can help:
Intro to my problem:
I have a 2012 Prius V, which has built in Bluetooth and an USB port. My Evo 3D lacked the right level of bluetooth AVRCP profile needed in order to display track names, artwork, etc, on my Prius Nav screen through bluetooth. So to work around that, I would plug in my Evo 3D into the Prius's USB port, then I would select "Disk drive/USB mass storage mode" on the phone and voila! My car saw all my music, complete with track names, album artwork, etc.
My main problem:
All of my music is in my 16GB MicroSD card, so I figured just putting it into my new LTE Evo would suffice...but it didnt. When I plug in my LTE Evo, the "Disk drive/USB mass storage mode" NO LONGER triggers my car detecting it. I noticed a new option, called "Media Sync." Selecting that WILL trigger my car dectecting the phone storage, but it ONLY detects the BUILT IN phone storage, not what's on my MicroSD card.
What's even worse...
Also, if you are wondering, the LTE Evo, despite having Bluetooth 4.0, STILL DOES NOT have the right level of AVRCP needed to display album artwork and track names over bluetooth. I was very, extremely disappointed when I realized this. I ve always been a loyal Anti-Apple/Pro-Windows/pro-Android kinda tech guy, but how come Iphones have been able to do this (track names and album artwork over bluetooth) for several years and this new super phone of ours cannot?
Where I need your help:
How can I make it so that my car can recognize my MicroSD card, not just my phone's storage?
I'm not gonna be forced to stick my music into my phone's built in storage instead of my MicroSD card, am I?
Isnt there any software/firmware or mods/rooting stuff I can do to enable tracknames and album artwork over bluetooth on this phone, since it already has bluetooth 4.0 after all?
Well, thank you very much for your time and I hope y'all have some awesome answers, more than greatly appreciated.
Click to expand...
Click to collapse
1.MeanBean Rom I get awesome tether speeds
2. Known issue there is no fix
3. MeanBean Rom
Sent from my EVO using xda premium
scoot0073 said:
1.MeanBean Rom I get awesome tether speeds
2. Known issue there is no fix
3. MeanBean Rom
Sent from my EVO using xda premium
Click to expand...
Click to collapse
So you know for a fact MeanBean ROM will fix both bluetooth AVRCP profile issue and Wifi tether speeds? Cuz if so, sir, you just made my day!
darkleafar said:
So you know for a fact MeanBean ROM will fix both bluetooth AVRCP profile issue and Wifi tether speeds? Cuz if so, sir, you just made my day!
Click to expand...
Click to collapse
Mean bean fixes only your #1 issue...
1.3 AVCRP Bluetooth profile is not available even on a custom kernel, since meanbean uses stock kernel with elemental X over clock modules, it doesn't have the fix for your issue #3, I've read somewhere else about this feature that even the iphone has but not this phone... Good Luck!
Sent from my EVO using xda app-developers app
jocarog said:
Mean bean fixes only your #1 issue...
1.3 AVCRP Bluetooth profile is not available even on a custom kernel, since meanbean uses stock kernel with elemental X over clock modules, it doesn't have the fix for your issue #3, I've read somewhere else about this feature that even the iphone has but not this phone... Good Luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I was told CyanogenMod fixed this. Any truth to this claims?
Yea I miss read about the Bluetooth part, my bad Homie
Sent from my EVO using xda premium
Im running cyanogen mod but my car stereo doesn't have that profile so I can't test for you, plus I haven't been able to drive in a month after a surgery... I remember somebody asking thicklizard about this feature in his arc reactor thread and also in the meanbean thread... Maybe you can pm a kernel developer and see what's involved into getting this feature to work on our phones...
Sent from my EVO using xda app-developers app
jocarog said:
Im running cyanogen mod but my car stereo doesn't have that profile so I can't test for you, plus I haven't been able to drive in a month after a surgery... I remember somebody asking thicklizard about this feature in his arc reactor thread and also in the meanbean thread... Maybe you can pm a kernel developer and see what's involved into getting this feature to work on our phones...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Dude I just rooted for the first time ever. I could not begin to tell you who develops kernels to save my life. But I would have to be S-Off for a custom kernel, right? Anybody with Cyanogen Mod wants to chime in on whether AVRCP 1.3 or higher is present?
Holy crap! A google search answered my own question, they claim AVRCP 1.3 was working on Cyanogen Mod 10.0 but that it broke on 10.1. Link here https://jira.cyanogenmod.org/browse/CYAN-20
So, can I just flash 10.0 to my phone? what is the difference between 10.0 and 10.1? are they both jellybean builds?
And another thing, the wife was testing the wifi tether on my phone with her I PAD and connection breaks after about 15 minutes. So it looks like it isnt working after all. I just like turns off by itself. Anybody know why this could be?
darkleafar said:
And another thing, the wife was testing the wifi tether on my phone with her I PAD and connection breaks after about 15 minutes. So it looks like it isnt working after all. I just like turns off by itself. Anybody know why this could be?
Click to expand...
Click to collapse
There is a setting that can be turning it off in the app by itself or it could be the jellybean task killer what rom is she using? And yea you can flash cm 10.0, is jellybean 4.1; cm 10.1 is jellybean 4.2... If you are s-on just remember to extract the boot.img and flash it on fastboot with this command: fastboot flash boot boot.img.
Good Luck!
jocarog said:
There is a setting that can be turning it off in the app by itself or it could be the jellybean task killer what rom is she using? And yea you can flash cm 10.0, is jellybean 4.1; cm 10.1 is jellybean 4.2... If you are s-on just remember to extract the boot.img and flash it on fastboot with this command: fastboot flash boot boot.img.
Good Luck!
Click to expand...
Click to collapse
BUt i was just told if I have RUU 3.16 then i have to downgrade to 3.15 because the 3.16 touchscreen drivers are too new and have not been implemented into the kernel in any AOSP ROMs. correct?
darkleafar said:
BUt i was just told if I have RUU 3.16 then i have to downgrade to 3.15 because the 3.16 touchscreen drivers are too new and have not been implemented into the kernel in any AOSP ROMs. correct?
Click to expand...
Click to collapse
Correct, for that you need to be s-off... Backup all of your stuff and head over to the dirty Racun thread or Facepalm...in the original android development section...