Hi all, 

Just an FYI, 

Allowing net.soti.settingsmanager/.BluetoothActivity and com.android.settings as a hidden items from the kiosk profile have solved my issue.

Thanks All

Hello Walid,

Thank you for your post, can you please try enable_system_app com.android.bluetooth script on the device?

Regards,

Adding the bundle ID for the Bluetooth did not make any difference.

Regards 

Hi Walid,

The right steps to solve your problem, irrespective of the device brand/model or firmware/agent versions,  should normally be:

1. Temporarily disable the kiosk mode profile configuration

2. Do whatever is needed to allow the bluetooh setup/GUI to run, while sending the script "identify_activity" and/or monitor the app/activity being run with Soti (e.g. process manager in remote-control session) or third-party task manager app during the process.

3. Add the app/activity found in step 2 in the application-run-control whitelist or kiosk definition so that the task can be repeated when the kiosk mode is  active.

4. Re-enable the kiosk mode profile configuration. 

Hi Walid,

Thank you for advising us that your post has been solutioned. Please let us know what reply you found to assist you in solving your inquiry so others may benefit from this information by selecting "is solution".

Regards,

Hi Everyone,

I'm facing the same issue but I feel like I'm missing a step here:

-Same device: Samsung Galaxy Tab Active 2.

When pairing the BT in the lockdown, the chirp can be heard but the popup won't show. I'm able to make it work outside the lockdown.

1) I'm not sure how to use the "identify_activity" script. When I launch it in the command prompt from the remote sessions, it returns Unknown Command "identify_activity". and when I send it through the device page, it doesn't trigger any logs.

 EDIT: once you allow mobicontrol to "Access Data usage" under special accesses. the "identify_activity" command works. BUT, it does turn the device in the state referred to in #3. Remote access is very slow and clients are offset. in my case the popup is "com.android.settings/.bluetooth.BluetoothPairingDialog" 

2) referring to other posts from Raymond, I was able to add an item to my lockdown with "launch://com.android.settings/.Settings$BluetoothSettingsActivity". This partially works out: I have to select it once, then it works after. therefore, whenever I hide it, it never going to work since I can't launch it at first. *I would like that to be seamless to the user anyway so it's not very relevant.

EDIT: the Bluetooth now works if I add 2 new rows in the lockdown (these works when hidden and don't need to be launched explicitly):

-launch://com.android.settings

-launch://net.soti.settingsmanager/.BluetoothActivity

3) In my profile for the lockdown, in Advanced parameters, there is one name "Samsung Package Disabling" that we always used. When I uncheck this box, I need to allow additional permission to Mobicontrol to "access data usage tracking". Then, everything works fine BUT remote sessions become terribly slow and any clicks with the mouse are offset of about an inch to the right. making it almost unusable

 EDIT: All delays and offset where corrected by the following scripts

_resetfailedrcdetectionflag
restartagent

4) Adding white-list doesn't seem to do a thing... maybe I'm doing it wrong? I though the white-list would do the same as adding the hidden rows in the lockdown but it doesn't seems to do anything