Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt6.5 Android What Problem.. Debug Mode
Forum Updated to NodeBB v4.3 + New Features

Qt6.5 Android What Problem.. Debug Mode

Scheduled Pinned Locked Moved Solved Mobile and Embedded
7 Posts 2 Posters 660 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    dongkyu
    wrote on 1 Jun 2023, 06:16 last edited by
    #1

    QT : 6.5
    Crator : 9.0.2

    Qt Kits
    f32a69b3-9a6e-4e37-aae0-a8f120a3c87a-image.png

    Android SDK, NDK JDK Version
    4ad23a3e-146e-4663-9c26-b4eca1cece09-image.png

    Emulator Warning
    ad8464f6-c1f7-4a2c-8b0d-87ea40422ef4-image.png

    Error
    f579c05d-0c59-4c06-b497-8845c22a0359-image.png

    Make Source Code
    fdcd3a6e-2163-4c23-a583-abd9f075b7b6-image.png

    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.

    A 1 Reply Last reply 1 Jun 2023, 22:06
    0
    • D dongkyu
      2 Jun 2023, 01:51

      @Axel-Spoerl

      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!..

      A Offline
      A Offline
      Axel Spoerl
      Moderators
      wrote on 2 Jun 2023, 03:11 last edited by Axel Spoerl 6 Feb 2023, 03:14
      #4

      @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.exeanyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.

      Let us know, if it worked out.

      Software Engineer
      The Qt Company, Oslo

      D 2 Replies Last reply 2 Jun 2023, 05:20
      0
      • D dongkyu
        1 Jun 2023, 06:16

        QT : 6.5
        Crator : 9.0.2

        Qt Kits
        f32a69b3-9a6e-4e37-aae0-a8f120a3c87a-image.png

        Android SDK, NDK JDK Version
        4ad23a3e-146e-4663-9c26-b4eca1cece09-image.png

        Emulator Warning
        ad8464f6-c1f7-4a2c-8b0d-87ea40422ef4-image.png

        Error
        f579c05d-0c59-4c06-b497-8845c22a0359-image.png

        Make Source Code
        fdcd3a6e-2163-4c23-a583-abd9f075b7b6-image.png

        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.

        A Offline
        A Offline
        Axel Spoerl
        Moderators
        wrote on 1 Jun 2023, 22:06 last edited by
        #2

        @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

        Software Engineer
        The Qt Company, Oslo

        D 1 Reply Last reply 2 Jun 2023, 01:51
        0
        • A Axel Spoerl
          1 Jun 2023, 22:06

          @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

          D Offline
          D Offline
          dongkyu
          wrote on 2 Jun 2023, 01:51 last edited by
          #3

          @Axel-Spoerl

          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!..

          A 1 Reply Last reply 2 Jun 2023, 03:11
          0
          • D dongkyu
            2 Jun 2023, 01:51

            @Axel-Spoerl

            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!..

            A Offline
            A Offline
            Axel Spoerl
            Moderators
            wrote on 2 Jun 2023, 03:11 last edited by Axel Spoerl 6 Feb 2023, 03:14
            #4

            @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.exeanyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.

            Let us know, if it worked out.

            Software Engineer
            The Qt Company, Oslo

            D 2 Replies Last reply 2 Jun 2023, 05:20
            0
            • A Axel Spoerl
              2 Jun 2023, 03:11

              @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.exeanyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.

              Let us know, if it worked out.

              D Offline
              D Offline
              dongkyu
              wrote on 2 Jun 2023, 05:20 last edited by
              #5

              @Axel-Spoerl

              After changing the architecture to x86_64, it worked.
              ADB.exe Error ignored.
              Thank you for answer!

              But there is another problem.. Please see the image below..
              951135b7-6a0b-47dd-8adb-076bfc942c76-image.png

              When I debug like the image above, the problem occurred.
              How can I solve this?

              1 Reply Last reply
              0
              • A Axel Spoerl
                2 Jun 2023, 03:11

                @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.exeanyway, to replace it with the x86_64 version. Let's hope that number 2 disappears by itself.

                Let us know, if it worked out.

                D Offline
                D Offline
                dongkyu
                wrote on 2 Jun 2023, 05:31 last edited by
                #6

                @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!

                A 1 Reply Last reply 2 Jun 2023, 09:50
                0
                • D dongkyu has marked this topic as solved on 2 Jun 2023, 05:31
                • D dongkyu
                  2 Jun 2023, 05:31

                  @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!

                  A Offline
                  A Offline
                  Axel Spoerl
                  Moderators
                  wrote on 2 Jun 2023, 09:50 last edited by
                  #7

                  @dongkyu
                  Thanks, so please mark the thread solved.

                  Software Engineer
                  The Qt Company, Oslo

                  1 Reply Last reply
                  0

                  1/7

                  1 Jun 2023, 06:16

                  • Login

                  • Login or register to search.
                  1 out of 7
                  • First post
                    1/7
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved