Note that there are some explanatory texts on larger screens.

plurals
  1. POadb devices command shows nothing
    primarykey
    data
    text
    <p>At the moment I'm busy with the Android SDK. I got it working, but when I entered <code>$sudo adb</code> shell. It gave <code>sudo: adb: command not found</code>. For this problem I checked this link: <a href="https://stackoverflow.com/questions/5510284/adb-devices-command-not-working">adb devices command not working</a> But if I enter $sudo adb devices now. Noting happens.</p> <p>Not even *daemon not running. starting it now op port 5037 * and the rest. But it looks like this:</p> <pre><code> michiel@ubuntu: ~$ sudo adb devices michiel@ubuntu: ~$ </code></pre> <p>So I can enter the next command. Someone knows how to fix that? It's the same with $sudo adb shell. Nothings comes up.</p> <p>When I enter adb devices without the sudo. I get the error: </p> <pre><code>-bash: /usr/local/sbin/adb: No such file or directory. </code></pre> <h3>But it's there!</h3> <pre><code>echo $PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/michiel/jdk1.6.0_29/bin:home/michiel/android-sdk-linux/tools:/home/michiel/android-sdk-linux/platform-tools </code></pre> <h3>Edit</h3> <p>When I start Eclipse now, I get the next error: <code>Failed to get the adb version: Cannot run program"/home/michiel/android-sdk-linux/platform-tools/adb":java.io.IOException:error=2, No such file or directory.</code></p> <h2>SOLVED</h2> <p>Last weekend I installed a clean install of Ubuntu. I downloaded the <code>ia32.lib and openjdk</code> instead of java jdk and install is manually. After some struggling I managed to connect the device and now I can see it. Thx for the help :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload