Device Performance Classification
How Luciq classifies Android devices into performance tiers and how data collection is reduced on constrained devices.
Last updated
How Luciq classifies Android devices into performance tiers and how data collection is reduced on constrained devices.
On Android, the SDK automatically classifies devices into performance tiers based on hardware capabilities such as CPU, RAM, and memory class. On lower-tier devices, the SDK reduces data collection to protect app performance and prevent issues like ANRs or out-of-memory errors.
This classification is SDK-wide — it applies to all Luciq products, not just Session Replay. See What Gets Reduced for how each data type is affected.
LOW
Low-end
~30%
AVERAGE
Mid-range
~60%
HIGH
High-end
100%
Classification runs once per SDK start, based on the device's hardware capabilities.
A device is classified Low-end if any of the following is true:
Android version
Below 5.1 (Lollipop MR1, API level 22)
CPU cores
2 or fewer
Total RAM
2 GB or less
Otherwise, a device is classified Mid-range if any of the following is true:
Android version
Below 7.0 (Nougat, API level 24)
Per-app memory class
160 MB or less
CPU
Fewer than 8 cores, or combined max CPU frequency ≤ 2055 MHz
Everything else is classified High-end.
These thresholds may be tuned in future SDK versions, and specific device models can be re-classified remotely by Luciq.
There is no emulator-specific rule — emulators are classified using the same hardware signals as physical devices:
A default Android Virtual Device (2 GB RAM) is classified Low-end because its RAM is at the 2 GB threshold.
An AVD configured with more than 2 GB of RAM and more than 2 vCPUs escapes the Low-end tier and is typically classified Mid-range (emulators generally don't expose readable CPU frequency information, so they don't qualify for High-end).
If you don't want your development, staging, or CI emulators classified as low-end, configure the AVD with at least 3 GB of RAM and 4 vCPUs.
When the SDK reduces data collection on a constrained device, the following are affected:
Session Replay
Navigation mode only
Configured mode
Configured mode
Session Profiler
~18 seconds
~36 seconds
Full duration
Network and Console Logs
30% retained
60% retained
Full
Repro Steps
30% retained
60% retained
Full
When viewing a bug report, crash occurrence, or session from a constrained device:
A device classification badge appears in the details panel showing the device tier and the percentage of data collected (e.g., "Low-end · 30% data collected").
If session profiler data, repro steps, or screenshots are unavailable due to data reduction, the dashboard displays a message explaining that data collection was reduced on that device to protect app performance.
Device classification is currently available on Android only. This behavior is automatic and does not require any configuration. If you need classification disabled for a specific app (for example, a staging build), contact Luciq support.
Last updated