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

Using 2D barcode imagers on Android Enterprise Devices delivering data via broadcast intents. #48

Open
3 tasks done
RaymondBuil opened this issue Jul 27, 2021 · 4 comments

Comments

@RaymondBuil
Copy link

Describe the bug, issue or concern

To make use of Android Enterprise recommended devices there is a need to be able to implement and use 2D barcode Imagers which are inplemented in these devices.

To make this possible, an intent broadcast receiver needs to be added to the QrCodeScannerFragment. Android Enterprise devices such as Zebra Technologie's Mobile Devices TC2X, TC5x, TC7x as well as the ET5x series (all running on Android Enterprise) are capable of sending an broadcast intent with additional information as soon as a QR Barcode gets scanned with the integrated imager. (no use of camera). This makes the barcode scanning procedure more flexibele as these imager are build for barcode scanning purposes.

As often Android Enterprise devices are used within the Events business, an integration of 2D imagers is a must have.
Besides using the integrated barcode imager, also BlueTooth enabled ringscanners can be used to scan the QR Barcode. Same mechnisme is being used to send the QR Barcode content for validation.

Sample code on how to implement can be provided. We have used these source files to test and implement the Zebra 2D Imagers being used at the TC2x, TC5x, TC7x and ET5x series.

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context

Add any other context about the problem here.

Governance

@SanderVeer
Copy link
Contributor

SanderVeer commented Aug 10, 2021

Hi @RaymondBuil,

Thanks for reaching out! Supporting 2D scanners is absolutely something we want to do. We've actually been working on this behind the scenes, and a test of our implementation is currently underway. For this we've made use of Zebra's EMDK instead of Datawedge, which I believe you're describing in the ticket.

Could you elaborate how or why Datawedge would potentially be a better fit rather than using the EMDK? From my understanding Datawedge requires some extra setup regarding profiles to get up and running in combination with our CoronaCheck Scanner app, whereas the EMDK gets bundled and allows users of supported Zebra devices to start using their 2D scanner right away.
If this isn't the case I'd love to give Datawedge another try to support a wider range of devices, but during internal testing it seemed using the EMDK was the most foolproof way of letting our users use their 2D scanners.

I'm looking forward to your reply!

@RaymondBuil
Copy link
Author

RaymondBuil commented Aug 11, 2021 via email

@modest-mark
Copy link

Dear Sander,

To complete the story: There's a lot of 2D scanning Android hardware. Would be nice to for instance offer possibility to use a keyboard wedge function. This currently is not working. Camera only.

Appreciate the possibility to get this working.

Best regards, have a great weekend!

Mark Pronk

@DanielDM325
Copy link

I agree with Mark,

This would be a great addition to this app.

Daniel

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

4 participants