W/ContextImpl(14368): Calling a method in the system process without a qualified user: :1487 :494 :494 I/CompanionService(13584): bluetoothStateChangeReceiver action = .STATE_CHANGEDĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:Bose SoundLink Wireless Mobile speakerĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:ANDYĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:obd2ecuĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:Glass 6014ĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:P311ĭ/CachedBluetoothDevice(14368): Clearing all connection state for dev:Logitech MX5000 Keyboard I/BtOppRfcommListener(23958): stopping Accept Thread
#Bluetooth stack android Bluetooth#
I/BluetoothAdapterState(23958): Entering PendingCommandState State: isTurningOn()=false, isTurningOff()=trueĭ/BluetoothManagerService( 578): Message: 60ĭ/BluetoothManagerService( 578): MESSAGE_BLUETOOTH_STATE_CHANGE: prevState = 12, newState=13ĭ/BluetoothManagerService( 578): Bluetooth State Change Intent: 12 -> 13ĭ/BluetoothMapService(23958): STATE_TURNING_OFFĭ/BluetoothMapService(23958): MAP Service closeService in I/BluetoothAdapterState(23958): Bluetooth adapter state changed: 12-> 13ĭ/BluetoothAdapterService(23958): Broadcasting updateAdapterState() to 1 receivers.ĭ/BluetoothAdapterProperties(23958): onBluetoothDisable() When disabling: D/BluetoothManagerService( 578): disable(): mBluetooth = mBinding = falseĭ/BluetoothManagerService( 578): Message: 2ĭ/BluetoothManagerService( 578): Sending off request.ĭ/BluetoothAdapterState(23958): CURRENT_STATE=ON, MESSAGE = USER_TURN_OFFĭ/BluetoothAdapterProperties(23958): Setting state to 13 If it is of any use, I captured some of the adb output after disabling Bluetooth. Is there a way to find out what is responsible for reactivating Bluetooth all the time? Googling around, it seems that this could be due to a misbehaving app, but there doesn't seem to be a good solution for finding out which app. It can be turned off, but will come back a minute or so later. I have seen this problem on a Nexus 4 and Nexus 5.