Qt6.5 Android What Problem.. Debug Mode
-
wrote on 1 Jun 2023, 06:16 last edited by
QT : 6.5
Crator : 9.0.2I am using Qt 6.5 version and Creator 9.0.2 version. How can I resolve Emulator warnings and errors? I have been searching for solutions on Google for three days without success. Can you please help me? Thank you so much in advance.
-
Thank you for your response.
Since this is my first time using Qt for Android, should I download the adb.exe file again from the SDK Manager? If not, I apologize, but is it possible to receive C++ implementation example files?I want Study and Setting Qt android!..
Moderatorswrote on 2 Jun 2023, 03:11 last edited by Axel Spoerl 6 Feb 2023, 03:14@dongkyu
OK, do I understand correctly: Android simulator and the kits mentioned in the screenshots have been installed on the system. Getting the Android emulator up and running hasn't succeeded at all - so far.I assume, the instructions here and here have been followed.
What may be a bit misleading in the documentation pages linked above: The list of supported devices mentions, that they are supported with the architectures armv7 and arm64_v8a. If you are working with an emulator, this list can make you believe, that you have to install an emulator with one of those architectures and let it emulate one of the devices from the list. The screenshots indicate, that this is what has happened on your system. It's actually wrong. Always install an emulator matching the host system's architecture: x86_64 in your case. Any other emulator will work with full hardware abstraction, which makes it extremely slow.
So let's return to the error message.
=> Issue number 1: Lack of speed.
Solution: Remove the am64_v8a emulator and install one for x86_64. That gets you rid of the "seriousperformance" problems.=> Issue number 2:
adb.exe
The error message says it's obsolete, which I would interpret as "Neither necessary, nor used, but existing anyway".
That sounds like a misleading error message to me.
A possible explanation is: It timed out without having finished, whatever it was supposed to do.IMHO it's not worth investigating number 2 any further. Solving number 1 will uninstall this emulator with its
adb.exe
anyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.Let us know, if it worked out.
-
QT : 6.5
Crator : 9.0.2Qt Kits
Android SDK, NDK JDK Version
Emulator Warning
Error
Make Source Code
I am using Qt 6.5 version and Creator 9.0.2 version. How can I resolve Emulator warnings and errors? I have been searching for solutions on Google for three days without success. Can you please help me? Thank you so much in advance.
@dongkyu
The available compile kits look like the host system is x86_64.
The emulator reporting "seriousperformance" problems, emulates arm64 on x86_64. That's likely to be the reason for the slowness. I wonder how adb.exe can be obsolete. Maybe that's just a fixed part of the error message.That said, please try if using the Android 6.5.0 Clang x86_64 kit delivers better performance. I use arm architectures only on physical devices. Last time I tried armeabi-v7a (4 weeks ago), the latest emulator version was broken
-
@dongkyu
The available compile kits look like the host system is x86_64.
The emulator reporting "seriousperformance" problems, emulates arm64 on x86_64. That's likely to be the reason for the slowness. I wonder how adb.exe can be obsolete. Maybe that's just a fixed part of the error message.That said, please try if using the Android 6.5.0 Clang x86_64 kit delivers better performance. I use arm architectures only on physical devices. Last time I tried armeabi-v7a (4 weeks ago), the latest emulator version was broken
wrote on 2 Jun 2023, 01:51 last edited byThank you for your response.
Since this is my first time using Qt for Android, should I download the adb.exe file again from the SDK Manager? If not, I apologize, but is it possible to receive C++ implementation example files?I want Study and Setting Qt android!..
-
Thank you for your response.
Since this is my first time using Qt for Android, should I download the adb.exe file again from the SDK Manager? If not, I apologize, but is it possible to receive C++ implementation example files?I want Study and Setting Qt android!..
Moderatorswrote on 2 Jun 2023, 03:11 last edited by Axel Spoerl 6 Feb 2023, 03:14@dongkyu
OK, do I understand correctly: Android simulator and the kits mentioned in the screenshots have been installed on the system. Getting the Android emulator up and running hasn't succeeded at all - so far.I assume, the instructions here and here have been followed.
What may be a bit misleading in the documentation pages linked above: The list of supported devices mentions, that they are supported with the architectures armv7 and arm64_v8a. If you are working with an emulator, this list can make you believe, that you have to install an emulator with one of those architectures and let it emulate one of the devices from the list. The screenshots indicate, that this is what has happened on your system. It's actually wrong. Always install an emulator matching the host system's architecture: x86_64 in your case. Any other emulator will work with full hardware abstraction, which makes it extremely slow.
So let's return to the error message.
=> Issue number 1: Lack of speed.
Solution: Remove the am64_v8a emulator and install one for x86_64. That gets you rid of the "seriousperformance" problems.=> Issue number 2:
adb.exe
The error message says it's obsolete, which I would interpret as "Neither necessary, nor used, but existing anyway".
That sounds like a misleading error message to me.
A possible explanation is: It timed out without having finished, whatever it was supposed to do.IMHO it's not worth investigating number 2 any further. Solving number 1 will uninstall this emulator with its
adb.exe
anyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.Let us know, if it worked out.
-
@dongkyu
OK, do I understand correctly: Android simulator and the kits mentioned in the screenshots have been installed on the system. Getting the Android emulator up and running hasn't succeeded at all - so far.I assume, the instructions here and here have been followed.
What may be a bit misleading in the documentation pages linked above: The list of supported devices mentions, that they are supported with the architectures armv7 and arm64_v8a. If you are working with an emulator, this list can make you believe, that you have to install an emulator with one of those architectures and let it emulate one of the devices from the list. The screenshots indicate, that this is what has happened on your system. It's actually wrong. Always install an emulator matching the host system's architecture: x86_64 in your case. Any other emulator will work with full hardware abstraction, which makes it extremely slow.
So let's return to the error message.
=> Issue number 1: Lack of speed.
Solution: Remove the am64_v8a emulator and install one for x86_64. That gets you rid of the "seriousperformance" problems.=> Issue number 2:
adb.exe
The error message says it's obsolete, which I would interpret as "Neither necessary, nor used, but existing anyway".
That sounds like a misleading error message to me.
A possible explanation is: It timed out without having finished, whatever it was supposed to do.IMHO it's not worth investigating number 2 any further. Solving number 1 will uninstall this emulator with its
adb.exe
anyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.Let us know, if it worked out.
wrote on 2 Jun 2023, 05:20 last edited by -
@dongkyu
OK, do I understand correctly: Android simulator and the kits mentioned in the screenshots have been installed on the system. Getting the Android emulator up and running hasn't succeeded at all - so far.I assume, the instructions here and here have been followed.
What may be a bit misleading in the documentation pages linked above: The list of supported devices mentions, that they are supported with the architectures armv7 and arm64_v8a. If you are working with an emulator, this list can make you believe, that you have to install an emulator with one of those architectures and let it emulate one of the devices from the list. The screenshots indicate, that this is what has happened on your system. It's actually wrong. Always install an emulator matching the host system's architecture: x86_64 in your case. Any other emulator will work with full hardware abstraction, which makes it extremely slow.
So let's return to the error message.
=> Issue number 1: Lack of speed.
Solution: Remove the am64_v8a emulator and install one for x86_64. That gets you rid of the "seriousperformance" problems.=> Issue number 2:
adb.exe
The error message says it's obsolete, which I would interpret as "Neither necessary, nor used, but existing anyway".
That sounds like a misleading error message to me.
A possible explanation is: It timed out without having finished, whatever it was supposed to do.IMHO it's not worth investigating number 2 any further. Solving number 1 will uninstall this emulator with its
adb.exe
anyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.Let us know, if it worked out.
wrote on 2 Jun 2023, 05:31 last edited by@Axel-Spoerl
solved
I had to wait. I didn't read the article properly.
Thanks for the reply, and thanks again for your valuable time! -
-
@Axel-Spoerl
solved
I had to wait. I didn't read the article properly.
Thanks for the reply, and thanks again for your valuable time!@dongkyu
Thanks, so please mark the thread solved.
1/7