Skip to main content
ComponentsEngineMobile AppRUM JS
Availability2022.1 or later

Device Information

Non-sensitive device context captured

Application Usage Monitoring

Permission-based app usage data

KPIs

Device KPIs and availability

Troubleshooting

Resolve device monitoring issues

​
Overview

The GermainUX Android application collects device-level performance and usage telemetry permitted by Android. It helps teams determine whether device conditions contribute to poor application performance or user productivity, including:
  • Low battery
  • High CPU or memory usage
  • Limited storage
  • Poor or changing network connectivity
  • Device or Android-version compatibility
  • Monitored process or service problems
  • Application usage, when Android Usage Access is granted
Available telemetry depends on the Android version, device manufacturer, application permissions, management profile, and background-execution restrictions. GermainUX Android Device Observability is not a mobile-device-management platform. It does not replace an MDM or EMM product for device enrollment, policy enforcement, application distribution, remote locking, or device wiping.

​
Device Information

GermainUX can collect non-sensitive device context available to the monitoring application, such as:
  • Manufacturer
  • Brand
  • Model
  • Android version
  • Application version
  • Device language or locale
  • Screen and hardware characteristics available through Android
  • Network type
  • Device or monitoring identifier
Avoid collecting hardware identifiers or other persistent identifiers unless they are required, available through supported APIs, and approved by the organization.

​
Battery Monitoring

Available battery telemetry can include:
  • Battery level
  • Charging state
  • Power source
  • Battery-low and battery-okay events
  • Power-saving state
Battery information can help determine whether failures, slow operations, interrupted sessions, or reduced background activity correlate with low-power conditions. Battery health and detailed hardware diagnostics may not be available consistently across Android devices.

​
CPU and Memory Monitoring

Depending on Android permissions and APIs, GermainUX can collect measurements such as:
  • CPU usage available to the monitoring application
  • System memory state
  • Available memory
  • Low-memory events
  • Monitoring-process memory
  • Monitored application-process memory, where accessible
Modern Android versions restrict visibility into other applications and their processes. GermainUX should not be described as providing unrestricted CPU or memory inspection of every application installed on the device.

​
Storage Monitoring

Available storage measurements can include:
  • Internal storage capacity
  • Available internal storage
  • Storage utilization
  • External or removable storage, when present and accessible
  • Low-storage events
Android scoped-storage rules restrict access to the content of other applications and protected storage areas. GermainUX monitors available capacity and approved paths; it does not inspect arbitrary files belonging to other applications.

​
Network Monitoring

Depending on the device and permissions, GermainUX can collect network context such as:
  • Connected or disconnected state
  • Wi-Fi or cellular transport
  • Metered-network state
  • Available network capabilities
  • Network usage or bandwidth measurements available to the application
  • IP information exposed by Android
Mobile-generation labels and network details can vary by Android version, carrier, and device. VPNs, private DNS, proxies, and network-address translation can also affect the reported context. Use network telemetry to correlate application failures and performance with connectivity conditions rather than as a replacement for dedicated network monitoring.

​
Application Usage Monitoring

When the user or device administrator grants Android Usage Access, GermainUX may collect permitted application-usage information such as:
  • Application opened or moved to the foreground
  • Usage duration
  • Last-used time
  • Application usage frequency
Android Usage Access is a special permission that must be explicitly granted in device settings or through an approved managed-device process. Without Usage Access, GermainUX cannot provide comprehensive usage information for other applications. Application usage data can be privacy-sensitive. Collect it only on organization-owned or appropriately managed devices and only for approved applications and purposes.

​
Process and Service Monitoring

Android restricts access to information about other applications’ processes and services, especially on modern releases. GermainUX can monitor:
  • Its own process and service
  • Processes belonging to an integrated application, where supported
  • Limited system information exposed by Android
  • Approved application or service events provided through supported integrations
It cannot be assumed to enumerate or inspect every running process and service on an unmanaged modern Android device. For detailed monitoring of a specific Android application, integrate the GermainUX Mobile App library directly into that application.

​
Device Events

GermainUX can collect selected system events delivered to the monitoring application, potentially including:
  • Network changes
  • Battery state changes
  • Power connection changes
  • Power-saving mode changes
  • Storage conditions
  • Locale or time-zone changes
  • Device startup
  • Configuration changes
