<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic This is an issue that we are in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Ghost-adb-instance-causing-debug-issues/m-p/1018751#M37238</link>
    <description>&lt;P&gt;This is an issue that we are currently looking into. Your previously mentioned workaround is the recommended approach at this time.&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2015 16:38:09 GMT</pubDate>
    <dc:creator>Elroy_A_Intel</dc:creator>
    <dc:date>2015-10-15T16:38:09Z</dc:date>
    <item>
      <title>Ghost adb instance causing debug issues</title>
      <link>https://community.intel.com/t5/Software-Archive/Ghost-adb-instance-causing-debug-issues/m-p/1018750#M37237</link>
      <description>&lt;P&gt;I have been having an increasing problem with XDK Android debugging. Essentially, the debugger will launch the app on the device, but will not attach itself, so instead of getting the Chrome Dev Tools interface in XDK, I am returned to the 'You can now begin your remote debugging session' view. The Android device, meanwhile, continues to run the application with no problem. No yellow bars, no error messages. Opening and closing XDK sometimes, but not always resolves the issue - increasingly I was having to solve this by restarting the machine.&lt;/P&gt;

&lt;P&gt;Looking at running services, after XDK is closed, I noticed that an instance of the adb is still running - I am assuming that is the Android Debug Bridge (http://developer.android.com/tools/help/adb.html) started by XDK, but apparently not killed correctly. See screenshot below:&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Capture (2).PNG"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/8126i96C067B1CA4446F0/image-size/large?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="Capture (2).PNG" alt="Capture (2).PNG" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Hitting 'End Task' and rerunning the debugger will allow me to get back to normal operations.&lt;/P&gt;

&lt;P&gt;Short of writing a script that kills all instances of that process when I run into this problem, are there any recommended solutions?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2015 14:49:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Ghost-adb-instance-causing-debug-issues/m-p/1018750#M37237</guid>
      <dc:creator>Matthew_G_6</dc:creator>
      <dc:date>2015-10-14T14:49:12Z</dc:date>
    </item>
    <item>
      <title>This is an issue that we are</title>
      <link>https://community.intel.com/t5/Software-Archive/Ghost-adb-instance-causing-debug-issues/m-p/1018751#M37238</link>
      <description>&lt;P&gt;This is an issue that we are currently looking into. Your previously mentioned workaround is the recommended approach at this time.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2015 16:38:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Ghost-adb-instance-causing-debug-issues/m-p/1018751#M37238</guid>
      <dc:creator>Elroy_A_Intel</dc:creator>
      <dc:date>2015-10-15T16:38:09Z</dc:date>
    </item>
  </channel>
</rss>

