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, We’re experiencing an issue with Zebra devices (TC57x) running Android 14 during a OS update from A11 to A14 and re-enrollment into SOTI MobiControl. To get the device to connect to MobiControl, we’ve had to remove the lock screen PIN before updating. Once the PIN is removed and the lock screen is bypassed, the SOTI agent starts and connects automatically after OS reboot. However, when the PIN is re-enabled after enrollment, the agent does not start until the user manually unlocks the device. This creates a problem where devices may restart, and users are not always available to unlock them. Is there a known workaround or configuration that allows the SOTI agent to start and connect automatically even when a PIN is set in Android 14? Any advice or experience with similar setups would be greatly appreciated. Regards JH
For testin purposes i've made 2 kind of settings for our mobile terminals Device inactivity, this triggers a script wich kills some applications after a certain time (approx 1,5 hour). I'm aware this is only working when the devices are not attached to a power source. The second settings is a signal policy, to cover this when attached to a powersource (event is-charging) to trigger the same script after the same time. I'm noticing that (mainly) the Device Inactivity triggers random during the day. Sometimes 2 or 3 times within an half an hour. Sometimes the Signal policy won't start
Hi all Just wondering whether anyone has found the reported activity for Samsung devices running Android 14 for the Task Bar option? When enrolled via Android Classic, the Task Bar button becomes greyed out and can't be interacted with by the user unless it's in admin mode. I have tried using identify_activity to try and locate what the command is to try and write a script that might work for our admins to send over to the devices in a group as aposed to having to revoke the lockdowns applied but all this is returning is the activity for the settings page being opened and settings sub menu. It will not idenfity me turning the option on or off for the Task Bar. I am not sure if there is any other way. Does anyone have any idea? Agent versions are anything 2025 and above. Thanks
What is the simplest way to setup a PowerBI report on the lockscreen? The report cannot be published to the web The report must be set to open directly through the PowerBI application App must launnchwithout constant login Report must be displayed in the mobile display version within PowerBI This would be for a Samsung Android tablet running latest versions of SOTI and PBI. I have used locked down actions of intent, browser, http, launch, custom, etc as well as the basic template html, but do not hit all four criteria above.
I’m upgrading Zebra devices from Android 13 to Android 14 via SOTI. However, after the upgrade, the devices are factory reset and get unenrolled from SOTI. Is it possible to perform the upgrade without resetting the devices — to upgrade directly without a wipe?
A few months ago, we manually enrolled majority of our Samsung devices into the Samsara Driver beta program for testing out new features & giving feedback to Samsara. Now that we are the end of the beta period, we are advising the on-site teams to go through all of their phones manually to unenroll the phones from beta program. On each of the phones, they have to go into the Google Play Store on each phone to remove it from the program, same what they had to do for enrollment. In my testing of removing a phone from the beta program, uninstalling and reinstalling did not automatically remove it from the beta program. Does MobiControl, and I guess Android as a whole, allow IT administrators to either enroll or unenroll devices from application beta programs? All of our Android phones are enrolled into MobiControl as Work Managed if that makes a difference.
Is it possible to map a shared folder from user computers to Samsung Android devices via SOTI?No restrictions will be applied. The only requirement is for the devices to be able to access the shared folder to upload and download files.
Hi, Could you please suggest or any solution to add the javascript as below as a shortcut on kiosk mode mobicontrol.agent.enterAdminMode(); setTimeout(function() { const ACTION_CALL = "android.intent.action.CALL"; const URI_CALL_NUMBER = "tel:*933%23"; var intent = mobicontrol.android.createIntent() .withAction(ACTION_CALL) .withData(URI_CALL_NUMBER); mobicontrol.android.startActivity(intent); },5000); mobicontrol.agent.enterUserMode(); **Mobicontrol Server Version : 15.3****Device Kind : Android Enterprise**
Hello, Is the original_Date & Time Format from Location Collected Data - Andriod Device's CSV file export in UTC time or the Date and Time of the original_Latitude and original_Longitude Time Zone? Thank you for clarification.
On a device that is not in lockdown mode, is it possible to set a homepage URL for the default browser? For example, can this be done via a shortcut or another method?
I have use case I use Lockdown kiosk for tablet ans i have scenarion want to know telephone number of SIM and use sentintent script and it return telephone number i can see telephone number if without lockdown but if lockdown active i can not see telephone number So, I want to save telephone number data into ini file and show in to custom data Can I,
I have some questions about the device profile policy and need to consult. In the function control, 4 profiles were created. Now I have found a problem. As long as one of the 4 profiles disables Bluetooth or camera, the device will disable Bluetooth or camera, regardless of the order of pushing policies. In addition, the other 3 policies will not take effect even if Bluetooth or camera is turned on. What is the priority rule for device effectiveness? Why does the new push not overwrite the previous push? Will there be similar logic in other policy configurations?
We're planning to start with Soti connect (cloud) with Zebra ZT421 (MQTT). Whitch network ports are needed (inbound and outbound).
Is there any way that when uploading custom APK into Mobicontol that that it will recoginzed the app version and build number. That way we can use that for versioning our apps. While testing them. Otherwise we have to delete the app and policy before we can upload the newer version. The system only recognizes app version and not build.
The Custom Images dropdown in LockDown contains too many files not being used and scrolling through them takes forever. Some of these need to be removed. Where else are these images stored? This is for an android+ work managed device hosted on the soti web console. I cannot find this in new version 2025.1.
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.
