gpt4 book ai didi

Android手机 "DCD ON"错误,在Logcat中不断运行

转载 作者:搜寻专家 更新时间:2023-11-01 08:45:55 28 4
gpt4 key购买 nike

我正在尝试运行和测试我的应用程序,但是在我的 LogCat 中(除了我的应用程序中通常的堆栈跟踪之外),我得到了所有这些奇怪的额外红色错误,并且不知道它是什么从。令人沮丧的是,当我只是试图查找我的应用程序错误时,它会不断添加更多行,因此很难滚动以查找我的应用程序错误。即使我没有按手机上的任何东西,它也会不断添加这些奇怪的 DCD ON 行等等......知道如何阻止它们成为我的 LogCat 吗?我使用的是三星 Galaxy 5。谢谢。

LogCat

02-02 20:01:17.245      264-749/? E/AudioResampler﹕ Unsupported sample format, 1 bits, 1 channels
02-02 20:01:17.255 264-7385/? E/AudioSink﹕ received unknown event type: 1 inside CallbackWrapper !
02-02 20:01:17.535 763-7387/? E/android.os.Debug﹕ !@Dumpstate > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error
02-02 20:01:18.185 763-1211/? E/Watchdog﹕ !@Sync 21626
02-02 20:01:18.285 255-255/? E/SMD﹕ DCD ON
02-02 20:01:21.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:21.805 7438-7438/? E/QSEECOMAPI:﹕ Error::Failed to open /dev/qseecom device
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ QSEECom_start_app failed: path = /firmware/image, fname = tima_pkm
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ max_sendmsg_size = 262208, max_recvmsg_size = 262208, ret = 0xffffffff
02-02 20:01:21.805 7438-7438/? E/QSEECOMAPI:﹕ Error::Failed to open /dev/qseecom device
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ QSEECom_start_app failed: path = /firmware/image, fname = tima_pkm
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ max_sendmsg_size = 262208, max_recvmsg_size = 262208, ret = 0xffffffff
02-02 20:01:21.805 7438-7438/? E/QSEECOMAPI:﹕ Error::Failed to open /dev/qseecom device
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ QSEECom_start_app failed: path = /firmware/image, fname = tima_pkm
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ max_sendmsg_size = 262208, max_recvmsg_size = 262208, ret = 0xffffffff
02-02 20:01:21.805 7438-7438/? E/QSEECOMAPI:﹕ Error::Failed to open /dev/qseecom device
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ QSEECom_start_app failed: path = /firmware/image, fname = tima_pkm
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ max_sendmsg_size = 262208, max_recvmsg_size = 262208, ret = 0xffffffff
02-02 20:01:21.805 7438-7438/? E/QSEECOMAPI:﹕ Error::Failed to open /dev/qseecom device
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ QSEECom_start_app failed: path = /firmware/image, fname = tima_pkm
02-02 20:01:21.805 7438-7438/? E/TZ: qc_tlc_communication﹕ max_sendmsg_size = 262208, max_recvmsg_size = 262208, ret = 0xffffffff
02-02 20:01:23.055 763-1092/? E/lights﹕ write_int failed to open -1
02-02 20:01:24.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:27.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:30.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:33.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:36.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:39.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:42.295 255-255/? E/SMD﹕ DCD ON
02-02 20:01:45.305 255-255/? E/SMD﹕ DCD ON
02-02 20:01:48.195 763-1211/? E/Watchdog﹕ !@Sync 21627
02-02 20:01:48.305 255-255/? E/SMD﹕ DCD ON
02-02 20:01:51.305 255-255/? E/SMD﹕ DCD ON
02-02 20:01:54.305 255-255/? E/SMD﹕ DCD ON
02-02 20:01:57.305 255-255/? E/SMD﹕ DCD ON
02-02 20:02:00.305 255-255/? E/SMD﹕ DCD ON
02-02 20:02:03.305 255-255/? E/SMD﹕ DCD ON
02-02 20:02:06.305 255-255/? E/SMD﹕ DCD ON
02-02 20:02:09.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:12.305 255-255/? E/SMD﹕ DCD ON
02-02 20:02:15.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:18.195 763-1211/? E/Watchdog﹕ !@Sync 21628
02-02 20:02:18.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:21.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:24.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:27.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:30.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:33.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:36.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:39.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:42.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:45.325 255-255/? E/SMD﹕ DCD ON
02-02 20:02:48.185 763-1211/? E/Watchdog﹕ !@Sync 21629
02-02 20:02:48.325 255-255/? E/SMD﹕ DCD ON
02-02 20:02:51.325 255-255/? E/SMD﹕ DCD ON
02-02 20:02:54.315 255-255/? E/SMD﹕ DCD ON
02-02 20:02:57.325 255-255/? E/SMD﹕ DCD ON
02-02 20:02:58.045 763-1043/? E/WifiStateMachine﹕ Error! unhandled message{ when=-3ms what=135188 target=com.android.internal.util.StateMachine$SmHandler }
02-02 20:02:58.315 763-763/? E/LocSvc_flp﹕ I/===> int flp_inject_location(FlpLocation*) line 194
02-02 20:02:58.315 763-763/? E/LocSvc_utils_q﹕ D/msg_q_snd: Sending message with handle = 0x7F8AE188
02-02 20:02:58.315 763-763/? E/LocSvc_utils_ll﹕ D/linked_list_add: Adding to list data_obj = 0x7F8AE188
02-02 20:02:58.315 763-1253/? E/LocSvc_utils_q﹕ D/msg_q_rcv: Received message 0x7F8AE188 rv = 0
02-02 20:02:58.315 763-1253/? E/LocSvc_api_v02﹕ I/---> locClientSendReq line 2332 QMI_LOC_INJECT_POSITION_REQ_V02
02-02 20:02:58.325 763-763/? E/LocSvc_utils_q﹕ D/msg_q_snd: Finished Sending message with handle = 0x7F8AE188
02-02 20:02:58.325 763-1969/? E/LocSvc_ApiV02﹕ I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 113 QMI_LOC_INJECT_POSITION_REQ_V02
02-02 20:02:58.335 763-1253/? E/LocSvc_api_v02﹕ D/loc_free_slot:299]: freeing slot 0
02-02 20:03:00.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:03.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:06.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:09.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:12.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:15.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:18.195 763-1211/? E/Watchdog﹕ !@Sync 21630
02-02 20:03:18.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:21.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:24.325 255-255/? E/SMD﹕ DCD ON
02-02 20:03:27.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:30.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:33.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:36.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:39.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:42.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:45.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:48.195 763-1211/? E/Watchdog﹕ !@Sync 21631
02-02 20:03:48.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:51.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:54.335 255-255/? E/SMD﹕ DCD ON
02-02 20:03:57.335 255-255/? E/SMD﹕ DCD ON
02-02 20:04:00.335 255-255/? E/SMD﹕ DCD ON
02-02 20:04:03.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:06.335 255-255/? E/SMD﹕ DCD ON
02-02 20:04:09.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:12.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:15.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:18.195 763-1211/? E/Watchdog﹕ !@Sync 21632
02-02 20:04:18.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:21.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:24.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:27.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:30.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:33.345 255-255/? E/SMD﹕ DCD ON
02-02 20:04:36.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:39.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:42.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:45.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:48.195 763-1211/? E/Watchdog﹕ !@Sync 21633
02-02 20:04:48.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:51.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:54.355 255-255/? E/SMD﹕ DCD ON
02-02 20:04:57.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:00.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:03.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:06.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:09.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:12.355 255-255/? E/SMD﹕ DCD ON
02-02 20:05:15.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:18.195 763-1211/? E/Watchdog﹕ !@Sync 21634
02-02 20:05:18.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:21.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:24.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:27.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:30.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:33.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:35.575 763-1092/? E/lights﹕ write_int failed to open -1
02-02 20:05:35.575 763-989/? E/PersonaManagerService﹕ Unable to read user list
02-02 20:05:35.675 763-965/? E/ViewRootImpl﹕ sendUserActionEvent() mView == null
02-02 20:05:35.745 763-1020/? E/InputDispatcher﹕ channel ~ Channel is unrecoverably broken and will be disposed!
02-02 20:05:35.745 763-1020/? E/InputDispatcher﹕ channel ~ Channel is unrecoverably broken and will be disposed!
02-02 20:05:35.805 763-964/? E/MoreInfoHPW_ViewGroup﹕ Parent view is not a TextView
02-02 20:05:35.815 7635-7635/org.azurespot E/dalvikvm﹕ >>>>> Normal User
02-02 20:05:35.815 7635-7635/org.azurespot E/dalvikvm﹕ >>>>> org.azurespot [ userId:0 | appId:10252 ]
02-02 20:05:36.015 7635-7635/org.azurespot E/MoreInfoHPW_ViewGroup﹕ Parent view is not a TextView
02-02 20:05:36.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:39.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:41.585 763-1092/? E/lights﹕ write_int failed to open -1
02-02 20:05:42.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:45.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:48.195 763-1211/? E/Watchdog﹕ !@Sync 21635
02-02 20:05:48.375 255-255/? E/SMD﹕ DCD ON
02-02 20:05:51.365 255-255/? E/SMD﹕ DCD ON
02-02 20:05:54.375 255-255/? E/SMD﹕ DCD ON
02-02 20:05:57.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:00.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:03.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:06.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:09.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:12.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:15.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:18.205 763-1211/? E/Watchdog﹕ !@Sync 21636
02-02 20:06:18.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:21.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:24.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:27.375 255-255/? E/SMD﹕ DCD ON
02-02 20:06:30.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:30.925 7707-7707/? E/dalvikvm﹕ >>>>> Normal User
02-02 20:06:30.925 7707-7707/? E/dalvikvm﹕ >>>>> com.sec.spp.push:RemoteDlcProcess [ userId:0 | appId:10041 ]
02-02 20:06:31.395 9257-11405/? E/SPPClientService﹕ [b] __PingReply__
02-02 20:06:31.465 7707-7707/? E/SPPClientService﹕ ============PushLog. commonIsShipBuild. stop!
02-02 20:06:31.465 7707-7707/? E/SPPClientService﹕ [PushClientApplication] Push log off : This is Ship build version
02-02 20:06:33.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:36.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:39.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:42.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:45.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:48.205 763-1211/? E/Watchdog﹕ !@Sync 21637
02-02 20:06:48.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:51.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:54.385 255-255/? E/SMD﹕ DCD ON
02-02 20:06:57.385 255-255/? E/SMD﹕ DCD ON
02-02 20:07:00.385 255-255/? E/SMD﹕ DCD ON
02-02 20:07:03.385 255-255/? E/SMD﹕ DCD ON
02-02 20:07:06.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:09.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:12.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:15.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:18.205 763-1211/? E/Watchdog﹕ !@Sync 21638
02-02 20:07:18.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:21.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:24.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:27.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:30.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:33.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:36.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:39.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:42.395 255-255/? E/SMD﹕ DCD ON
02-02 20:07:43.135 763-1043/? E/WifiStateMachine﹕ Error! unhandled message{ when=-1ms what=135188 target=com.android.internal.util.StateMachine$SmHandler }
02-02 20:07:43.355 763-763/? E/LocSvc_flp﹕ I/===> int flp_inject_location(FlpLocation*) line 194
02-02 20:07:43.365 763-763/? E/LocSvc_utils_q﹕ D/msg_q_snd: Sending message with handle = 0x80EBC410
02-02 20:07:43.365 763-763/? E/LocSvc_utils_ll﹕ D/linked_list_add: Adding to list data_obj = 0x80EBC410
02-02 20:07:43.365 763-1253/? E/LocSvc_utils_q﹕ D/msg_q_rcv: Received message 0x80EBC410 rv = 0
02-02 20:07:43.365 763-1253/? E/LocSvc_api_v02﹕ I/---> locClientSendReq line 2332 QMI_LOC_INJECT_POSITION_REQ_V02
02-02 20:07:43.365 763-763/? E/LocSvc_utils_q﹕ D/msg_q_snd: Finished Sending message with handle = 0x80EBC410
02-02 20:07:43.365 763-1969/? E/LocSvc_ApiV02﹕ I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 113 QMI_LOC_INJECT_POSITION_REQ_V02
02-02 20:07:43.375 763-1253/? E/LocSvc_api_v02﹕ D/loc_free_slot:299]: freeing slot 0
02-02 20:07:45.405 255-255/? E/SMD﹕ DCD ON
02-02 20:07:48.205 763-1211/? E/Watchdog﹕ !@Sync 21639
02-02 20:07:48.405 255-255/? E/SMD﹕ DCD ON
02-02 20:07:51.405 255-255/? E/SMD﹕ DCD ON
02-02 20:07:54.405 255-255/? E/SMD﹕ DCD ON
02-02 20:07:57.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:00.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:03.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:06.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:09.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:12.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:15.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:18.205 763-1211/? E/Watchdog﹕ !@Sync 21640
02-02 20:08:18.405 255-255/? E/SMD﹕ DCD ON
02-02 20:08:21.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:24.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:27.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:30.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:33.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:36.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:39.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:42.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:45.415 255-255/? E/SMD﹕ DCD ON
02-02 20:08:48.205 763-1211/? E/Watchdog﹕ !@Sync 21641
02-02 20:08:48.425 255-255/? E/SMD﹕ DCD ON
02-02 20:08:51.425 255-255/? E/SMD﹕ DCD ON
02-02 20:08:54.425 255-255/? E/SMD﹕ DCD ON
02-02 20:08:57.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:00.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:03.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:06.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:09.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:12.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:15.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:18.205 763-1211/? E/Watchdog﹕ !@Sync 21642
02-02 20:09:18.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:21.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:24.425 255-255/? E/SMD﹕ DCD ON
02-02 20:09:27.435 255-255/? E/SMD﹕ DCD ON
02-02 20:09:30.435 255-255/? E/SMD﹕ DCD ON
02-02 20:09:33.435 255-255/? E/SMD﹕ DCD ON
02-02 20:09:36.435 255-255/? E/SMD﹕ DCD ON

