> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/device-performance-classification.md).

# Device Performance Classification

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](#what-gets-reduced) for how each data type is affected.

## Device Tiers

| Tier    | Dashboard Label | Data Collected |
| ------- | --------------- | -------------- |
| LOW     | Low-end         | \~30%          |
| AVERAGE | Mid-range       | \~60%          |
| HIGH    | High-end        | 100%           |

## How Devices Are Classified

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:

| Signal          | Threshold                              |
| --------------- | -------------------------------------- |
| 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:

| Signal               | Threshold                                                    |
| -------------------- | ------------------------------------------------------------ |
| 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**.

{% hint style="info" %}
These thresholds may be tuned in future SDK versions, and specific device models can be re-classified remotely by Luciq.
{% endhint %}

### Emulators

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.

## What Gets Reduced

When the SDK reduces data collection on a constrained device, the following are affected:

| Data Type                | Low-end              | Mid-range       | High-end        |
| ------------------------ | -------------------- | --------------- | --------------- |
| 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            |

## What You'll See on the Dashboard

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.

{% hint style="info" %}
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.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/device-performance-classification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.