gpt4 book ai didi

android - logcat 中的 LocSvc 错误消息

转载 作者:太空狗 更新时间:2023-10-29 12:41:09 24 4
gpt4 key购买 nike

经过各种 Google 搜索后,我找不到答案,所以:

我编写了一个送货跟踪应用程序,我们的司机会在 LG G2 设备上随身携带该应用程序。它使用 XMPP 与总部交谈并上传信息,并使用 GPS 跟踪我们的车辆。今天,突然间所有的追踪都停止了。我们的每台设备都认为它们整天都在基地……有点奇怪,我想,一个月左右没有新软件投入生产。因此,我从我们的一个驱动程序中获得了一个设备,并将其插入 Eclipse 以查看它在做什么,而 LogCat 中充满了以下内容:

08-27 16:31:24.944: E/LocSvc_api_v02(955): V/locClientSendReq:2413] qmi_client_send_msg_sync returned 0
08-27 16:31:24.944: E/LocSvc_api_v02(955): V/convertQmiResponseToLocStatus:681]: result = 0, error = -6564, status = 0
08-27 16:31:24.944: E/LocSvc_api_v02(955): V/loc_sync_send_req:512]: select_id = 0,locClientSendReq returned 0
08-27 16:31:24.944: E/LocSvc_api_v02(955): D/loc_free_slot:299]: freeing slot 0
08-27 16:31:24.944: E/LocSvc_api_v02(955): V/loc_sync_send_req:539]: success (select id 0)
08-27 16:31:24.944: E/LocSvc_ApiV02(955): D/Got Zpp fix location validity (lat:1, lon:1, timestamp:1 accuracy:1)
08-27 16:31:24.944: E/LocSvc_ApiV02(955): D/(50.9496151, -2.6051965), timestamp 1409153485700, accuracy 3168.393066
08-27 16:31:24.944: E/LocSvc_ulp_log(955): V/creating msg ULP_MSG_REPORT_POSITION
08-27 16:31:24.944: E/LocSvc_ulp_log(955): V/creating msg ox60b
08-27 16:31:24.944: E/LocSvc_ulp_log(955): V/flags: 63
08-27 16:31:24.944: E/LocSvc_ulp_log(955): source: 4
08-27 16:31:24.944: E/LocSvc_ulp_log(955): latitude: 50.949615
08-27 16:31:24.944: E/LocSvc_ulp_log(955): longitude: -2.605197
08-27 16:31:24.944: E/LocSvc_ulp_log(955): altitude: 94.844193
08-27 16:31:24.944: E/LocSvc_ulp_log(955): speed: 6.000000
08-27 16:31:24.944: E/LocSvc_ulp_log(955): bearing: 0.712935
08-27 16:31:24.944: E/LocSvc_ulp_log(955): accuracy: 3168.393066
08-27 16:31:24.944: E/LocSvc_ulp_log(955): timestamp: 1409153485700
08-27 16:31:24.944: E/LocSvc_ulp_log(955): rawDataSize: 0
08-27 16:31:24.944: E/LocSvc_ulp_log(955): rawData: 0x0
08-27 16:31:24.944: E/LocSvc_ulp_log(955): Session status: 0
08-27 16:31:24.944: E/LocSvc_ulp_log(955): Technology mask: 1
08-27 16:31:24.944: E/LocSvc_utils_q(955): D/msg_q_snd: Sending message with handle = 0x735B4310
08-27 16:31:24.944: E/LocSvc_utils_ll(955): D/linked_list_add: Adding to list data_obj = 0x735B4310
08-27 16:31:24.944: E/LocSvc_utils_q(955): D/msg_q_snd: Finished Sending message with handle = 0x735B4310
08-27 16:31:24.944: E/LocSvc_eng(955): V/Exiting int loc_eng_get_zpp_handler(loc_eng_data_s_type&) line 2044 0
08-27 16:31:24.944: E/LocSvc_MsgTask(955): D/MsgTask::loop() 701679 listening ...
08-27 16:31:24.944: E/LocSvc_utils_q(955): D/msg_q_rcv: Waiting on message
08-27 16:31:24.944: E/LocSvc_libulp(955): I/===> int ulp_msg_process_start_req() line 414
08-27 16:31:24.944: E/LocSvc_libulp(955): I/int ulp_msg_process_start_req(), at ulp state = 1
08-27 16:31:24.944: E/LocSvc_libulp(955): V/Exiting int ulp_msg_process_start_req() line 459 -1
08-27 16:31:24.944: E/LocSvc_libulp(955): V/Exiting int ulp_msg_process_system_update(UlpSystemEvent) line 1398 0
08-27 16:31:24.944: E/LocSvc_ulp_log(955): V/deleting msg UNKNOWN (0x60e)
08-27 16:31:24.944: E/LocSvc_utils_q(955): D/msg_q_rcv: Waiting on message
08-27 16:31:24.944: E/LocSvc_utils_ll(955): D/linked_list_remove: Removing from list
08-27 16:31:24.944: E/LocSvc_utils_q(955): D/msg_q_rcv: Received message 0x735B4310 rv = 0
08-27 16:31:24.944: E/LocSvc_libulp(955): D/void ulp_msg_main(void*) received msg of type: 0x60b
08-27 16:31:24.944: E/LocSvc_libulp(955): I/===> int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*) line 1427
08-27 16:31:24.944: E/LocSvc_libulp(955): I/int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*), zpp session status = 0, source: 4, flags = 0x3f, lat = 50.949615, lon = -2.605197, uncertainty = 3168.393066, tech_mask = 0x1
08-27 16:31:24.944: E/LocSvc_libulp(955): I/===> bool ulp_zpp_engine_running() line 62
08-27 16:31:24.944: E/LocSvc_libulp(955): V/Exiting bool ulp_zpp_engine_running() line 73 1
08-27 16:31:24.944: E/LocSvc_libulp(955): I/int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*), first_fix_pending 1, request active = 1,zpp running 1, zpp state 1
08-27 16:31:24.944: E/LocSvc_libulp(955): I/===> int ulp_msg_send_generic_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*, const GpsLocationExtended*, const void*) line 942
08-27 16:31:24.944: D/Ulp_jni(955): Location CB invoked

这有什么可担心的吗?我对这里的“error = -6564”特别感兴趣:

08-27 16:31:24.944: E/LocSvc_api_v02(955): V/convertQmiResponseToLocStatus:681]: result = 0, error = -6564, status = 0

我试图用谷歌搜索,但无济于事。非常感谢任何帮助。

最佳答案

它们标记为已过时 https://code.google.com/p/android/issues/detail?id=62285我不知道为什么。这个问题仍然发生在我的 gs4 上。有了那么多消息,我的应用程序真的很难调试,因为 logcat 很快就会溢出。我非常担心电池耗尽。

关于android - logcat 中的 LocSvc 错误消息,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/25531534/

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