Open GoogleCodeExporter opened 9 years ago
Can you try if the ZXing Barcode Scanner works for you? This is the one I
originally used for Bitcoin Wallet. Does it make a difference if you tick or
untick the setting "No continuous focus" in ZXing?
Original comment by andreas....@gmail.com
on 15 Dec 2013 at 10:06
I just tried ZXing Barcode Scanner. There is no difference. I manipulated the
"continuous focus" setting, also the "use auto focus", "1D Barcodes", and
"Invert scan" settings, in every permutation.
It fails to successfully scan the code, and the focus continues to refocus
every second or so.
Original comment by adammack...@gmail.com
on 15 Dec 2013 at 10:58
Just out of curiosity, did you try other (non-Bitcoin) QR codes?
I suggest filing an issue with ZXing and see what they say. If they fix the
problem I can probably just apply the same patch. I'll keep this issue open as
a reminder.
As a workaround, try using one of the scanners that work and see if they handle
opening bitcoin URIs properly. Bitcoin Wallet accepts URIs from other apps.
Original comment by andreas....@gmail.com
on 15 Dec 2013 at 11:07
I have filed issue zxing issue 1822:
https://code.google.com/p/zxing/issues/detail?id=1822
Per your suggestion I've tested with ten different QR codes, two of which were
Bitcoin URLs, one having a label. No difference except QuickMark failed on the
two (non-Bitcoin) codes that have the most information. Details are in the
referenced zxing issue.
Original comment by adammack...@gmail.com
on 16 Dec 2013 at 2:24
If you've been following the progress of the ZXing issue, you know the ticket
has been closed. After rigorous technical analysis by the ZXing development
team, it has been determined that there is no bug in the ZXing Barcode Scanner
app, which is known with 99% certainty by reason that the ZXing code has been
worked on my programmers who write only bugless code. Moreover, there is
strong evidence of user error, namely the user chose to run the app on a
defective device, as proven by the fact that the app doesn't run on the device.
Since the developers were able to resolve this non-issue without the necessity
of making any changes to the ZXing code, there has been nor will be any changes
with regard hereto.
Original comment by adammack...@gmail.com
on 17 Dec 2013 at 4:39
Original issue reported on code.google.com by
adammack...@gmail.com
on 15 Dec 2013 at 9:35