LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ADB on Slackware (https://www.linuxquestions.org/questions/slackware-14/adb-on-slackware-894707/)

Synderesis 07-30-2011 08:13 PM
ADB on Slackware
 
Just wondering if anyone else is developing apps for Android on Slackware? I'm hoping to try my hand at it soon, but for some reason, I can't get "adb devices" to show my device. It just displays a blank line.

When I use lsusb, my device is shown though so I don't see what's wrong. Mounting on Slackware has always been somewhat of a nightmare for me, so that might be what's going wrong here. Anyone have any idea?

MS3FGX 07-31-2011 07:32 AM
Have you added the appropriate lines to the UDEV rules, or else started the ADB server as root? By default, the device will not be accessible by a normal user account, so it wouldn't show up under "adb devices" even if it was properly detected.

skriatok 05-20-2012 02:39 PM
Quote:
Originally Posted by MS3FGX (Post 4429884)
Have you added the appropriate lines to the UDEV rules, or else started the ADB server as root? By default, the device will not be accessible by a normal user account, so it wouldn't show up under "adb devices" even if it was properly detected.
have same problem... adb running on multilibrary system... lsusb is showing my phone but adb devices is clear
udev rules applied

Alien Bob 05-20-2012 03:45 PM
You have to start the adb server as root if you are unable to get a device listing using "adb devices". I have to do so myself.

For instance, when I run "adb devices" I get this output:
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
????????????    no permissions
Then, run this:
Code:
$ adb kill-server
$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

$ adb devices
List of devices attached
SH226TJ00810    device
Eric

skriatok 05-20-2012 04:25 PM
Quote:
Originally Posted by Alien Bob (Post 4683424)
You have to start the adb server as root if you are unable to get a device listing using "adb devices". I have to do so myself.

For instance, when I run "adb devices" I get this output:
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
????????????    no permissions
Then, run this:
Code:
$ adb kill-server
$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

$ adb devices
List of devices attached
SH226TJ00810    device
Eric
aye! done that... so again:

phone htc desire s (saga)
is showing different lsusb when fastboot or when conected normaly running (that's normal)
when normaly running adb does notice the phone, once in fastboot mode adb devices is blank not even permission problem

Alien Bob 05-20-2012 04:34 PM
Ah, you did not give us dull details in your first post then!
The "adb devices" does not work for devices which are in fastboot mode. Instead you should use the commmand "fastboot devices" to get a listing of the attached device when it is in fastboot mode.

Eric

skriatok 05-21-2012 02:56 AM
Quote:
Originally Posted by Alien Bob (Post 4683446)
Ah, you did not give us dull details in your first post then!
The "adb devices" does not work for devices which are in fastboot mode. Instead you should use the commmand "fastboot devices" to get a listing of the attached device when it is in fastboot mode.

Eric
Erick cheers... Thank you... Once again detailed info is a detailed info... I'll improve thank you...

SOLVED for me


All times are GMT -5. The time now is 11:39 AM.