Logcat中提示这些信息，程序直接闪退，不知道出错在哪里 大神帮忙看看

CC攻城狮 2018-11-18 12:53:11 
11-18 12:46:30.604      280-280/? E/QSEECOMAPI:﹕ Error::Cannot open the file /firmware/image/vivokeymaster.mdt

11-18 12:46:30.604      280-280/? E/QSEECOMAPI:﹕ Error::Loading image failed with ret = -1

11-18 12:46:30.684      280-328/? E/QSEECOMAPI:﹕ Error::Cannot open the file /firmware/image/vivokeymaster.mdt

11-18 12:46:30.684      280-328/? E/QSEECOMAPI:﹕ Error::Loading image failed with ret = -1

11-18 12:46:40.594  11072-11072/? E/PushFactory﹕ getPushInstance not found push instance.

11-18 12:47:10.544  11235-11235/? E/SQLiteLog﹕ (283) recovered 37 frames from WAL file /data/data/com.android.providers.media/databases/external.db-wal

11-18 12:47:10.664      280-280/? E/QSEECOMAPI:﹕ Error::Cannot open the file /firmware/image/vivokeymaster.mdt

11-18 12:47:10.664      280-280/? E/QSEECOMAPI:﹕ Error::Loading image failed with ret = -1

11-18 12:47:30.714  11307-11328/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87AD480(STAT_DATA_ID)

11-18 12:47:30.714  11307-11328/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87AF098(STAT_DATA_ID)

11-18 12:47:30.854  11307-11328/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87D8680(STAT_DATA_ID)

11-18 12:47:30.864  11307-11328/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87DA4E8(STAT_DATA_ID)

11-18 12:47:40.554    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Empty response

11-18 12:47:40.554    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Exception: com.android.internal.telephony.CommandException: GENERIC_FAILURE

11-18 12:47:40.564  11348-11367/? E/SIM1﹕ internalOpenLogicalChannel(aid): throw CardException

11-18 12:47:40.564    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Empty response

11-18 12:47:40.564    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Exception: com.android.internal.telephony.CommandException: GENERIC_FAILURE

11-18 12:47:40.574  11348-11367/? E/SIM1﹕ internalOpenLogicalChannel(aid): throw CardException

11-18 12:47:40.574  11348-11367/? E/SmartcardService ACE ARF﹕ Error opening logical channel open channel failed

11-18 12:47:40.574    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Empty response

11-18 12:47:40.574    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Exception: com.android.internal.telephony.CommandException: GENERIC_FAILURE

11-18 12:47:40.584  11348-11367/? E/SIM1﹕ internalOpenLogicalChannel(aid): throw CardException

11-18 12:47:40.584  11348-11367/? E/SmartcardService ACE ARF﹕ Error opening logical channel open channel failed

11-18 12:47:40.594    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Empty response

11-18 12:47:40.594    1804-1804/? E/PhoneInterfaceManager﹕ [PhoneIntfMgr] iccOpenLogicalChannel: Exception: com.android.internal.telephony.CommandException: GENERIC_FAILURE

11-18 12:47:40.594  11348-11367/? E/SIM1﹕ internalOpenLogicalChannel(aid): throw CardException

11-18 12:47:40.594  11348-11367/? E/SmartcardService ACE ARF﹕ Error opening logical channel open channel failed

11-18 12:47:40.794  11348-11367/? E/SmartcardService ACE ARF﹕ SIM1 rules not correctly initialized! [Parser] Cannot retreive type

11-18 12:47:40.794  11348-11367/? E/SmartcardService﹕ [Parser] Cannot retreive type

11-18 12:47:56.574    1397-3094/? E/BigDataLog﹕ java.lang.ArrayIndexOutOfBoundsException: length=8; index=-1

11-18 12:48:05.824      888-921/? E/GpsXtraDownloader﹕ No XTRA servers were specified in the GPS configuration

11-18 12:48:10.924  11521-11521/? E/DexLoadOat﹕ Success

11-18 12:48:11.084  11521-11521/? E/MSF.C.NativeConfigStore﹕ loadso arm msfbootV2 resultCode=3387394

11-18 12:48:11.084  11521-11521/? E/MSF.C.NativeConfigStore﹕ loadso msfbootV2 true resultCode=3387394 cost=17

11-18 12:48:11.314  11521-11521/? E/MSF.C.CodecWarpper﹕ loadso arm codecwrapperV2 resultCode=3387394

