On Wed, Aug 4, 2010 at 12:19 PM, Pavan Savoy <pavan.sa...@gmail.com> wrote: > #service hciattachd /system/bin/hciattach -s 115200 /dev/s3c_serial1 > any 460800 flow NULL > #user root > #group bluetooth net_bt_admin > #disabled > #oneshot > > is almost correct except for the hciattach"d" part.. > so your entry should be ... > > service hciattach /system/bin/hciattach -s 115200 /dev/s3c_serial1 any > 460800 flow NULL > user root > group bluetooth net_bt_admin > disabled > oneshot > > And no there is no hcid anymore since bluez4.x.. it is now > bluetoothd.. which you have it properly.. > > Assuming you have your rfkill driver in right place, and it has > exposed the /sys/class/rfkill/rfkill0/state entry .. everything should > automagically work !! > > > On Wed, Aug 4, 2010 at 11:57 AM, Ajith Kamath <sjce.aj...@gmail.com> wrote: >> Hi all, >> >> I'm able to start bluetooth after porting only from command line. >> I give following commands and it works >> >> #hciattach -s 115200 /dev/s3c_serial1 any 460800 flow NULL >> #hciattach -s 115200 /dev/s3c_serial1 bcm2035 460800 flow NULL >> >> Doing this brings bluetooth up for me. >> But I want to put this in init.rc file so that it happens in boot itself. >> But its not working. >> Can someone tell how to put it in init.rc >> >> Also from references i have realised that hcid is not at all there in >> system/bin or in data/misc/hcid >> Can some one please advice on this. >> >> commented parts in init.rc relating to bluetooth are things I tried but >> didn't work >> >> Thanks, >> Ajith >> >> >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting >> > > > > -- > --Pavan Savoy >
-- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
