> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android/known-devices-information.md).

# FAQs

{% hint style="danger" %}
This SDK is deprecated and will receive limited support. Please adopt the v10 SDK: [https://github.com/smileidentity/docs/blob/main/mobile/android/broken-reference/README.md](https://github.com/smileidentity/docs/blob/main/mobile/android/broken-reference/README.md "mention")
{% endhint %}

### What Android versions does the SDK support?

* Our library supports minimum API level 19 (Android 4.4)
* When using AndroidX maximum supported API level is 32 (Android 12)

### Why is the SDK so large?

The Smile SDK is large on file, however, this is due to the inclusion of multiple ABIs as listed [here](https://developer.android.com/ndk/guides/abis). We recommend leveraging APK splits by ABI or App Bundles to ensure that the end user will not download the whole SDK but rather only what their phone needs. So while the *full* APK is large, the large APK is not what the end user actually ends up downloading.

You can look more on how this works [here](https://developer.android.com/studio/build/configure-apk-splits) if you are using APKs and [here](https://developer.android.com/guide/app-bundle) if you are using an app bundle

### Which CPU architectures (ABIs) are supported?

* arm64-v8a
* armabi-v7a
* x86
* x86\_64


---

# 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://legacy-docs.usesmileid.com/integration-options/mobile/android/known-devices-information.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.