Zebra TC80 Enterprise Keyboard Lockdown error

Solved

Hi,

Customer is usning TC80 AOSP 02-10-02-L-00-A with CFE10, Agent 13.6.0.1257 and MobiControl 14.2.2 (similar behavior was also on 14.2.1) with Enterprise Keyboard as default input method and when scan trigger button on handle is pressed Android shows error message "Application Enterprise Keyboard unfortunately stopped working" while in Lockdown - I've added com.symbol.mxmf.csp.enterprisekeyboard to the Lockdown that works after restart but after some time or when I unlock Lockdown as Admininstrator and then back to User mode the error keeps appeararing again.

But when Ent. Keyboard is displayed (input text field selected) it works as expected .. but still shows error message on trigger press

When I look to downloaded device agent activity log I can see that the package is whitelisted by Lockdown but also blacklisted?! among with other settings package in line:

..

2019-02-01 22:01:34.883|pool-2-thread-1|I|AP|[TimerPollingForcedManualBlacklistProcessor][applyProfile] - begin {[Lockdown blocked:[com.android.launcher, com.android.systemui/.recents.RecentsActivity,...com.symbol.mxmf.csp.enterprisekeyboard..., com.android.settings/.ConfirmLockGeneric], enabled:true, forcePolling:true, SamsungSoftBlocking:false]}|

..

Any ideas appreciated (Whitelist feature did not help)

P.S: Also another package that should run on background I've added to the Lockdown items is listed in above log as both whitelisted and blacklisted but it doesn't shows error message when trigger is pressed so possibly it just don't run sometimes.

6 years ago
Android
ANSWERS
BG
Bastian, Goud
6 years ago

Hi,

I had the exact same issue and was able to fix it. I found out that it happens when the user is pressing the scan button. Remap the scan trigger button from R1 to L1 in settings --> key programmer.

Solution
MD
Matt Dermody Diamond Contributor
6 years ago

We've been experiencing this issue for quite some time ourselves. Have tried whitelisting EKB but didn't realize that its showing upon the blacklist too. 

BR
Ben Ragland
6 years ago

I currently have a case open with Zebra for this same issue. The good news is that they are able to reproduce it.

You could call in and make a case for the same issue. It may help escalate it a bit.

BR
Ben Ragland
6 years ago

Hey Goud, could you possibly upload a screenshot of your remap config?

By default, the trigger is the GripTrigger key when referenced in MX.

I don't understand how GripTrigger would be mapped to R1 by default so I am just trying to understand that aspect.

BR
Ben Ragland
6 years ago

Good news!

Zebra has provided us with a hotfix for this issue to be installed onto LG11. The test build of the patch successfully eliminated the EKB from crashing as seen before.

They should be officially releasing this patch soon for both GMS and non-GMS. I will try to respond here once the patch is available on Zebra's website.