I'm pretty far from being a C++ expert, but I think this may be due to holding a reference to the Config beyond it's lifetime?

See StartDiscovery(): https://cs.android.com/android/platform/superproject/main/+/main:packages/modules/adb/client/transport_mdns.cpp;drc=2c73f5abdf31943e12c68e75f8148c10d2abbf6a;l=154?q=transport_mdns.cpp&ss=android

void StartDiscovery() {
    ...

    g_state->task_runner->PostTask([]() {
        //  optional<Config> created here
        auto config = GetConfigForAllInterfaces();
        if (!config) {
            return;
        }

        // long-lived reference of config given to OpenScreen
        g_state->service = discovery::CreateDnsSdService(g_state->task_runner.get(),
                                                         g_state->reporting_client.get(), *config);

        for (int i = 0; i < kNumADBDNSServices; ++i) {
            auto receiver = std::make_unique<ServiceReceiver>(
                    g_state->service.get(), kADBDNSServices[i], OnServiceReceiverResult);
            receiver->StartDiscovery();
            
            ...
        }

       ...

       // config destructed here
    });
}

A word on impact:

• We rely on WiFi debugging because we use the USB port for additional devices.
• This has made WiFi based debugging unreliable and painful to use because when ADB crashes the connection is lost and is not automatically re-created. Often it can required manually toggling WiFi debugging on the tablet.

I've left Wireshark running over the weekend to detect truncated MDNS queries and can confirm they are killing ADB. The truncated messages seem like valid network traffic, so it shouldn't be killing ADB.

Attached are wireshark records in a screenshot which line up with the ADB logs (timezone is Adelaide +10:30):

daniel@RES-0128:/ressys/maxedge$ cat /tmp/adb.5005.log | grep -ie Bridge -e OSP | tail
01-15 00:02:38.265 37828 37828 F adb     : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0: 
01-15 00:02:41.413 37846 37846 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 07:58:02.786 37846 37846 F adb     : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0: 
01-15 07:58:05.928 40026 40026 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:02:46.408 40026 40026 F adb     : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0: 
01-15 08:02:48.548 40054 40054 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:11:55.906 40054 40054 F adb     : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0: 
01-15 08:11:59.048 40092 40092 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:48:03.117 40092 40092 F adb     : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0: 
01-15 08:48:06.280 41928 41928 I adb     : main.cpp:63 Android Debug Bridge version 1.0.41

Have made a PR: https://android-review.googlesource.com/c/platform/packages/modules/adb/+/2909778

My previous comment giving the steps to replicate the issue appears to have been deleted. I have since forgotten the specifics of the steps, but can share the broad outlines.

