IssueTracker

var loop = function() { // do cool stuff }

doc/api/n-api.md

I'm on 34.0.5 now for a few weeks now and the problem is still the same as with previous version - adb only works for a few minutes after killing it.

Hello, I'm mostly experiencing this while developing on the Android emulators, but it's happening on all emulators and on a physical device (specs below). In terms of connection it happens on the emulator, usb-C cable (tried 2 different ones, with 2 different original Apple hubs) and on Wi-Fi debugging connection.

In terms of reproducibility, it's reproducible 100%. But I can't trigger it. I stop ADB by running killall -9 adb, Android studio reconnects it and it works for cca. 15-30 minutes. And then at some point, suddenly, stops working.

Symptoms:

• logcat in AS stops updating
• trying to install the app through AS doesn't work (says "waiting for devices" but never finishes)
• debugger doesn't connect
• adb commands mostly don't respond, except for --help or --version (I guess because they're static and don't rely on server)

About ADB_LUBUSB, I'm only running adb from Android Studio. How do I tell it to export that value to 1? I also don't know how to get logs on adb. Googling didn't help, I only found instructions on how to get logs off the Android device that's connected over adb, not for the adb itself. Any tips?

Computer

Apple M1 Max
macOS Ventura 13.6

Android Studio

Android Studio Giraffe | 2022.3.1 Patch 4
Build #AI-223.8836.35.2231.11090377, built on November 13, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Devices

Emulator Pixel 4, API 33, Android 13.0 Google Play, arm64-v8a (used mostly)
Emulator Pixel 6a, API 34, Android 14.0 Google Play, arm64-v8a
OnePlus 8, Android 13

Java version

➜  ~ java --version
openjdk 17.0.6 2023-01-17
OpenJDK Runtime Environment Temurin-17.0.6+10 (build 17.0.6+10)
OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (build 17.0.6+10, mixed mode)

ADB version

➜  ~ adb --version
Android Debug Bridge version 1.0.41
Version 34.0.5-10900879
Installed as /Users/.../Library/Android/sdk/platform-tools//adb
Running on Darwin 22.6.0 (arm64)

I set the ADB_LIBUSB to 1 and it still happened:

➜  ~ killall -9 adb
➜  ~ export ADB_LIBUSB=1  
➜  ~ echo $ADB_LIBUSB 
1
➜  ~ adb devices
List of devices attached
emulator-5554	device

// 1 hour later ...

➜  ~ echo $ADB_LIBUSB   
1
➜  ~ adb devices
^C                   <- I had to kill the command manually as it didn't return anything for 1 minute
➜  ~ killall -9 adb
➜  ~ adb devices
List of devices attached
emulator-5554	device

https://zoho.com/us/expense/kb/reports/share-my-report/

فعلت تحديث كامل للفون software

Hey sh... sorry for the late reply. The problem is still here. I tried the steps you wrote above and I can't activate the root user, I get this:

➜  ~ adb shell setprop persist.adb.trace_mask 0
Failed to set property 'persist.adb.trace_mask' to '0'.
See dmesg for error reason.
➜  ~ adb root
adbd cannot run as root in production builds
➜  ~ 

What does this mean? Any way around that?

I managed to find a solution to the problem adbd cannot run as root in production builds, I had to use the emulator without Play Store included, I had only the Google APIs.

Regarding the original issue, this weekend I updated my Android Studio to the stable Iguana 2023.2.1 and I also update SDK which included ADB 35.0.0-11411520 (1.0.41) and for the past 27 hours I didn't have to kill adb once. So it seems the problem is fixed, at least for me. Thanks!

How install

Reinstall all

I'm sad to inform you that the issue reappeared. My whole team and I are back to killing adb on an hourly basis. :(

I'm on

Android Debug Bridge version 1.0.41
Version 35.0.0-11411520
Running on Darwin 23.5.0 (arm64)

And Android Studio is

Android Studio Jellyfish | 2023.3.1 Patch 1
Build #AI-233.14808.21.2331.11842104, built on May 15, 2024
Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

#270205252

https://support.microsoft.com/en-us/feed/rss/ec99850d-21a3-8453-ca47-447a97b72d4c

Job #7016766573 failed for bfa1f69b05c111e8b5a0cd597b19b227a1dd14c2:

https://raw.githubusercontent.com/michaelWuensch/BitBanana/master/docs/REPRODUCE.md

@gh voda unlimited 💓.tnl

This fix has made my custom AOSP based device not being recognized as an Android device (not there at all on the adb devices list). Only downgrading to 34.0.4 helps. OSX Sonoma 14.5, MacBook Air M2.

Let me know if you'd like me to provide some debug logs to help with fixing that in the latest version.

I need to Update my New Phone right now to android 15

Hello, this issue is very present for us. We have a custom AOSP-based device (Android 10) that now often fails to be shown in the device list or hangs on the install command. Sometimes, downgrading to adb prior to 34.0.5 fixes the issue, sometimes upgrading above 34.0.4 fixes it. Sometimes it cannot be fixed. So far we were unable to find a correlation between OS&hardware and the step that fixes it.

Here are adb host logs from a device that attempted connecting with adb 34.0.4-10411341. It is an M1 Pro with Ventura 13.6.1.

One file has the logs where the device was not listed with adb devices, the other file are the logs from where adb devices showed the device, but then adb install hung indefinitely.

both of those traces seem to be using the non-libusb macOS usb backend, which is no longer supported. please repro with a 35.* adb using libusb.

#404

Kongpc14567@gmail.com