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. Debugging on physical Android device gives error code
Forum Updated to NodeBB v4.3 + New Features

Debugging on physical Android device gives error code

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
androidandroid debugadb devices
9 Posts 3 Posters 2.4k Views 2 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.
  • K Offline
    K Offline
    koahnig
    wrote on 20 Jan 2019, 15:18 last edited by
    #1

    I have managed to connect to physical Android device for debugging.

    Failed to get process path. Reason: The command "c:\Users\blabla\AppData\Local\Android\Sdk\platform-tools\adb.exe" terminated with exit code 1..
    
    "org.qtproject.example.SatelliteInfo_NTrial" died.
    

    I have checked a couple of times with "adb devices" that the actual device is listed. It is also shown for selection when the debug process is kicked off.

    However, very often I am receiving the error message above. Has anyone an idea what the cause is respetively how to work around?

    Vote the answer(s) that helped you to solve your issue(s)

    R 1 Reply Last reply 20 Jan 2019, 18:30
    0
    • K koahnig
      20 Jan 2019, 15:18

      I have managed to connect to physical Android device for debugging.

      Failed to get process path. Reason: The command "c:\Users\blabla\AppData\Local\Android\Sdk\platform-tools\adb.exe" terminated with exit code 1..
      
      "org.qtproject.example.SatelliteInfo_NTrial" died.
      

      I have checked a couple of times with "adb devices" that the actual device is listed. It is also shown for selection when the debug process is kicked off.

      However, very often I am receiving the error message above. Has anyone an idea what the cause is respetively how to work around?

      R Offline
      R Offline
      raven-worx
      Moderators
      wrote on 20 Jan 2019, 18:30 last edited by
      #2

      @koahnig
      maybe QTCREATORBUG-20841?
      Check if the run-as command is supported on the device.

      What device? Samsung?
      What QtCreator version? If possible a downgrade to 4.5 might help.

      --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
      If you have a question please use the forum so others can benefit from the solution in the future

      K 1 Reply Last reply 20 Jan 2019, 19:02
      1
      • R raven-worx
        20 Jan 2019, 18:30

        @koahnig
        maybe QTCREATORBUG-20841?
        Check if the run-as command is supported on the device.

        What device? Samsung?
        What QtCreator version? If possible a downgrade to 4.5 might help.

        K Offline
        K Offline
        koahnig
        wrote on 20 Jan 2019, 19:02 last edited by koahnig
        #3

        @raven-worx said in Debugging on physical Android device gives error code:

        @koahnig
        maybe QTCREATORBUG-20841?
        Check if the run-as command is supported on the device.

        I am trying USB-debugging

        What device? Samsung?

        Huawei P10

        What QtCreator version? If possible a downgrade to 4.5 might help.

        Qt creator 4.8.1
        Windows 10 64 bit
        Qt 5.11.3
        newest Android SDK
        Android NDK r10e

        Tried also the newest NDK, but this does not support g++ as reported by creator. Checked and it is really missing there.

        Funny thing is once in a while debug run (F5) does start the application on phone, but most of the time it does not (90%). It is acting completely unpredictable.

        Vote the answer(s) that helped you to solve your issue(s)

        R 1 Reply Last reply 21 Jan 2019, 07:45
        0
        • M Offline
          M Offline
          mvuori
          wrote on 20 Jan 2019, 19:38 last edited by
          #4

          There might be something in the Huaweis... I have a P20 that doesn't debug (I haven't spent much time solving the issue; I do any debugging an a Sony)

          K 1 Reply Last reply 21 Jan 2019, 19:49
          0
          • K koahnig
            20 Jan 2019, 19:02

            @raven-worx said in Debugging on physical Android device gives error code:

            @koahnig
            maybe QTCREATORBUG-20841?
            Check if the run-as command is supported on the device.

            I am trying USB-debugging

            What device? Samsung?

            Huawei P10

            What QtCreator version? If possible a downgrade to 4.5 might help.

            Qt creator 4.8.1
            Windows 10 64 bit
            Qt 5.11.3
            newest Android SDK
            Android NDK r10e

            Tried also the newest NDK, but this does not support g++ as reported by creator. Checked and it is really missing there.

            Funny thing is once in a while debug run (F5) does start the application on phone, but most of the time it does not (90%). It is acting completely unpredictable.

            R Offline
            R Offline
            raven-worx
            Moderators
            wrote on 21 Jan 2019, 07:45 last edited by
            #5

            @koahnig
            so did you check if the device supports the "adb run-as" command?
            Did you try to downgrade QtCreator?

            --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
            If you have a question please use the forum so others can benefit from the solution in the future

            K 2 Replies Last reply 21 Jan 2019, 09:37
            0
            • R raven-worx
              21 Jan 2019, 07:45

              @koahnig
              so did you check if the device supports the "adb run-as" command?
              Did you try to downgrade QtCreator?

              K Offline
              K Offline
              koahnig
              wrote on 21 Jan 2019, 09:37 last edited by
              #6

              @raven-worx said in Debugging on physical Android device gives error code:

              @koahnig
              so did you check if the device supports the "adb run-as" command?

              Newest SDK does not support. Have switched back to an older version which supports "run-as", but no luck either.
              This is still creator 4.8.1.

              Did you try to downgrade QtCreator?

              Still in process and fighting with tool chains at the moment.

              Vote the answer(s) that helped you to solve your issue(s)

              1 Reply Last reply
              0
              • R raven-worx
                21 Jan 2019, 07:45

                @koahnig
                so did you check if the device supports the "adb run-as" command?
                Did you try to downgrade QtCreator?

                K Offline
                K Offline
                koahnig
                wrote on 21 Jan 2019, 09:56 last edited by
                #7

                @raven-worx

                Failed to contact debugging port.
                

                This is with Qt creator 4.5.2, NDK r10e and an older SDK 26.0.2.

                Vote the answer(s) that helped you to solve your issue(s)

                1 Reply Last reply
                0
                • M mvuori
                  20 Jan 2019, 19:38

                  There might be something in the Huaweis... I have a P20 that doesn't debug (I haven't spent much time solving the issue; I do any debugging an a Sony)

                  K Offline
                  K Offline
                  koahnig
                  wrote on 21 Jan 2019, 19:49 last edited by koahnig
                  #8

                  @mvuori

                  You could be right that Huawei P10 is not cooperative. Activated my old Nexus Tablet and the debugging worked immediately and three times in a row. Switching back Huawei P10 running immediately into the return code again. Once in a while the debug maystart also with Huawei, but the debugging was not really either. The breakpoints were not accepted.

                  Either this is a hardware issue or the Android version might be also the reason. My Nexus 7 tablet runs Android 5.1, while the Huawei P10 runs Android 8.0.

                  Vote the answer(s) that helped you to solve your issue(s)

                  1 Reply Last reply
                  0
                  • K Offline
                    K Offline
                    koahnig
                    wrote on 21 Jan 2019, 20:07 last edited by
                    #9

                    Switched back to newer SDK folder holder a different adb version 1.0.40. That version did not support the run-as command as indicated above. Exited creator, started it again and did a rebuild and started debug on Nexus 7 without problems.

                    BTW all has been tested with creator 4.8.1 after I have seen no difference to old creator version 4.5.2.

                    Vote the answer(s) that helped you to solve your issue(s)

                    1 Reply Last reply
                    0

                    7/9

                    21 Jan 2019, 09:56

                    • Login

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