title: Chrome remote devices only detects android phone with android studio open
body: <p>I have already started developing an android app in the past and I found today that we can inspect a page on the browser of a remote device using the Remote devices tool on Chrome Dev Tools.</p>
  
  <p>To my surprise, my Android device wasn't being recognized in the Remote devices tab on Chrome, despite having already been detected previously in Android Studio in the past.</p>
  
  <p>I opened Android Studio to test if I could still deploy the app on the Android phone and... I could. And now I noticed that the phone was recognized in Chrome... WHAT?!</p>
  
  <p>I closed Android Studio and it went away again. When reopening Android Studio the phone isn't detected by Remote devices imediatly, it is only detected after I click run and the Select Deployment Target window appears.</p>
  
  <p>I suspect it has something to do with the initialization of the ADB, but I don't know what that is, it only says it is initializing when I click run on Android Studio. When Android Studio is closed I guess that is also closed and I need it to be running at all times. How can I keep it running outside of Android Studio and am I really supposed to be doing it or do I have something installed incorrectly?</p>
  
  <p>Details:</p>
  
  <p>Computer OS: Windows 10</p>
  
  <p>Computer Chrome version: 70.0.3538.77</p>
  
  <p>Android OS version: 7.0.0; SM-A520F Build/NRD90M</p>
  
  <p>Android Chrome version: 70.0.3538.64</p>
  
  <p>Android Studio Version: 3.2</p>
  
  <p>EDIT: Ok, so I downloaded the android standalone platform-tools from here: <a href="https://developer.android.com/studio/releases/platform-tools" rel="nofollow noreferrer">https://developer.android.com/studio/releases/platform-tools</a></p>
  
  <p>And ran a command line inside the downloaded folder and these were the results:</p>
  
  <p><code>C:\Users\rmarques\Desktop\platform-tools&gt;adb devices
  List of devices attached
  * daemon not running; starting now at tcp:5037
  * daemon started successfully
  521008c4650534ed        device</code></p>
  
  <p>So the problem is that the daemon is not running. After I close the command line it keeps running and my phone is still being recognized on remote devices.
  I understand that having a daemon start on boot every time may not be the best practice but it should start when I connect my phone using USB right?</p>
  
  <p>EDIT2: <a href="https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&amp;utm_medium=redirect&amp;utm_campaign=2016q3" rel="nofollow noreferrer">https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&amp;utm_medium=redirect&amp;utm_campaign=2016q3</a> doesn't even mention needing SDK tools or ADB or whatever, only the Drivers of the phone and minimum chrome versions/android OS.</p>