Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow(er) QR code scanning on some (likely older) devices #29

Open
Klakurka opened this issue Jun 17, 2019 · 6 comments
Open

Slow(er) QR code scanning on some (likely older) devices #29

Klakurka opened this issue Jun 17, 2019 · 6 comments

Comments

@Klakurka
Copy link

Slow(er) QR code scanning on some (likely older) devices:

im_uname claims that QR code scanning on his LG G5 (Android 8) is slower than other wallets (eg. Crescent Cash) with a ~0.4s freeze when the code is scanned.

It would be good to get an idea how widespread this minor issue is as it would be ideal if as many devices as possible were performing as quick as possible.

On my personal OP6, Neutrino is by far the quickest to scan and doesn't have the small freeze/pause that most other wallets have.

@zquestz
Copy link
Contributor

zquestz commented Jun 30, 2019

It is by far the fastest for me too. It does use the scanning api's provided by google, so not sure exactly what we can do about this.

@Klakurka
Copy link
Author

I'm not technical but one potential option could be using a different scanner depending on the device if it turns out there's a pattern with which devices are slow (eg. A certain version of Android).

It would be good to pass this along to the google team working on this in case they're able to reproduce.

@nighthawk24
Copy link
Contributor

Crescent Cash uses https://github.com/zxing/zxing instead of google mobile vision lib that neutrino is using. I can investigate switching to zxing if it's faster and lighter.

Additionally, the deep link URI issue(#20) is kind of blocked due to the way the callback from the ScannerActivity is setup to only return results from the ScannerActivity to SendActivity.

@zquestz
Copy link
Contributor

zquestz commented Aug 26, 2019

@nighthawk24 I would love to see that blocker resolved for the deep linking. This is one of the more crucial features to add before we actually do a non-beta release. Do you have suggestions on how that can be refactored?

@nighthawk24
Copy link
Contributor

Yes, the deep links can be resolved in a standalone activity to open intents to SendActivity or other screens based on use case of the resolved URI.
Is there a way I could get permission to create branch so I can work within android-neutrino project instead of forking to my own branch when working on issues?

@zquestz
Copy link
Contributor

zquestz commented Aug 27, 2019

I have no issue with that, @cpacia is the admin so he would need to setup the privs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants