Aurélien Schelcher
Jun 08, 2016
8:18 am

MDM application in stopped state after a while

Hello,

 

My company is developping a MDM application for our customer devices. Until now it was working great. It was mainly installed on Samsung xCover 2 devices.

This app is using Google Cloud Messaging system allowing us to push order to the app from our cloud solution. Then the MDM app execute actions using Samsung SDK (install app, start app, stop app, wipe data,...) The application regularly ping our server to check that every thing is ok and will update our applications if needed. We use a boot receiver and then an alert manager to execute it regularly.

 

We started to use Samsung xCover 3 devices a few month ago. And now, after servale days/weeks of usage, devices started to have some issues. The application is not communicating with our cloud and we cannot send push command anymore using GCM.

We suspect that the application is in stopped state because it don't receive the BOOT_COMPLETED broadcast and the GCM push messages.

 

Do you have any idea why it happens ? Because we are now stuck on multiple devices as we cannot communicate with them...

 

Thanks in advance,

 

 

 

 

 

Similar topics

No similar topics found.
Kamil Kaszubski
Jun 08, 2016
9:09 am

Hello,

can you please check if xCovers 3 are running Android L? Probably Smart Manager is killing your app because it is not running in foreground.

In order to avoid such behavior you can use the fact that Smart Manager will not kill app without launcher attribute - you can create app which contains only service receiving GSM notifications and launching your MDM app to perform desired actions.

On devices with Android M you can also use below API in your MDM app to add it to Smart Manager's exception list.

setAdminRemoval(false);

Best regards

Aurélien Schelcher
Jun 08, 2016
11:52 am

Hi,

Thanks for your reply.

xCover 3 devices are in 5.1.1 yes. A few are still in 4.4.4 but I dont think we have issue with those yet.

Is there any way to confirm that it is Smart Manager that is stopping our MDM app ? (In logs or whatever ?)

An application without any launcher will never be "stopped" by the system ? (except throw settings I guess, right?)

If we set the admin removal to false, it will add itself in the exception list ? Or is it another command to do ?

Thanks,

Kamil Kaszubski
Jun 08, 2016
2:17 pm

Hi,

It may be confirmed with logs captured when your app was killed.

Yes, Smart Manager will not kill app which does not have launcher activity.

Yes, Smart Manager on devices with Android M will skip apps which have set Admin Removal flag to false.

Best regards

Comments

Could you tell me how I can do an app without having launcher activity?

Thanks

Ana LlamasOct 16, 2017 at 3:17 pm