android:我没有得到堆栈跟踪，电话只是挂起-6ren

android:我没有得到堆栈跟踪，电话只是挂起

转载作者：塔克拉玛干更新时间：2023-11-01 21:32:31

我暂停我的相机应用程序，然后切换回来拍照后，我的手机崩溃了。这只发生在我的三星 Galaxy S 上，在我的华为设备上它完全有效。我找到了导致错误的代码行。不幸的是，这些行非常有用，所以我不能删除它们:

public void surfaceDestroyed(SurfaceHolder holder) { // <14>
        Log.d(TAG,"surfaceDestroyed()");
        if(this.camera != null){
            camera.stopPreview();
            // the next two lines lead to the error after switching back to the app and taking a picure
            camera.release();
            this.camera = null;
        }
    }

不幸的是我没有得到堆栈跟踪。我得到的是:

12-17 12:45:01.609: ERROR/SecCamera(10857): cancelAutofocus() end, 0, 2
12-17 12:45:01.613: ERROR/SecCamera(10857): stopPreview()
12-17 12:45:01.613: ERROR/SecCamera(10857): fimc_v4l2_streamoff()
12-17 12:45:01.644: ERROR/CameraHardwareSec(10857): stopPreview() end
12-17 12:45:01.644: INFO/ShotSingle(10857): ShotSingle::takePicture end
12-17 12:45:01.644: DEBUG/SecCamera(10857): passed fmt = 1498831189 found pixel format[3]: YUV 4:2:2 packed, CbYCrY
12-17 12:45:01.695: WARN/CameraService(10857): width(800), height(480), format:jpeg
12-17 12:45:02.433: ERROR/SecCamera(10857): fimc_v4l2_streamoff()
12-17 12:45:02.793: INFO/DEBUG(2359): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-17 12:45:02.793: INFO/DEBUG(2359): Build fingerprint: 'samsung/GT-I9000/GT-I9000/GT-I9000:2.2/FROYO/NEJP5:user/release-keys'
12-17 12:45:02.793: INFO/DEBUG(2359): pid: 10857, tid: 11062  >>> /system/bin/mediaserver <<<
12-17 12:45:02.793: INFO/DEBUG(2359): signal 11 (SIGSEGV), fault addr 40b06000
12-17 12:45:02.797: INFO/DEBUG(2359):  r0 40b06000  r1 41043a40  r2 00024780  r3 00000000
12-17 12:45:02.797: INFO/DEBUG(2359):  r4 0002c5c0  r5 0000001c  r6 40d2c000  r7 00280a00
12-17 12:45:02.801: INFO/DEBUG(2359):  r8 00100000  r9 a811c479  10 40c2c000  fp 0002cbe0
12-17 12:45:02.801: INFO/DEBUG(2359):  ip a7913644  sp 40d2be60  lr a790d12b  pc afd0f4a8  cpsr 20000010
12-17 12:45:02.805: INFO/DEBUG(2359):  d0  643a64696f72646e  d1  6472656767756265
12-17 12:45:02.808: INFO/DEBUG(2359):  d2  6c8d6b716a8c6871  d3  678c6a71688d6a71
12-17 12:45:02.808: INFO/DEBUG(2359):  d4  668d6871698d6872  d5  678d6671648d6771
12-17 12:45:02.808: INFO/DEBUG(2359):  d6  648d6771668d6571  d7  638d6371658d6672
12-17 12:45:02.812: INFO/DEBUG(2359):  d8  0000000000000000  d9  0000000000000000
12-17 12:45:02.816: INFO/DEBUG(2359):  d10 0000000000000000  d11 0000000000000000
12-17 12:45:02.816: INFO/DEBUG(2359):  d12 0000000000000000  d13 0000000000000000
12-17 12:45:02.816: INFO/DEBUG(2359):  d14 0000000000000000  d15 0000000000000000
12-17 12:45:02.820: INFO/DEBUG(2359):  d16 417cd6d008000000  d17 3fe0000000000000
12-17 12:45:02.820: INFO/DEBUG(2359):  d18 3fe0000000000000  d19 3fe0000001312d00
12-17 12:45:02.824: INFO/DEBUG(2359):  d20 3f1153cbde08ad39  d21 bebbb90e9e9bc9e2
12-17 12:45:02.824: INFO/DEBUG(2359):  d22 3ff0000000000000  d23 3feb70bba144e0a7
12-17 12:45:02.828: INFO/DEBUG(2359):  d24 3e66376972bea4d0  d25 0000000000000000
12-17 12:45:02.828: INFO/DEBUG(2359):  d26 0000000000000000  d27 0000000000000000
12-17 12:45:02.832: INFO/DEBUG(2359):  d28 0000000000000000  d29 0000000000000000
12-17 12:45:02.836: INFO/DEBUG(2359):  d30 0000000000000000  d31 0000000000000000
12-17 12:45:02.836: INFO/DEBUG(2359):  scr 20000010
12-17 12:45:03.187: INFO/DEBUG(2359):          #00  pc 0000f4a8  /system/lib/libc.so
12-17 12:45:03.187: INFO/DEBUG(2359):          #01  pc 0000d128  /system/lib/libcamera.so
12-17 12:45:03.187: INFO/DEBUG(2359):          #02  pc 0000d2b2  /system/lib/libcamera.so
12-17 12:45:03.191: INFO/DEBUG(2359):          #03  pc 0001c4e0  /system/lib/libutils.so
12-17 12:45:03.191: INFO/DEBUG(2359):          #04  pc 000111b0  /system/lib/libc.so
12-17 12:45:03.191: INFO/DEBUG(2359):          #05  pc 00010ca0  /system/lib/libc.so
12-17 12:45:03.191: INFO/DEBUG(2359): code around pc:
12-17 12:45:03.191: INFO/DEBUG(2359): afd0f488 3a000009 f5d1f080 f5d1f0c0 f5d1f100 
12-17 12:45:03.191: INFO/DEBUG(2359): afd0f498 f421020d f421420d f5d1f100 e2522040 
12-17 12:45:03.191: INFO/DEBUG(2359): afd0f4a8 f400022d f400422d 2afffff8 e2822040 
12-17 12:45:03.191: INFO/DEBUG(2359): afd0f4b8 e2522020 3a000003 f421020d e2522020 
12-17 12:45:03.191: INFO/DEBUG(2359): afd0f4c8 f400022d 2afffffb e2822020 e3120010 
12-17 12:45:03.191: INFO/DEBUG(2359): code around lr:
12-17 12:45:03.191: INFO/DEBUG(2359): a790d108 fdd6f7f9 b1664607 f8d16a61 f85ee000 
12-17 12:45:03.195: INFO/DEBUG(2359): a790d118 19485c0c fe5ef7fd f8d419f1 f7f920b4 
12-17 12:45:03.195: INFO/DEBUG(2359): a790d128 f8d4ea9e ad0a3090 4628a910 f7fd9300 
12-17 12:45:03.195: INFO/DEBUG(2359): a790d138 2080ff5d f8d44629 f8dd2098 47e0c000 
12-17 12:45:03.195: INFO/DEBUG(2359): a790d148 f7fd4628 f8d4ff6f f012209c d0510f40 
12-17 12:45:03.195: INFO/DEBUG(2359): stack:
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be20  a791384c  /system/lib/libcamera.so
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be24  a79135f8  /system/lib/libcamera.so
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be28  a791384c  /system/lib/libcamera.so
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be2c  00000000  
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be30  00000000  
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be34  a790937f  /system/lib/libcamera.so
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be38  00000013  
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be3c  80e0a329  /system/lib/libseccameraadaptor.so
12-17 12:45:03.195: INFO/DEBUG(2359):     40d2be40  40d2c000  /dev/video0
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be44  40d2be94  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be48  00000000  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be4c  4eec80bd  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be50  00000000  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be54  0002c5c0  [heap]
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be58  df002777  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be5c  e3a070ad  
12-17 12:45:03.199: INFO/DEBUG(2359): #00 40d2be60  40a6f000  /dev/ashmem/MemoryHeapBase (deleted)
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be64  a790d12b  /system/lib/libcamera.so
12-17 12:45:03.199: INFO/DEBUG(2359): #01 40d2be68  0003d9d0  [heap]
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be6c  00000000  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be70  00000000  
12-17 12:45:03.199: INFO/DEBUG(2359):     40d2be74  afd10560  /system/lib/libc.so
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be78  00000000  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be7c  afd10560  /system/lib/libc.so
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be80  afd4372c  /system/lib/libc.so
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be84  afd43768  /system/lib/libc.so
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be88  0002cbd8  [heap]
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be8c  0002cc10  [heap]
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be90  00100000  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be94  42884a00  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be98  00000600  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2be9c  00000a00  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2bea0  00780000  
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2bea4  0003e804  [heap]
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2bea8  0003d9d0  [heap]
12-17 12:45:03.203: INFO/DEBUG(2359):     40d2beac  001422e2  
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2beb0  0002c5c0  [heap]
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2beb4  0002cbf8  [heap]
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2beb8  0002c5c0  [heap]
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2bebc  a790d2b1  /system/lib/libcamera.so
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2bec0  00000000  
12-17 12:45:03.207: INFO/DEBUG(2359):     40d2bec4  a790d2b7  /system/lib/libcamera.so
12-17 12:45:03.715: WARN/PowerManagerService(2474): Timer 0x3->0x3|0x3
12-17 12:45:04.543: INFO/DEBUG(2359): dumpmesg > /data/log/dumpstate_app_native.log
12-17 12:45:05.492: INFO/BootReceiver(2474): Copying /data/tombstones/tombstone_08 to DropBox (SYSTEM_TOMBSTONE)
12-17 12:45:05.586: INFO/dumpstate(11064): begin
12-17 12:45:06.562: INFO/dalvikvm(2474): threadid=3: reacting to signal 3
12-17 12:45:06.687: INFO/dalvikvm(2474): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:06.765: INFO/dalvikvm(2551): threadid=3: reacting to signal 3
12-17 12:45:06.773: INFO/dalvikvm(2551): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:06.966: INFO/dalvikvm(2559): threadid=3: reacting to signal 3
12-17 12:45:07.160: INFO/dalvikvm(2560): threadid=3: reacting to signal 3
12-17 12:45:07.199: INFO/dalvikvm(2960): threadid=3: reacting to signal 3
12-17 12:45:07.403: INFO/dalvikvm(3479): threadid=3: reacting to signal 3
12-17 12:45:07.519: INFO/dalvikvm(2560): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:07.551: INFO/dalvikvm(3871): threadid=3: reacting to signal 3
12-17 12:45:07.578: ERROR/dalvikvm(3871): Failed to write stack traces to /data/anr/traces.txt (182 of 3588): Interrupted system call
12-17 12:45:07.617: INFO/dalvikvm(3479): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:07.629: INFO/dalvikvm(2559): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:07.754: INFO/dalvikvm(5446): threadid=3: reacting to signal 3
12-17 12:45:07.769: INFO/dalvikvm(5446): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:07.937: INFO/dalvikvm(9448): threadid=3: reacting to signal 3
12-17 12:45:07.961: INFO/dalvikvm(9448): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.139: INFO/dalvikvm(9873): threadid=3: reacting to signal 3
12-17 12:45:08.152: INFO/dalvikvm(9873): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.238: INFO/dalvikvm(9907): threadid=3: reacting to signal 3
12-17 12:45:08.250: INFO/dalvikvm(9907): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.437: INFO/dalvikvm(10061): threadid=3: reacting to signal 3
12-17 12:45:08.488: INFO/dalvikvm(10365): threadid=3: reacting to signal 3
12-17 12:45:08.504: INFO/dalvikvm(10414): threadid=3: reacting to signal 3
12-17 12:45:08.504: INFO/dalvikvm(10499): threadid=3: reacting to signal 3
12-17 12:45:08.512: INFO/dalvikvm(10658): threadid=3: reacting to signal 3
12-17 12:45:08.512: INFO/dalvikvm(10672): threadid=3: reacting to signal 3
12-17 12:45:08.590: INFO/dalvikvm(10658): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.594: ERROR/dalvikvm(10672): Failed to write stack traces to /data/anr/traces.txt (1797 of 2305): Unknown error: 0
12-17 12:45:08.605: INFO/dalvikvm(10682): threadid=3: reacting to signal 3
12-17 12:45:08.613: ERROR/dalvikvm(10499): Failed to write stack traces to /data/anr/traces.txt (-1 of 3362): Math result not representable
12-17 12:45:08.613: ERROR/dalvikvm(10365): Failed to write stack traces to /data/anr/traces.txt (-1 of 2832): Math result not representable
12-17 12:45:08.625: INFO/dalvikvm(10731): threadid=3: reacting to signal 3
12-17 12:45:08.633: INFO/dalvikvm(10751): threadid=3: reacting to signal 3
12-17 12:45:08.640: INFO/dalvikvm(10770): threadid=3: reacting to signal 3
12-17 12:45:08.660: INFO/dalvikvm(10751): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.664: INFO/dalvikvm(10682): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.695: INFO/dalvikvm(10848): threadid=3: reacting to signal 3
12-17 12:45:08.707: INFO/dalvikvm(10061): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:08.897: INFO/dalvikvm(10924): threadid=3: reacting to signal 3
12-17 12:45:08.957: ERROR/dalvikvm(2960): Failed to write stack traces to /data/anr/traces.txt (682 of 19532): Interrupted system call
12-17 12:45:08.976: INFO/dalvikvm(10977): threadid=3: reacting to signal 3
12-17 12:45:09.004: ERROR/dalvikvm(10848): Failed to write stack traces to /data/anr/traces.txt (-1 of 3867): Math result not representable
12-17 12:45:09.015: INFO/dalvikvm(10924): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.040: INFO/dalvikvm(10770): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.043: INFO/dalvikvm(10983): threadid=3: reacting to signal 3
12-17 12:45:09.242: INFO/dalvikvm(10993): threadid=3: reacting to signal 3
12-17 12:45:09.275: ERROR/dalvikvm(10731): Failed to write stack traces to /data/anr/traces.txt (1108 of 4586): Unknown error: 0
12-17 12:45:09.275: INFO/dalvikvm(10977): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.277: INFO/dalvikvm(10983): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.281: ERROR/dalvikvm(10414): Failed to write stack traces to /data/anr/traces.txt (3626 of 7207): Unknown error: 0
12-17 12:45:09.293: INFO/dalvikvm(11009): threadid=3: reacting to signal 3
12-17 12:45:09.305: ERROR/dalvikvm(10993): Failed to write stack traces to /data/anr/traces.txt (-1 of 3504): Math result not representable
12-17 12:45:09.312: INFO/dalvikvm(11022): threadid=3: reacting to signal 3
12-17 12:45:09.336: INFO/dalvikvm(11009): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.351: INFO/dalvikvm(11036): threadid=3: reacting to signal 3
12-17 12:45:09.355: ERROR/dalvikvm(11022): Failed to write stack traces to /data/anr/traces.txt (1821 of 2769): Unknown error: 0
12-17 12:45:09.363: INFO/dalvikvm(11036): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:09.601: INFO/dalvikvm(11052): threadid=3: reacting to signal 3
12-17 12:45:09.871: INFO/dalvikvm(11052): Wrote stack traces to '/data/anr/traces.txt'
12-17 12:45:13.847: DEBUG/BatteryService(2474): update start
12-17 12:45:13.871: DEBUG/BatteryService(2474): updateBattery level:99 scale:100 status:2 health:2 present:true voltage: 4241 temperature: 390 technology: Li-ion AC powered:false USB powered:true icon:17302171
12-17 12:45:13.902: INFO/StatusBarPolicy(2474): BAT. status:2 health:2
12-17 12:45:23.715: WARN/PowerManagerService(2474): Timer 0x3->0x1|0x3
12-17 12:45:25.176: DEBUG/dalvikvm(3479): GC_EXPLICIT freed 21585 objects / 1426712 bytes in 405ms
12-17 12:45:30.716: WARN/PowerManagerService(2474): Timer 0x3->0x0|0x3
12-17 12:45:30.716: ERROR/PowerManagerService(2474): CurLock p:3 mPS:3
12-17 12:45:30.716: WARN/PowerManagerService(2474): type=SCREEN_DIM_WAKE_LOCK           'StayOnWhilePluggedIn Screen Dim' active (minState=1) activeT=686112
12-17 12:45:30.716: WARN/PowerManagerService(2474): type=PARTIAL_WAKE_LOCK              'StayOnWhilePluggedIn Partial' active (minState=0) activeT=686112
12-17 12:45:30.716: WARN/PowerManagerService(2474): type=SCREEN_BRIGHT_WAKE_LOCK        'KEEP_SCREEN_ON_FLAG' active (minState=3) activeT=32085
12-17 12:45:35.429: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doSetCircleMembership
12-17 12:45:35.429: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.429: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x006f
12-17 12:45:35.429: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doSetCircleMembership
12-17 12:45:35.429: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.429: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x007f
12-17 12:45:35.441: DEBUG/dalvikvm(10848): VFY: dead code 0x0072-0072 in Lcom/google/android/apps/plus/service/EsService;.doSetCircleMembership (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;[Ljava/lang/String;)V
12-17 12:45:35.441: DEBUG/dalvikvm(10848): VFY: dead code 0x0082-0082 in Lcom/google/android/apps/plus/service/EsService;.doSetCircleMembership (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;[Ljava/lang/String;)V
12-17 12:45:35.777: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.removePersonFromAllCircles
12-17 12:45:35.777: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.777: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x001d
12-17 12:45:35.785: DEBUG/dalvikvm(10848): VFY: dead code 0x0020-0020 in Lcom/google/android/apps/plus/service/EsService;.removePersonFromAllCircles (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Ljava/lang/String;)V
12-17 12:45:35.808: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doDeleteCircles
12-17 12:45:35.808: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.808: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x001d
12-17 12:45:35.808: DEBUG/dalvikvm(10848): VFY: dead code 0x0020-0020 in Lcom/google/android/apps/plus/service/EsService;.doDeleteCircles (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Ljava/util/ArrayList;Landroid/content/Intent;)V
12-17 12:45:35.812: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doDismissSuggestedPeople
12-17 12:45:35.812: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.812: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x0032
12-17 12:45:35.816: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doDismissSuggestedPeople
12-17 12:45:35.816: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.820: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x006f
12-17 12:45:35.824: DEBUG/dalvikvm(10848): VFY: dead code 0x0035-0035 in Lcom/google/android/apps/plus/service/EsService;.doDismissSuggestedPeople (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Landroid/content/Intent;)V
12-17 12:45:35.824: DEBUG/dalvikvm(10848): VFY: dead code 0x0072-0072 in Lcom/google/android/apps/plus/service/EsService;.doDismissSuggestedPeople (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Landroid/content/Intent;)V
12-17 12:45:35.824: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doReportAbuse
12-17 12:45:35.828: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.828: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x0029
12-17 12:45:35.832: DEBUG/dalvikvm(10848): VFY: dead code 0x002c-002c in Lcom/google/android/apps/plus/service/EsService;.doReportAbuse (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Landroid/content/Intent;)V
12-17 12:45:35.836: INFO/dalvikvm(10848): Could not find method java.io.IOException.<init>, referenced from method com.google.android.apps.plus.service.EsService.doSetPersonBlocked
12-17 12:45:35.836: WARN/dalvikvm(10848): VFY: unable to resolve direct method 40914: Ljava/io/IOException;.<init> (Ljava/lang/String;Ljava/lang/Throwable;)V
12-17 12:45:35.836: DEBUG/dalvikvm(10848): VFY: replacing opcode 0x70 at 0x002e
12-17 12:45:35.840: DEBUG/dalvikvm(10848): VFY: dead code 0x0031-0031 in Lcom/google/android/apps/plus/service/EsService;.doSetPersonBlocked (Landroid/content/Context;Lcom/google/android/apps/plus/content/EsAccount;Landroid/content/Intent;)V
12-17 12:45:41.070: VERBOSE/PicasaContentProvider(10848): querySettings: defaults: {video_upload_wifi_only=1, sync_on_wifi_only=1, auto_upload_account_type=null, sync_on_battery=1, sync_on_roaming=0, auto_upload_enabled=0, auto_upload_account_name=null}
12-17 12:45:43.847: DEBUG/BatteryService(2474): update start
12-17 12:45:43.867: DEBUG/BatteryService(2474): updateBattery level:100 scale:100 status:2 health:2 present:true voltage: 4241 temperature: 390 technology: Li-ion AC powered:false USB powered:true icon:17302171
12-17 12:45:43.922: INFO/StatusBarPolicy(2474): BAT. status:2 health:2
12-17 12:45:43.976: DEBUG/VoldCmdListener(2356): asec list
12-17 12:45:43.980: DEBUG/VoldCmdListener(2356): CommandListener::AsecCmd::runCommand -> org.piwik.mobile-2 
12-17 12:45:43.980: DEBUG/VoldCmdListener(2356): CommandListener::AsecCmd::runCommand -> la.droid.qr-1 
12-17 12:45:43.980: DEBUG/VoldCmdListener(2356): CommandListener::AsecCmd::runCommand -> com.picsart.studio-2 
12-17 12:45:43.980: DEBUG/VoldCmdListener(2356): CommandListener::AsecCmd::runCommand -> com.vtcreator.android360-1 
12-17 12:45:49.639: INFO/dumpstate(11064): done
12-17 12:45:49.816: WARN/AudioSystem(2474): AudioFlinger server died!
12-17 12:45:49.820: INFO/ServiceManager(2355): service 'media.audio_flinger' died
12-17 12:45:49.820: INFO/ServiceManager(2355): service 'media.player' died
12-17 12:45:49.820: INFO/ServiceManager(2355): service 'media.camera' died
12-17 12:45:49.820: INFO/ServiceManager(2355): service 'media.audio_policy' died
12-17 12:45:49.820: WARN/Camera(11022): Camera server died!
12-17 12:45:49.820: WARN/Camera(11022): ICamera died
12-17 12:45:49.820: ERROR/Camera(11022): Error 100
12-17 12:45:49.820: WARN/AudioSystem(2474): AudioPolicyService server died!
... and some further lines - will post them if you need them

有人知道如何解决这个问题吗？

最佳答案

我终于(经过几个小时，几乎几天的调试)通过删除预览 View 并重新实例化它解决了这个问题:

    @Override
    protected void onResume() {
        super.onResume();
        mSurfaceViewContainer.removeAllViews();
        mSurfaceView = new SurfaceView(mSurfaceViewContainer.getContext());
        mSurfaceViewContainer.addView(mSurfaceView, new FrameLayout.LayoutParams(ViewGroup.LayoutParams.MATCH_PARENT, ViewGroup.LayoutParams.MATCH_PARENT));

        SurfaceHolder previewHolder = mSurfaceView.getHolder();
        previewHolder.setType(SurfaceHolder.SURFACE_TYPE_PUSH_BUFFERS);
        previewHolder.addCallback(mSurfaceHolderCallback);
    }

关于android:我没有得到堆栈跟踪，电话只是挂起，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/8481402/

文章推荐： android - 如何编辑 Android strings.xml 文件中的多行字符串？

文章推荐： java - 在 Spring Data JPA 中创建分页

文章推荐： ios - 如何为 Branch.io 中的链接配置自定义域

文章推荐： java - 在 Java 中执行简单异步任务的最佳方式？

Javascript 表单验证(电话)
我有一个包含姓名、电子邮件和内容文本区域的表单。一切正常，但当我尝试为手机号码添加 1 个表单输入时，表单不会提交。 Javascript: function hgsubmit() { i
计划，电话/抄送
所以我正试图在 Scheme 中找出整个 call/cc 的东西。下面是我正在使用的代码: (+ 1 (call/cc (lambda (k) (if (number? k)
计划，电话/抄送
所以我正试图在 Scheme 中找出整个 call/cc 的东西。下面是我正在使用的代码: (+ 1 (call/cc (lambda (k) (if (number? k)
java - 平板电脑可以打电话吗？ (电话)
我在 list 中有权限: 检查电话是否正在使用的代码可能会为无法接听电话的平板电脑等设备启动安全异常。所以，我制作了这个方法来检查是否设备可以使用 TelephonyManager: priva
php - Facebook社交登录获取用户名、邮箱、电话
我想知道 facebook API 允许 PHP 网页提取以下用户数据的先决条件是什么: 姓名电子邮件电话据我了解，提取电话号码需要您的网站在 facebook/Websense 的白名单中吗？
iphone - 从我的应用程序中调用 iPhone 电话
我如何从我的应用程序调用特定号码的电话？给我一些执行此任务的逻辑或代码... 最佳答案使用 UIApplication 的 openURL: 方法: [[UIApplication sharedAp
uri - 电话 URI 中的加号是否应该编码？
在 URI 中，空格可以编码为 + .既然如此，那么在创建具有国际前缀的 tel URI 时是否应该对前导加号进行编码？哪个更好？两者在实践中都有效吗？ Call me Call me 最佳答案不
soap - 使用失眠症来打 SOAP 电话
我正在尝试使用 Insomnia 调用 SOAP 电话 - 特别是试图让帖子成功。我将 URL 定义为端点，并将正文类型作为带有 SOAP 内容(信封、标题、正文)的 XML。我在标题中定义了用户 I
networking - 是否可以在没有操作系统集成的情况下将数据从服务器推送到客户端(电话、计算机)
服务器有没有办法将一些数据无线无缝地推送到客户端，可能是 Windows(电话)、iPhone、Mac 或 Android 设备，没有任何操作系统集成？如果是这样，最好的设计模式是什么，最好的技术是
JavaScript Onclick 电话/电子邮件验证功能不起作用
我有一个搜索字段，我希望用户能够通过电话或电子邮件进行搜索。但是，我的 onclick 事件没有触发。我已经尝试过控制台工具，但似乎无法通过那里进行调试。 {% from "_form
websocket - 在新的弹出窗口中接听 Twilio 电话
如果重新加载接收调用的浏览器窗口，我将面临实时 Twilio 调用被丢弃的情况。有没有办法在不影响实时通话的情况下克服这种挫折？最佳答案 Twilio 布道者在这里。根据您的问题，我假设您使用的是
javascript - 在我的案例中如何解决我的 promise 电话
我试图在我的服务中减少我的 promise 对象。我有类似的东西 angular.module('myApp').service('testService', ['Employees','$q',
java - 如何调用 SIP 电话
我想在我的java应用程序中构建一个电话调用器。为此，我使用了 JAIN-SIP 库。第一次 INVITE 后，系统需要代理身份验证。第二个邀请是在“AuthenticationHelperImpl.
android - 电话 session 应用程序
两天前我正在开发一个 VOIP 应用程序，并成功地使用 Sinch 实现了一个普通的应用程序到应用程序调用。 .该应用程序运行良好。当我开始时，我在他们的文档中看到他们支持电话 session 。现
java - 驱动 Api 电话
我正在尝试创建一个 java 程序，它将创建 excel 文件并将其上传到谷歌驱动器中。上传后我需要它来授予权限。我已经完成了所有这些，但问题在于尝试将 excel 文件转换为 google 文件，以
Android SIP 电话 session
我想使用 Android Sip 进行电话 session .那可能吗？有人可以举一个有效的例子吗？使用该库是否有任何限制，比如它可以在 3G 或 4G 上工作？最佳答案当前的 Android S
java - 以编程方式接听 Android 电话
是否可以通过编程方式在 android 中接听电话？我发现有些地方不可能，但后来安装了应用程序 https://play.google.com/store/apps/details?id=com.a
javascript - 为什么我会收到未定义的 'children' 电话？
我试图在单击导航中的某个按钮后将一个类附加到 div。 $navButtons.on('click', navigationClick); // liseten to the navigation a
iphone - Monotouch 电话/通话状态？
在 Monotouch 中是否有任何方法可以读取电话或调用者服务的当前状态？我正在尝试寻找某种方式来读取通话是否处于事件状态或通话是否处于等待状态等。用谷歌搜索没有找到任何结果。希望运行一些代码
ios - 自动输入姓名/电话/电子邮件等
我可能正在搜索错误的内容，这可能解释了为什么我只能找到有关设置密码自动填充的信息。我正在寻找用户能够在应用程序中输入电子邮件、电话、名字和姓氏的功能，就像某些网站能够做到的那样，选项出现在键盘上方。

塔克拉玛干

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

android:我没有得到堆栈跟踪，电话只是挂起