diff options
Diffstat (limited to 'docs/html/tools/help')
| -rw-r--r-- | docs/html/tools/help/adb.jd | 98 | ||||
| -rw-r--r-- | docs/html/tools/help/proguard.jd | 31 |
2 files changed, 115 insertions, 14 deletions
diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index c25990f..c339943 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -27,6 +27,7 @@ page.tags="adb" </li> <li><a href="#logcat">Enabling logcat logging</a></li> <li><a href="#stopping">Stopping the adb server</a></li> + <li><a href="#wireless">Wireless usage</a></li> </ol> </div> @@ -1342,3 +1343,100 @@ application and sends 500 pseudo-random events to it.</p> You can then restart the server by issuing any other adb command. </p> +<h2 id="wireless">Wireless usage</h2> + +<p> +adb is usually used over USB. However, it is also possible to use over +Wi-Fi, as described here. +</p> + +<ol> + +<li> +Connect Android device and adb host computer +to a common Wi-Fi network accessible to both. +We have found that not all access points +are suitable; you may need to use an access point +whose firewall is configured properly to support adb. +</li> + +<li> +Connect the device with USB cable to host. +</li> + +<li> +Make sure adb is running in USB mode on host. +<pre> +$ adb usb +restarting in USB mode +</pre> +</li> + +<li> +Connect to the device over USB. +<pre> +$ adb devices +List of devices attached +######## device +</pre> +</li> + +<li> +Restart host adb in tcpip mode. +<pre> +$ adb tcpip 5555 +restarting in TCP mode port: 5555 +</pre> +</li> + +<li> +Find out the IP address of the Android device: +Settings -> About tablet -> Status -> IP address. +Remember the IP address, of the form <code>#.#.#.#</code>. +</li> + +<li> +Connect adb host to device: +<pre> +$ adb connect #.#.#.# +connected to #.#.#.#:5555 +</pre> +</li> + +<li> +Remove USB cable from device, and confirm you can still access device: +<pre> +$ adb devices +List of devices attached +#.#.#.#:5555 device +</pre> + +</ol> + +<p> +You're now good to go! +</p> + +<p> +If the adb connection is ever lost: +</p> + +<ol> + +<li> +Make sure that your host is still connected to the same Wi-Fi network your Android device is. +</li> + +<li> +Reconnect by executing the "adb connect" step again. +</li> + +<li> +Or if that doesn't work, reset your adb host: +<pre> +adb kill-server +</pre> +and then start over from the beginning. +</li> + +</ol> diff --git a/docs/html/tools/help/proguard.jd b/docs/html/tools/help/proguard.jd index 3ba7db2..aa9a0bc 100644 --- a/docs/html/tools/help/proguard.jd +++ b/docs/html/tools/help/proguard.jd @@ -25,11 +25,14 @@ parent.link=index.html <h2>See also</h2> <ol> - <li><a href="http://proguard.sourceforge.net/manual/introduction.html">ProGuard - Manual »</a></li> - - <li><a href="http://proguard.sourceforge.net/manual/retrace/introduction.html">ProGuard - ReTrace Manual »</a></li> + <li> + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard + Manual »</a> + </li> + <li> + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/retrace/introduction.html">ProGuard + ReTrace Manual »</a> + </li> </ol> </div> </div> @@ -146,14 +149,14 @@ proguard.config=/path/to/proguard.cfg </pre> <p>There are many options and considerations when using the <code>-keep</code> option, so it is - highly recommended that you read the <a href="http://proguard.sourceforge.net/manual/introduction.html">ProGuard - Manual</a> for more information about customizing your configuration file. The <a href= - "http://proguard.sourceforge.net/manual/usage.html#keepoverview">Overview of Keep options</a> and - <a href="http://proguard.sourceforge.net/index.html#/manual/examples.html">Examples section</a> - are particularly helpful. The <a href= - "http://proguard.sourceforge.net/manual/troubleshooting.html">Troubleshooting</a> section of the - ProGuard Manual outlines other common problems you might encounter when your code gets stripped - away.</p> + highly recommended that you read the + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard + Manual</a> for more information about customizing your configuration file. The + <em>Overview of Keep options</em> and <em>Examples</em> sections are particularly helpful. + The <a href= + "http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/troubleshooting.html">Troubleshooting + </a> section of the ProGuard Manual outlines other common problems you might encounter + when your code gets stripped away.</p> <h2 id="decoding">Decoding Obfuscated Stack Traces</h2> @@ -192,4 +195,4 @@ proguard.config=/path/to/proguard.cfg <p>How you save the <code>mapping.txt</code> file is your decision. For example, you can rename them to include a version or build number, or you can version control them along with your source - code.</p>
\ No newline at end of file + code.</p> |