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.
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, we have mobicontrol in version v 13 0 34 54 we used many zebra TC75X on android 7 with client mobicontrol on version 13 6 0 1476. Each time we install an app the user need to ACCEPT permission ... I would like to automate this, i've find in doc of mobicontrol the script for android + : afw_set_permission_policy grant I've include this inside the package builder (pre install script), add my apk inside. add package inside a profile and add profile to a device. But each time the permission appear on screen and user need to ACCEPT ... If I look inside the log of mobicontrol i have this entry: Script command is not supported by device (afw_set_permission_grant_state) Must i update the client or ? Anyone can tell me how i can automate this because we have many device ? thanks for your time
Hello everyone, I am trying to grant WRITE_SETTINGS permission to camera app on a Samsung device enrolled as Work Managed device (AE). I am using the command afw_set_permission_grant_state com.sec.android.app.camera android.permission.WRITE_SETTINGS allow but the permission does not change. What am I doing wrong? :)
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?
When I set up a data usage monitor under Rules > Telecom Expense Management, the newer Samsung devices require an elevated permission for the device agent to monitor data usage. This is under device settings which are not accessible as all the devices are heavily locked down, single-use devices. Is there a way to enable the permission en masse through Mobicontrol?
I have an enterprise B2B application that I distribute to devices via SOTI Package in a Profile. SOTI is properly installing the APK and is also now automatically granting the required permission (just storage) which is a nice feature recently introduced in this agent version. The issue that I'm now facing is that the app itself will no longer launch and I get a permissions related toast message error as soon as I try to launch it. The same version of the application works under the following circumstances: AEDO Managed Zebra MC33 running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.1.3.1587 and the 13.6.0.1567 Android Enterprise Agent.- App runs correctly AEDO managed Zebra VC80x running Android O (8.1.0) with LifeGuard 12 on SOTI server 14.2.2.1170 and the 13.6.0.1622 Android Enterprise Agent - App crashes on launch with permissions error. I'm trying to isolate my variables as much as possible to identify the root cause of this problem but I'm starting to think that it has to do with the automatic permission granting of the new agent version. Is there any way to disable this feature so that I can manually enable the app permissions? The forced upgrade to a newer agent version seems like a pretty frustrating side effect of leveraging Android Enterprise with a Play Store distributed agent. Is there any way to lock in a specific agent version for AEDO enrollment if it does end up being the Agent causing the problem?
Is there a way to run a script on an Android device and see what device permissions are needed for an app? I want to enable all the device permission to on for Soti Surf so the device isn't prompted to enable those settings. 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
