Device is busy error

[Iolaum]

I am testing mvt on my laptop and I am getting the following error:

$ mvt-android download-apks --output ./download-apks --virustotal
18:07:38 CRITICAL [mvt.android.modules.adb.base] Device is busy, maybe run `adb kill-server` and try again.

I think adb is working ok, because afterwards I can run a complex command such as:

# see installed applications:
$ adb shell "pm list packages -u -3" | cut -f 2 -d ":" | sort > installed-applications-$(date +%Y%m%d).info

and it works ok.

I 've also tried

$ adb kill-server
$ adb devices
# make sure permissions are given so that adb can see the device

but I got the error again.

I am running this on Fedora Silverblue 34 with the latest platform-tools 31.0.2 provided from Google.
My phone is a Le eco le pro 3 (zl1) running Lineage OS 18.1 with Gapps and Magisk.

[Iolaum]

I 've also tried the same process on a family member's Samsung Galaxy A40 updated with latest stock ROM device and got the same error. Getting the list of latest installed packages worked fine again.

[amirkarimi]

Same on Pixel 4 and Ubuntu 20.04.

Changed this:

mvt/mvt/android/modules/adb/base.py

Lines 64 to 65 in 065a62c

	except (USBErrorBusy, USBErrorAccess):
	log.critical("Device is busy, maybe run `adb kill-server` and try again.")

To:

except (USBErrorBusy, USBErrorAccess) as e:
    log.critical(f"Device is busy, maybe run `adb kill-server` and try again. {e}")

It reports:

CRITICAL [mvt.android.modules.adb.base] Device is busy, maybe run `adb kill-server` and try again. LIBUSB_ERROR_BUSY [-6]

So at least in my case, it's not access error.

[Nicceboy]

I had similar problem, and I had to make sure that ADB server daemon is not running on background.
Run adb kill-server but don't run adb devices afterwards, because it will start server again.

[davidmigloz]

In my case, it was because Android Studio was open.