Forgot to ask. How do I get my kernel options to stick in the BBBAndroid build process? My manual settings keep getting reverted when I build it.
Keith On Tue, Feb 10, 2015 at 10:26 AM, Andrew Henderson <hende...@icculus.org> wrote: > Well, Bluetooth being recognized by the kernel and Bluetooth being > accessible via the API are two very different animals. Enabling the > Bluetooth stack in the kernel, as well as the device drivers, is the first > step. Once that portion is done, your Bluetooth device must be registered > within the Android HAL to access it from the API. If you take a look in > the BBBAndroid source tree in > hardware/libhardware/include/hardware/bluetooth.h, you can see the > interface functions used to bridge the API to a Bluetooth device. I have > not checked into whether you can bypass all of this by using a USB > Bluetooth device, though. For example, if you are using a Bluetooth > keyboard with a USB/Bluetooth dongle plugged into the BBB, will the BBB see > it as a Bluetooth device or a USB keyboard? If you can leverage the USB > drivers and have the Bluetooth functionality of your device be "invisible" > to Android, then you're in luck. But, if you want to use the full > Bluetooth API to manage your device, BBBAndroid is missing the portion of > the HAL needed to make that happen. > > What is the nature of the Bluetooth device that you are using? > > > On Thursday, February 5, 2015 at 1:39:48 PM UTC-5, Keith Conger wrote: >> >> Has anyone managed to enable USB Bluetooth Adapter Support in >> BBBAndroid. I've read the Android > 4.2 can support USB bluetooth if built >> correctly. >> >> This is what I've tried so far: >> >> I set the following in "device/ti/beagleboneblack/BoardConfig.mk" >> BOARD_HAVE_BLUETOOTH := true >> >> And the following in "kernel/.config" >> CONFIG_BT=y >> CONFIG_BT_RFCOMM=y >> CONFIG_BT_RFCOMM_TTY=y >> CONFIG_BT_BNEP=y >> CONFIG_BT_BNEP_MC_FILTER=y >> CONFIG_BT_BNEP_PROTO_FILTER=y >> CONFIG_BT_HIDP=y >> >> # >> # Bluetooth device drivers >> # >> CONFIG_BT_HCIBTUSB=y >> CONFIG_BT_HCIBTSDIO=y >> CONFIG_BT_HCIUART=y >> CONFIG_BT_HCIUART_H4=y >> CONFIG_BT_HCIUART_BCSP=y >> CONFIG_BT_HCIUART_ATH3K=y >> CONFIG_BT_HCIUART_LL=y >> CONFIG_BT_HCIUART_3WIRE=y >> CONFIG_BT_HCIBCM203X=y >> CONFIG_BT_HCIBPA10X=y >> CONFIG_BT_HCIBFUSB=y >> CONFIG_BT_HCIVHCI=y >> CONFIG_BT_MRVL=y >> CONFIG_BT_MRVL_SDIO=y >> CONFIG_BT_ATH3K=y >> CONFIG_BT_WILINK=y >> >> However after I build a new image, most of the above are reverted to ‘m’ >> from ’y’. >> >> Created a file called “/system/etc/permissions/beagleboardblack.xml” >> that contains: >> >> <permissions> >> <feature name="android.hardware.bluetooth" /> >> </permissions> >> >> I'm new to the Android OS build environment, so I'm not sure if I missing >> something. I need Bluetooth for the project I'm working on. So I'm open >> to any options even if it means different hardware all together. >> >> Thanks in advance >> >> >> -- > 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 > beagleboard+unsubscr...@googlegroups.com. > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.