Hnm, you can fake the service hciattach too.. like what we do is ... service hciattach /system/bin/hciattach -l user root # changing user to root from bluetooth is a potential security issue # service hciattach_legacy is used instead of hciattach because, we dont # have nodes named ttyHS0 group bluetooth net_bt_admin misc disabled oneshot
so bluedroid thinks hciattach is running fine, but hciattach would just show help and quit.. On Fri, Oct 8, 2010 at 1:50 PM, MikeS <mstic...@gmail.com> wrote: > I'll look into fixing the rfkill toggling, but suppose I get that working. > Looking at bluedroid, it looks like it demands hciattach and a uart. Will > it work with a USB attached bluetooth module? > > Mike > > > On Fri, Oct 8, 2010 at 11:20 AM, Pavan Savoy <pavan.sa...@gmail.com>wrote: > >> 2.6.29? >> Ok then forget what I mentioned about BT subsystem creating an rfkill. >> >> So all you need is the 2.6.29's rfkill driver. >> You can find it at drivers/misc/ of the kernel/omap project under 2.6.29 >> branch on git.source.android.com >> >> well rfkill is VERY necessary for BT chips which need to be powered on by >> the apps processor. >> in you usb case, it might be always ON.. but same is not the case with >> most UART BT chips.. which is more frequent on an embedded system. >> >> So you can go ahead and remove off the rfkill toggling in bluedroid or >> write yourself a "fake" driver ... >> >> (USB BT is more often used in the PC/laptop category) >> >> > -- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting