Qt for Android Supported Versions Selection Guidelines | Qt 6.11
Description: Provides information about supported Android versions under a Qt release.

- Qt 6.11
- Supported Platforms
- Qt for Android
- Qt for Android Supported Versions Selection Guidelines
- Qt 6.11.2 Reference Documentation

How Qt for Android Works ◦ Building from source

# Qt for Android Supported Versions Selection Guidelines

To keep the supported versions to a level that’s maintainable by Qt, especially for LTS releases which are expected to live for a period of 3 years, Qt for Android has guidelines for selecting the supported versions for a given Qt release. This makes the selection clear and transparent, and help shape proper expectations of support for each Qt for Android release.

## Minimum Supported Version

The guidelines for selecting the minimum supported version are:

- Evaluate the minimum version once a year for the fall release of Qt, which would also cover LTS releases.
- Target at least 90% of the cumulative usage in the market as listed on apilevels.com at the time of the platform freeze deadline of a given fall release.
- The selection is done 1 month before the platform freeze, at which time we check what versions would fit the 90% range, and decide whether to select a more recent minimum version or not and to what new minimum version.
- The changes are communicated to the Qt development mailing list, and reflected in the release change log and Qt for Android documentation.
- In exceptional cases where a change is needed to a version that doesn’t respect the criteria above, it will be announced at the time of the platform freeze deadline along with reasons for the decision.

The minimum version changes will be reflected in our CI test runs, and in the build system (i.e. CMake and androiddeployqt), thus the released libraries would require said minimum version to run. To target older versions a Qt rebuild with appropriate build system changes would be needed. Even if such builds might work for older versions, note that they would fall outside of Qt official support scope. Although, the official Qt for Android libraries might or might not work for builds targeting older versions than the minimum for the release.

## Maximum Supported Version

In a spring Qt release, we aim to support an Android version which was released by Google in the fall of the year before. This becomes the new maximum supported version by Qt.

Qt LTS releases would also support new Android versions coming out to market for up to two years after the initial Qt LTS patch release. This allows users to target newer Android versions to comply with Google Play Store target SDK publishing policies. In effect, new Android versions released in this two year period will become the maximum versions supported for the LTS release in the following patch release of the Qt LTS version.

## Target Devices used in Automated Testing

Below is a list of Android devices used in automated testing of Qt for Android releases. The list is in API version order, then alphabetically for each version. The list is inclusive of but not limited to these devices:

Device | OS Version | Architecture | Form Factor
--- | --- | --- | ---
Huawei MediaPad M5 10 (CMR-W09) | Android 9 (API 28) | arm64-v8a,armeabi-v7a | Mobile
Pixel 3a | Android 10 (API 29) | arm64-v8a,armeabi-v7a | Mobile
Samsung Galaxy Tab S4 (SM-T835) | Android 10 (API 29) | arm64-v8a,armeabi-v7a | Tablet
Pixel 2 | Android 11 (API 30) | arm64-v8a,armeabi-v7a | Mobile
Pixel 2 XL | Android 11 (API 30) | arm64-v8a,armeabi-v7a | Mobile
Pixel 6 Pro | Android 12 (API 32) | arm64-v8a,armeabi-v7a | Mobile
Samsung Galaxy S21 (SM-G990B2) | Android 12 (API 31) | arm64-v8a,armeabi-v7a | Mobile
Pixel 4 | Android 13 (API 33) | arm64-v8a,armeabi-v7a | Mobile
Pixel 4A | Android 13 (API 33) | arm64-v8a,armeabi-v7a | Mobile
Pixel 7 Pro | Android 13 (API 33) | arm64-v8a | Mobile
Nothing Phone 1 (A063) | Android 14 (API 34) | arm64-v8a,armeabi-v7a | Mobile
Samsung Galaxy Tab A9+ (SM-X210) | Android 14 (API 34) | arm64-v8a,armeabi-v7a | Tablet
Pixel 8 | Android 15 (API 35) | arm64-v8a | Mobile
Samsung Galaxy A26 (SM-A266B) | Android 15 (API 35) | arm64-v8a,armeabi-v7a | Tablet
Pixel 6a | Android 16 (API 36) | arm64-v8a,armeabi-v7a | Mobile
Pixel 6a | Android 16 (API 36) | arm64-v8a,armeabi-v7a | Mobile
Pixel 7 | Android 16 (API 36) | arm64-v8a | Mobile
Pixel 7a | Android 16 (API 36) | arm64-v8a | Mobile
Pixel 8 | Android 16 (API 36) | arm64-v8a | Mobile
Pixel Tablet | Android 16 (API 36) | arm64-v8a | Tablet
Samsung Galaxy Tab 10 Lite (SM-X400) | Android 16 (API 36) | arm64-v8a,armeabi-v7a | Tablet
Samsung Galaxy S21 (SM-G990B) | Android 16 (API 36) | arm64-v8a,armeabi-v7a | Mobile
Pixel 6a | Android 17 Beta2 Cinnamonbun (API 36) | arm64-v8a,armeabi-v7a | Mobile

Note: The above table is accurate at the time of this Qt patch release only. It may change during the patch release cycle and should only be used as a reference for what The Qt Company can rapidly reproduce bugs on.

How Qt for Android Works ◦ Building from source