Event availability depends on Android broadcast restrictions, permissions, application state, and device-manufacturer behavior. Events related to calls, messages, contacts, Bluetooth devices, or other sensitive areas may require restricted permissions or may not be available. Do not request such permissions unless they are necessary, supported, and explicitly approved.

​
Deployment

  1. Obtain the approved GermainUX Android application.
  2. Install it through Google Play, a managed Google Play environment, or the organization’s approved application-distribution process.
  3. Configure the GermainUX environment and device-monitoring profile.
  4. Grant only the permissions required for the approved monitoring scope.
  5. Grant Usage Access only when application-usage monitoring is required.
  6. Apply battery-optimization settings only when approved and necessary.
  7. Confirm that the device can reach the GermainUX ingestion endpoint through HTTPS.
  8. Verify that device telemetry appears in GermainUX.
  9. Test on representative Android versions and device models.
  10. Roll out through the organization’s normal device-management process.
For managed fleets, use the existing MDM or EMM platform to distribute and configure the GermainUX application where supported.

​
Configure Device Context

Use consistent attributes to identify monitored devices and their purpose:
  • Environment
  • Device group
  • Device model
  • Android version
  • Business unit
  • Region
  • Application or workflow
  • Ownership type
  • Support group
Use a pseudonymous device identifier rather than a user name, email address, phone number, serial number, or another sensitive identifier whenever possible.

​
KPIs

Common Android device KPIs include: Not every KPI is available on every Android device.

​
Dashboards and Analysis

Android device dashboards can display:
  • Devices reporting telemetry
  • Android versions
  • Device manufacturers and models
  • Battery levels
  • CPU and memory
  • Storage capacity
  • Network state
  • Application usage
  • Device events
  • Process or service status
  • Related application errors and transactions
Segment application performance by device conditions to identify patterns such as:
  • Crashes concentrated on a device model
  • Slow transactions on a particular Android version
  • Synchronization failures on cellular networks
  • Application interruptions associated with low memory
  • Poor performance when storage is nearly full

​
Alerts

Configure alerts for actionable conditions such as:
  • Device no longer reporting
  • Sustained high resource usage
  • Low available storage
  • Repeated low-memory events
  • Critical monitored process or service unavailable
  • Connectivity loss affecting an important workflow
  • Unexpected application-usage change on managed devices
A device that stops reporting may be offline, powered down, restricted by Android, or unable to reach GermainUX. Treat missing telemetry as a monitoring condition rather than proof of device failure.

​
Privacy and Security

Before deployment:
  • Collect only telemetry required for an approved purpose.
  • Avoid sensitive device and user identifiers.
  • Do not collect message, call, contact, or location data unless explicitly required and authorized.
  • Restrict application-usage monitoring to approved applications.
  • Use HTTPS for all telemetry.
  • Apply access controls and retention policies.
  • Document monitoring for affected users.
  • Follow applicable employment, privacy, and regulatory requirements.
  • Review Google Play and managed-device policies.
Permissions granted by Android do not by themselves establish organizational authorization to collect the data.

​
Validation

After deployment:
1

Confirm that the device appears in GermainUX

2

Verify manufacturer, model, and Android version

3

Check battery, memory, storage, and network telemetry

4

Grant and test Usage Access if required

5

Change network and charging states

6

Confirm that supported events are received

7

Verify monitoring while the application is backgrounded

8

Test device-manufacturer battery restrictions

9

Confirm that unapproved applications and sensitive data are excluded

10

Verify alerts and reports

​
Troubleshooting

​
The device does not report

Verify:
  • The GermainUX application is installed and enabled.
  • The ingestion URL is correct.
  • The device can reach GermainUX through HTTPS.
  • Required permissions are granted.
  • Battery optimization or background restrictions are not stopping collection.
  • VPN, proxy, firewall, or device policy permits the connection.
  • The application version is supported.

​
Application usage is missing

Confirm that:
  • Android Usage Access is granted.
  • The device policy permits usage collection.
  • The application was used during the selected period.
  • The Android version exposes the required usage events.
  • GermainUX privacy rules do not exclude the data.

​
Process information is incomplete

This is expected on modern Android versions, which restrict visibility into other applications. Integrate the GermainUX Mobile App library into the application requiring detailed monitoring.

​
Data differs across device models

Compare Android versions, manufacturer-specific background restrictions, permissions, power-management policies, and available system APIs.

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.