There's a new home for Articles. Find Articles on Our Product Support Page.
We are looking to adding a couple of scripts to the pre or post boot so that the Wifi and the P1, P2, P3 buttons are remapped for the Zebra WT6000. We have WT6000 that lose their wifi settings and sometimes their setting for P1, P2, P3 buttons. MobiControl doesn't seem to push out programming of buttons and once the wifi isn't working MobilControl can't talk to the device. I can program bar codes for StageNow but we lock down the system after it's fully booted for warehouse staff. Wondering if anyone has done this and how?
I am having difficulty sending some scripts to my Android Enterprise device - Samsung A50, Android 9. Our platform is version 15.0.1.1181 and the agent version is 14.1.6.1018. The scenario is: Firstly I noticed that after sending the script unlock, the logs need to update to state “Custom log (New authentication password applied)” before sending the kill_application and/or start script. After I did this I noticed that my test device successfully completed the scripts correctly each time – however, I then started sending them to other devices and was finding they hadn’t worked. This then has led me to find another issue: I believe what is happening is – if the device is pressed or touched by the user once the script is sent – then the following scripts: kill_application com.commontime.infinity.jobmenuprod start com.commontime.infinity.jobmenuprod will work correctly. However, if the user does not touch the device at all once the script is sent (I have found 30-60 seconds or more) then the final script is not correctly ran. The device appears to run the start script once the user opens or touches the device, but if this does not happen then the script is not ran at all – almost as though the device forgets that that start script needs to be ran. I have also tried sending it at three separate scripts – firstly sending the script unlock, and waiting for the logs to update to state “Custom log (New authentication password applied)”, next sending the kill_application script and waiting for this to appear in the logs, and then finally sending the third script – start. Again, if I press or enter the device manually as soon as the final script is sent, then the application does load once the screen is opened – yet, if I wait and enter or select the device after 30-60 seconds or more the application does not start – again as though the device has forgotten it needs to complete the third and final script. To confirm in all instance – the unlock and kill_application scripts are correctly working each time – it is just the start application that is causing an issue. Please could you provide any advice on how I can ensure the scripts each run - without user interference? Thank you
Hi Support I Have been design Device Enrollment for my Clients but i have some issue i cant find out My Device : ZEBRA ET51 Android OS 9.1 Mobicontrol Server version Version: 15.0.2.1049 Mobicontrol Client version 14.2.1 Build 1083 1. I use Mobistage Setup and create XML File to use with MX Script on SOTI Mobixontrol 2. I want to use MX Script as Profile Enrollment step because of when ZEBRA ET51 have been enrolled to Mobicontrol server and got XML FILE (from Mobistage) via File Sync rules 3. I want to MXScript to execute XMl File 4. How to do mxscript as profile
Hi support I Want to open application on my device How to open it I use script as below showmessagebox "New Information please go tp App XX" NO_TIMER 1 YESif %ShowMessageBoxReturn% == IDYES goto Open App.APK << How to Open App?
Hello dear SOTI-community, I want to enforce a lockdown on our Android devices with only two or three apps being offered to the user. Unfortunately, I currently have to enable the settings app as well, because if I update one of our apps (self-programmed app), the device will prompt the user for permissions, which he or she is not allowed to permit if the settings app is not enabled. I am already using a post-install-script, but the commands don't seem to work: afw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO_ELM allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO_AFW allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA_ELM allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA_AFW allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.CAMERA allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.RECORD_AUDIO allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_EXTERNAL_STORAGE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.READ_EXTERNAL_STORAGE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.CALL_PHONE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_COURSE_LOCATION allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_FINE_LOCATION allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.RECEIVE_SMS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.SEND_SMS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_SETTINGS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.VIBRATE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WAKE_LOCK allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_WIFI_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_NETWORK_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_FINE_LOCATION allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_COARSE_LOCATION allowafw_set_permission_grant_state com.ignitix.systemone android.permission.BLUETOOTH allowafw_set_permission_grant_state com.ignitix.systemone android.permission.BLUETOOTH_ADMIN allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CALL_PHONE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CHANGE_WIFI_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.FOREGROUND_SERVICE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.GET_ACCOUNTS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.INTERNET allowafw_set_permission_grant_state com.ignitix.systemone android.permission.KILL_BACKGROUND_PROCESSES allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_PROFILE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_CONTACTS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_PHONE_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.REQUEST_INSTALL_PACKAGES allowafw_set_permission_grant_state com.ignitix.systemone android.permission.RECEIVE_BOOT_COMPLETED allowafw_set_permission_grant_state com.ignitix.systemone android.permission.VIBRATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WAKE_LOCK allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_SETTINGS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_EXTERNAL_STORAGE allowafw_set_permission_grant_state com.ignitix.systemone com.honeywell.provisioner.ACCESS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.NFC allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CAMERA allowafw_set_permission_grant_state com.ignitix.systemone android.permission.RECORD_AUDIO allowafw_set_permission_grant_state com.ignitix.systemone android.permission.FLASHLIGHT allowafw_set_permission_grant_state com.ignitix.systemone com.android.settings/.Settings$AppWriteSettingsActivity allowafw_set_permission_grant_state com.ignitix.systemone com.android.settings.Settings$AppWriteSettingsActivity allowafw_set_permission_grant_state com.ignitix.systemone com.android.browser.permission.READ_HISTORY_BOOKMARKS allowafw_set_permission_grant_state com.ignitix.systemone com.google.android.gms.permission.ACTIVITY_RECOGNITION allowbatteryoptimize allow com.ignitix.systemone Although it should permit practically everything, our Android 7.1.0 devices still want the permission for system setting access and battery optimization from the user. Our Android 8 devices want even more permissions to be sanctioned by the user. Which script command will work properly? Does anyone have any experience regarding this type of problem?
Script for once of day app cache and data clearing on android plus
Hi, is there any possibility to shutdown the device via SOTI? Unfortunately shutdown isn't working. Thanks for any ideas, Regards
Hi SOTI support I want to use script that 1. change device from vibration to sound 2. Set sound volume 3. use writesecuresetting -sys I try to find writesecuresetting -sys document but i cannot Device Samsung Mobile Android 8-10 Google Enterprise
We have multiple Android devices, in KIOSK mode, each which we can enable/disable from the MobiControl panel using the _adminmode on/off This requires that the android device have access to the internet.My question then goes on, would it be possible that, through our on android app, that we could enable/disable the KIOSK mode? Lets say we have a simple app with Admin On/Off, using the slider, it would invoke the MobiControl app, telling it to enable or disable KIOSK mode, just as the MobiControl site, sending scripts to the device.Thanks in advance.
Hi, does anyone know of a way to reset a default application on an Android Plus device via a script? We're using Android KitKat on TC55's. Some users have accidentally clicked the wrong app and selected 'Always'. As the wrong app is on the blacklist it fails to open. Rather than remote onto each device and clear the default in the settings, I wondered if I could clear and then set the correct app via a script? In the meantime, I'm going to have to remove the 'wrong' app from the blacklist. Thanks.
Hi everyone, We recently deployed 30 Android devices. They have been enrolled while being on Android OS 9. Some end-users updated their devices and now Mobi app doesn't connect anymore to our DS. The reason is that our mobicontrol server have a self-sign certificate with SHA1 and Android 10 doesn't support it. We have an inventory of Windows Mobile CE 6.5 (which don't support TLS 1.2) and we don't wanna update this certificate yet because it would disconnect all those PC pockets. I've pushed a script to disable the system OS update but I believe this script only last 30 days on Android Enterprise devices. Is pushing the script again after 30 days will extend the policy ? Thanks for your help,
Looking on script that moves (or copies) a file located under %sdcard% to the home scree. Use case is a pdf we have pushed to the devices via package and want it on the home screen for easy access.
I have a few devices where remote controle flag is not visible, so i can't take the devices remotely over. when i send a script to those PDAs to activate the RC flag i get an error. So scripts are not accepted. Can you help me with this issue. Device: TC75 Android + SOTI version info: 15.0.2.1049
I have a few devices where remote controle flag is not visible, but when i send a script to those PDAs i get an error. So scripts are not accepted. Can you help me with this issue. Device: TC75 Android + SOI version info: 15.0.2.
Hello, Could someone please tell me how to launch the MobiControl agent via script ? I try this : sendintent -a "intent:#Intent;action=android.intent.action.MAIN;category=android.intent.category.LAUNCHER;component=net.soti.mobicontrol.coppernic;end" But as you can see bellow, the system requires manual action (and I want to launch the script on 1000+ Android+ devices) : Many thanks for your help !
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