1. Attached is a PCAP containing a truncated message.
2. Replay this PCAP over UDP (using a tool like https://github.com/ska-sa/udpreplay)

I am able to repro. I can reply with tcpreplay.

tcpreplay -i en0 ~/Downloads/truncated\ mDNS\ packets.pcapng

It looks like we are not using openscreen properly. Config should live as long as the Service is alive. The docs of MdnsResponder and MdnsServiceImpl are explicit.

MdnsResponder:

 // |record_handler|, |sender|, |receiver|, |task_runner|, |random_delay|, and
  // |config| are expected to persist for the duration of this instance's
  // lifetime.

MdnsServiceImpl

  // |task_runner|, |reporting_client|, and |config| must exist for the duration
  // of this instance's life.

Fixed in aosp/2909778

Eihafmryelhafmaree@gmail.com

Eihafmryelhafmaree@gmail.com

daemon not running; starting now at tcp:5037

Mine has an error with ui nit just the I, not sure how literal this verbose problem is...please keep us updated.....64 arm correct?

bugreport-X692-GL-QP1A.190711.020-2024-10-18-14-13-07.zip

navarretesergio404@gmail.com

Reda

https://drive.google.com/open?id=1AaFQQv5BQwDTOFOnTjGr1OBpyMbwJ0Mw

https://issuetracker.google.com/294120933#attachment46070672

Bardzo dobre

Zadowolony

Scan hacking

Please update my best practice

Excelente inicio

Please update

Done

tnx

Brigadao

Add a comment

.

Dnnddndn

https://www.earntp.com/m/h1jze

حل المشكلات

The problem is still the same after upgrading to version 34.0.1. I had to rollback to 33.0.3 to be able to install APK on my devices.

Boa noite sou novo aqui mecânico de motos a 30 anos preciso evoluir rs

Boa noite como sou mecânico de motos preciso de velocidade 🚄

Como destravar evoluir perdão fuiii tão rápido que não dei boa-noite

He he

When I tried running the: $adb kill-server && adb root command after running the: $export ADB_LIBUSB=1 command I got the following error: adb: unable to connect for root: device offline

So I just ran the adb install after I set the export ADB_LIBUSB=1 and it installed successfully.

Hi

Hey everyone! I had the same problem and this solution fixed my issues. I wanted to share the issue I was facing with ADB on a physical device. It was driving me crazy, but I managed to resolve it, and I thought it would be helpful to share it here for anyone who might face the same problem in the future.

First off, let me provide some context. I'm using a MacBook Pro Mid 2012 with an Intel 7 processor, and I'm running MacOS Monterey using OpenCore-Legacy-Patcher. The emulator was working fine, but I encountered errors when connecting a physical device (Samsung) to my setup.

When I ran flutter doctor -v without any phone connected, everything seemed to be in order. However, when I connected my phone, things went south. The error message I received was:

Exception: Unable to run "adb", check your Android SDK installation and ANDROID_SDK_ROOT environment variable:
/Users/me/Library/Android/sdk/platform-tools/adb

After some investigation, I came across this solution and it worked for me. Here are the steps I took:

1. Open a terminal window.
2. Run the following commands:

export ADB_LIBUSB=1
adb kill-server && adb root

After running these commands, I ran flutter doctor -v again, and voila! The issue was resolved, and everything was working smoothly. Here's the output I received:

[✓] Flutter (Channel stable, 3.3.3, on macOS 12.6.5 21G531 darwin-x64, locale en-CA)
    • Flutter version 3.3.3 on channel stable at /Users/lifen/SDKs/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18a827f393 (8 months ago), 2022-09-28 10:03:14 -0700
    • Engine revision 5c984c26eb
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/lifen/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • ANDROID_SDK_ROOT = /Users/lifen/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F17a
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • SM A520W (mobile) • 521011e6fca754cf • android-arm64 • Android 8.0.0 (API 26)
    • macOS (desktop) • macos • darwin-x64 • macOS 12.6.5 21G531 darwin-x64
    • Chrome (web) • chrome • web-javascript • Google Chrome 113.0.5672.126

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Explanation from ChatGPT:

The commands you ran did two things:

export ADB_LIBUSB=1: This command sets the ADB_LIBUSB environment variable to 1. When this variable is set, ADB uses the libusb library instead of the default USB library. This can sometimes resolve issues with device detection if there are problems with the default USB library.

adb kill-server && adb root: This command does two things. First, adb kill-server stops the ADB server process. Then, adb root restarts the ADB server with root permissions. This can resolve issues with device detection if the ADB server was not running or was running without the necessary permissions.

So, in summary, your issue was likely due to a problem with ADB, either because the Android SDK was not installed correctly, the ANDROID_SDK_ROOT environment variable was not set correctly, or the ADB server was not running with the necessary permissions. The commands you ran changed how ADB interacts with USB devices and restarted the ADB server with root permissions, which resolved the issue.

I hope this solution works for you too! If you have any questions or need further assistance, feel free to ask. Happy coding!

adb is GitHub the issue? olsonsebastian13@gmail.com SEBASTIAN S OLSON (406)849-1540✅

I concur the issue exists on MacOS Ventura 13.5 (M1) and adb Version 34.0.4-10411341.

An excerpt from the adb log:

adb server killed by remote request
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:1155 kicking transport 0x141e05120 fdd8dd0
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:407 BlockingConnectionAdapter(fdd8dd0): stopping
08-31 15:49:48.894 41776 3136798 I adb     : usb_osx.cpp:617 Kicking handle
08-31 15:49:48.894 41776 3136804 E adb     : usb_osx.cpp:592 usb_read failed with status: e00002eb
08-31 15:49:48.894 41776 3136804 I adb     : transport.cpp:339 fdd8dd0: read failed: Undefined error: 0
08-31 15:49:48.894 41776 3136804 I adb     : transport.cpp:1248 fdd8dd0: connection terminated: read failed
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:425 BlockingConnectionAdapter(fdd8dd0): stopped

Setting the ADB_LIBUSB fixes an issue.

Sorry, forgot to mention, it's on Android 9.0.6.

ReevesCharles

Attaching three files with logs:

1. ADB_LIBUSB is set -- OK.
2. ADB_LIBUSB is unset -- FAILS.
3. ADB_LIBUSB is set and copy over tcpip succeeds.

Correction to the above (can't edit):

3. ADB_LIBUSB is UNSET and copy over tcpip succeeds.

This is marked as closed and in the release notes for 34.0.4 but I'm not sure it's actually been addressed.

Running 34.0.4 adb very often hangs on install on my laptop. Reverting to 33.0.3 fixes the issue as mentioned above.

Once adb hangs on install it will also hang on any other commands until I run adb kill-server && adb start-server. This fixes the issue for a short period of time, but the next install will often fail.

I'm running this on a Macbook Pro with an M1 chip, running Ventura 13.4.

adb kill-server && adb start-server

Is there any update on this? My team and I are strongly affected by this as it really breaks the flow if you have to restart adb every couple of minutes. It works for a few builds but then quickly stops working... Is there anything we can do locally to circumvent the problem until the problem is fixed?

Adb kill server

Thank

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