Appcrash about zxing HOT 3 CLOSED

Thank you, I see a couple of these each week. It means that the device is not sending back the amount of data it says it will according to its preview size. You can show the logs from the application initialization too, and I bet dollars to donuts the previous size will not be consistent with a preview frame of 460800 bytes. If that's the case, it's just a device bug. The workaround might be to hack the app for the device, but it wouldn't be an app problem. If you think it's an app problem, a patch would be welcome.

from zxing.

I do not think it is only a device bug due to the fact that the previous version(4.5.2) worked without any problem.
If there is any free time i will try to find the problem. Any suggestions where to look?

from zxing.

Here is generally what happens: device says it supports X. App sets X.
Device does not actually support X and fails to init the camera. Its
preview size among other things revert to some default that does not match
the configuration it reports.

The previous version didn't set X, and provides a way to disable X.

What you want to do is comment out camera configuration until it works in
CameraCOnfiguration.java

On Thu, Feb 13, 2014 at 8:46 PM, Georg Semmler [email protected]:

I do not think it is only a device bug due to the fact that the previous
version(4.5.2) worked without any problem.
If there is any free time i will try to find the problem. Any suggestions
where to look?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/56#issuecomment-35023869
.

from zxing.