No response on ADB devices

[thefrog]

Until i can discover more about it I’m holding off on the update. I need to read more into what is changing to see how its affecting adb. Until then I can only guess that an adb update will be needed.

[Astra]

Sure sir,

And what i think from my perspective
adb version is working well where the daemon is not needed

but for devices and others daemon is used to run
So, it might be the issue of dbus unit. well It’s just my assumption.

[pebcak]

@Astra

it might be the issue of dbus unit

adb works fine on my end with the following:

$ uname -r 
6.7.0-zen1-1-zen

$ pacman -Ss dbus
core/dbus 1.14.10-2 [installed]
    Freedesktop.org message bus system
core/dbus-broker 35-2 [installed]
    Linux D-Bus Message Broker
core/dbus-broker-units 35-2 [installed]
    Linux D-Bus Message Broker - Service units

$ adb version
Android Debug Bridge version 1.0.41
Version 34.0.4-android-tools
Installed as /usr/bin/adb
Running on Linux 6.7.0-zen1-1-zen (x86_64)

$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
xxxx.......xxxx......xxxx

[Astra]

Then why is daemon is not running on mine

[fred666]

What happens when you do this command? If there is something wrong with the adb deamon it will show a error i guess?

# adb start-server

[Astra]

Finally fixed it.
This was all because of traccar an open source Modern GPS Tracking Platform a project that I was working on

Apparently Traccar server was still installed on this dev system and uses the same port ADB uses. Removing or Stopping Traccar fixed the issue.

Start the Traccar using sudo systemctl start traccar
Stop the Traccar using sudo systemctl stop traccar

Sorry @thefrog and other guys for making trouble. And many thanks for guiding me