Hi, I'm currently trying two approaches:
1) Integrating android-x86's bluedroid 2) Using android-bluez as a replacement to bluedroid Neither is functional yet :( I'll report back when I have something working. Keith On Monday, February 16, 2015 at 1:17:03 PM UTC-7, LW wrote: > > Hi Keith, > > I am working on similar project and very interested your progress. > > I have a Knivao BTD-400 Bluetooth USB adapter (it uses Broadcom BCM20702A0 > chip). My work is based on the TI stock Beaglebone Black android code base > (JB 4.2 Kernel 3.2.0). I noticed that the BCM20702A0 is supported by > default. > > By adding the VID and PID of the USB adapter to the btusb_table in btusb.c > and perform an echo in android shell like: echo "0x05ac, 0x21e8" > > /sys/bus/usb/driver/btusb/new_id, the hci0 interface will shown up under > /sys/class/bluetooth/hci/hci0 > > Then I can the hciconfig to bring hci0 up / down and use hcitool to do > scan and detect other bluetooth devices (hciconfig and hcitool are ported > from ICS). It seems that the USB bluetooth device at kernel level is alive. > As you know in JB4.2 it seems that the UART interface is the by-default > interface between the android and kernel. Basically I am not able to enable > the bluetooth from android. The interface is missing. I am trying to figure > out how to bridge the gap here. > > It seems that you made progress on the android side but couldn't detect > supported device. I wonder if you could share the information on porting > and building the bluedroid ( assuming using android-x86). > > Thanks, > > Lei > > > > > On Wednesday, February 11, 2015 at 10:26:23 AM UTC-5, Keith Conger wrote: >> >> Getting closer. I have everything built and running bdt, produces a >> logcat message that there is no supported device. This is with two >> different adapters. I've posted some questions to the android-x86 list >> including which adapters are supported. I think I'm getting close. >> >> Also I found that there is a android-bluez project that is a drop in >> replacement for bluedroid. I may try that next. >> >> https://01.org/bluez-android >> >> >> On Tuesday, February 10, 2015 at 3:29:53 PM UTC-7, Keith Conger wrote: >>> >>> That was it RFKILL needed to be built in also. Rebuilding. >>> >>> On Tue, Feb 10, 2015 at 2:06 PM, Andrew Henderson <[email protected]> >>> wrote: >>> >>>> Try configuring the kernel using the "menuconfig" target (like "make >>>> menuconfig" in the makefile). I suspect that you are manually setting >>>> something in the .config and there are other settings that conflict with >>>> it. Normally, these conflicts are managed via the Kconfig or menuconfig >>>> interface (i.e. it just takes options away from you or forces some items >>>> to >>>> be modules). Make sure that the options that you are setting are actually >>>> all compatible with each other. If all else fails, you can manually >>>> insmod >>>> modules in the init.{ro.hardware}.rc file inside of Android during boot. >>>> >>>> On Tuesday, February 10, 2015 at 3:41:52 PM UTC-5, Keith Conger wrote: >>>>> >>>>> It built without errors. I'm having trouble with the kernel though. >>>>> I made sure kernel/.config and am335x_evm_android_defconfig both had >>>>> CONFIG_BT=y. I re-ran make in the root of BBBAndroid. As soon as I >>>>> answered the questions about the USB gadget driver it reverted to >>>>> CONFIG_BT=m >>>>> along with the other options I modified. Any ideas Andrew? >>>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "BeagleBoard" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/beagleboard/X4HYHv9cC-0/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Keith Conger >>> keith DOT conger AT gmail DOT com >>> http://thecongers.org >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
