Hi,lzh20044178, I have met with the same problem with you.I can not start bluetooth from UI,but it can be done by manually. On my phone, $bttest enable enable =0
Could you please explain more details about how you solve this problem? I don't understand "the reason is the sdptool service is running. close it" The log is as below: D/BluetoothDeviceService( 43): Bluetooth state 0 -> 1 D/BluetoothDeviceService( 43): Bluetooth state 1 -> 0 V/BluetoothEventRedirector( 160): Received android.bluetooth.intent.action.BLUETOOTH_STATE_CHANGED V/BluetoothEventRedirector( 160): Received android.bluetooth.intent.action.BLUETOOTH_STATE_CHANGED Look forward to your help! Thanks! On 3月17日, 上午10时57分, lzh20044178 <[email protected]> wrote: > thanks for your help, now start bluetooth from UI successfully, the reason is > the sdptool service is running. close it, and i skiped rfkill in bluetooth.c > > 在2009-03-13，"Nick Pelly" <[email protected]> 写道： > > > > > > >On Wed, Mar 11, 2009 at 1:57 AM, NickS <[email protected]> wrote: > > >> Hi: > >> ?On my Netbook > >> $bttest enable > >> enable > >> =0 > > >> command hciconfig -a and hcitool scan can get information of device. > > >That's good. Your chip is powered and the uart is working. > > >Did hcitool scan show other devices? Then the TI chip firmware is > >correctly loaded. > > >> But turn on from UI, there's no any response. it's why? have no any > >> idea. i don't want to analyze from app of UI. > > >What does logcat say? > > >Is hcid running? > >Is hciattach running? > > >>?I skiped rfkill in > >> bluetooth.c,because my platform have no use it. I think I have started > >> services about bluetooth. follow my init.rc > >> ? ?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 > >> service hfag /system/bin/sdptool add --channel=10 HFAG > >> ? ?user bluetooth > >> ? ?group bluetooth net_bt_admin > >> ? ?disabled > >> ? ?oneshot > > >init.rc looks good. > > >Try starting hcid and hciattach manually (as Sean suggested) > > >Try modifying init.rc to run hcid via /system/bin/logwrapper > >service hcid /system/bin/logwrapper /system/bin/hcid -s -n -f > >/etc/bluez/hcid.conf > >So you can see its output in logcat. > > >Unfortunately you cannot run hciattach in logwrapper, it triggers some > >strange timeout bug (I wonder if anyone can figure this out for me). > > >And yes please post the output of logcat when you try to enable BT from the > >UI. > > >You can also modify a lot of the Bluetooth source to enable more > >logging. Look for DBG flags. > > >Some more tips inhttp://source.android.com/projects/bluetooth-faqbut > >you might have read them. > > >Nick- 隐藏被引用文字 - > > - 显示引用的文字 - --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
