Local Android Phone Acquisition Errors¶

Several issues might cause intaQt to not be able to acquire a local Android phone. A phone is available to intaQt when the intaQt application starts automatically upon plugging in the phone. To confirm its availability, visit the http://localhost:8080/phones link and see if the phone appears on the list of locally available phones.

Note: If the HTTP Server is configured to a different port than 8080, the URL will contain that port's number.

Troubleshooting Steps¶

The following steps should be taken to ensure that intaQt is running properly and the phones are in their correct state:

First ensure that intaQt was started using the Cockpit with the -a option .
If the error still persists, check that the Developer Options and USB debugging are enabled on the target phone, as described here.
Check the state of the locally attached phones by calling adb devices in a terminal console. The device's serial number should show up there and have the status device.

Example

1
2
3

$ adb devices
List of devices attached
044e1df9308aaa95    device

If the local Android phone's acquisition status is offline or no permissions, the following procedure may resolve the problem:

Check if the phone is not set on "Only Charge" mode.
Turn the USB Debugging option off and on again, remove the cable and reconnect it. Run adb devices.
Restart the adb server by calling adb kill-server in a terminal console.
Unplug the phone, reboot it, then plug it again.
Unplug the phone, disable and then re-enable Developer Options and USB debugging on the phone. Next, plug the phone into a different USB port on the computer.
Change the connected mode (Charging Mode, MTP, PTP) may also help with making the devices available (especially on Windows)

Note: For additional information, refer to the Android Run Apps on a Hardware Device page or the following ADB Troubleshooting Link.