11 Replies Latest reply on Sep 28, 2016 2:43 PM by Michael Bedford

    EMDK service is not closed, next startup takes a long time

    Michael Bedford

      Hello all, this is not so much of an issue that I need help with but more, an observation I had and I wanted to point it out for others as well as start a discussion. Of course, if there is something I can do better OR there is a possibility for Zebra to enhance the EMDK to correct this, then that would be appreciated too.


      At first, I was having issues where the scanner would not return any results. The lights would light up but no beep, no barcode results. While troubleshooting with breakpoints, I noticed that one of the first things you should do is get the EMDK manager, which I was doing right away.


      When the EMDK manager returns, it raises a callback, called:


      void EMDKManager.IEMDKListener.OnOpened(EMDKManager emdkManager)


      which in turn, will call InitScanner(); and at that point, you will be good to go, ready to scan, fully initialized.


      However, when I was having issues, I noticed that the callback, OnOpened, would not raise at all or sometimes would eventually raise but take 30+ seconds or even minutes which of course delays the InitScanner by that amount of time and you cannot scan during this time.


      The culprit that I found is OnPause and OnDestroy must get raised to DeinitScanner and release the EMDK manager, which makes sense. But, guess what, when you are debugging in Visual Studio and you hit stop, it instantly stops and from what I can tell, OnPause and OnDestroy do not get called. This leaves the EMDK manager out there.


      How can you tell? Go to Android Settings > Apps > Running and you will see "EMDK Service" is running even when your app is closed or you are not debugging. If the EMDK Service is running, it causes this slowdown of the callback the next time you try to run your app. So, you have to do one of two things:

      1. When debugging, make sure to hit back arrow on the android device BEFORE you stop the debugger.

      2. You can go to apps > Running and select the EMDK Service and then click "Force Stop". This will kill it and you will be good.


      If you shutdown the app gracefully (number 1 above) you will see that the EMDK service is removed from the running apps.


      This happens even on the BarcodeScanningTutorial provided by Zebra for the EMDK. You can see this happen by loading the tutorial into Visual Studio and start debugging. The first time, all will be fine. Now, click the stop button to stop debugging and try to start back up. While you were stopped, you could note that the EMDK service never closes. You could also note the delay on the callback OnOpened. When the demo is started back up, you will note it is stuck on "Status: EMDK Opened successfully ..." and doesn't go to this status "Scanner is idle and ready to submit read." like it should. Finally, you will note that you cannot scan a barcode during all of this.


      While this seems to be an issue with debugging in Visual Studio, it has me concerned. What happens if my app gets in a weird state in production and the service does not get stopped properly?


      That said, I believe that Zebra should look at this. It seems that even if the EMDK service IS still running when the app is started and the EMDK manager tries to GetEMDKManager on startup, it should be able to either return the currently running instance or kill and restart or something in a more timely manner rather than sitting there doing nothing.


      Hope this helps some people and hopefully there is a workaround or something to ensure this won't be an issue.





        • Re: EMDK service is not closed, next startup takes a long time
          Michael Bedford

          This has taken on a whole new life, it has now become an issue and a major bug. Again, when I call GetEMDKManager, if the EMDKService is already running, it takes forever for the IEMDKListener to return OnOpened. It seems like, in my experience, most calls like this should work as follows:

          1. Is the service already running? If so, grab the service instance. (Note this is the part not working or working slowly).

          2. If the service is already running but we cannot grab the instance, start a new one for this call.

          3. If the service is not running, start it.

          4. When it is necessary (ie setting emdkManager to null, dispose or with GC) then stop the service.


          It appears that the only thing in that list working reliably is number 3. I would say maybe number 4 but I don't know if the times the service is left running is because of the Android lifecycles not firing or if there is also an issue with number 4.


          All that said, today, there was a whole new but related issue.


          We were doing extensive testing and not using Visual Studio debugging. Therefore, we were closing the app gracefully and as such, the onStop and onDestroy Android lifecycles SHOULD have been firing and ultimately stopping the EMDK service. But, this was not the case. Randomly, after a few hours of testing fine, the scanner stopped working. Multiple graceful shutdowns and startups of the app would not recover the scanner. When I looked in running services, EMDK service did not appear to be running at any time (whether when it should have been or not, meaning whether my app was running or not). This was odd and different behavior. However, on a whim, I noticed that while you are viewing the running services, there is a link at the top that says "Show Cached Services". I clicked that and there was the EMDK service. I manually killed it and suddenly, my app starting working, meaning the scanner started working again.


          So now, this still is similar to yesterday where when the service is already running, things just are not happy. However, the new question is what is this new state it can also get into where the service is cached as well?


          This is now causing major reliability problems. I hope somebody has some feedback and can help me get this resolved. Otherwise, I am not looking into ways to force stop the EMDK service from inside my app, though I fear Android will not allow me to do so.





          • Re: EMDK service is not closed, next startup takes a long time
            Michael Bedford

            The answer to this original post was to get the EMDK service updated to the latest version, which at this time is 4.1.2.


            The method to update the EMDK service on a one device at a time basis is to follow the guide that Bill posted above.


            Aside from that, I need to work with my team to check the EMDK service version of each new device we receive and either update it or look in to using something like StageNow (which I have not used yet).


            Thank you all for the help.