No Matches Found!
Try with a different search term
Hi,
We have a couple of users experiencing battery issues recently, which they believe is related to MobiControl. Are there any known issues? We are using the latest agent version. The phones in question are Samsung Galaxy S5 Minis
Their MobiControl runs automatically every time they turn on the phone, is there a way to stop this and only have it running when manually opened?
Thanks
Could you elaborate more clearly what the battery issues are? What is the standby time for a fully charged S5 Mini before and after MobiControl is used? Is similar problem found in other device brand/model?
It is normal that MobiControl device agent is running in the background when a device is powered up, and this itself normally should not significantly reduce device standby time. However, deploying power hungry policies to be run by the agent can make a big difference. What policies (profiles, rules and advanced configurations) have been deployed to the S5 Mini's?
Hi Raymond,
Thank you for your reply, The user in question has said that since the agent was installed his device will not last a day charged now, when before it would last more than that quite easily.
As far as I'm aware the same policies have been deployed to these devices as to others, but is there any specific rules or configurations what are power hungry? I can then check them. If there is a way to export the information to send to you please let me know and I'll send them across.
Thanks!
Some of the MobiControl policies that can seriously affect battery life include:
- GPS hardware enforced always on with feature control policy
- data collection rule with very frequent collection schedule (every 2 or 5 minutes, say)
- file-sync or package deployment rule set to frequent update and always overwrite old file/package of the same name
- update schedule in advanced configurations set to very short interval compared to the default 2-hour
- new feature control policy to disable doze mode on some supported Android 6+ devices
etc.
Hi Raymond,
Just looking at our rules, we don't actually have any Application Catalog, File Sync, Device Relocation, Data Collection or Alerts rules. We just have Add Device rules. Could this be what is causing the issue? I can't find any settings you mentioned to check...
Sorry if this is a tad confusing.
Tom.
What profile payload(s) have been deployed to the device? Doze mode and advance configurations are also not rules. Have you checked them yet?
You might also need to check this device log from the web console to see if the server is frequently trying to connect to the device.
