Hi! have you fixed this problem?
I have the same. that is, I can use bttest and other command line tools, while from UI I got this dbus crash....why? do you know? thx! Marco On Wednesday, January 25, 2012 8:54:43 AM UTC+1, Alvin Wong wrote: > > I am porting Android 2.3.7 to my custom platform. > I've added BOARD_HAVE_BLUETOOTH := true to my BoardConfig.mk > I've also added the hciattach service to my init.PLATFORM.rc. > > That's all I get when I try to switch on Bluetooth from the Settings > UI: It becomes gray for half a second and return unchecked. > > Logcat: > D/BluetoothService( 865): Bluetooth state 10 -> 11 > V/BluetoothEventRedirector( 1135): Received > android.bluetooth.adapter.action.STATE_CHANGED > D/BluetoothService( 865): Bluetooth state 11 -> 10 > V/BluetoothEventRedirector( 1135): Received > android.bluetooth.adapter.action.STATE_CHANGED > > As my board doesn't use rfkill for power control, I modified the code > of bluedroid to make it look for my sysfs path to toggle Bluetooth > power. > > Running `bttest enable` make `hcitool dev` show a device and I am able > to perform `hcitool scan` and `hcitool inq`. I also see logs in > `dmesg`. > > Can anyone help me with this? -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
