I managed to start bluetooth on nookie froyo, BT scan is working well(on command line), sometimes it shows devices in the android gui.
The steps : ( use at your own risk and only for comfirmed devs)
Add bluetooth capabilities (HCILL) in kernel
Toggle the WL12XX_RFKILL flag on in evt1a defconfig.
Take the bluetooth firmware (bts file) from gforge.ti ( wl1271 firmware) for froyo pandroid and put it into /system/lib/firmware, alias /lib/firmware to /system/lib/firmware (useful for command line).
boot the kernel
and then
echo 0 >/sys/class/rfkill/rfkill0/state
echo 1 >/sys/class/rfkill/rfkill0/state
hciattach -s 115200/dev/ttyS1 texas
hcitool scan must show you your BT devices (if discoverable)
Stability is not yet here, Maybe some problems with UART high speed handling ?
This is very positive, it seems that the wl1271 chip is well connected to omap3621...
• Note II (Nov 2012)
• S3 (Nov 2012)
• T-Mobile Vibrant (Jul 2010)
• Odin/Mini Kies are your Friends
• THRIVE (Aug 2011)
• T-mobile G1 (OCT 2008)
• Use current Ubuntu on i7 960 & Win7 in VM for Odin
If I have helped you in any way, please click "Thanks" button bottom right
Forgive my ignorance on the subject but what does this mean? maybe the remote possibility of finally being able to use skype and actually talk with a bluetooth earpiece/headset?
1) The hardware is in fact connected. One less thing wait for the salting crew to find.
2) It is possible bluetooth can now be activated in software, since the devs now know it is not a complete waste of time trying to activate hardware that is present but not live.
It’s been well established that XDA-Developers isthedestination for resources relating to … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?