Is there a way to see where memory is being used?
Do you have Fusion, RxLogger, or Enterprise Home Screen logging enabled? I think Fusion logging is likely the biggest culprit but it could be either of the other two as well depending on how the logging is configured.
We haven't enable any of those.
All of the devices were enrolled and configured at the same time but some of the devices are full but other still have some space left.
Are you looking just in /sdcard/ ? There are other directories like /enterprise/ that are liable to contain files. Beyond that, 5 GB still seems like a lot of storage to already be consumed on those devices after enrollment.
I've only been looking in /sdcard/
I'll take a look at /enterprise/
The device have got European maps on for Co-Pilot, the maps alone are 5GB.
Detailed statistics of memory/storage usage of each app are not gathered by Soti device agent.
If you or some of your colleague are Android programmer, the easiest to get what your want is to modify some open-source memory manager app to export required data to XML/INI file for custom data collection back to your MobiControl server.
Found that the issue is with Google applications updating.
I know I could use a NON-GMS version of the OS but the devices are already with the customer.
Is there anyway to disable the applications that are installed as default and uninstall the applications?
Youtube is one of the applications that is taking up some space.
Yes, you can use Zebra's MX layer (distributable via SOTI with mxconfig script) to individually disable apps based on their package name/ bundle ID or you could use the Application blacklist under feature control in SOTI. I would suggest starting with the SOTI route since it is more straightforward and integrated within the console UI.
Zebra also has a global setting for disabling all GMS features on GMS devices but that is limited to their Helios devices like the TC57 so I don't believe the Atlas based TC56 has support for that.
Thanks for the response.
I don't want to use an application run control as we're having issues where the device gets stuck on the boot screen.
We were advised by Zebra and Soti to remove this to prevent this issue going forward.
Could you provide anymore information on the MX layer please?