Forums » Replicant development »
Unable to use adb with Samsung Galaxy N2; Thunar shows blinking phone icon and adb says no devices found
Added by Nichlas Severinsen over 7 years ago
Hi all, I'm kind of new so go ahead and yell at me if I get something wrong or if this is a duplicate.
I'm having a problem with a Samsung Galaxy N2 running the latest released version of Replicant (6.0 0002) as of 2017-09-21.
Attached is a video of the problems I am having (file: 'adb_what.webm').
Shortly put:
I am able to connect the N2 to a GNU/Linux computer, mount, read files, charge, etc. But when I enable android debugging on the phone and try to run an adb command (effectively starting the adb daemon on GNU/Linux), thunar shows the phone icon flashing/blinking. After some seconds adb says 'error: no devices/emulators found'.
I have to manually kill the adb daemon to make the blinking stop.
What am I doing wrong, and is there a fix? Has anybody else experienced this or had a similar problem?
Edit: Running the command as root makes no difference, btw.
| adb_what.webm (796 KB) adb_what.webm | Video of the problem I am having with adb |
Replies (2)
RE: Unable to use adb with Samsung Galaxy N2; Thunar shows blinking phone icon and adb says no devices found - Added by Nichlas Severinsen over 7 years ago
Almost seems to be some sort of problem with the binary distributed in the Arch repositories. When I run adb version I get:
Android Debug Bridge version 1.0.39
Revision 8.0.0_r4
And this is the binary that is causing the flashing/blinking and the no devices/emulators found.
I installed platform-tools from the AUR which comes with (or compiles) its own adb binary:
/opt/android-sdk/platform-tools/adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
And using that binary instead of the default /usr/bin/adb binary from the official repositories works, I am now able to run seemingly all adb commands and connect to my Note 2..
Real weird.
RE: Unable to use adb with Samsung Galaxy N2; Thunar shows blinking phone icon and adb says no devices found - Added by Wolfgang Wiedmeyer over 7 years ago
Thanks for confirming this! This was also reported on the mailing list in a related thread.
Unfortunately, it's not too uncommon that newer ADB versions quickly become incompatible with earlier Android versions. I believe I had a similar issue with Replicant 4.2 and an ADB version from Android 5.x sources.