Qt
Internal/Contributor docs for the Qt SDK. Note: These are NOT official API docs; those are found at https://doc.qt.io/
Loading...
Searching...
No Matches
android-manifest-file-configuration.qdoc
Go to the documentation of this file.
1// Copyright (C) 2021 The Qt Company Ltd.
2// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
3
4/*!
5\page android-manifest-file-configuration.html
6\title \Q4A Manifest File Configuration
7\ingroup androidplatform
8\brief Provides details on the AndroidManifest.xml configuration.
9\previouspage android-openssl-support.html
10\nextpage android-services.html
11
12The Android Manifest is an XML file necessary for any Android app. It contains
13app configuration for different settings and features that the app uses, as well
14as details on the app itself, such as, package name, app name, version, etc.
15Permissions and hardware features can also be set from the manifest.
16
17\Q4A maintains a version of \c {AndroidManifest.xml} with default
18configuration that include features, permissions and other configuration
19used by the build system which are needed for building and running Qt apps
20on Android.
21
22\section1 Qt Project to Manifest Configuration
23
24Qt defines some \l {Android: App Manifest <meta-data>}{meta-data} that is passed
25from the build systems and to \l {Deploying an Application on Android}{androiddeployqt}
26which populates the manifest with the correct values without explicitly setting
27these in the manifest file. Such \l {Android: App Manifest <meta-data>}{meta-data}
28is assigned a value in the form \c {"-- %%INSERT_VALUE%% --"}, for example:
29
30\badcode
31<manifest ...
32 android:versionCode="-- %%INSERT_VERSION_CODE%% --"
33 ...
34</manifest>
35\endcode
36
37This would be populated with the version code that is set in, for example,
38\c CMake.
39
40\section1 Qt Default Configuration
41
42Qt sets the following manifest configuration by default:
43
44\table
45\header
46 \li Section
47 \li Option
48 \li Description
49\row
50 \li {1, 5} \l {Android: App Manifest <manifest>}{<manifest>}
51 \li package
52 \li Sets the package name. The default value is \c {org.qtproject.example.app_name}.
53 \warning This field is deprecated and moved to \c build.gradle. It will be removed
54 in an upcoming release.
55\row
56 \li android:installLocation
57 \li Sets the app's installation location, whether internal or external storage.
58 The default value is \c auto.
59\row
60 \li android:versionCode
61 \li Sets the internal version code. Populated from \c ANDROID_VERSION_CODE (qmake)
62 and \c QT_ANDROID_VERSION_CODE (CMake). The default value is \c 1.
63\row
64 \li android:versionName
65 \li Sets the public version name. Populated from \c ANDROID_VERSION_NAME (qmake)
66 and \c QT_ANDROID_VERSION_NAME (CMake). The default value is \c {1.0}.
67\row
68 \li <supports-screens>
69 \li Sets the screen sizes that the app supports,
70 default values are \c anyDensity, \c largeScreens,
71 \c normalScreens, and \c smallScreens.
72\row
73 \li {1, 4} \l {Android: App Manifest <application>}{<application>}
74 \li android:name
75 \li The application class name. Default value is
76 \c {org.qtproject.qt.android.bindings.QtApplication}.
77\row
78 \li android:label
79 \li The application name label. Default value is the Qt project's target name.
80 This can be set using \l {QT_ANDROID_APP_NAME}.
81\row
82 \li android:icon
83 \li The application icon as a reference to a drawable or mipmap resource. This
84 tag is not used unless set using \l {QT_ANDROID_APP_ICON} or set manually
85 in the \c {AndroidManifest.xml}.
86\row
87 \li android:hardwareAccelerated
88 \li Sets hardware acceleration preference. The default value is \c true.
89\row
90 \li {1, 6} \l {Android: App Manifest <activity>}{<activity>}
91 \li android:name
92 \li The activity class name. The default value is \c {org.qtproject.qt.android.bindings.QtActivity}.
93\row
94 \li android:configChanges
95 \li Lists configuration changes that the activity handles. Default value is
96 \c orientation, \c uiMode, \c screenLayout, \c screenSize,
97 \c smallestScreenSize, \c layoutDirection, \c locale, \c fontScale,
98 \c keyboard, \c keyboardHidden, \c navigation, \c mcc, \c mnc, \c density.
99\row
100 \li android:launchMode
101 \li The method used to launch the activity. The default value is \c singleTop.
102\row
103 \li android:screenOrientation
104 \li The orientation of the activity's display on the device. The default value is \c unspecified.
105\row
106 \li <intent-filter>
107 \li Specifies the types of intents that the activity can respond to. Default value is
108 \badcode
109 <action android:name="android.intent.action.MAIN"/>
110 <category android:name="android.intent.category.LAUNCHER"/>
111 \endcode
112\row
113 \li android:exported
114 \li Sets whether the activity can be launched by components of other applications.
115 The default value is \c true.
116\endtable
117
118\target android-manifest-qt-specific-metadata
119\section1 Qt Specific Meta-data
120
121In addition to the default manifest configuration that Qt sets, Qt defines
122some meta-data that is valid for Qt apps only. Such meta-data is usually
123under the \c <activity> section in the form:
124
125\badcode
126<meta-data
127 android:name="meta-data-name"
128 android:value="meta-data-value" />
129\endcode
130
131The following is a list of such meta-data defined by Qt:
132
133\table
134\header
135 \li Meta-data Name
136 \li Description
137\row
138 \li android.app.lib_name \target android.app.lib_name
139 \li The filename of the native C++ library that is used by the activity.
140 \note This attribute is mandatory and shouldn't be removed.
141 Default value is the Qt project's target name.
142\row
143 \li android.app.extract_android_style
144 \li The method used to extract the native Android Style information.
145 For more information, see \l {Style Extraction}.
146 The default value is \c minimal.
147\row
148 \li android.app.background_running \target android.app.background_running
149 \li Sets whether the app keeps running tasks in the background.
150 Setting this to \c true is the equivalent of setting the environment
151 variable \c QT_BLOCK_EVENT_LOOPS_WHEN_SUSPENDED to \c 0.
152 The default value is \c false.
153
154 \warning Setting this to \c true may cause unexpected crash if the
155 application tries to draw after \l {QGuiApplication::applicationStateChanged()}
156 signal is sent with a \l {Qt::ApplicationSuspended} state.
157\row
158 \li android.app.arguments \target android.app.arguments
159 \li Sets a list of arguments to pass to the app \c {"arg1 arg2"}.
160 Populated from \c ANDROID_APPLICATION_ARGUMENTS (qmake) and
161 \c QT_ANDROID_APPLICATION_ARGUMENTS (CMake).
162 Default value is not set.
163\row
164 \li android.app.splash_screen_drawable_portrait
165 \li Sets a drawable for a splash screen specific to portrait mode.
166 For example: \c {android:resource="@drawable/splash_portrait"}.
167 Default value is not set.
168\row
169 \li android.app.splash_screen_drawable_landscape
170 \li Sets a drawable for a splash screen specific to landscape mode.
171 For example: \c {android:resource="@drawable/splash_landscape"}.
172 Default value is not set.
173\row
174 \li android.app.splash_screen_drawable
175 \li Sets a drawable for a splash screen at the start of the app.
176 \note Orientation specific splash screens are checked first,
177 if not set, this is used instead.
178 For example: \c {android:resource="@drawable/splash"}.
179 Default value is not set.
180\row
181 \li android.app.splash_screen_sticky
182 \li Sets whether the splash screen stays visible until explicitly hidden
183 by the app.
184 For more information, see
185 \l {QNativeInterface::}{QAndroidApplication::hideSplashScreen()}.
186\row
187 \li android.app.trace_location
188 \li Specifies a location on device where the application can save tracing files.
189 For example: /storage/emulated/0/Android/data/<app_package_name>/files/.
190 This is needed when using Common Trace Format (CTF) tracing backend.
191 \note The application needs storage permission for the location.
192 Default: not set.
193\endtable
194
195\section2 Application Specific Meta-data
196
197Some meta-data attributes are application-wide, and should be placed under
198the \c <application> section:
199
200\table
201\header
202 \li Meta-data Name
203 \li Description
204\row
205 \li android.app.system_libs_prefix \target android.app.system_libs_prefix
206 \li Specifies a custom system library path to use for library loading lookup.
207 This is necessary when using Qt libraries installed outside an app's
208 default native (JNI) library directory.
209 The default value is \c {/system/lib/}.
210\endtable
211
212\section2 Meta-data in Services
213
214Some meta-data attributes can also be used in \l {Android Services}{Services}.
215The main ones are:
216
217\list
218 \li \l {android.app.lib_name}
219 \li \l {android.app.background_running}
220 \li \l {android.app.arguments}
221\endlist
222
223\section2 Qt Permissions and Features
224
225Different Qt modules might require some Android permissions or features to
226function properly, for example, Camera permission in \l {QtMultimedia}.
227\l{The androiddeployqt Tool} takes care of including such requirements into the
228Android manifest during the build. Qt defines the following lines into the
229manifest, which they get replaced by
230the actual values:
231
232\badcode
233<manifest ...
234 <!-- %%INSERT_PERMISSIONS -->
235 <!-- %%INSERT_FEATURES -->
236 ...
237</manifest>
238\endcode
239
240\note If those lines are removed from the project manifest, Qt won't be
241able to include the correct permissions. So some functionalities
242might not work properly.
243
244\section3 Customizing Permissions
245
246Since Qt 6.8.1, it is possible to override the default permissions set
247by Qt modules. This is useful if you need to define the same permissions
248as used by a Qt module, but with additional or different attributes.
249
250There are two ways to achieve this. First way is to use
251\l {qt_add_android_permission} CMake function in the application's
252\c {CMakeLists.txt}. Permissions defined this way take precedence over
253the same permissions defined by Qt modules, avoiding duplication.
254
255Second way is to manually define these permissions in the Android
256manifest file. Permissions defined this way take precedence over permissions
257set by Qt modules, or set with \l {qt_add_android_permission}.
258
259\section2 Style Extraction
260
261Qt uses different methods to determine how Qt Widgets and Qt Quick Controls
262should be styled:
263
264\list
265 \li \c full: when using Qt Widgets or Qt Quick Controls 1.
266 \note This method is obsolete as it uses some Android non-SDK interfaces, that were
267 restricted by Google starting from Android 9.0 (API 28). You should use one of the other methods.
268 \li \c default or \c minimal: when using Qt Quick Controls 2 and no Qt Widgets or Qt Quick
269 Controls 1. This is faster than using the default or full options.
270 \li \c none: no style extraction.
271\endlist
272
273\section1 Qt Manifest before 6.2 Release
274
275Versions of Qt earlier than 6.2 used to have an additional set of meta-data
276defined by Qt. These attributes used to manage dependencies and some were
277used by the discontinued \c Ministro service. With Qt 6.2, they should be removed.
278Here is a list of these attributes:
279
280\list
281 \li android.app.qt_sources_resource_id
282 \li android.app.repository
283 \li android.app.bundled_libs_resource_id
284 \li android.app.bundle_local_qt_libs
285 \li android.app.use_local_qt_libs
286 \li android.app.libs_prefix
287 \li android.app.load_local_libs_resource_id
288 \li android.app.load_local_jars
289 \li android.app.static_init_classes
290 \li android.app.qt_libs_resource_id
291 \li android.app.ministro_not_found_msg
292 \li android.app.ministro_needed_msg
293 \li android.app.fatal_error_msg
294\endlist
295
296For more information on the Android Manifest, see
297\l{Android: App Manifest}{Android App Manifest}.
298*/