Download the Android Enterprise device agent from the Google Play Store or the MobiControl Android Enterprise Agent Downloads page.
| MCMR‑43937 | The SOTI MobiControl agent became stuck in a connecting state and did not reconnect. |
| MCMR‑43949 | On some Samsung devices, remote control sessions could not be started. |
| MCMR‑43962 | App installations through XT Hub were delayed when devices entered low-power states. |
| MCMR‑44008 | On dual-screen devices, remote control sessions did not display correctly. |
| MCMR‑44065 | Calls Missed, Calls Dropped, and Calls Completed fields remained empty in the Data Collection policy on Samsung devices. |
| MCMR‑44067 | In some time zones, scheduled scripts and package installations did not run at the correct time. |
| MCMR‑ 44074 | In Lockdown mode, push-to-talk and media key presses from USB-C accessories were not recognized. |
| MCMR‑44478 | The clearappcache command was not clearing the app cache on Zebra devices. |
| MCMR‑ 44644 | On devices with names containing special characters, the agent failed to reconnect to the Deployment Server after the agent was restarted, or the device was rebooted. |
| MCMR‑44690 | On Sonim devices, mouse clicks during a remote control session did not register in some applications. |
Download the Android Enterprise device agent from the Google Play Store or the MobiControl Android Enterprise Agent Downloads page.
| MCMR‑44443 | In Authenticated Lockdown mode, users were prompted to obtain additional permissions during Microsoft Entra ID sign-in, preventing them from completing their login process. |
Download the Android Enterprise device agent from the Google Play Store or the MobiControl Android Enterprise Agent Downloads page.
| MCMR‑27432 | On Panasonic devices, the agent crashed when retrieving battery information. |
| MCMR‑41900 | During COPE enrollment, Terms and Conditions content with HTML formatting was not displayed correctly. |
| MCMR‑43565 | When sending a message to a device using the "Until User Presses OK" option, the message was automatically dismissed before the user could respond. |
| MCMR‑43587 | On some Android 14 devices, remote control sessions with audio recording did not start correctly. |
| MCMR‑43664 | Apps that had been closed or force-stopped were still reported as running in the foreground by the foreground app tracking JavaScript API. |
| MCMR‑43793 | Packages were not installed correctly when a pre-installation script was configured. |
| MCMR‑43806 | Apps that were also configured as device launchers could not be launched from the Lockdown Home screen. |
| MCMR‑43833 | Devices became inaccessible after the native Settings app was blocked using Application Run Control. |
| MCMR‑43955 | Tapping the “Free” button in the Google Play tab of the App Policy did not open the Google Play store on some devices. |
| MCMR‑43978 | App configurations were being reapplied to devices even when no changes had been made. |
Download the Android Enterprise device agent from the Google Play Store or the MobiControl Android Enterprise Agent Downloads page.
| MCMR‑41690 | In Shared Device Mode, the shared device account was removed from the device when a user logged out, preventing subsequent users from signing in. |
| MCMR‑43607 | On some devices, the SOTI MobiControl agent did not start correctly after the device was restarted. |
Download the Android Enterprise device agent from the Google Play Store or the MobiControl Android Enterprise Agent Downloads page.
Android 16 devices are now officially supported for Android Classic, allowing administrators to manage and configure all current Android Classic features in SOTI MobiControl.
Utilize device location data to have greater visibility on your devices’ locations to have better operational control and decision-making:
You can now manage the device screen brightness to have better control over battery life and device visibility in different working conditions:
Leverage deeper management controls on your Castles devices for enhanced security and seamless device administration:
| MCMR‑42676 | SUNMI devices did not enter sleep mode when idle in Lockdown mode. |
| MCMR‑43189 | On some landscape-oriented tablet devices, annotations were misaligned when using the screen drawing feature during remote-control sessions. |
| MCMR‑42926 | On some Android 11 Zebra devices, the "MXMF is loading, please wait" screen did not dismiss automatically after restart when Lockdown mode was enabled. |
| MCMR‑42704 | On some devices, App Policy downloads and installations were delayed or did not complete when the device was in sleep mode. |
| MCMR‑42715 | On Zebra devices, incorrect password attempt counts did not reset after the device was wiped using an Authentication profile. |
| MCMR‑42897 | Remote control sessions displayed a truncated screen on devices using the Rockchip rk3588s chipset. |
| MCMR‑43113 | The SOTI MobiControl Android agent crashed when a user tapped the pending action prompt to enable location permissions. |
| MCMR‑42840 | The agent failed to initialize correctly on Point Mobile devices due to an outdated OEM library. |
