On Thu, Oct 21, 2010 at 2:20 PM, Pavan Savoy <pavan.sa...@gmail.com> wrote:
> I suppose the basic BOARD_HAVE_BLUETOOTH flag is already set?
> and the JNI layer actually make calls to bluedroid !!!
>
> Yep, BOARD_HAVE_BLUETOOTH is set.
> 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?
>
> Did this, and now it is calling bluedroid (not sure why it didn't before
... )
Error I get is now
E/bluedroid( 895): bt_enable: Timeout waiting for HCI device to come
up
This means the ioctl call to the socket isn't succeeding.
BUT, just above this is the following comment:
// Try for 10 seconds, this can only succeed once hciattach has sent
the
// firmware and then turned on hci device via HCIUARTSETPROTO ioctl
So when I commented out hciattach, it looks like I also disabled some
initializing of the device.
Will go try and hunt down HCIUARTSETPROTO in hciattach and what it is doing
to "turn it on".
I'm assuming (hoping) that the socket is going directly to hci0, and I just
have to set something
via the ioctl to turn it on.
Mike
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
