When we quit Qt in an Android app, we also quit the Java thread created to act as the Qt main thread. This works well for normal Qt for Android apps, where the lifetime of the Qt part and the whole Android app is essentially the same. However, in QtQuick for Android Qt can be just a part of the entire app, and the lifecycles are not directly tied. Hence, we might want to quit Qt when the part of the app that has it is not active, and restart it when the Qt part of the app comes active again, and for this we need to create a new QtThread. Set the QtThread variable to null when it has been terminated, and if it's required again, create a new instance. Task-number: QTBUG-130610 Pick-to: 6.8 Change-Id: I430e195fd319a20c9627ed98d6f30858cebc49c4 Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io> (cherry picked from commit 7c7b63f3e85436125baf2211bc5e10556736241b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
…
Description
Languages
C++
84.3%
HTML
4.9%
C
3.9%
CMake
3.6%
Objective-C++
2%
Other
0.8%