Send Messages to Android For Work Devices (device owner)

Solved
EG
Edgar Gomez
coopebombas

Hello

We are testing some Motorola phones (Moto E4 Plus, G5, C,)with Android for Work Owner device . We have several issues and I would appreciate your comments on them:

1. With  lockdown applied, the status bar is not visible so users may not see the battery level, signal, etc. There is not option to show it.

2. When you send a message, it does not pop up the message but instead you have to open de Mobicontrol agent to see the message (the agent is shown in the lockdown)

3.In the devices (E4Plus, G5) that do not have physical buttoms (back, home, menu) it is not possible to exit lockdown.

I also found that E4Plus allows remote control. The others , remote view.

Motorola Devices

Thank you

7 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
7 years ago (edited 7 years ago)

I have tested tens of phones and tablets from Samsung, Huawei, Lenovo, etc. running Android Enterprise managed-device mode (i.e, device owner mode) for my customers, and basically have not encountered the same problems as you have now with Motorola models.

(1) In most case, the status bar is controllable.  There are options in feature control and kiosk mode payloads to configure whether to show/disallow status bar & its expansion, as shown in the following snapshots for MobiControl v13.4:

 

In some devices, disabling status bar is not possible. 

(2) Sending message results in message popped up in the middle of the screen (just the same as in generic Andorid or Android+ agent) in all cases.

(3) All such devices support remote view by design.  If a relevant remote control plugin (downloadable as .pcg from Soti web site) is pushed onto  the target device,  remote control is available. 

Unfortunately,  I still haven't the chance to test any of the Motorola devices you mentioned.  What MobiControl server version  are you using?  What about the Android version of the models?  Have you checked for any firmware upgrade on each model?   As Android Enterprise platform/API  are still evolving continuously  by Google (and  chased by EMM software and OEM hardware vendors), newer device models released in the last few months running 7.x and 8.x should have lower chances of getting the glitches that you have now. 

Solution