The first thing you can do is to disable the kiosk, and find all the name of activities associated with the pairing process on the device.   Once that is done,  the bundle-ID and activity names need to be added to the kiosk whitelist to allow such activities to be runnable when the kiosk mode is switched back on.

Thanks for this answer,, i'm on a 13.4 version.

All the steps you gave are available ?

Yes, all that I said in my previous post apply to both MobiControl  v14.x and  v13.4.

ok

I found in feature control how to desactivate the "Validation of association" step.

Nevertheless, I don't visualize how to do the following steps, I'm a bit newbie on android.

"find all the name of activities associated with the pairing process on the device",

What kind of software i should use for that ?

"the bundle-ID and activity names need to be added to the kiosk whitelist"

Where is this option ?

thanks in advance

For the bundle-ID and activity name, you can try sending the MobiControl script "identify_activity" to the device when the activity is running in the device foreground.

Once you get the name, you can add it as any other kiosk item to get it on the whitelist.  Simple massaging of the html template can easily be done to hide the added item from being activated on the device screen by any device end-user.

For the bundle-ID and activity name, you can try sending the MobiControl script "identify_activity" to the device when the activity is running in the device foreground.

 ok when executing the script in shell, reply is ok, and I've got no notification on terminal or in process list or application list

Once you get the name, you can add it as any other kiosk item to get it on the whitelist.  Simple massaging of the html template can easily be done to hide the added item from being activated on the device screen by any device end-user.

I'm sorry but there's some example somewhere ?

Hello

I found in another topic the way to have the result of identify activity, so for other reader, launch as a script, the result is in the log of the terminal

it's these three steps

com.android.nfc/.handover.ConfirmConnectActivity

com.android.settings/.Settings$BluetoothSettingsActivity

com.android.settings/.bluetooth.BluetoothPairingDialog

I have to found how to do whitelist in kiosk to achieve your soluce, Raymond. I'm very gratefull for your help.

I made a mistake, it's not with a kiosk but with a lockdown.

Is it always possible ?

For various Android platforms on MobiControl,  kiosk mode and lockdown menu are actually the same thing.   So unless your "lockdown" refers to something different from "lockdown menu",   there should be no misinterpretation for anyone

For the three activity items you found, you can first test whether the approach works by adding kiosk items with links such as

    Launch://com.android.nfc/.handover.ConfirmConnectActivity  

    etc.

and see if the pairing operation can be successfully completed when the kiosk mode is active.

If so, just take away the icon and unnecessary fields in the html to make the item more or less invisible/inaccessible.

Ryamond

That's exactly what 'im trying to do, in fact, the first step, "com.android.nfc/.handover.ConfirmConnectActivity", is available on kiosk without modification. It's a popup which indicate the fact that I confirm or not the association

The second step, "com.android.settings/.Settings$BluetoothSettingsActivity", is desactived when, in feature control, I tick the "Disable Bluetooth Contact Sharing" box when lockdown is inactive. For the moment, I dont desactivate it when using a lockdown, but doesn't display.

So the third step "com.android.settings/.bluetooth.BluetoothPairingDialog", is blocking too, I don't have the popup to validate the pairing.

in kiosk mode, I configure this

I tried with launch or not, case sensitive, the result is the same as explain above.

When I access to com.android.settings/.Settings$BluetoothSettingsActivity, in fact, bluetooth settings, I had the message "pair with mod com one" and this is a success.

So the question is: why do the last popup doesn't display when I'm on lockdown screen ?

There may be some other conflicting EMM policies deployed that make your test failing.

What is your device brand and model?

What are the version and build numbers of your MobiControl device agent and server?

What are the active MDM API's reported in the configuration tab of your device agent?

What advanced option(s) in the Kiosk mode have you checked/enabled?

If you have feature control payload deployed, what options have you checked/enabled?

There may be some other conflicting EMM policies deployed that make your test failing.

What is your device brand and model?

M3 Mobile SM15N Android 8.1 GMS

What are the version and build numbers of your MobiControl device agent and server?

Server 13.4.0.4266, device 13.8.0.1047

What are the active MDM API's reported in the configuration tab of your device agent?

LG MDM 1 advance android plus 1.0, Android plus 1.15, Work managed device, RC+ (1.16.0.100)

I downloaded the M3 MDM plugin on https://docs.soti.net/mobicontrolagentdownloads

What advanced option(s) in the Kiosk mode have you checked/enabled?

I've enabled the activity suppression and the hide home floating button

If you have feature control payload deployed, what options have you checked/enabled?

I don't know why your device is M3 but the active MDM API includes "LG MDM 1 advance android plus 1.0".  This looks really strange.  Unfortunately, I don't have similar device as yours to look into and do more tests. 

The feature-control options look OK to me.  I'm not sure if disabling "activity suppression" Kiosk option will make a difference on your device.

Also, you might be missing one or more activities (i.e. on top of the three you found so far) that are crucial to the pairing process.  You might need more time and/or skill to identity them.

Hello Raymond

I don't know why your device is M3 but the active MDM API includes "LG MDM 1 advance android plus 1.0".  This looks really strange.  Unfortunately, I don't have similar device as yours to look into and do more tests. 

I don't know too, but if it's strange for you, I can told you that a have a problem with the remote control feature, the remote screen isn't displayed, no problems with the remote view after accepting the connexion. I don't know where search. I will do another topic after.

The feature-control options look OK to me.  I'm not sure if disabling "activity suppression" Kiosk option will make a difference on your device.

At start, it was to display the wifi signal, time and other options on the screen top, maybe redunding with feature control now. I had to check it.

Also, you might be missing one or more activities (i.e. on top of the three you found so far) that are crucial to the pairing process.  You might need more time and/or skill to identity them.

I send a script with about 100 executions of identify_activity paused by a sleepex 300 and 200, in log, there's only these three steps.