Enabling tethering on Android Mobile Startup

I've been up and down rabbit holes looking for a solution to this issue. We have Android mobile phones with the Soti application for the drivers to use in our company. The drivers also have an Intermec CK70 device they use to scan barcodes. We are looking to get these "pads", as we call them, to connect with the Android phones via mobile hotspot for transmitting data.

We have the devices locked down through SOTI so the drivers have no access to settings configurations. We are in need of some way to have the mobile hotspot ALWAYS on (without rooting the devices) but, it seems once the phone is power cycled the hotspot turns off and stays off by default.

Edited 4 years ago
Android Scripting
ANSWERS
MD
Matt Dermody Diamond Contributor
4 years ago (edited 4 years ago)

If there was a native Android Enterprise management API for enabling the Hotspot on a device it would likely be exposed via the Feature Control options in SOTI. 

Upon inspection of a recent MC version it does not appear that particular option is available. You can control whether or not the end user has the ability to manually administer the tethering settings themselves with the first option, but no option to actually force it to on. 

The next place I would typically look if a configuration setting is not natively exposed by Android Enterprise is at the OEM specific configuration extensions offered by the Manufacturer. In the case of Zebra devices for instance I can see that there is a MX configuration setting specific to Zebra devices that can be distributed via SOTI in order to force the Hotspot to On. I cannot confirm whether or not this will persist through a reboot but it does at least look to be in the right direction.

This of course is specific to Zebra Android devices however. You would likely need to check with Honeywell OEMConfig to see if any equivalent settings exist for your Honeywell devices. Or if you have a different brand of mobile phones you'd have to check with the specific manufacturer.

Note that these extra configuration options exposed by enterprise manufacturers like Zebra and Honeywell are one of the big differentiators of these devices over standard consumer grade Android devices. Android Enterprise defines the bare minimum set of management capabilities for Android and then companies like Zebra and Honeywell expand beyond that as there are more granular and specific requirements for dedicate devices in enterprise environments. 

Beyond the OEM specific configuration options you might potentially be able to use writesecuresetting scripting if you're able to capture the secure setting value you're trying to enable. The usage of that scripting has been more restrictive in the world of Android Enterprise however. 

CA
Cody Asfeld
4 years ago (edited 4 years ago)

Thank you for the reply!

I may have misworded slightly, however. The devices we wish to have the hotspot activated on are not the Honeywell or Intermec devices. We wish the hotspot activated on our Android Samsung Galaxy A11, and in turn, have the CK70 devices be connecting to the hotspot on the Galaxy phones.

Do you have any insight on how this could be achieved? I seem to be more aware now how these phones do have these configuration settings pretty locked down.

RC
Raymond Chan Diamond Contributor
4 years ago

As you are using lockdown menu on your Android devices, you might consider adding extra lockdown item to allow limited configuration of Wifi Hotspot using item such as

   Launch://com.android.settings/.Settings$WifiTetherSettingsActivity

Please note that different Android device brands/models  or firmware versions may have different name, or even no equivalent activity, as the above-mentioned activity.

Also, depending on the specific UI design in your device firmware, using the above approach may expose security loophole(s) for device end-user to access other settings pages/tabs.  Please check before using this approach on production devices.