Scanner stops using the profile intermittently

Sometimes after the scanner hasn't been used in a while the EMDK ignores the profile being used and goes back to it's defaults of just using the keystroke inputs. The profile I'm using turns off the keystroke inputs and uses intents instead. The app I've written connects to the scanner when it starts or comes into the foreground and disconnects from the scanner when it goes into the background. I haven't been able to find out the exact frequency of when this happens.

When this happens, I can close the app and open it up again and the profile gets loaded just fine. Other times I need to restart the device before the profile starts working again. Both of these situations are not ideal, as we really just want it to work without these sorts of workarounds.

I have added some logging and it doesn't look like I'm getting any errors from the EMDK when the app connects or when it process the profile. Is there a proper way to ensure the profile will be applied every time?

I saw mention of a similar problem in and the suggestion of possibly using the DataWedge APIs instead of the EMDK. Is this still the recommendation?

EMDK service version - 6.7.10.1010

OS version - 7.1.2

Device model - TC75EK

Anonymous (not verified)
Hi Steven, typically you

Hi Steven, typically you would use either EMDK OR DataWedge - I presume the profiles you are referring to are the Data Capture profiles and please note that these are going away (please see   for more information).

I couldn't say why the wrong profile is being applied in the situation you describe but you could try disabling other DataWedge profiles or configuring the default profile to also send intents, as a fallback.  There is a way to determine the active profile using the DataWedge API (Get Active Profile - Zebra Technologies TechDocs ) but I would consider that a last resort, this should 'just work'.  Are you applying the profile every time the app comes to the foreground?  It is only necessary to specify the profile once.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Steven Martin
I'm not sure what the exact

I'm not sure what the exact name of the profiles are but in Visual Studio I access them via the top menu with EMDK > Profile Manager.

The app does apply the profile every time it connects to the scanner. Though if the capture profiles are being deprecated then I'll migrate to using DataWedge first then come back here if there are similar problems. Assuming the same principal applies here though? Just apply the DataWedge profile once when the app starts and disconnect/reconnect as needed?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Anonymous (not verified)
Once you have configured

Once you have configured DataWedge there isn't any need to re-apply the profile as it will be remembered across an application switch or device boot (but will be cleared during a factory reset, enterprise reset or if DataWedge is reset).  A lot of customers will configure DataWedge with a database file and you may also find   helpful.

Thanks.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments