<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: AndroidTether</title>
	<atom:link href="http://thegothicparty.com/dev/android/androidtether/feed/" rel="self" type="application/rss+xml" />
	<link>http://thegothicparty.com/dev/android/androidtether/</link>
	<description>Developement notes</description>
	<lastBuildDate>Sat, 16 Jul 2011 05:46:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: dev</title>
		<link>http://thegothicparty.com/dev/android/androidtether/comment-page-1/#comment-5</link>
		<dc:creator>dev</dc:creator>
		<pubDate>Thu, 29 Jan 2009 08:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://thegothicparty.com/dev/?p=48#comment-5</guid>
		<description>In Terminal, I look for the &lt;em&gt;adb&lt;/em&gt; process using the command:
&lt;code&gt;ps -acx -o pid,command&lt;/code&gt;
This will list all processes for the current user, with a neat 2 columns format.

To stop the &lt;em&gt;adb&lt;/em&gt; server, I first execute the command &lt;code&gt;adb kill-server&lt;/code&gt;, which generally stops a well behaved &lt;em&gt;adb&lt;/em&gt; process. Then, using the &lt;em&gt;{pid}&lt;/em&gt; returned by &lt;code&gt;ps ...&lt;/code&gt;, I execute &lt;code&gt;kill {pid}&lt;/code&gt;. I too have found this mechanism not entirely reliable, since occasionally some lingering &lt;em&gt;(adb)&lt;/em&gt; processes seem to simply refuse to go away, even if sent a &lt;code&gt;kill -9 {pid}&lt;/code&gt;.</description>
		<content:encoded><![CDATA[<p>In Terminal, I look for the <em>adb</em> process using the command:<br />
<code>ps -acx -o pid,command</code><br />
This will list all processes for the current user, with a neat 2 columns format.</p>
<p>To stop the <em>adb</em> server, I first execute the command <code>adb kill-server</code>, which generally stops a well behaved <em>adb</em> process. Then, using the <em>{pid}</em> returned by <code>ps ...</code>, I execute <code>kill {pid}</code>. I too have found this mechanism not entirely reliable, since occasionally some lingering <em>(adb)</em> processes seem to simply refuse to go away, even if sent a <code>kill -9 {pid}</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonEBarker</title>
		<link>http://thegothicparty.com/dev/android/androidtether/comment-page-1/#comment-4</link>
		<dc:creator>JonEBarker</dc:creator>
		<pubDate>Tue, 27 Jan 2009 16:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://thegothicparty.com/dev/?p=48#comment-4</guid>
		<description>Prior to using the Android Tether app, I tried to use the adb terminal command with no success.  The tether app worked yesterday, but fails to work today.  I think it may be conflicting with adb process.  Is there way to stop the adb process?  I can&#039;t find it running in the activity monitor and don&#039;t know the terminal command.  THANKS!!</description>
		<content:encoded><![CDATA[<p>Prior to using the Android Tether app, I tried to use the adb terminal command with no success.  The tether app worked yesterday, but fails to work today.  I think it may be conflicting with adb process.  Is there way to stop the adb process?  I can&#8217;t find it running in the activity monitor and don&#8217;t know the terminal command.  THANKS!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