11-18 12:48:11.314  11521-11521/? E/MSF.C.CodecWarpper﹕ loadso codecwrapperV2 true resultCode=3387394 cost=24

11-18 12:48:11.454  11521-11521/? E/MD5﹕ loadso arm msfbootV2 resultCode=3387394

11-18 12:48:11.454  11521-11521/? E/MD5﹕ loadso msfbootV2 true resultCode=3387394 cost=1

11-18 12:48:13.784  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_927547EC5A34E1607BB6B37F1C641A0F_New

11-18 12:48:13.784  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_7C6F7F47EDA1BFF2E3D3C8850C1E752B_New

11-18 12:48:13.784  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_0C5C95957142DF887AA69CF7D0F23777_New

11-18 12:48:13.784  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_C363B876F806F58A89F193C154366C5A_New

11-18 12:48:13.784  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_E663CBF15481D9C1AE0B4941C003DA6F_New

11-18 12:48:13.794  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_C7EA5EB77A230A6FB8EF8E39C56D9E8A_New

11-18 12:48:13.804  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_C6D29E83D9F0FCA7E490D765A7EBEC36_New

11-18 12:48:13.804  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_69B8F0478203E8F8A8337738A64EED7C_New

11-18 12:48:13.804  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_5EA9BF89960EA7F0940CF27FBD08DDE8_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_992482D38A8D86A50D20A18AFC50ACD6_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_B3E306996F17893FC0BB2D9E5D307063_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_51AE7FF892C8DC611E75D5EF6C64558E_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_F6343732F152525A2180D4FD8DB5C4F4_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_E8C5C8068035FA819284F1FC135CF81C_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_9FF86814DCD7E0076AD4471DB821C30B_New

11-18 12:48:13.814  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_93798A979206DECB44098F0DB5B0A24D_New

11-18 12:48:13.824  16214-11591/? E/SQLiteLog﹕ (1) no such table: mr_troop_455086D812174355FFD1F5684EF06C26_New

11-18 12:48:13.964  11521-11543/? E/mqq﹕ waitInit when empty:

    java.lang.RuntimeException:

            at mqq.app.MobileQQ.waitAppRuntime(MobileQQ.java:853)

            at com.tencent.common.app.BaseApplicationImpl.getRuntime(ProGuard:170)

            at com.tencent.mobileqq.app.DeviceProfileManager.a(ProGuard:282)

            at com.tencent.mobileqq.statistics.battery.BatteryStatsImpl.a(ProGuard:219)

            at com.tencent.mobileqq.statistics.battery.BatteryStatsImpl.a(ProGuard:150)

            at agnu.run(ProGuard:79)

            at mqq.os.MqqHandler.handleCallback(MqqHandler.java:331)

            at mqq.os.MqqHandler.dispatchMessage(MqqHandler.java:97)

            at mqq.os.MqqHandler$NativeHandler.dispatchMessage(MqqHandler.java:344)

            at android.os.Looper.loop(Looper.java:135)

            at android.os.HandlerThread.run(HandlerThread.java:61)

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_get_profile_list: profile technology sent 0

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_umts_common_profile_tlvs: ignoring unknown TLV type=3f

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_umts_common_profile_tlvs: ignoring unknown TLV type=3e

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_umts_common_profile_tlvs: ignoring unknown TLV type=3d

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_get_profile_list: profile technology sent 1

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c3

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c2

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c1

11-18 12:48:14.154      273-569/? E/QC-QMI﹕ qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c0

11-18 12:48:14.164      273-569/? E/QC-QMI﹕ qmi_wds_route_look_up: unknown response TLV type = 11

11-18 12:48:15.904  16214-16333/? E/SQLiteLog﹕ (1) no such table: ContactMatch

11-18 12:48:15.904  16214-16333/? E/SQLiteLog﹕ (1) no such table: ContactBinded

11-18 12:48:16.064      503-503/? E/QMI_FW﹕ open_lookup_sock_fd: Lookup sock fd creation failed

11-18 12:48:16.064      503-503/? E/QMI_FW﹕ xport_open: socket creation failed - 13

11-18 12:48:16.064      503-503/? E/QC-QMI﹕ qmi_client_init_instance() error -1

11-18 12:48:16.284      503-503/? E/QMI_FW﹕ open_lookup_sock_fd: Lookup sock fd creation failed

11-18 12:48:16.284      503-503/? E/QMI_FW﹕ xport_open: socket creation failed - 13

