I suppose the basic BOARD_HAVE_BLUETOOTH flag is already set? and the JNI layer actually make calls to bluedroid !!!
Can you put in couple of debugs in the /frameworks/base/core/jni/android_server_BluetoothService.cpp" ? just to make sure you are in-fact building the right things? On Thu, Oct 21, 2010 at 2:11 PM, ms12 <mstic...@gmail.com> wrote: > Ok, I'm back trying to get this to work. To recap, trying to get an > external usb connected bluetooth device to work. > I've updated to android 2.1 Eclair. > One change I've noticed is that there is no longer and hcid service, > but there is a new bluetoothd service. > I've fixed the bluedroid so it doesn't open rfkill directories (there > are none, assumes power is always on) and does not start hciattach as > suggested above. > > Manually doing an > > hciconfig hci0 up > > seems to enable communications with the device. I can get it to > discover my phone, for example, via hcitool scan at the console. > > What I can't do is enable it from the Settings panel UI in Android. > Looks like maybe it blinks on for a ms or two, then goes right back > off. > I've put log entries in bluedroid/bluetooth.c set_bluetooth_power() > and it never goes there. The only thing I get in the log is > > I/power ( 915): *** set_screen_state 1 > I/power ( 915): *** set_screen_state 1 > I/power ( 915): *** set_screen_state 1 > V/BluetoothEventRedirector( 983): Received > android.bluetooth.adapter.action.STATE_CHANGED > V/BluetoothEventRedirector( 983): Received > android.bluetooth.adapter.action.STATE_CHANGED > > I get the impression I'm missing a part of the enable process > somewhere. It doesn't even try and call the bluedroid stuff. > > Any ideas on where to look? > Tbanks much in andvance > Mike > -- --Pavan Savoy -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting