System Events Captured

Updated on Apr 27, 2026
Published on Jul 28, 2025

2 minute(s) read

Article summary

Applicable to Administrators

Android Capture sends two types of events to the administrator:

Summary of the status and users.
Events performed by users on their Android device. The following table lists the events that are captured by the app:

Event Name	Event description	Body Text
Install Event	The event is triggered after the user successfully installs the application and sign in for the first time. The event is not triggered if the user doesn’t sign up to the app. The event is triggered again if the user re-installs the app.	Android Capture Installed (xx.xx.x)
Version Upgrade Event	The event is triggered after every manual or automatic version update of the app. User intervention is not required to trigger this event.	Android Capture Version Updated (xx.xx.x)
Idle Event	The event is triggered after every 24 hours of inactivity. Inactivity means no incoming or outgoing messages or calls. The app resets to count towards 24 hours after every incoming or outgoing message or call.	Android Capture heartbeat – last archiving event on Date/time. No archiving for X days
Low Storage Event	The event is triggered when the device storage reaches below 1 GB. The event will be re-sent every 24 hours as long as the device storage doesn’t rise above 1 GB. Note Smarsh does not delete the files of recorded voice call from the call recordings folder on the phone. Smarsh does not delete SMS or MMS messages from the messages database on the phone. Low Storage event data is stored in the database only and can be requested from Smarsh support.	The device has reached minimum internal storage threshold of XX MB
Roaming Event	The event is triggered every 24 hours while the device is in “Roaming” state.	The device is in Roaming state
Idle + Pending Messages Event	The event is triggered every 24 hours of inactivity. Inactivity means no incoming or outgoing messages or calls. The app resets to count towards 24 hours after every incoming or outgoing message or call. Message delivery can be pending when the app is working in “WiFi-Only” mode. This event is not observed when the app is working in “Wi-Fi + Cellular data” mode.	Android Capture heartbeat Pending: 7 SMS, 1 MMS, 4 Calls
Recording Enabled Event	The event is triggered when call recording is enabled on the device.	Call Recording Enabled
Recording Disabled Event	The event is triggered when call recording is disabled on the device.	Call Recording Disabled
Recording Terminated During Call	The event is triggered when a recording is terminated during an active call.	User <username> mobile <phone_number> recording was terminated during the call. Call length 00:00:32, Recording length 00:00:04
Missing Permissions Event	The event is triggered when the app detects that required permissions are missing on the device.	Missing Phone permission Missing SMS/MMS permission Missing Call logs permission
Failed Recordings Event	The event is triggered when one or more call recordings fail to process.	Call Recording Failed.
Wrong Recording Folder Event	The event is triggered when the app detects that the recording folder path is incorrect.	The wrong call recording folder was set. The app will not archive calls with records until proper recording folder is chosen
Battery Not Ignoring Optimizations Event	The event is triggered when battery optimization is not disabled for the Android Capture app. This may affect recording performance.	Battery optimization ON. Using mobile networks and syncing data can be restricted for the application, in this case the App will not have the ability to archive calls and messages. Please make sure the user turns battery optimization OFF.

Was this helpful?