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. Adroid Debugging Fail
QtWS25 Last Chance

Adroid Debugging Fail

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
4 Posts 3 Posters 1.6k Views
  • 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.
  • E Offline
    E Offline
    ebonnett
    wrote on last edited by
    #1

    And yet something else to stop me from debugging on Android. Has anyone seen this issue? Here are the specifics on my dev environment:

    Qt Creator 4.6.2 using 5.11.0
    SDK - API's 28 and 27
    NDK - r10e
    Phones used: Nexus 6P, Galaxy S7, Galaxy S9, Galaxy Note 4
    OS - Windows 10

    Failed to get process path. Reason: The command "C:\Users<myUserName>\AppData\Local\Android\Sdk\platform-tools\adb.exe" terminated with exit code -1..
    Unexpected run control state RunControlState::Stopped when worker AndroidRunner started.

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mvuori
      wrote on last edited by
      #2

      If I remember right, people have complained about this for Qt 5.11. Anyway, it has serious bugs for Android, so you really should upgrade to 5.11.1 -- that's what bug fixing upgrades are for.

      1 Reply Last reply
      0
      • E Offline
        E Offline
        ebonnett
        wrote on last edited by
        #3

        Yep, I'm aware of what bug fixing point releases are for. That didn't fix it. Still seems like there is something continuously blocking the ports Qt is going for. Is anyone familiar with a way to see who's got the port locked up?

        1 Reply Last reply
        0
        • V Offline
          V Offline
          Vikas Pachdha
          wrote on last edited by
          #4

          Please check if the devices you are using supports "run-as" command. Some Samsung devices don't support the "run-as" command. QTC debugging workflow depends on "run-as" command and this might be the problem in your case. Just do "./adb shell run-as your_package_name pwd" and see if your device supports it.

          1 Reply Last reply
          2

          • Login

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