Bluetooth not working when in Managed Device mode

After enrolling the TC57 device into Google EMM, it not possible to perform a Bluetooth pairing. Fresh out the box the device pairs, as soon as I put the device in Managed mode it doesn't work anymore.
The device is not displaying the PIN setting and after a while it shows an error "...….wrong pin or passkey"
I'm not trying to connect through an application, I'm in the settings trying to pair that way.
I have tried the follow settings com.zebra.bluetooth, without any success
I seems that Managed mode locks down the Bluetooth connect, so I am looking for a way to permit that function again.

Matt Dermody
Do you plan on actually using

Do you plan on actually using Google EMM in a production sense or are you just testing it out? The reason I ask is that I don't think it is going to offer anywhere near the management capabilities of an EMM platform like SOTI or WorkspaceOne(AirWatch). Even if Bluetooth is disabled by default as a feature, the Google EMM may not expose any configurable options to re-enable it whereas another more capable platform likely will.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Stig Nielsen
Need Zebra specific setting

Of course, I am using an MDM system behind the EMM, but I didn’t want to go into a discussion on what system to use. Every MDM system relies on EMM to push policies to the Android devices (only Samsung has it’s one API)

It’s only Zebra devices that disable Bluetooth parring when in managed Device mode, so it is a Zebra specific setting I am asking for.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
Bluetooth

Hi, Zebra are not doing anything special to the Bluetooth on a managed device - unless you are setting something Zebra specific.  I mean, we have a number of Zebra specific MX functions (http://techdocs.zebra.com/mx/) including disabling Bluetooth which are accessible from a number of EMMs but it sounds from your question like you are not setting anything specific to Zebra.  Which EMM are you using exactly?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Stig Nielsen
Using MX function

Thanks for the reply, I have looked through the link and found this one that could explain what we are seeing "Bluetooth Pairing Pop-up Enable/Disable"
It looks to me that the pop-up is disabled on the device.

Can you please help me to get deeper into the documentation to locate the format of the Android policy to be applied ?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Stig Nielsen
Using MX functions

Thanks for the reply, I have looked through the link and found this one that could explain what we are seeing "Bluetooth Pairing Pop-up Enable/Disable"
It looks to me that the pop-up is disabled on the device.

Can you please help me to get deeper into the documentation to locate the format of the Android policy to be applied ?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
Apologies for the late

Apologies for the late response but I remembered this thread after I learned something speaking with a colleague on Friday.  In Oreo when our devices are put into Managed Device mode then all of our value added applications are disabled such as StageNow or DataWedge.  One such application is the device Bluetooth, com.symbol.btapp and you can reenable this package either from your EMM (if the EMM supports enable system app) or through MX AppManager's EnableApplication, https://techdocs.zebra.com/mx/appmgr/.  We are looking at addressing / changing this behaviour in future releases as it can be confusing.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments