SHARE
TWEET

oos9 - eas - bt crash - mcd

a guest Jun 18th, 2019 114 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 06-18 11:56:33.496 D/GattService( 9233):  profile started successfully
  2. 06-18 11:56:33.497 D/BluetoothAdapterService( 9233): handleMessage() - Message: 2
  3. 06-18 11:56:33.497 D/BluetoothAdapterService( 9233): handleMessage() - MESSAGE_PROFILE_SERVICE_REGISTERED
  4. 06-18 11:56:33.497 D/BluetoothAdapterService( 9233): handleMessage() - Message: 1
  5. 06-18 11:56:33.497 D/BluetoothAdapterService( 9233): handleMessage() - MESSAGE_PROFILE_SERVICE_STATE_CHANGED
  6. 06-18 11:56:33.497 W/BluetoothAdapterService( 9233): onProfileServiceStateChange() - Gatt profile service started..
  7. 06-18 11:56:33.497 I/bt_btif ( 9233): QTI OMR1 stack: enable: start restricted = 0
  8. 06-18 11:56:33.498 E/bt_vnd_log( 9233): init_vnd_Logger, Logger Not enabled from config file
  9. 06-18 11:56:33.498 I/bt_stack_manager( 9233): event_start_up_stack is bringing up the stack
  10. 06-18 11:56:33.498 I/bt_core_module( 9233): module_start_up Starting module "btif_config_module"
  11. 06-18 11:56:33.498 I/bt_core_module( 9233): module_start_up Started module "btif_config_module"
  12. 06-18 11:56:33.498 I/bt_core_module( 9233): module_start_up Starting module "btsnoop_module"
  13. 06-18 11:56:33.498 D/bt_snoop( 9233): start_up: vendor_logging_level values is 65535
  14. 06-18 11:56:33.498 I/bt_core_module( 9233): module_start_up Started module "btsnoop_module"
  15. 06-18 11:56:33.498 I/bt_core_module( 9233): module_start_up Starting module "hci_module"
  16. 06-18 11:56:33.498 I/bt_hci  ( 9233): hci_module_start_up
  17. 06-18 11:56:33.499 I/bt_osi_thread( 9233): run_thread: thread id 9265, thread name hci_thread started
  18. 06-18 11:56:33.499 D/bt_osi_wakelock( 9233): wakelock_initialize_native opening wake locks
  19. 06-18 11:56:33.499 D/bt_hci  ( 9233): hci_module_start_up starting async portion
  20. 06-18 11:56:33.499 I/bt_hci  ( 9233): hci_initialize
  21. 06-18 11:56:33.501 I/bt_hci  ( 9233): hci_initialize: IBluetoothHci::getService() returned 0x70bd2ebaa0 (remote)
  22. 06-18 11:56:33.502 W/vendor.qti.bluetooth@1.0-bluetooth_hci(  543): BluetoothHci::initialize()
  23. 06-18 11:56:33.502 W/vendor.qti.bluetooth@1.0-data_handler(  543): DataHandler:: Init()
  24. 06-18 11:56:33.502 I/vendor.qti.bluetooth@1.0-data_handler(  543): Open init_status 2
  25. 06-18 11:56:33.502 D/vendor.qti.bluetooth@1.0-wake_lock(  543): Init wakelock is initiated
  26. 06-18 11:56:33.502 I/vendor.qti.bluetooth@1.0-uart_controller(  543): soc need reload patch = 1
  27. 06-18 11:56:33.502 D/vendor.qti.bluetooth@1.0-power_manager(  543): SetPower: enable: 0
  28. 06-18 11:56:33.503 D/vendor.qti.bluetooth@1.0-power_manager(  543): GetRfkillFd: rfkill_fd: 9
  29. 06-18 11:56:33.503 D/vendor.qti.bluetooth@1.0-power_manager(  543): ControlRfkill: rfkill_fd: 9, enable: 0
  30. 06-18 11:56:33.612 D/vendor.qti.bluetooth@1.0-power_manager(  543): SetPower: enable: 1
  31. 06-18 11:56:33.612 D/vendor.qti.bluetooth@1.0-power_manager(  543): GetRfkillFd: rfkill_fd: 9
  32. 06-18 11:56:33.612 D/vendor.qti.bluetooth@1.0-power_manager(  543): ControlRfkill: rfkill_fd: 9, enable: 1
  33. 06-18 11:56:33.722 D/vendor.qti.bluetooth@1.0-wake_lock(  543): Acquire wakelock is acquired
  34. 06-18 11:56:33.722 D/vendor.qti.bluetooth@1.0-uart_transport(  543): Init:> soc_type: 2, need_reload: 1
  35. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-uart_transport(  543): ConfigUart: fd: 9, p_cfg: 0x786ef2c00c
  36. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-uart_transport(  543): ConfigUart: baud {0x0, 0x1002}, fmt: 0x8209
  37. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-uart_transport(  543): ConfigUart: data_bits: 0x30, parity: 0x0, stop_bits: 0x0
  38. 06-18 11:56:33.726 I/vendor.qti.bluetooth@1.0-uart_transport(  543): ConfigUart: HW flow control enabled
  39. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-uart_transport(  543): OpenUart: succeed to open /dev/ttyHS0, fd: 9
  40. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-uart_transport(  543): InitTransport: soc_type(2), opening '/dev/ttyHS0' return fd=9
  41. 06-18 11:56:33.724 W/bluetooth@1.0-s(  543): type=1400 audit(0.0:540): avc: denied { getattr } for path="/data/vendor/oemnvitems/447" dev="dm-0" ino=423 scontext=u:r:hal_bluetooth_qti:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=0
  42. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): PatchDLManager
  43. 06-18 11:56:33.726 D/vendor.qti.bluetooth@1.0-ibs_handler(  543): InitInt: tty_fd = 9
  44. 06-18 11:56:33.727 E/vendor.qti.bluetooth@1.0-bluetooth_address(  543): BD address read from /data/vendor/oemnvitems/447 iFilelen=6: c9:a1:d1:fb:ee:c0
  45. 06-18 11:56:33.727 E/vendor.qti.bluetooth@1.0-bluetooth_address(  543): /data/vendor/oemnvitems/447 ok
  46. 06-18 11:56:33.727 I/vendor.qti.bluetooth@1.0-uart_transport(  543): ## userial_vendor_ioctl: UART Flow On
  47. 06-18 11:56:33.727 D/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): WipowerCurrentChargingStatusReq: Sending EDL_WIP_QUERY_CHARGING_STATUS_CMD
  48. 06-18 11:56:33.779 E/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadHciEvent: Unexpected event : protocol byte: 5
  49. 06-18 11:56:33.779 E/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): HciSendWipowerVsCmd: Failed to charging status cmd on Controller
  50. 06-18 11:56:33.779 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadVsHciEvent: Unexpected event! : opcode: 2
  51. 06-18 11:56:33.779 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): GetVsHciEvent: Failed to receive HCI-Vendor Specific event
  52. 06-18 11:56:33.779 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): WipowerCurrentChargingStatusReq: WP Failed to get HCI-VS Event from SOC
  53. 06-18 11:56:33.779 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): CheckEmbeddedMode: Wipower status req failed (0xffffff92)
  54. 06-18 11:56:33.780 E/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): CheckEmbeddedMode: wipower_flag_: 0
  55. 06-18 11:56:33.780 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543):  SocInit
  56. 06-18 11:56:33.780 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): SocInit: reserved param
  57. 06-18 11:56:33.780 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadNewHciEvent: Got an invalid proto byte: 0
  58. 06-18 11:56:33.840 I/chatty  (  543): uid=1002 bluetooth@1.0-s identical 933 lines
  59. 06-18 11:56:33.840 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadNewHciEvent: Got an invalid proto byte: 0
  60. 06-18 11:56:33.844 W/bluetooth@1.0-s(  543): type=1400 audit(0.0:541): avc: denied { read } for name="ssrdump" dev="dm-0" ino=123 scontext=u:r:hal_bluetooth_qti:s0 tcontext=u:object_r:ramdump_vendor_data_file:s0 tclass=dir permissive=0
  61. 06-18 11:56:33.840 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadNewHciEvent: Got an invalid proto byte: 0
  62. 06-18 11:56:33.847 I/chatty  (  543): uid=1002 bluetooth@1.0-s identical 105 lines
  63. 06-18 11:56:33.847 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadNewHciEvent: Got an invalid proto byte: 0
  64. 06-18 11:56:33.847 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): ReadVsHciEvent: Unexpected event! : opcode: 5
  65. 06-18 11:56:33.847 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): GetVsHciEvent: Failed to receive HCI-Vendor Specific event
  66. 06-18 11:56:33.847 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): HciSendVsCmd: Failed to get ReadVsHciEvent Event from SOC
  67. 06-18 11:56:33.847 E/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): Failed to attach the patch payload to the Controller!
  68. 06-18 11:56:33.847 I/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): SocInit: Fail to get chipset Version (0xffffff92)
  69. 06-18 11:56:33.847 E/vendor.qti.bluetooth@1.0-patch_dl_manager(  543): PerformChipInit: SoC initialization failed: -110
  70. 06-18 11:56:33.847 E/vendor.qti.bluetooth@1.0-uart_controller(  543): Init failed
  71. 06-18 11:56:33.847 D/vendor.qti.bluetooth@1.0-uart_transport(  543): CleanUp:> soc_type: 2, need_reload: 1
  72. 06-18 11:56:33.847 D/vendor.qti.bluetooth@1.0-uart_transport(  543): userial clock off
  73. 06-18 11:56:33.848 I/vendor.qti.bluetooth@1.0-uart_transport(  543): DeInitTransport: Transport is being closed!
  74. 06-18 11:56:33.848 D/vendor.qti.bluetooth@1.0-wake_lock(  543): Release wakelock is released
  75. 06-18 11:56:33.848 W/vendor.qti.bluetooth@1.0-data_handler(  543): Controller Init failed
  76. 06-18 11:56:33.849 E/vendor.qti.bluetooth@1.0-logger(  543): DeleteDumpsIfRequired: Cannot open dump location /data/vendor/ssrdump/
  77. 06-18 11:56:33.890 E/bt_hci  ( 9233): initializationComplete: HCI Init failed
  78. 06-18 11:56:34.008 D/AppTracker( 1941): App Event: quick_bt
  79. 06-18 11:56:34.012 D/BluetoothManagerService( 1213): enable(com.android.systemui):  mBluetooth =android.bluetooth.IBluetooth$Stub$Proxy@615a095 mBinding = false mState = BLE_TURNING_ON
  80. 06-18 11:56:34.012 D/BluetoothManagerService( 1213): enable returning
  81. 06-18 11:56:34.013 D/BluetoothManagerService( 1213): MESSAGE_ENABLE(0): mBluetooth = android.bluetooth.IBluetooth$Stub$Proxy@615a095
  82. 06-18 11:56:34.045 W/NotificationService( 1213): Toast already killed. pkg=com.tortel.syslog callback=android.app.ITransientNotification$Stub$Proxy@f373f14
  83. 06-18 11:56:34.049 D/AbstractTracker( 1941): Event success
  84. 06-18 11:56:34.415 D/BluetoothManagerService( 1213): MESSAGE_RESTART_BLUETOOTH_SERVICE
  85. 06-18 11:56:34.417 D/BluetoothAdapterService( 9233): enable() - Enable called with quiet mode status =  false
  86. 06-18 11:56:34.418 I/AdapterState( 9233): BLE_TURNING_ON : Unhandled message - BLE_TURN_ON
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top