Debugging on physical Android device gives error code
-
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)
-
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?
@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. -
@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.@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 r10eTried 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.
-
@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 r10eTried 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.
@koahnig
so did you check if the device supports the "adb run-as" command?
Did you try to downgrade QtCreator? -
@koahnig
so did you check if the device supports the "adb run-as" command?
Did you try to downgrade QtCreator?@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.
-
@koahnig
so did you check if the device supports the "adb run-as" command?
Did you try to downgrade QtCreator?Failed to contact debugging port.This is with Qt creator 4.5.2, NDK r10e and an older SDK 26.0.2.
-
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)
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.
-
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.
