There's a new home for Articles. Find Articles on Our Product Support Page.
Hi, It is possible to gather the Location from an Android Enterprise enrolled device that is always in Lockdown? Agent Version: 14.2.0.1069 Supported APIs: SamsungMdmV57, Samsung RC v1, Samsung KNOX v3.3, Work Managed Device SOTI Version: 15.0.0.6019
The device 's log shows error as below HTTP UNKNOWN HOST EXCEPTION Please help me to fix this error I also provide my SOTI information as below : Current version: 14.4.0.4857 On premises server
Hello, We are currently using a mixture of Telecom Expense Management (TEM) and a simple HTML lockdown we've developed internally. The issue we are currently facing is since we have such various devices in our possession, developing a lockdown and system to issue it is challenging. We currently only have one lockdown profile and this has some issues with some models. We've discovered today that some of our devices have different application names for the dialer. One uses "com.samsung.android.dialer" and the others seem to use "com.samsung.android.contacts/com.android.dialer.DialtactsActivity" from my testing. Is it possible to include two package names in the lockdown but only show the one installed on the device? I'm not entirely against having another profile, but I feel like it might be more work in the future if we ever need to modify these profiles later on. Another issue that we've encountered is that the user cannot modify settings on the device. I believe in the past they were able to modify the device settings unless we checked the "disable settings changes" under the status bar in the lockdown menu. I could technically install the SOTI settings application, and will likely do so, but it does not have the ability to adjust the hotspot on the device and some of our users need access to modify the hotspot settings. MobiControl Version: 14.4.8.1043 Agent version: 14.1.8.1111 Models: S7, S8, S8+, S9, S9+, Note8, Note9, Note10, A50 (some models are AT&T firmware and some unlocked) OS: 7.11, 8.0, 8.1, 9.0, and 10. DA+ 95% majority, only about 10-11 devices enrolled with AE.
After our Android 9 devices have updated to Android 10 they no longer can connect to the mobicontrol server. The user receive a SSL Handshake failed error message. I have tried updating the self-signed root certificate from SHA-1 to SHA-256 but they still will not connect. Is there any way to resolve this? Thanks.
I have a Zebra TC57 running in lockdown mode and have disabled the status bar pulldown but now when trying to connect to a wifi network that uses a captive portal for authentication there appears to be no way to access the view/dialog to process the portal login. I would prefer to not have the users have access to the status bar if possible, but so far that is the only way I have been able to get this to work. Ideally the captive portal login would just pop up when detected like it normally would (like when connecting to WiFi at a hotel or restaurant) but it seems like something in the way lockdown works prevents that even with the status bar enabled. With the status bar enabled you have to see that the wifi connection has a small X on it and pull down the status bar to see the system alert, tap on it, and then the captive portal pop up appears for you to finish the authentication. Has anyone seen this before and/or is there a solution that I am missing to make this work?
I am using the Settings Manager and trying to limit which SSIDs these devices connect to, The issue i am having is that when we forget the SSID from within Settings Manager it does not actually forget the SSID... Agent Version: 14.1.8.1111 Using the latest Settings Manager Version.
Hello, I am running into this error while trying to upgrade an existing package on our Zebra TC56 devices. I did read some other posts and I can verify that we are upgrading an existing package with a newer apk, as opposed to adding a different package. I incremented the version number within the package builder as well. I haven't ran into this issue with any other packages before, and the apk launches just fine if I install it manually. The problem then is that the permissions are reset and there are two copies of the same program. Ideally I want to preserve our permissions, which should work if I can upgrade the same package, but it keeps erroring out. Any suggestions would be welcome. Thanks!
I want to lockdown and not show the status bar, but I also want to show the wifi signal/connection, battery, etc settings gained by SOTI from Zebra. If I have Zebra Android Enterprise devices is this possible? Sorry should have been more specific. They didn't want the bar. Was trying to add to the actual lock-down HTML. Sorry I was not more specific. Thanks
Hello, Recently we've been seeing S10e devices enrolled in MobiControl are rebooting into recovery and not allowing the phone to boot without doing a factory reset. Are there any known issues with the S10e and MobiControl? Or any solutions to this problem?
Hello Can you help me. My company has developed a delivery app deployed oncustomer sites with SOTI. Our application is not able to "dicuss" with Waze to send a delivery adress that WAZE must open to provide the best way to driver. Question : is there any sandbox feature implemented in SOTI MC ? If yes can I disable this feature ? Thx. Steve.
Is there a way to script "clearing" the cache of an app by using Mobi. In the example, we need to clear the app cache of google Maps however the only way I know to do this presently is to go to settings, then app, then google maps and then click clear cache. This works fine for a few devices but I may need to do it for hundreds. Any suggestions?
Hi, Has anyone got a list of which filter criteria work with which OS? I'm trying to use a filter on Android 4.4 with MobiControl 13. I've tried 'HasApplication' and 'Custom Data' but neither of them work. After 'HasApplcation' failed the first time, I created a custom data that was a boolean value to identify devices that had the application or not. I though this might work in teh filter criteria, but it doesn't, all I get is "Internal Server Error". Thanks in advance for any replies! Adam
Yesterday the upgrade made android terminals (Honeywell VM1A) unusable. No issue neither with Windows CE devices nor with Windows Desktop devices. The upgrade from the old agent HoneywellMobiControl1400NewGen_1579 to the latest available HoneywellMobiControl1417NewGen_1117 led to the following problem: - the terminal remains locked on boot on the honeywell logo and does not arrive when the lockdown is loaded. We tried to install the old agent in a brand new device but it doesn't get the profiles from the server, they still remain pending; just remote control works. We have not proven the behavior of a brand new terminal with the new agent 14.1.7. We have seen that a non-branded version 14.1.8.1111 default is also available but we haven't tried to install it yet. Is there any issue on using the non-branded version? Is it possible to revert the Add Device Rule to use the old agent? Maybe new rule? Do you have any suggestions? Thank you really much in advance.
Is it possible to systematically create a text file with a device attribute such as serial number to a device folder? we use SOTI v13.4 soon to move to V14.4. The devices will vary by model but should be on android version 6 to 9.
Hello, I have around 250 Honeywell CT60 units. When adding com.android.settings to blacklist, the unit will not start up again after I turn it off. It is stuck on Honeywell start/boot screen, and I have to Factory Reset the unit to get it on again. I blaclist many other apps, but it only crashes when I add settings to blacklist. My mission is to prevent the user of the unit to access settings on the device. I used this controll earlier, but after i updated Soti to the latest version, the CT60 crash. So its working on the unit, but not on the version of Soti im running I guess Any idea what to do? Tried on Android 7.1.1 and 9. same result. Soti MobiControl 15.1.0.3413
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.
New contributors starting their journey. Should have more than 250 points.