11-18 12:48:16.284      503-503/? E/QC-QMI﹕ qmi_client_init_instance() error -1

11-18 12:48:16.304  11691-11720/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87ABBF0(STAT_DATA_ID)

11-18 12:48:16.304  11691-11720/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B87ADB60(STAT_DATA_ID)

11-18 12:48:16.494  11691-11720/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B86F9688(STAT_DATA_ID)

11-18 12:48:16.494  11691-11720/? E/SQLiteLog﹕ (284) automatic index on sqlite_sq_B86FA268(STAT_DATA_ID)

11-18 12:48:16.854     888-1689/? E/LocSvc_eng﹕ W/AgpsReleasedState: unrecognized event 3

11-18 12:49:12.004    7573-7575/? E/QC-QMI﹕ qmi_client [7573] 184: failed to locate client data

11-18 12:49:12.004      394-394/? E/QC-QMI﹕ qmuxd: RX on fd=21 returned error=0 errno[2:No such file or directory]

11-18 12:49:12.004      394-394/? E/QC-QMI﹕ QMUX qmux_client_id=184 not found in qmux client list, unable to remove

11-18 12:49:12.574      273-578/? E/QC-time-services﹕ Receive Passed == base = 12, unit = 1, operation = 0, result = 0

11-18 12:49:12.574      307-520/? E/QC-time-services﹕ Daemon: Time-services: Waiting to acceptconnection

11-18 12:49:12.584      273-578/? E/QC-time-services﹕ Receive Passed == base = 13, unit = 1, operation = 0, result = 0

11-18 12:49:12.594      307-520/? E/QC-time-services﹕ Daemon:
...全文
425 1 打赏 收藏 转发到动态 举报
写回复
用AI写文章
1 条回复
切换为时间正序
请发表友善的回复…
发表回复
usecf 2018-11-20
  • 打赏
  • 举报
 回复
重新抓下log 在你的log中搜索fatal关键字 看看有什么异常信息
Android软件开发之程序中时时获取logcat日志信息
雨松MOMO带你做软件 Android软件开发之程序中时时获取logcat日志信息 黄英大家下载阅读 哇咔咔~~
2021-11-12 Android adb logcat 查看 app 闪退崩溃crash的信息方法，“-s“选项 和 *:S ＜tag＞，adb logcat -s AndroidRuntime。
一、我这里开机后settings会clash，我想知道这部分的错误log。 二、如果直接adb logcat，也是可以打出这个信息，但是很难找到这个信息，输出的log太多了。 三、那如何过滤掉那么多无用的信息，只看到clash信息呢？ 1、"-s"选项 : 设置输出日志的标签, 只显示该标签的日志; 2、*:S <tag>' prints only <tag>, '<tag>:S' suppresses all <tag&g...
华为的手机usb调试，闪退后logCat日志被瞬间清空 。
新买了个华为的P7！ 开发平台是androidstudio，如果app程序闪退，logcat会出现错误日志，但是华为的机器遇到闪退会立马重启APP（而有的机器是出现XXXAPP已停止运行日志会停在错误处），但华为重启了APP日志就马上会被清空，然后重新开始打印新日志（我要看错误日志啊NND给我清空重新开始！）。 so：错误日志立马就没了。 大神们help！ 我现在解决方案是闪退时候
快速定位Android闪退问题的方法
写Android程序时，经常会遇到各种各样的问题导致应用闪退。下面就来总结下应用闪退时，我们有什么方法去定位问题。首先我们应该用 adb logcat -v time 命令把日志打印出来，直接用AS的logcat也可以，只是有的时候logcat会出现清空日志的情况，还是adb命令的日志靠谱。有了日志，可以通过查找以下几个字段来快速定位问题： Exception：查看所有发生异常的地方，看看是不是有没
安卓app一运行就闪退，logcat，提示“应用过期”，求大神解答
logcat提示信息如下： 05-12 01:00:10.383: E/AndroidRuntime(11330): FATAL EXCEPTION: main 05-12 01:00:10.383: E/AndroidRuntime(11330): Process: com.mm.mealapp.activity, PID: 11330 05-12 01:00:10.383: E/Andr
Android

80,359

社区成员

91,290

社区内容

发帖
与我相关
我的任务
社区描述
移动平台 Android
androidandroid-studioandroidx 技术论坛（原bbs）
社区管理员
  • Android
  • yechaoa
  • 失落夏天
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章