title: ADB over TCP - Devices are connected and online but installing shows Error: Device not found
body: <p>Good day,</p>
  
  <p>I've been using a VMWare android machine and installing .apks on it but after my computer was unexpectedly shut down and tried to re-install a package I've been having the following problem:</p>
  
  <pre><code>$ adb -s 192.168.1.2 install 'myapp.apk'
  error: device not found
  - waiting for device -
  </code></pre>
  
  <p>However I was able to connect the VM using adb connect 192.168.1.2 which is the ip currently assigned on the android, (seen it on ctrl+f1 netcfg) and then shows:</p>
  
  <pre><code>connected to 192.168.1.2:5555
  
  $ adb devices
  List of devices attached 
  emulator-5554   offline
  192.168.1.2:5555    device
  </code></pre>
  
  <p>so it appears to be online.</p>
  
  <p>Troubleshooting steps taken before posting:</p>
  
  <ul>
  <li>$adb kill/start-server</li>
  <li>Reconfigured the VM Network (I have it bridged and Internet connection works fine).
  -Suspending/Shutting down and Restarting VM.
  -Restarting Internet connection (Router/PC connections)</li>
  </ul>
  
  <p>Kindly assist with situation or post links of another issue related to mine that I probably did not find (sorry for that..)</p>
  
  <p>Thanks!</p>
  
  <p>Edit: I'm using Fedora as OS, Eclipse for developing</p>