Hi, It is hard to help with the information you have given. If you can scan from the command line then that is a very good start. Do you have the logs when you try and turn BT on/off from the UI? I would try instrumenting the UI code and JNI code with log statements to see where exactly it fails.
Nick On Tue, Jul 21, 2009 at 11:11 AM, Bzbit<[email protected]> wrote: > > I'm having problems with enable/disable the BT device from the GUI. > > So here is my status so far - > > hciconfig + hcitool are working (I can scan). > even - bttest enable + disable are working, as I understand this > means hcid is working ok. > > As far as I can see bttest enable - is calling the same bt_enable > function as from the jni, then why the GUI is not able to work? > Can someone please help me with this? > > Here is my init.rc - (the hciattach & rfkill are not relevant I > removed them from the code) > ---------------- > # chmod 0660 /dev/ttyS1 > # chown bluetooth bluetooth /dev/ttyS1 > service dbus /system/bin/dbus-daemon --system --nofork > socket dbus stream 660 bluetooth bluetooth > user bluetooth > group bluetooth net_bt_admin > service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf > socket bluetooth stream 660 bluetooth bluetooth > socket dbus_bluetooth stream 660 bluetooth bluetooth > group bluetooth net_bt_admin misc > disabled > oneshot > #service hciattach /system/bin/hciattach -n /dev/ttyS1 texas 115200 > # user bluetooth > # group bluetooth net_bt_admin misc > # disabled > # oneshot > -------------------- > thx > > On Jul 19, 9:47 pm, Bzbit <[email protected]> wrote: >> I have removed the "CONFIG_ANDROID_PARANOID_NETWORK" from the Kernel >> now I can see the device under "hciconfig -a". >> but still I dont see it under "hcitool dev" >> >> On Jul 16, 7:39 pm, Bzbit <[email protected]> wrote: >> >> > Hi >> >> > I'm like to makeBluetoothwork on my x86 platform, >> > I added - BOARD_HAVE_BLUETOOTH := true and resolved compilation errors >> > as mentioned in - >> > "http://groups.google.com/group/android-porting/browse_frm/thread/ >> > 7bef542d21e14c11/0291b67ee7236d6b?lnk=gst&q=bluetooth >> > +usb#0291b67ee7236d6b" >> >> > I can tell that the driver (I have an SDIO device), came up & >> > registered as an hci device. >> > However - nothing is happening. I cant turn theBluetoothon in >> > Androids UI & in "hcitool dev" there are no devices. >> > (I did not see a call ro bt_sdio_open) >> >> > In addition I added the following to init.rc - >> >> > service dbus /system/bin/dbus-daemon --system --nofork >> > socket dbus stream 660bluetoothbluetooth >> > userbluetooth >> > groupbluetoothnet_bt_admin >> >> > service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf >> > socketbluetoothstream 660bluetoothbluetooth >> > socket dbus_bluetooth stream 660bluetoothbluetooth >> > # init.rc does not yet support applying capabilities, so run as root >> > and >> > # let hcid drop uid tobluetoothwith the right linux capabilities >> > groupbluetoothnet_bt_admin misc >> > disabled >> >> > service hfag /system/bin/sdptool add --channel=10 HFAG >> > userbluetooth >> > groupbluetoothnet_bt_admin >> > disabled >> > oneshot >> >> > service dun /system/bin/sdptool add --channel=2 DUN >> > userbluetooth >> > groupbluetoothnet_bt_admin >> > disabled >> > oneshot >> >> > service hsag /system/bin/sdptool add --channel=11 HSAG >> > userbluetooth >> > groupbluetoothnet_bt_admin >> > disabled >> > oneshot >> >> > But this did not help as well, >> > Guys please help I'm in the dark here... >> >> > Thx > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
