Issue with event listener when device is trying to locate an asset

// Expert user has replied.
p prashant prashant 1 year 6 months ago
55 1 0

We have been working on the development of an Android application that tracks RFID-trackable assets based on their tag ids. This Android app will be installed on the zebra hand-held reader device. We have a couple of queries. Could you please have a look and answer them.

In the event that the zebra device is supposed to start locating a single asset, we have set up an event handler that goes to sleep for about 5 seconds and then we stop the event handling session. During this time, the event listener scans the device and attempts to locate the asset and if captured it returns the Peak RSSI value and shows up on the screen. ( we have followed the below document for tracking assets:

https://www.zebra.com/content/dam/zebra_new_ia/en-us/manuals/barcode-scanners/software/sdk-for-android-dg-en.pdf )

There are a few challenges here :

  1. Now the challenge is that the app fails quite a lot of time and we have no idea what happened under the hood. We should be able to capture of the logs of the application. Can you plz tell us if it's possible to capture the logs?
  2. The app gets slow and takes time to respond. Could it be due to the 5 seconds sleep time introduced when setting up the event handler?
  3. So far, we have been managing the development remotely, we will have the device with us soon. Is it possible to connect to the device through a USB and we could fetch the logs on our development environment?

I have attached the piece of code which is trying to establish a locate asset event handling session. Is this the best way to achieve the same?

Thanks

Prashant

Please Register or Login to post a reply

1 Replies

D Daniel Neamtu

Hi Prashant,

I see the link you've mentioned in the post is not working, could you please share it back again?

- It is totally possible to debug the application and check what's happening also under the hood of the SDK.

- First thing I've noticed from the Screenshot is that you guys are trying to listen for the events but this task should be done on a IO Thread so either with an AsyncTask, ExecutorService or Coroutines if using Kotlin. Yes, the cause could also be because of the 5 seconds sleep which shouldn't be required anymore if using one of the suggested methods.

- Yes, absolutely. You'll be able to get better insights after you get the physical device.

Also, check out this guide (if not already) as a further reference, it contains more examples:

https://techdocs.zebra.com/dcs/rfid/android/2-0-2-94/samples/hellorfid/…;

CONTACT
Can’t find what you’re looking for?