What brand(s) or model(s) of devices have you deployed? And what are the version and build numbers of your Android Plus device agent(s)?  What feature control options did you deploy to your devices?

Feature-Control option mentioned at https://discussions.soti.net/thread/script-for-turning-on-gps-location-service/  is for Android Enterprise devices only.

"writesecuresetting"  itself and supported arguments are always specific to particular OEM brand or even to specific device model(s). What was discussed at https://discussions.soti.net/thread/script-for-change-location-mode/ was for some Zebra devices, and your devices are probably different.

Hi,

These are all Samsungs, S&s and S8s. Agent is 13.5.0.1327 . I don't know the build #.

Feature Control options:

Disable NFC

Disable GPS Mock Locations

Disable Factory Reset

Block OS Upgrade

Enforce GPS Availability

Disable Installation from Unknown Sources

Disable removal of Mobicontrol Agent

Prevent Uninstallation of Managed Apps

Disable Doze Mode

Disable Portable WiFi Hotspot

Disable Incoming SMS Messaging

Disable Outgoing SMS Messaging

Disable Incoming MMS Messaging

Disable Outgoing MMS Messaging

Disable addition of New Email Accounts

1327 is the build number of your device agent.  Could you please give details/screenshot of how and what battery-saving mode has been set on your device?

"Enforce GPS Availability" feature-control option is the right one to force GPS hardware always on.  However, your problem may be due to the battery saving mode configured, which probably has higher precedence in your device firmware that causes the GPS hardware to be off even if the feature-control option has been enabled.  Another possible cause is that your device agent gets pre-empted in the battery saving mode.

Frankly speaking, I am not aware of similar problem on Samsung devices running earlier Android version.  However, I can't rule out such possibility, especially for newer Android versions which are more aggressive in power management.  What is the Android firmware version of your device?  I'll see if I can duplicate similar problem in my Samsung test device(s) before I can start finding any possible solution. 

My gut feeling is that you likely need to recall your devices unless you can silently start remote control session on them.  The battery saving mode should have been tested out thoroughly  (and possibly disallowed) before deployment to remote sites.

This isn't an isolated case, we've had dozens of phones do this. I even have old threads that were abandoned about the same issue. SOTI support wasn't able to resolve. What we do is set the GPS mode to High Availability (required for some of our apps), and then the problem arises where the mode sets itself back to Battery Saving, and the other modes are greyed out. The only solution I've seen is to uninstall and reinstall Mobicontrol, which tells us that Mobicontrol is somehow locking out the setting. However I'm looking for a fix that can be deployed remotely.

EDIT: Perhaps a script that will reinstall Mobicontrol?

The quality of  Soti support services you receive can vary significantly and sometimes depends on your luck.  That is my personal experience in the last few years.

You still haven't given any details on how and what you set your so-called "battery saving" mode, nor have you stated your Android firmware version.

My apologies.

My method for setting the GPS Location Mode is done manually when we provision the phones, and they are set to High Availability. When I say "manually", I mean going into the phone's Settings, Location, and choosing "High Availability."

The problem is the phones are setting themselves to Battery Saving and greying out the other options. Battery Saving causes issues with some of our corporate apps.