Locating Android devices

Setting up and carrying out the tracking of Android devices using Lost Mode and location services

Last adaptation to the version: 2.4 (04.2025)

New:

Requirements updated
Section ‘’'Activation in profile'‘’ removed and replaced by corresponding wiki link for prerequisites
New section: Lost Mode
Screenshots updated

Messages can be added to Localization
A corresponding entry in the Auditlog is added

Last updated:

Requirements updated

notempty

This article refers to a Beta version

Requirements

In order for Android devices to be located via the portal, various requirements must be met:

For locating, it is an enrolled Android device in the operating modes COBO up to Android version 11 or COPE up to Android version 13
For Lost Mode, it is an enrolled Android device in the operating modes COBO from Android version 11 or COPE from Android version 13
The Android profile connected to the Android device has the localization function activated
On the Android device, the Securepoint app MDM Toolbox with the plugin MDM Location was granted access to the device location

Notes

notempty

There is no constant, but a targeted localization
A message appears on the device indicating localization has occurred (no silent localization)

notempty

The location tracking process is logged in the audit log

Available under

Locating

Granting permissions on the device

On the device, the app must be opened once to grant the following permissions:

Confirm privacy policy and licence of the app MDM Toolbox and the plugin MDM Location Plugin (Fig. 1- 5)
Allow localisation (Fig.6 - 7)
Allow background activity (Fig.8 - 9)


1.	2.	3.


Abb.1	Abb.2	Abb.3


Abbildungen

Fig.1

Fig.2

Fig.3

Fig.4

Fig.5

Fig.6

Fig.7

Fig.8

Fig.9

Fig.10

Lost Mode
An Android device ‘’'cannot'‘’' be set to Lost mode if: the Android device is already in Lost mode Lost mode has been manually ended in the last 12 hours there has been a password reset from the Android device in the last 12 hours the work profile of the COBO or COPE operating mode is paused
Locate under Mobile Security Android Devices choose device / show details tab Operations
Activate Lost Mode	A pop-up window appears in which a message can be entered, stating the company, address, e-mail address and telephone number The message appears in the Auditlog
	The following then happens on the Android device: Lost mode is activated Device starts to ring Two buttons appear: ‘'My device’' & ‘'Device found’' If nothing is done and the device continues to ring, the location is sent after 5 minutes Interaction with the device ‘'My device’' button the device stops ringing and after it has been unlocked, the lost mode is deactivated in the portal the device does not send its location ‘'Device found’' button the device stops ringing and remains locked by the PIN the device sends its location after 5 minutes

Locate
Locate under Mobile Security Android Devices choose device / show details tab Operations
Locate	A pop-up window appears in which a reason can be selected: Device loss, Employee left, or Other reason If Other reason is selected for Reason, a justification must be entered in User-defined reason The message appears in the Auditlog	The pop-up window with the message text field
	The Confirm button locates the device and displays the current location on a map	Display in the portal
	A message appears on the unit indicating that the location has been made

Auditlog

Under General Auditlog the localization actions are displayed with the corresponding message for each action.
These auditlog messages are listed with "Location".
For this purpose, the message entered above is also entered. This thus serves as justification for the localization of the Android device.
Likewise, the localized Android device is displayed.

notempty

The auditlog displays entries from the last 90 days. Older entries are automatically deleted.

The Export button downloads the auditlog as a .csv file.

Requirements

Notes

Locating

Granting permissions on the device

Lost Mode

Locate

Auditlog