No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hey, I have an application that needs to use a barcode reader. on kiosk mode, it is not asking if it is able to use the device. when I log out and run it as admin it works but after restarting, it forgets that setting again. As far as I can see I have given all permissions so the device can use the application. What I'm doing wrong or I can't use afw#mobicontrol enrolling method for ELO?
I've read other posts about this but everything I've tried to this point hasn't worked so I figured I'd open this up to the community. Here is our scenario: MobiControl Cloud instance 15.3 Android Classic device agents 15.0.1.1051 We are using Sonim XP8 devices only. Devices are used in the service industry and are locked down via lockdown screen. Devices have no access to apps outside of what is displayed on the lock down page. Yes, I've tried Android Enterprise but it doesn't work for our environment. Especially the remote assistance part where permission is required. Before Android 10 we were able to roll out APKs and silently install without issue. As we are all aware, when running some apps for the first time, users will be prompted for Location, Storage, Camera, etc. access before use. The problem is, when the device is Locked Down, users can't accept those permissions. Device admins must unlock the device, accept the permissions then lock the device. But even if the user could accept these permissions, they may tap the wrong answer making the apps useless, especially when it comes to location. How do we work around this? It is imperative that when we add or update apps, that our technicians can pick up their devices and get to work without having to deal with prompts and unlocks. If anyone can shed light on this, it would be greatly appreciated. If possible, I'd like to keep answers limited to the SOTI environment only without having to introduce 3rd party solutions mixed in.
Hello! We are managing Samsung Galaxy devices as Work Managed AE devices. When trying to edit any permissions in any app, this is not possible because it is blocked by MobiControl. It affects apps from Managed Google Play and from puplic Google Play. The apps have all their requested permissions activated (Location, Storage etc.). Even after sending the following script, the apps installed after its execution have all permissions activated and not changeable by user. afw_set_permission_policy deny or afw_set_permission_policy prompt What is the cause of this behaviour? We do not execute any scripts when enrolling these devices.
Hi, It is my first post so apologies if I'll do anything not correct. We're using Mobi Control version 14.4.9.1034 and the query is for Samsung A02s, Samsung A12, Moto G6 and G8 devices enrolled as Android Enterprise. I'm after a post install script on File sync rule to enable 'Allow permission' function within Change system settings for certain application. We will need in near future to update this application every month or so. I have attached a screen shot to provide more details what I'm after. Please let me know if it is possible or if any further details I can provide. Kind regards, Norbert
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?
Hello, I am referencing a similar but less specific question here: https://discussions.soti.net/thread/set-app-permissions-with-soti/ I am using Android+ management with SOTI MobiControl. Basically I understand how to use Stagenow to create an XML that can then be called in the Post Install script in MobiControl package builder. However, within StageNow I cannot find anything that will allow me to grant permissions automatically for an app (basically automatically granting the pop up for Location, Storage, etc). Can anyone help me find the actual commands I could manually add to my XML or perhaps a StageNow configuration I'm missing? Thank you!
Hi, I already read some forum posts about this topic. It should be possible to install an application and grant the needed permissions if the application is installed with mxconfig and a StageNow xml file. I tested this in two ways: 1) manually copy the apk file and xml file (AppMgr to install the apk) to the device. Send script via Soti MobiControl with mxconfig xml file. The application is installed on the device with the needed permissions. 2) Building a Soti package with MC Studio. Copying the files to the device and include a postinstall script. The mxconfig command is in the postinstall script, same command as in 1). The application is installed, but doesn't get the needed permissions automatically like in 1). I tested differnt applications, same behaviour as mentioned above. Does anyone have an idea why this isn' working? Device is Zebra TC56, Android 7.1.2 with Update19 (Non GMS), Agent version 13.7.0.1031. Soti MobiControl version is 14.3.0.3144. Thanks.
Hi all, Is it possible to automatically grand all required permissions when installing an app via Mobicontrol? Some command that I can add to the packages?
Hi everybody, is it possible to grant permissions to access the device storage for an app which was not installed by SOTI Mobi Control? By default the app does not have any permissions. Setting the permissions via the device settings is not an option for us. Are there any solutions with "writesecuresettings" or anything else? Watchsettings did not produce a log entry. Simon
Hey Guys, Is there any chance to set up App-Permissions within SOTI on an Zebra TC20 Device? We build an App which sets Wallpaper, changes Notifications an stuff like that. We can execute all these settings remote with the sendintent command. Unfortunately the App needs the Storage Permission wihich is not allowed after installation. Can Soti, MCStudio, Script Command Set or anything else grant the permissions without User action? Thanks!
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
