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. Android app doesn't run
Forum Updated to NodeBB v4.3 + New Features

Android app doesn't run

Scheduled Pinned Locked Moved Solved Mobile and Embedded
87 Posts 7 Posters 21.0k Views 3 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.
  • mzimmersM mzimmers

    @JoeCFD bingo. Now my device shows as ready to use.

    Unfortunately, I'm now back to my original error:

    Activity Manager threw the error: Error type 3
    Error: Activity class {org.qtproject.example.weatherinfo/org.qtproject.qt.android.bindings.QtActivity} does not exist.
    

    And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.

    How do these settings compare with yours?
    Screenshot 2024-01-05 083441.png

    JoeCFDJ Offline
    JoeCFDJ Offline
    JoeCFD
    wrote on last edited by JoeCFD
    #42

    @mzimmers I have JDK 11 and yours is 17. 17 is for Android 14. I do not think Galaxy has 14 now. Check the Android version in your tablet. Mine is 13.

    mzimmersM 1 Reply Last reply
    0
    • JoeCFDJ JoeCFD

      @mzimmers I have JDK 11 and yours is 17. 17 is for Android 14. I do not think Galaxy has 14 now. Check the Android version in your tablet. Mine is 13.

      mzimmersM Offline
      mzimmersM Offline
      mzimmers
      wrote on last edited by
      #43

      @JoeCFD mine appears to be 11.

      When I change my JDK to 11, I get the following errors:
      Screenshot 2024-01-05 084838.png
      Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions.

      JoeCFDJ JKSHJ 2 Replies Last reply
      0
      • mzimmersM mzimmers

        @JoeCFD mine appears to be 11.

        When I change my JDK to 11, I get the following errors:
        Screenshot 2024-01-05 084838.png
        Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions.

        JoeCFDJ Offline
        JoeCFDJ Offline
        JoeCFD
        wrote on last edited by JoeCFD
        #44

        @mzimmers click SDK Manager button to install Android 13 SDKs

        mzimmersM 1 Reply Last reply
        0
        • JoeCFDJ JoeCFD

          @mzimmers click SDK Manager button to install Android 13 SDKs

          mzimmersM Offline
          mzimmersM Offline
          mzimmers
          wrote on last edited by
          #45

          @JoeCFD
          nobody home when I have JDK11 selected:
          Screenshot 2024-01-05 163838.png

          1 Reply Last reply
          0
          • mzimmersM mzimmers

            @JoeCFD mine appears to be 11.

            When I change my JDK to 11, I get the following errors:
            Screenshot 2024-01-05 084838.png
            Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions.

            JKSHJ Offline
            JKSHJ Offline
            JKSH
            Moderators
            wrote on last edited by
            #46

            @mzimmers said in Android app doesn't run:

            Do I need to dig up an earlier version of the SDK now?

            That's a bit tricky:

            • The Latest version of the SDK Command-Line tools (v11+) requires JDK 17 now. In contrast, v10 of the Tools can work with JDK 11.
            • Qt Creator expects you to use the SDK Manager to install the "Latest" version of the tools. So if you've upgrade those tools, you're expected to use JDK 17 too.

            And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.

            Hmm... that's weird. Sorry, I don't know if it's related to JDK 17 or not. (I haven't upgraded so I'm still using JDK 11 + SDK Command-Line Tools v10)

            Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

            mzimmersM 1 Reply Last reply
            0
            • JKSHJ JKSH

              @mzimmers said in Android app doesn't run:

              Do I need to dig up an earlier version of the SDK now?

              That's a bit tricky:

              • The Latest version of the SDK Command-Line tools (v11+) requires JDK 17 now. In contrast, v10 of the Tools can work with JDK 11.
              • Qt Creator expects you to use the SDK Manager to install the "Latest" version of the tools. So if you've upgrade those tools, you're expected to use JDK 17 too.

              And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.

              Hmm... that's weird. Sorry, I don't know if it's related to JDK 17 or not. (I haven't upgraded so I'm still using JDK 11 + SDK Command-Line Tools v10)

              mzimmersM Offline
              mzimmersM Offline
              mzimmers
              wrote on last edited by mzimmers
              #47
              This post is deleted!
              1 Reply Last reply
              0
              • mzimmersM Offline
                mzimmersM Offline
                mzimmers
                wrote on last edited by
                #48

                Using Android Studio's SDK Manager, I was able to install Android 13.0 (Tiramisu), and command-line tools 10:
                Screenshot 2024-01-06 141139.png

                Screenshot 2024-01-06 140903.png
                and now my Android settings in Creator are totally whack:
                Screenshot 2024-01-06 141805.png
                I'm going around in circles here. Any ideas are appreciated.

                JoeCFDJ 2 Replies Last reply
                0
                • mzimmersM mzimmers

                  Using Android Studio's SDK Manager, I was able to install Android 13.0 (Tiramisu), and command-line tools 10:
                  Screenshot 2024-01-06 141139.png

                  Screenshot 2024-01-06 140903.png
                  and now my Android settings in Creator are totally whack:
                  Screenshot 2024-01-06 141805.png
                  I'm going around in circles here. Any ideas are appreciated.

                  JoeCFDJ Offline
                  JoeCFDJ Offline
                  JoeCFD
                  wrote on last edited by
                  #49

                  @mzimmers the SDKs from Android SDK Manager are not in your kit yet. Click SDK Manager button to add them.

                  mzimmersM 1 Reply Last reply
                  0
                  • JoeCFDJ JoeCFD

                    @mzimmers the SDKs from Android SDK Manager are not in your kit yet. Click SDK Manager button to add them.

                    mzimmersM Offline
                    mzimmersM Offline
                    mzimmers
                    wrote on last edited by
                    #50

                    @JoeCFD it doesn't work - there's nothing in the package window to add when I've selected JDK 11.

                    ekkescornerE 1 Reply Last reply
                    0
                    • mzimmersM mzimmers

                      @JoeCFD it doesn't work - there's nothing in the package window to add when I've selected JDK 11.

                      ekkescornerE Offline
                      ekkescornerE Offline
                      ekkescorner
                      Qt Champions 2016
                      wrote on last edited by
                      #51

                      @mzimmers I'm using JDK 17 for Qt 5.15.15 and 6.6

                      ekke ... Qt Champion 2016 | 2024 ... mobile business apps
                      5.15 --> 6.8 https://t1p.de/ekkeChecklist
                      QMake --> CMake https://t1p.de/ekkeCMakeMobileApps

                      1 Reply Last reply
                      0
                      • mzimmersM mzimmers

                        Using Android Studio's SDK Manager, I was able to install Android 13.0 (Tiramisu), and command-line tools 10:
                        Screenshot 2024-01-06 141139.png

                        Screenshot 2024-01-06 140903.png
                        and now my Android settings in Creator are totally whack:
                        Screenshot 2024-01-06 141805.png
                        I'm going around in circles here. Any ideas are appreciated.

                        JoeCFDJ Offline
                        JoeCFDJ Offline
                        JoeCFD
                        wrote on last edited by
                        #52

                        @mzimmers I am running Qt 6.6.1 on Linux with qtcreator 11.0.3 and do not have any issue with the settings.

                        SDK path is not writable?

                        mzimmersM 1 Reply Last reply
                        0
                        • JoeCFDJ JoeCFD

                          @mzimmers I am running Qt 6.6.1 on Linux with qtcreator 11.0.3 and do not have any issue with the settings.

                          SDK path is not writable?

                          mzimmersM Offline
                          mzimmersM Offline
                          mzimmers
                          wrote on last edited by
                          #53

                          @JoeCFD I'm running on Windows 11. According to the properties of my Sdk folder, it was partially read-only, but I changed that, and it didn't help.

                          When I try to run the SCK manager, I get this error:
                          Screenshot 2024-01-08 073403.png

                          JoeCFDJ 1 Reply Last reply
                          0
                          • mzimmersM mzimmers

                            @JoeCFD I'm running on Windows 11. According to the properties of my Sdk folder, it was partially read-only, but I changed that, and it didn't help.

                            When I try to run the SCK manager, I get this error:
                            Screenshot 2024-01-08 073403.png

                            JoeCFDJ Offline
                            JoeCFDJ Offline
                            JoeCFD
                            wrote on last edited by
                            #54

                            @mzimmers

                            The error message indicates that you are trying to run a Java class file compiled with a higher version of the Java compiler than the version of the Java Runtime Environment (JRE) you have installed.

                            In this case:

                            Class file version 61.0 corresponds to Java 17.
                            Class file version 55.0 corresponds to Java 11.
                            

                            ==============================================================
                            Your installation is messed up.

                            mzimmersM 1 Reply Last reply
                            0
                            • JoeCFDJ JoeCFD

                              @mzimmers

                              The error message indicates that you are trying to run a Java class file compiled with a higher version of the Java compiler than the version of the Java Runtime Environment (JRE) you have installed.

                              In this case:

                              Class file version 61.0 corresponds to Java 17.
                              Class file version 55.0 corresponds to Java 11.
                              

                              ==============================================================
                              Your installation is messed up.

                              mzimmersM Offline
                              mzimmersM Offline
                              mzimmers
                              wrote on last edited by
                              #55

                              @JoeCFD said in Android app doesn't run:

                              Your installation is messed up.

                              Well, that's an understatement. From a terminal, I get this:

                              C:\Users\michael.zimmers>java -version
                              openjdk version "21.0.1" 2023-10-17 LTS
                              OpenJDK Runtime Environment Temurin-21.0.1+12 (build 21.0.1+12-LTS)
                              OpenJDK 64-Bit Server VM Temurin-21.0.1+12 (build 21.0.1+12-LTS, mixed mode, sharing)
                              

                              Is this not the same JRE instance that Creator is trying to use?

                              JoeCFDJ 1 Reply Last reply
                              0
                              • mzimmersM mzimmers

                                @JoeCFD said in Android app doesn't run:

                                Your installation is messed up.

                                Well, that's an understatement. From a terminal, I get this:

                                C:\Users\michael.zimmers>java -version
                                openjdk version "21.0.1" 2023-10-17 LTS
                                OpenJDK Runtime Environment Temurin-21.0.1+12 (build 21.0.1+12-LTS)
                                OpenJDK 64-Bit Server VM Temurin-21.0.1+12 (build 21.0.1+12-LTS, mixed mode, sharing)
                                

                                Is this not the same JRE instance that Creator is trying to use?

                                JoeCFDJ Offline
                                JoeCFDJ Offline
                                JoeCFD
                                wrote on last edited by JoeCFD
                                #56

                                @mzimmers It is likely some java classes in Android/Sdk were built in Java 17 at the beginning. They were not rebuilt when you switched to Java 11.

                                Wait: you have JDK 21?

                                mzimmersM 1 Reply Last reply
                                0
                                • JoeCFDJ JoeCFD

                                  @mzimmers It is likely some java classes in Android/Sdk were built in Java 17 at the beginning. They were not rebuilt when you switched to Java 11.

                                  Wait: you have JDK 21?

                                  mzimmersM Offline
                                  mzimmersM Offline
                                  mzimmers
                                  wrote on last edited by
                                  #57

                                  @JoeCFD said in Android app doesn't run:

                                  Wait: you have JDK 21?

                                  I have JDK 11, 17 and 21. I just don't know which one to use in my JDK/SDK/NDK/tools/JRE cocktail.

                                  JoeCFDJ 1 Reply Last reply
                                  0
                                  • mzimmersM mzimmers

                                    @JoeCFD said in Android app doesn't run:

                                    Wait: you have JDK 21?

                                    I have JDK 11, 17 and 21. I just don't know which one to use in my JDK/SDK/NDK/tools/JRE cocktail.

                                    JoeCFDJ Offline
                                    JoeCFDJ Offline
                                    JoeCFD
                                    wrote on last edited by
                                    #58

                                    @mzimmers I guess you can not have all of them. Remove 17 and 21 and SDK. Reinstall SDK if you use Java 11 which is recommended by Android for Andorid 13.

                                    @ekkescorner wrote he is ok with 17. I have not tried it. You can try it out as well.

                                    mzimmersM 1 Reply Last reply
                                    0
                                    • JoeCFDJ JoeCFD

                                      @mzimmers I guess you can not have all of them. Remove 17 and 21 and SDK. Reinstall SDK if you use Java 11 which is recommended by Android for Andorid 13.

                                      @ekkescorner wrote he is ok with 17. I have not tried it. You can try it out as well.

                                      mzimmersM Offline
                                      mzimmersM Offline
                                      mzimmers
                                      wrote on last edited by
                                      #59

                                      @JoeCFD but according to JKSH's post this is going to create a mismatch.

                                      JoeCFDJ 1 Reply Last reply
                                      0
                                      • mzimmersM mzimmers referenced this topic on
                                      • mzimmersM mzimmers

                                        @JoeCFD but according to JKSH's post this is going to create a mismatch.

                                        JoeCFDJ Offline
                                        JoeCFDJ Offline
                                        JoeCFD
                                        wrote on last edited by
                                        #60

                                        @mzimmers I do not know the mismatch issue. I have only Open Java 11 in my Linux computer.

                                        mzimmersM 1 Reply Last reply
                                        0
                                        • JoeCFDJ JoeCFD

                                          @mzimmers I do not know the mismatch issue. I have only Open Java 11 in my Linux computer.

                                          mzimmersM Offline
                                          mzimmersM Offline
                                          mzimmers
                                          wrote on last edited by mzimmers
                                          #61

                                          An update: I was able to install my application from the command line (using adb.exe). So, there's nothing wrong with my .apk file; it appears the problem is in Creator 12.0.1 (or the way I'm using it).

                                          ekkescornerE 2 Replies Last reply
                                          0

                                          • Login

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