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?
I ran into an issue with an S9 being upgraded to Android 10. It was doing the same thing, rebooting into recovery.
It turned out to be my "Application Run Control" settings, as I had an entry blocking %settings%, which would crash the Keyguard process right after the device started, which would trigger recovery mode.
I removed that entry from my Application Run Control list, and it was fine, though I did need to factory reset the device as well, as it would reboot before Mobicontrol could launch and get the new profile installed.
Do you have problem in ALL your S10e dervices or only to SOME?
Has there been any recent update to either the device firmware, device agent or MobiControl server?
Its happened on most of our S10e devices so far. Both on Android OS 9 and 10 as well as Android+ enrollment and Android Enterprise enrollment.
We recently did a server (and deployment server) upgrade to the latest web console version. It's happened to devices that were enrolled before and after the change.
Device firmware updates are blocked. Agent version is the latest.
Tyler,
Are these multi carrier or are you just a one carrier shop? If you are multi carrier are you only seeing it with one carrier compared to another?
Thanks
Jason
So all the S10e's we have are on VZW and we have not see this type of behavior. However I have just a few AT&T devices ( S8 and S9 ) that all of a sudden will do updates and get stuck in safe mode and will not come out of that mode unless we do a full wipe.
Interesting. Sounds like a similar issue
Our devices use Bell Mobility, which I believe use the same hardware as AT&T.
Hi Tyler,
Since there are problems for most but not all of your S10e devices, you could also rule out possibe cause(s) based on pattern of the devices (e.g. firmware version, libraries included, agent version, policies deployed, etc,) that are OK.
Do you have similar problem for devices of other brand/model(s) enrolled on th same server?
It's looking like that might be our issue as well, I had com.android.settings in the application blacklist. Removed it and so far so good.
FYI, I was given a command to block settings in a script:
manualblacklist add com.android.settings
manualblacklist on
Hi Tyler,
Thank you for advising us that you have found a solution for your post. Please let us know what reply you found to assist you in solving your inquiry so others may benefit from this information by selecting "is solution".
Regards,