最佳答案

我讨厌工具无法完成您需要它们完成的工作。就像你遇到的问题一样,我挣扎了很长时间。最初我尝试使用命令行并将 grep 链接在一起,但似乎在丢失所有输出之前您只能链接几个。我在这上面浪费了很多时间。

DCD ON 由 /system/bin/smdexe 产生。您可以尝试过滤掉运行 smdexe 的 PID。

如果您使用的是 Mac,我认为最好的选择是使用 LogRabbit(我是该工具的创建者,所以我当然有偏见)。

通过启动记录器,然后右键单击您的应用程序名称,只查看您在 LogRabbit 中的消息。选择“添加过滤器...”。保存过滤器并从列表中选择。现在您只会看到您的应用程序数据。您可以做更多的事情,但这是一个很好的起点。

以下是有关您可以做什么的一些教程: https://www.youtube.com/watch?v=HeildKynnuc&list=PLZVr2R6DumNZUoMZRndqM7cL63gp2NTYE

希望对您有所帮助。

顺便说一下,这是一个动画 GIF,我认为它解释了 Android Studio 和 Eclipse 中 logcat 的滚动锁定是什么样的:http://imgur.com/q8q0pJC

关于Android手机 "DCD ON"错误,在Logcat中不断运行,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/28292177/

28 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com