使用zxing扫描二维码出现黑屏
来源:互联网 发布:福州南威软件java 编辑:程序博客网 时间:2024/06/08 05:56
最近在项目中遇到一个问题,使用zxing扫描二维码发现在一个设备上出现黑屏,然后通过调试定位问题
给出的日志是
04-22 14:51:42.492: D/(4999): Surface destroy: ANDROID_NATIVE_WINDOW_MAGIC04-22 14:51:53.862: D/LewaResources(5139): cookie name=/data/app/com.example.qr_codescan-2.apk04-22 14:51:53.902: D/(5139): Pixel Format : GGL_PIXEL_FORMAT_RGBA_888804-22 14:51:53.902: D/(5139): Updating FBO content dimensions04-22 14:51:54.112: D/CameraConfigurationManager(5139): Default preview format: 17/yuv420sp04-22 14:51:54.112: D/CameraConfigurationManager(5139): Screen resolution: Point(800, 1216)04-22 14:51:54.112: D/CameraConfigurationManager(5139): preview-size-values parameter: 1280x720,720x480,640x480,640x360,352x288,320x240,176x14404-22 14:51:54.112: W/CameraConfigurationManager(5139): screenResolution-size: 800:121604-22 14:51:54.112: D/CameraConfigurationManager(5139): Camera resolution: Point(800, 1216)04-22 14:51:54.112: D/CameraConfigurationManager(5139): Setting preview size: Point(720, 480)04-22 14:51:54.122: E/MipcaActivityCapture(5139): error04-22 14:51:54.122: E/MipcaActivityCapture(5139): java.lang.RuntimeException: setParameters failed04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.hardware.Camera.native_setParameters(Native Method)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.hardware.Camera.setParameters(Camera.java:1651)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.mining.app.zxing.camera.CameraConfigurationManager.setDesiredCameraParameters(CameraConfigurationManager.java:83)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.mining.app.zxing.camera.CameraManager.openDriver(CameraManager.java:130)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.example.qr_codescan.MipcaActivityCapture.initCamera(MipcaActivityCapture.java:135)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.example.qr_codescan.MipcaActivityCapture.surfaceCreated(MipcaActivityCapture.java:158)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.SurfaceView.updateWindow(SurfaceView.java:572)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.SurfaceView.access$000(SurfaceView.java:86)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.SurfaceView$3.onPreDraw(SurfaceView.java:175)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:975)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1867)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5600)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.Choreographer$CallbackRecord.run(Choreographer.java:771)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.Choreographer.doCallbacks(Choreographer.java:574)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.Choreographer.doFrame(Choreographer.java:544)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:757)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.os.Handler.handleCallback(Handler.java:733)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.os.Handler.dispatchMessage(Handler.java:95)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.os.Looper.loop(Looper.java:149)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at android.app.ActivityThread.main(ActivityThread.java:5045)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at java.lang.reflect.Method.invokeNative(Native Method)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at java.lang.reflect.Method.invoke(Method.java:515)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:805)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:621)04-22 14:51:54.122: E/MipcaActivityCapture(5139): at dalvik.system.NativeStart.main(Native Method)04-22 14:51:54.132: I/dalvikvm(5139): Total arena pages for JIT: 1104-22 14:51:54.132: I/dalvikvm(5139): Total arena pages for JIT: 1204-22 14:51:54.132: I/dalvikvm(5139): Total arena pages for JIT: 1304-22 14:51:54.132: I/dalvikvm(5139): Total arena pages for JIT: 1404-22 14:51:54.142: D/CameraManager(5139): Calculated framing rect: Rect(160, 428 - 640, 788)04-22 14:51:54.142: I/dalvikvm(5139): Total arena pages for JIT: 1504-22 14:51:54.152: D/zhangxianjia(5139): init runded corner04-22 14:51:54.252: D/(5139): Surface destroy: ANDROID_NATIVE_WINDOW_MAGIC
然后思考是不是设置的 preview-size有问题 ,后来测试发现并没有问题
最后试着去掉
然后问题就解决,猜测可能是这个设备对底层做工处理。
以上只是目前的一种解决办法,但肯定不是最好的,有空还是会继续研究一下!
0 0
- 使用zxing扫描二维码出现黑屏
- 关于使用ZXing扫描二维码出现中文乱码的问题
- 关于使用ZXing扫描二维码出现中文乱码的问题
- 使用ZXing实现二维码扫描
- 使用ZXing实现二维码扫描
- 使用ZXing实现二维码扫描
- 使用ZXing实现二维码扫描
- 使用ZXing实现二维码扫描
- 使用ZXing扫描二维码和生成二维码
- Zxing扫描二维码返回键黑屏处理c
- ZXing扫描二维码在iphone中的使用
- zxing 二维码扫描 配置和使用
- 二维码扫描第三库ZXing的使用
- 二维码扫描:ZBar,ZXing的使用
- 二维码扫描:ZBar,ZXing的使用
- 使用ZXing扫描条形码和二维码
- 使用Zxing实现Android二维码扫描
- android 二维码扫描(zxing使用小结)
- Reverse Linked List II
- hdu题目分类
- quick-cocos2d-x游戏开发【4】——添加文本
- HDU 5206
- quick-cocos2d-x游戏开发【5】——创建菜单
- 使用zxing扫描二维码出现黑屏
- SYN Flood和SYN cookie
- C++如何设置默认堆栈的大小
- leetcode 日经贴,Cpp code -Linked List Cycle II
- 发布企业版应用遇到“无法安装应用程序,证书无效”、“无法下载应用程序,此时无法安装”
- C/C++ 字符串输入输出
- 逆向分析之花指令2
- ArcGIS拓扑检查步骤与修正拓扑错误技巧
- 【Shadow DOM】 渲染与隔离