-
Notifications
You must be signed in to change notification settings - Fork 20
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
dcssdkEventScannerAppeared not firing when usb scanner attached Android 14 #18
Comments
SDK 2.6.22.0 is supposed to fix this issue but not posted yet . |
Found it on demo app on same repository.
…On Fri, Jul 26, 2024, 15:19 Riadzebra ***@***.***> wrote:
SDK 2.6.22.0 is supposed to fix this issue but not posted yet .
Could you advise how did you get 2.6.22.0 SDK ?
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7K6D2FQ7VVPFN5T7QTEEDZOILRRAVCNFSM6AAAAABLEQBAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJSGM3TMNZRHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Could you outline the steps you are using to reproduce the problem . |
After factory reset do we need to add in SNAPI mode ?
But if its one cabled scanner then it should connect right ? scan snapi
barcode should be for multiple scanner then needed right ?
Because when its implemented that time never scanned snapi barcode and its
still able to connect to app. Right now its stops in android 14.
Or can you help to find out correct way do that ?
…On Fri, Jul 26, 2024, 22:05 Riadzebra ***@***.***> wrote:
Could you outline the steps you are using to reproduce the problem .
I have done a test here with no issues . Did you make sure to set the
scanner to SNAPI after the factory reset ?
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7K6DZEZC7VPEYG3X7FJVDZOJ3EPAVCNFSM6AAAAABLEQBAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGEYDQOJSHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
you can not communicate with scanner if the scanner is not set to SNAPI you can refer to setup process using the scanner control demo app part of the SDK https://techdocs.zebra.com/dcs/scanners/sdk-android/sample-apps/ |
Can you try Scanner DS9308 as its usb scanner. Before that it doesn't
require that to be convert in SNAPI ? After upgrading to latest one it's
stop working. Can you share, how to convert USB scanner to SNAPI mode ?
…On Fri, Jul 26, 2024, 22:55 Hardik Mehta ***@***.***> wrote:
After factory reset do we need to add in SNAPI mode ?
But if its one cabled scanner then it should connect right ? scan snapi
barcode should be for multiple scanner then needed right ?
Because when its implemented that time never scanned snapi barcode and its
still able to connect to app. Right now its stops in android 14.
Or can you help to find out correct way do that ?
On Fri, Jul 26, 2024, 22:05 Riadzebra ***@***.***> wrote:
> Could you outline the steps you are using to reproduce the problem .
> I have done a test here with no issues . Did you make sure to set the
> scanner to SNAPI after the factory reset ?
>
> —
> Reply to this email directly, view it on GitHub
> <#18 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AC7K6DZEZC7VPEYG3X7FJVDZOJ3EPAVCNFSM6AAAAABLEQBAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGEYDQOJSHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***
> com>
>
|
Can you explain tye following term written on that doc ?
Configure its USB host mode to SNAPI.
As its not mentioned how to do that. As barcode is only the option then
its not mentioned. Becuase in android tabs that have usb port can directly
detect it. Still this statement creating confusion.
If you can guide us for the same then it would be great and its really
help us. Can you please help for the same.
…On Fri, Jul 26, 2024, 23:09 Riadzebra ***@***.***> wrote:
all our scanner will folow the same process and setting the scanner to
snapi is requirement that would always the case . please refer to the link
i shared and to our samples .
the SNAPI barcode is part of the steps .
Please see below for your convinence
image.png (view on web)
<https://github.com/user-attachments/assets/ac2547e8-3803-4d8f-88b0-3b8811a76e9e>
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7K6D23N2XN6KNGYFTCRU3ZOKCW3AVCNFSM6AAAAABLEQBAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGIYDENZSGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
the scanner by default its set to USB HID keyboard which is one way protocol . to communicate with wired scanner using SDK you need to use SNAPI protocol for USB scanner . in case of BT scanner you need to set it to BT SSI . This is described in our sdk sample and the documentation . I have shared earlier link below https://techdocs.zebra.com/dcs/scanners/sdk-android/sample-apps/ You can refer to following statements addtionally from the user guide for your scanner you have the following page 239 and 240 , you have |
Did you run the testing ? |
Yeah checking for the same. Seems okay with SNAPI mode.
…On Fri, Aug 2, 2024, 18:47 Riadzebra ***@***.***> wrote:
Did you run the testing ?
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7K6D774ZKA3UMNVO276XLZPOBFTAVCNFSM6AAAAABLEQBAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGM4DOMBWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
After updating scanner sdk to latest one 2.6.22.0 dcssdkEventScannerAppeared stopped firing.
device connection mode is. :
DCSSDK_OPMODE_SNAPI
When you factory reset device and then try to connect to this mode its not firing that
dcssdkEventScannerAppeared
Can you hlep with that.
Android OS : Android 14
Device Samsung X200 tablet.
The text was updated successfully, but these errors were encountered: