Related
Hey all,
I have been using my Eris with a bluetooth Stereo for a quite a while, but when I rooted the phone over to a 2.1 ROM it started using Simple Secure Pairing (SSP) when authenticating the bluetooth headphones. My car stereo doesn't support this (its brand new too...).
So, the question is has anyone ever looked into disabling SSP and forcing it to use the old static key method of pairing in 2.1?
I am not adverse to diving in and doing the dev work, I just wanted to make sure someone hasn't already done it. If I do need to dive in does anyone know if its possible to disable it via a config file, or will I need to backport the bluez stack?
Thanks for all the great work,
traetox
I too am having this issue. Worked fine in 1.5 but ever since root it will play audio through pioneer head unit but phone won't connect. I will patiently await a fix.
-------------------------------------
Sent via the XDA Tapatalk App
Oh, so that's what's up.
I'm having a similar problem with my Jabra Cruiser bluetooth speakerphone/FM transmitter. What mine does, though, is it will connect and I can use it to listen to music and do the normal speakerphone functions like it normally would, but none of the media buttons will work anymore. It's not a huge inconvenience, since I mount my phone in the car anyway (long commute). It's only a problem if I need to have Google Navigation in the foreground but still want to change songs.
Patiently waiting. You devs are awesome, if you don't get enough sycophantic slobbering already.
ok, so I did some digging on mine and it turns out that I can pair with a simple bluetooth headset via the '0000' key. But the phone attempts to go through the full key negotiation to connect the "bluetooth headphones." So i can get audio via the headset negotiated connection, but it sounds awful without full AD2P.
I am getting a ROM kitchen setup and will try and map the 1.5 bluez stack onto the 2.1 source and see where that gets me.
Thanks for the input.
Thanks for working on this! I've tried to incorporate some of the Bluetooth files as well as the WLAN.ko from other roms into my Rom but have been unsuccesful. I am running damage control 2.08 that I ported. I was originally unable to get WiFi or Bluetooth to work until I copied the WLAN.ko from the oc patch now both work minus the phone. Don't know if this helps but figured i let you know. If you have those files from a 1.5 Rom I will try them in my port and let you know what the results are.
-------------------------------------
Sent via the XDA Tapatalk App
bt issues as well any fix
I have posted several times on this can not get an answer Have the same issues anyone with experience know what I can do?
Here is my situation I have driod eris ee2.1 on verizon before root I could auto connect bt to my pioneer avic d3 with phone audio only I had to manually connect media audio every time but I got used to it but since root I now can connect to media audio only and when I try to connect phone audio it dissconnects in less than a minute I am at a loss as to what to do thought maybe someone has experienced this and figured it out Thanks in advance.
suppliesidejesus said:
Oh, so that's what's up.
I'm having a similar problem with my Jabra Cruiser bluetooth speakerphone/FM transmitter. What mine does, though, is it will connect and I can use it to listen to music and do the normal speakerphone functions like it normally would, but none of the media buttons will work anymore.
Click to expand...
Click to collapse
I have a Jabra Crusier, and I'm having an issue with a lot of ROMs where I can not connect to it and stream music over bluetooth. I have found that Aloysius v6 Maps rom by Spencer Moore works well with the bluetooth thing. You may have to connect and disconnect a few times here and there to get it to connect, but it's been the best ROM for it. I used V11 Maps and it worked for a little while, but stopped connecting properly just recently.
There are a few known bugs with v6, but I'm fiddling with V11 to try and get the bluetooth to stay perm. Once I get it, I'll let Spencer Moore know and get him any new updates I come across.
Just an update. I am able to pair and connect to phone using white widow Rom.
-------------------------------------
Sent via the XDA Tapatalk App
I downloaded the Wii controller app on the market, but it gives me the message. Error! your device does't support bluetooth!
has anybody else got the wii mote to connect to there device for gaming.
i got an ass of emulators, roms, and isos so i need a decent input method
From what I understand, the bluetooth stack in samsung's version of Android isn't properly implemented or is missing features of version 2.2 etc. In effect, keyboards,mice, bluetooth controllers wont work until an updated bt stack is hacked into the roms. More than likely will be implemented in CM6 methinks. Cant wait!
Thanks for the explanation. 2.2 on galaxy s is gonna be very nice.
Sent from my SGH-T959 using XDA App
the problem is most likely that the program is designed for bluetooth 2.1 and we have bluetooth 3.0 so there is a compatability issue there. when they update the program to the newest bluetooth version, it should work again
Good to know. I sure hope that is the only issue plaguing the software. Not really wanting to deal with old bt stack ala HTC with Sense.
Any update, I'm using darky 10.2 but still doesn't seem to work (the app seems to stop when it detects the phone type, rather than any specific error)
Read the previous posts, it doesn't work on Samsung roms, aosp (cyanogen) roms do support it though.
I wish it worked too...
What about ICS?
Sent from my Vibrant
Update: I am now going to be updating this thread with Roms that work with the WiiMoteController app and other HID support. If you have any extra info, please either post or PM me.
It seems that these are mostly roms built from the ground up, ones with 99% of the samsung crap removed. Here's to hoping for a nice BT stack!
Rom Compatibility List
---------------------
[ROM] Vanilla FroYo AOSP v0.8.1P -Works with WiiMote IME
[ROM][ALPHA] MIUI V3 -Works with WiiMote IME
-----------------
Original Post:
I was wondering with EB01, whether HID input was supported. I really want to use a bluetooth controller with my phone
Anyone know of a way to get it working?
I noticed that I was able to connect to other phones using bluetooth after EB01, maybe it'll work with a controller too.
no, HID doesn't work yet. Regular android doesn't support it, but CM6 and CM7 do, so once kaos gets his builds working with bluetooth, we'll finally have or HID support.
wrong forum btw
my droid x would pair with a wii remote stock
I had a thought, the Galaxy Tab has Bluetooth HID support on it. Can that be ported to our Fascinate?
Bump for great justice, anyone with a clue feel like looking into this?
There's not much to do beside wait for punkkaos unless you want to help him port CM7. I've been wanting this too, so maybe if I ever get some time I might play around with the cyanogenmod source. But I have no experience writing operating systems so don't expect anything from me.
I have successfully paired and used my wiimote with my fascinate on jt's aosp using the WiiMoteController app in the market eventhough the post says bluetooth is borked. So idk what's up with that.
Sent from my SCH-I500 using XDA App
paired but does it connect?
I've paired my BT HID keyboard with most ROMS I've tried, but i have never connected, and never been able to use it yet. Punk Kaos is the only one i know who is working on a solution.
I will have to try pairing my wii remote than, I'll let you know results.
Update : Didn't work on JT's Superclean EB01.
I have a Wiimote working on jamezelle's MIUI, so I guess that means it works.
-Sent from the future using my time machine
Oh nice! I didn't realize wiimote works on AOSP but I guess the main thing that's broken for that is bluetooth headsets? Now I need to find my bluetooth keyboard and maybe get another wiimote just for gaming. Kind of glad the bluetooth game gripper flopped, I can just get another wiimote although the PS3 controller would imo be better for emulators.
I didn't think of that, I'm going to look for an app for it
times_infinity said:
I have successfully paired and used my wiimote with my fascinate on jt's aosp using the WiiMoteController app in the market eventhough the post says bluetooth is borked. So idk what's up with that.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
For me it won't even turn on bluetooth on vanilla aosp 0.8.1. Did you just enable it in settings?
@newtype: superclean is not an aosp rom so it still has Samsung's bluetooth stack, meaning it won't work.
i have the apple wireless keyboard working on jamzelle's MIUI v4 rom!
is there a way.. and if so can somebody work on this, i used an app before on my tablet called blueputdroid that worked as a bluetooth remote for the playstation3, but when i try to use it now it gives me an error that the bluetooth stack (im stock rom) is unsupported and suggests using cyanogenmod (nothing against that, but i would prefer to stay on the stock rom right now as i enjoy it.)
so hopefully someone can work on, or port a bluetooth stack to work with this rom if its possible?
friendly bump
I would start with an email to the dev of the app. The SGS II is an incredibly popular phone. See if they can make the app compatible, instead of trying to replace core system files to be compatible with an app.
Sent from my SGS II
I had a couple of questions about using Spirit FM Radio app on CM 7.2. And I would like to know in detail about it.
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
CM9 hasn't got a radio am I right? (Btw I'm new to the forum I couldn't find a topic to write this I'm sorry
What phone are you using?
When Bluetooth is enabled FM is enabled too because they locate at the same chip. It's the easiest way to enable FM and so is CM radio doing. Spirit FM (and stock LG) does it little bit harder by only enabling FM thus saving some starting time and battery (battery part is not a 100% fact though, only my own speculation).
You can remove CM radio, it is not needed.
Recommended method by author in Spirit is CyanogenMod. I don't know exactly what are the differences between different methods but stick with CyanogenMod.
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
4silvertooth said:
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
moby_test said:
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
Click to expand...
Click to collapse
How did u finally come to that conclusion that it does use Bluetooth? And if it does... Does that mean that there is no big difference in the way Spirit, Cyanogen mod and LG FM radio app works?
I have my own thread for questions, 1st link in my sig: http://forum.xda-developers.com/showthread.php?p=13379669
And I respond to emails and PMs, but sometimes respond on my thread for all to benefit. Or just let me know a thread's been opened...
See below for answers:
sweettaniyaa said:
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
Click to expand...
Click to collapse
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
OK for SGA?
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
donzzy said:
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
Click to expand...
Click to collapse
Off-topic, and you should ask on my thread anyway, or check post 2 of my thread. Please don't respond here.
Canned response now:
The Simpsons taught me that among Hemingway's words of wisdom was:
“The shortest answer is doing the thing.”
IE, why don't you just try it ? It's free and only takes a minute or two I think.
There's even an intro that can be read and will give some useful information on configuration.
Then if you have trouble, you can come back, report it, and hope for an answer.
mikereidis said:
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
Click to expand...
Click to collapse
Thank you for clearing it to me. But I don't know... something weird happened to me. I was using Spirit FM radio app whole day yesterday but the Blue-tooth icon never showed up. But today when tried the app again It has been showing the Blue-tooth icon. I don't get it. What changed? I tried re-booting and everything. Still the same.