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.
Good morning i have several hundred devices (Honeywell EDA71) which have been enrolled using the afw#mobicontrol method. i have added an package and i am getting the File i/o error and it wont install. i have managed to remote to one device and manually turn off google play protect and the app then installs when a force package reinstallation. is there a way to turn this off via a script as i cant manually remote to each device to turn it off thanks Daryl update: i have found this in another thread but it does not seem to work writesecureprofstring DeviceFeature DisableVerifyApps 1 apply featurecontrol
Hi! I just wanted to share a solution for bypassing Google Play Protect problem when installing your apps. We had this problem for one of our apps but we came up with the following workaround: Create an Application Run Control profile and set it to blacklist: com.android.vending (Which is the Google Play store) Also create a Feature Control profile with the setting for "Disable Verify Apps Enforcement" ticked. Have the Application Run Control profile assigned to the devices as long as they don't have the correct version/not even installed of the app which are getting blocked all the time. So far this seems to work but we can't really tell if the app gets totally blacklisted in the future which will make Play Protect to actually delete the app but I have not heard of anything like that before.
I am wondering if anyone has found a way to not only "ungray" the setting under Settings > Google > Security > Google Play Protect so that it can be toggled, but also actually toggle it OFF. SOTI provided two methods for doing the first item, to re-enable the setting so that it can be manually toggled. The methods are actually the same thing (a feature control) done two different ways: (1) Send script command: writesecureprofstring DeviceFeature DisableVerifyApps 1 apply featurecontrol (2) Create / assign a Feature Control that has "Disable Verify Apps Enforcement" checked. In my experience, these have the effect of re-enabling the toggle on the GPP setting, but leaving the setting toggled ON. It then has to manually be toggled OFF. I have certain apps that are mission-critical and mass-deployed, so touching each device to turn off GPP scanning for first deployment and subsequent app updates is absolutely not a feasible option. So far, SOTI Support has been unable to provide a means to programmatically toggle that option OFF. My other rather large challenge with this is, under AEDO, I've found that a Lockdown Screen profile has the side effect of toggling GPP back on, and graying it back out again so that it once again cannot be toggled off. SOTI says that this is the "expected behavior," to which I respond, WHY? Perhaps I am missing a pertinent concept here, but to my mind it is ridiculous to have a lockdown screen profile that also has the effect of locking GPP scanning on. These corporate users need app installations and app updates -- and those need to happen while the lockdown screen is in place. I've found that if the lockdown profile is already applied, the above two methods will have the effect of "ungraying" the GPP option so that it can manually be turned off. BUT if the lockdown profile ever is re-applied, or refreshes itself due to an editing change (such as perhaps adding an entry for whatever new app(s) are intended to be applied), then GPP is again turned on and the toggle is grayed out. This is very frustrating. I need a way to turn GPP scanning off, and KEEP it off, until I (and only I) tell it that it can turn back on again, Any advice would be appreciated. Thank you, Mark
Hello everyone, I encounter some issue (as some of you I have seen!) regarding the deployment of an APK on a AEDO device. The profile stay in a "Install Failed" status (Failed to Install (File I/O Error)). On the device I have the following message from the Google Play Protect : If I click on "INSTALL ANYWAY" the app is correctly installed. If I deploy a FC profile with the "Disable verivy apps enforcement" feature : I am able to manually disable the GPP Scan : This is the same thing / result as if I sent the following script on the device : writesecureprofstring DeviceFeature DisableVerifyApps 1apply featurecontrol If I manually disable the "Scan device for security threats" option, I can deploy my APK via my profile without any problems. Also, I am able to install my APK directly on the device from a USB driver for example. Question : Is there a way to disable the "Scan device for security threats" with a script or a trick ? For now, the solution is to blacklist Google Play via an App run control profile. But I use a managed Google Play store and I need Google Play on the device... The complete solution would therefore be : 1/ Deploy App Run Control profile 2/ Deploy APK 3/ Revoke App Run Control profile Quite tedious.... Thank you !
Hey Guys, i need Help to write a Script for disabling Google Play Protect. I have get following URI String by using the Script "watchsettings on" Custom log (URI:content://settings/global SETTING:package_verifier_user_consent VALUE:-1) How can i write a Script for Honeywell now to distribute it via Profile on alle Honeywell Devices? I tried follow Scripts: Script was sent to device (sendintent URI:content://settings/global SETTING:package_verifier_user_consent VALUE:-1) Script was sent to device (sendintent -a "Intent://settings/global SETTING:package_verifier_user_consent VALUE:-1") Script was sent to device (sendintent -a "intent:content://settings/global SETTING:package_verifier_user_consent VALUE:-1") Script was sent to device (sendintent - b "content://settings/global SETTING:package_verifier_user_consent VALUE:-1") On alle these Scripts Nothing happend, the Google Play protrect was still enabled. Can anyone 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
