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 QR Code Reading Issues on Samsung A4E Devices with Android 13: Plugin or Device Troubleshooting? #24

Open
andrerds opened this issue Dec 13, 2023 · 2 comments

Comments

@andrerds
Copy link

Expected Behaviour

Fast reading QRCode

Actual Behaviour

I'm experiencing a slowdown issue when reading QR codes on Samsung A4E devices. This model is taking longer than expected. My question is whether anyone has encountered something similar or if it could be related to a specific plugin. I'm also wondering if it might be a device-specific issue.

The device in question is a Samsung A4E running Android 13.

Platform and Version (eg. Android 5.0 or iOS 9.2.1)

Android 13

(Android) What device vendor (e.g. Samsung, HTC, Sony...)

Samsung

@okhiroyuki
Copy link
Owner

Hi, @andrerds

I would like to know more details.
For example, can you give us a video of the QR code being scanned and how long it takes to scan it?

Note that I do not own your device, so it is most likely difficult to reproduce.

@andrerds
Copy link
Author

Hi, @andrerds

I would like to know more details. For example, can you give us a video of the QR code being scanned and how long it takes to scan it?

Note that I do not own your device, so it is most likely difficult to reproduce.

Hi, everything good, thank you for responding so promptly.

Unfortunately, due to company privacy policies, I can't share a video of the QR code being scanned. I understand your curiosity regarding this specific aspect.

Regarding the delay in reading the QR code, I've made some test requests, such as trying to scan another QR code, uninstalling and reinstalling the app, among others. These tests can help us better understand the origin of the problem.

It's worth mentioning that we have the same app in other locations, and this is the first report of such an issue. This makes the situation a bit more challenging as we don't have previous cases to compare.

Unfortunately, as it's a client's device issue, I can't directly access logs or perform deeper checks, making it more difficult to identify the root cause. I'm working hard to resolve this, and if more information or possible solutions arise, I'll be more than happy to share them.

Thanks again for your interest and understanding.

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

2 participants