安卓x8670eth0

⑴ 安裝Android-x86無法上網怎麼辦

1 首先確定機子是處於聯網狀態的。 進入Android-x86的終端模擬器（相當於Win系統的命令提示符）。 2 輸入命令「ip a」獲取所有網卡配置如果可以發現eth0網卡，那麼恭喜，系統已經認出了VM的虛擬網卡，可以繼續看下面了。如果沒發現這個eth0，那麼還是將此系統刪除，重新安裝別的版本吧。Android-x86有好幾個版本，我試驗之後發現eeepc的版本對網卡的支持比較好。 3 用su命令獲取最高許可權。 4 為網卡指定ip、掩碼、網關等信息。如果DHCP可用，則執行「dhcpcd eth0」自動獲取，如果沒有DHCP服務可用，則可以手動指定，命令是：su ifconfig eth0 192.168.10.250 netmask 255.255.255.0 up route add default gw 192.168.10.1 dev eth0。相信能看到本文此處的小盆友都能看明白，就不再解釋了。 5 設置dns。執行如下命令：setprop net.dns18.8.8.8，如果你不想用google的這個dns伺服器，也可以使用本地的，不過要保證可用。 6 至此，我們已經為eth0網卡配置了ip和dns信息，登錄Android-x86，打開自帶的瀏覽器，可以發現瀏覽網頁已經木有問題了，但是想要下載某些軟體的時候，還是無法下載，下載進度條會一直停止不動，一些系統自帶的服務（如地圖）也仍然無法使用。這是因為系統只認wifi，沒有wifi設備系統就認為沒有上網，為乙太網卡配置IP和DNS之後可以騙過瀏覽器，但是系統不認那一套，所以上網的問題只能是初步解決，希望有高手可以解決這個問題。（貌似網上已經有一位日本友人做出了VirtualBox虛擬機下的鏡像，VMware下的還有待高手繼續開發）另，看到有的網友提出了別的解決方案：通過「電子郵件」設置好自己的賬戶，然後在電腦上將需要安裝的APK文件發給自己，在虛擬上打開收件箱就可以直接安裝了。這倒是一種不錯的解決方案。

⑵ 濡備綍debug android cts

鍚鍔ㄥ拰鍏抽棴ADB鏈嶅姟錛坅db start-server鍜宎dbkill-server錛
緇忎綔鑰呮祴璇曪紝妯℃嫙鍣ㄥ湪榪愯屼竴孌墊椂闂村悗錛宎db鏈嶅姟鏈夊彲鑳斤紙鍦╓indows榪涚▼涓鍙浠ユ壘鍒拌繖涓鏈嶅姟錛岃ユ湇鍔＄敤鏉ヤ負妯℃嫙鍣ㄦ垨閫氳繃USB鏁版嵁綰胯繛鎺ョ殑鐪熸満鏈嶅姟錛変細鍑虹幇寮傚父銆傝繖鏃墮渶瑕侀噸鏂板筧db鏈嶅姟鍏抽棴鍜岄噸鍚銆傚綋鐒訛紝閲嶅惎Eclipse鍙鑳戒細瑙ｅ喅闂棰橈紝浣嗛偅姣旇緝楹葷儲銆傚傛灉鎯蟲墜宸ュ叧闂璦db鏈嶅姟錛屽彲浠ヤ嬌鐢ㄥ備笅鍛戒護錛
1. adb kill-server
鍦ㄥ叧闂璦db鏈嶅姟鍚庯紝瑕佷嬌鐢ㄥ備笅鍛戒護鍚鍔╝db鏈嶅姟錛
1. adb start-server

閾炬帴DLNA緗戠粶鐨勫懡浠わ細
ifconfig eth0 down; ifconfig eth0 hw ether 00:00:00:00:fd:87; ifconfig eth0 up; udhcpc

涓嬮潰鐨勬柟娉曟槸鏇撮傚悎RD 鏉debug CTS issue鐨刢ts榪愯屾柟寮, 榪欐牱瑙ｅ喅浜嗕竴涓澶ч棶棰: 濡傛灉鐢╝ndroid浼犵粺鏂瑰紡鍘昏繍琛宑ts鐨勮瘽,蹇呯劧宸茬粡琚玞ts 榪愯岀幆澧冨崰鐢ㄤ簡adb絝鍙,鐢╡clipsedebug灝辨棤娉曞湪鍙﹀栦竴鍙版満鍣ㄤ笂榪涜(渚嬪俁DPC, eclipse debug涔熼渶瑕乤db ), 鍞涓鐨勬柟寮, 灝辨槸鎶奱ndroid鐨剆ource code鎼鍒癱ts 榪愯岀殑ubuntu鏈哄櫒涓, 鐢變簬size鐗瑰埆澶,闈炲父涓嶄究.

涓嬮潰浠嬬粛鐨勮繍琛屾柟寮, 鐩存帴鐢╝db 鍘繪ā鎷 cts鐜澧冪殑榪愯屾柟寮, 鍞涓鐨勭己鐐規槸, 涓涓猼est涓涓猼est 鐨勮繍琛. 浣嗘槸, 瀵筊D鏉ヨ,榪欏弽鑰屾槸浼樼偣! 鏂逛究蹇鎹.

榪欎釜鏂規硶姒傛嫭涓涓嬪氨鏄: 鍦ㄦ垜浠鐨刡ranch 涓婂氨鏈塩ts 鐨剆ourcecode, 鎴戜滑鍙浠ヤ慨鏀瑰叾涓鏌愪釜test case鎵瀵瑰簲鐨 apk source, 涔嬪悗,build 鍑 apk, 鐒跺悗瀹夎呭埌鏉垮瓙涓婂幓run. 濡傛灉鎴戜滑淇鏀圭殑testcase apk,灝辨槸娣誨姞浜嗕竴浜沵essage/log涔嬬被鐨, 灝辯珛鍗沖彲浠ュ湪榪愯岃繃紼嬩腑浣撶幇鍑烘潵. 鍚屾椂,鎴戜滑鍙浠ュ埄鐢╡clipse/ddms鐩哥粨鍚 debug android framework閮ㄥ垎, 褰撶劧, 鐢變簬鎴戜滑涔熸湁apk鐨剆ourcecode, 涔熷彲浠debug test case apk鏈韜.

璇峰弬鑰:
鍒氬仛瀹屽疄楠 , 鍐欎笅 SOP 緇欏悇浣嶅弬鑰冣
涔嬪緦鑻ユ湁 RD 闇瑕, 涔熷彲浠ュ弬鑰冭繖浠解.

Steps:
1)cmd> cd android/ics-4.x (鍒 android 鐩褰)
2)cmd>make cts

Q) 濡備綍鐭ラ亾0801鐨刢ts 鐗堟湰 ?
A)cmd> catandroid/ics-4.x/tools/tradefed-host/src/com/android/cts/tradefed/build/CtsBuildProvider.java| grepCTS_BUILD_VERSION
Result:public static final String CTS_BUILD_VERSION = "4.0.3_r2";

3)cmd>cd out/host/linux-x86/cts/android-cts/repository/testcases
4)鎵懼埌闇瑕佹祴璇曠殑apk 騫禼opy 鍒癙C絝痜ile folder
Ex: CtsTestStubs.apk, CtsOsTestCases.apk, android.core.tests.runner.apk, CtsMyExampleTestCases.apk

5)紜瀹歅C 鍙鐢╝db 榪炲埌target
6)
cmd>adbinstall CtsMyExampleTestCases.apk (瀹夎呴渶瑕佹祴璇曠殑 apk)
cmd>adb install CtsTestStubs.apk (榪欐槸google澶у氬師鐢焧estapk 闇瑕佺敤鍒扮殑 stub)
cmd>adbinstall CtsOsTestCases.apk
cmd>adbinstall android.core.tests.runner.apk
7)cmd>adb shell pm list instrumentation (鐢ㄦ潵鏌ョ湅宸茬粡瀹夎呯殑instrumentation, 姣忎釜 CTS 鐢ㄦ祴鐨 apk 閮芥槸鐢╥nstrumentation)
Result:
Instrumentation:com.android.cts.myexample/android.test.InstrumentationTestRunner (target=com.android.cts.myexample)
8)
鏁翠釜 package 嫻嬭瘯
cmd>adbshell am instrument 鈥搘 鈥搑 com.android.cts.myexample/android.test.InstrumentationTest(鎵ц岃 test package)
姝ゆ椂鍙鏌ョ湅 failed (濡備笅:Step8 test result example),涔熷彲閫忚繃 logcat log鏉ョ湅 fail (濡備笅:[test result from logcat])

鍗曚竴class嫻嬭瘯
cmd> adb shellam instrument 鈥揺 classandroid.myexample.cts.MySampleCalculatorTest鈥搘 鈥搑com.android.cts.myexample/android.test.InstrumentationTestRunner
cmd> adb shellam instrument 鈥揺 classandroid.os.cts.MyHelloTest鈥搘 鈥搑com.android.cts.os/android.test.InstrumentationCtsTestRunner
鍗曚竴function嫻嬭瘯
cmd> adbshell am instrument 鈥揺 classandroid.myexample.cts.MySampleCalculatorTest#testAdd鈥搘 鈥搑com.android.cts.myexample/android.test.InstrumentationTestRunner

9) 縐婚櫎嫻嬭瘯鐢 apk (cmd: adb uninstall<app_name> 脿 <app_name>鍙浠 target 絝鏌ヨ: ls /data/app )
cmd> adb uninstall com.android.cts.os
cmd> adb uninstall com.android.cts.stub
cmd> adb uninstall com.android.cts.myexample

=== [Step8: test result example] ===
INSTRUMENTATION_STATUS:id=InstrumentationTestRunner
INSTRUMENTATION_STATUS: current=1
INSTRUMENTATION_STATUS:class=android.myexample.cts.MySampleCalculatorTest
INSTRUMENTATION_STATUS: stream=
android.myexample.cts.MySampleCalculatorTest:
INSTRUMENTATION_STATUS: numtests=2
INSTRUMENTATION_STATUS: test=testAdd
INSTRUMENTATION_STATUS_CODE: 1
INSTRUMENTATION_STATUS:id=InstrumentationTestRunner
INSTRUMENTATION_STATUS: current=1
INSTRUMENTATION_STATUS:class=android.myexample.cts.MySampleCalculatorTest
INSTRUMENTATION_STATUS: stream=.
INSTRUMENTATION_STATUS: numtests=2
INSTRUMENTATION_STATUS: test=testAdd
INSTRUMENTATION_STATUS_CODE: 0
INSTRUMENTATION_STATUS:id=InstrumentationTestRunner
INSTRUMENTATION_STATUS: current=2
INSTRUMENTATION_STATUS: class=android.myexample.cts.MySampleCalculatorTest
INSTRUMENTATION_STATUS: stream=
INSTRUMENTATION_STATUS: numtests=2
INSTRUMENTATION_STATUS:test=testSubtration
INSTRUMENTATION_STATUS_CODE: 1
INSTRUMENTATION_STATUS:id=InstrumentationTestRunner
INSTRUMENTATION_STATUS: current=2
INSTRUMENTATION_STATUS:class=android.myexample.cts.MySampleCalculatorTest
INSTRUMENTATION_STATUS: stream=
Failure in testSubtration:
junit.framework.AssertionFailedError:expected:<20> but was:<30>
atandroid.myexample.cts.MySampleCalculatorTest.testSubtration(MySampleCalculatorTest.java:63)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:545)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551)

INSTRUMENTATION_STATUS:numtests=2
INSTRUMENTATION_STATUS:stack=junit.framework.AssertionFailedError: expected:<20> but was:<30>
at android.myexample.cts.MySampleCalculatorTest.testSubtration(MySampleCalculatorTest.java:63)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:545)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551)

INSTRUMENTATION_STATUS:test=testSubtration
INSTRUMENTATION_STATUS_CODE: -2
INSTRUMENTATION_RESULT: stream=
Test results forInstrumentationTestRunner=..F
Time: 0.079

FAILURES!!!
Tests run: 2, Failures: 1, Errors: 0

INSTRUMENTATION_CODE: -1

===[test result from logcat] ====

/ethernet(6210): Loading ethernet jni class
D/AndroidRuntime(6210): Calling main entry com.android.commands.am.Am
I/ActivityManager(1143): Force stopping package com.android.cts.myexample uid=10036
I/ActivityManager(1143): Start proc com.android.cts.myexample for added applicationcom.android.cts.myexample: pid=6220 uid=10036 gids={}
I/TestRunner(6220): started: testAdd(android.myexample.cts.MySampleCalculatorTest)
I/TestRunner(6220): finished: testAdd(android.myexample.cts.MySampleCalculatorTest)
I/TestRunner(6220): passed: testAdd(android.myexample.cts.MySampleCalculatorTest)
I/TestRunner(6220): started: testSubtration(android.myexample.cts.MySampleCalculatorTest)
I/TestRunner(6220): failed: testSubtration(android.myexample.cts.MySampleCalculatorTest)
I/TestRunner(6220): ----- begin exception -----
I/TestRunner(6220):
I/TestRunner(6220): junit.framework.AssertionFailedError: expected:<20> butwas:<30>
I/TestRunner(6220): at junit.framework.Assert.fail(Assert.java:47)
I/TestRunner(6220): atjunit.framework.Assert.failNotEquals(Assert.java:282)
I/TestRunner(6220): at junit.framework.Assert.assertEquals(Assert.java:64)
I/TestRunner(6220): atjunit.framework.Assert.assertEquals(Assert.java:201)
I/TestRunner(6220): atjunit.framework.Assert.assertEquals(Assert.java:207)
I/TestRunner(6220): at android.myexample.cts.MySampleCalculatorTest.testSubtration(MySampleCalculatorTest.java:63)
I/TestRunner(6220): at java.lang.reflect.Method.invokeNative(NativeMethod)
I/TestRunner(6220): at java.lang.reflect.Method.invoke(Method.java:511)
I/TestRunner(6220): at junit.framework.TestCase.runTest(TestCase.java:154)
I/TestRunner(6220): at junit.framework.TestCase.runBare(TestCase.java:127)
I/TestRunner(6220): atjunit.framework.TestResult$1.protect(TestResult.java:106)
I/TestRunner(6220): at junit.framework.TestResult.runProtected(TestResult.java:124)
I/TestRunner(6220): at junit.framework.TestResult.run(TestResult.java:109)
I/TestRunner(6220): at junit.framework.TestCase.run(TestCase.java:118)
I/TestRunner(6220): at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
I/TestRunner(6220): atandroid.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
I/TestRunner(6220): atandroid.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:545)
I/TestRunner(6220): atandroid.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551)
I/TestRunner(6220): ----- end exception -----
I/TestRunner(6220): finished: testSubtration(android.myexample.cts.MySampleCalculatorTest)
I/ActivityManager(1143): Force stopping package com.android.cts.myexample uid=10036
I/ActivityManager(1143): Killing proc 6220:com.android.cts.myexample/10036: force stop
D/AndroidRuntime(6210): Shutting down VM

⑶ 請教EM1和eth0的區別是什麼

在centos6.4之前，如果6.2,6.3安裝後網卡名稱都是em開始，如果想用eth0這種名稱，或者是自定義名稱，可以參照以下來實施。
第一步：修改/boot/grub/grub.conf
增加一個 biosdevname=0 的啟動參數
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-220.el6.x86_64)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-220.el6.x86_64 ro root=UUID=6e7bf859-80f1-4875-8e8a-6f0fbdc9c90d nomodeset rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us rd_NO_MD quiet rhgb crashkernel=auto LANG=zh_CN.UTF-8 rd_NO_LVM rd_NO_DM biosdevname=0
initrd /boot/initramfs-2.6.32-220.el6.x86_64.img
第二步：修改當前網卡配置文件的名稱
mv ifcfg-em1 ifcfg-eth0
mv ifcfg-em2 ifcfg-eth1
第三步：修改網卡配置文件內容，把em1全部修改改為eth0
[root@xingfujie ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
IPADDR=XXXXX
PREFIX=24
GATEWAY=XXXXX
DNS1=XXXXX
DEFROUTE=yes
UUID=XXXXXX
HWADDR=XXXXXX
全部修改完畢後，reboot從起電腦即可。

⑷ 涓轟粈涔坴irtualbox涓嬪畨瑁卆ndroid x86涓嶈兘涓婄綉

鐪嬩笂鍘葷郴緇熷彧鏄娌℃湁鎵懼埌dhcp鏈嶅姟鍣錛岃窡閭ｅ彞鎻愮ず涔熶笉涓瀹氭湁鍏崇郴錛岄偅鍙ユ彁紺虹殑鎰忔濇槸璇寸郴緇熼噷闈㈡病鏈夊崟璋冭℃椂鍣錛岃℃椂鏈夊彲鑳芥湁閿欙紝涓嶈繃鎯蟲潵瀵繪壘dhcp鏈嶅姟鍣ㄤ竴鑸涓嶄細澶涔咃紝搴旇ヤ笉浼氭湁澶氬ぇ褰卞搷銆
ifb0: broadcasting for a lease鍜屽悗闈㈢殑閭ｅ彞timeout涔嬮棿澶ф傞殧浜嗗氫箙

⑸ 濡備綍鍦╒irtualBox鉶氭嫙鏈轟腑瀹夎匒ndroid x86

1銆侀栧厛涓嬭澆騫跺畨瑁咃細
銆銆(浣犲綋鐒跺彲浠ラ夋嫨浣跨敤VMWare錛屼絾鍒蹇樿癡MWare涓嶆槸鍏嶈垂鐨勩傚ソ鍚э紝鎴戞壙璁ゅ湪鍥藉唴闅忎究楗朵竴鍦堝彲浠ユ壘鍒版棤鏁扮牬瑙ｇ増鎴栬呮敞鍐岀爜錛屼絾鏈夊厤璐硅屼笖寮婧愮殑VirtualBox鑳芥浛浠ｏ紝灝變笉瑕佸仛榪欐牱鐨勪簨鎯呬簡銆傛瘯絝熷ぇ瀹朵篃鏄鍋氬紑鍙戠殑錛屽紑鍙戜竴嬈句駭鍝佹槸澶氫箞涓嶆槗錛屼綘鎳傚緱錛)

銆銆鍦ㄤ笅杞紸ndroid-x86鐨勬椂鍊欙紝涓瀹氳佹敞鎰忎笅杞界殑鐗堟湰銆傚傛灉浣跨敤VirtualBox榪愯岀殑璇濓紝涓瀹氳板緱鍦ㄤ笅杞絉OM鏃墮夋嫨EEEPC鐗堛傛嵁鎴戝疄璺電粡楠屾潵鐪嬶紝鍏朵粬鐗堟湰鐨凴OM鍦╒irtualBox涓婂畨瑁呬互鍚庣綉緇滈厤緗閮戒細鍑洪棶棰橈紝閭ｄ箞灝卞け鍘繪剰涔変簡銆傚傛灉浣跨敤VMWare鍒欏彲浠ラ殢鎰忛夋嫨鐗堟湰錛堣矊浼礆級銆傚傛灉澶у朵笉鎯沖湪鍚庨潰鐨勯厤緗涓瑙夊緱錏嬬柤錛屽氨璇蜂笅杞紼EEPC鐗堢殑ISO鍚с

銆銆2銆佹柊寤鴻櫄鎷熸満
銆銆VirtualBox涓鏂板緩鉶氭嫙鏈烘椂錛歄perationSystem 鍜 Version鍒嗗埆閫夋嫨 Other銆丱ther/Unknown銆傛帴涓嬫潵鍒嗛厤鍐呭瓨銆佺‖鐩樺ぇ灝忕瓑銆傚唴瀛樺ぇ灝忔帹鑽768M鎴栬1G宸﹀彸瓚充互銆傜‖鐩樺ぇ灝忓垯鍙浠ユ牴鎹瀹為檯鎯呭喌鍒嗛厤鍚堥傜殑鏁板箋傝繖涓榪囩▼澶綆鍗曪紝榪欓噷灝變笉鍐嶅氳В閲婁簡銆

銆銆3銆佸畨瑁匛EEPC鐗圛SO

銆銆鉶氭嫙鏈哄惎鍔ㄤ箣闂達紝鏂板緩CD-ROM騫跺皢ISO鏂囦歡鍒跺畾鍒板叾涓銆

銆銆鉶氭嫙鏈虹綉緇滅被鍨嬮夋嫨妗ユ帴Bridged Adapter銆

銆銆絎涓嬈″惎鍔ㄨ櫄鎷熸満錛屾牴鎹鐪嬪埌鐨勫悜瀵煎皢鏂板緩鍒嗗尯錛屽苟鍦ㄨュ垎鍖哄畨瑁匒ndroid-x86鐩稿簲鐨処SO緋葷粺銆傜敱浜庝笉闇瑕佸叾浠栬繃澶氱殑璁劇疆錛屾墍浠ュ皢鍒嗛厤鐨勭‖鐩樺叏鏁版牸寮忓寲鎴恊xt3鏍煎紡錛屽苟鍦ㄥ叾涓瀹夎呭嵆鍙銆傚畨瑁呭畬鎴愪箣鍚庡惎鍔ㄨ櫄鎷熸満錛屽氨鍙浠ョ湅鍒板彲鐖辯殑Android榪愯屽暒銆傝繖閫熷害錛屽彲鐪熶笉鏄鐩栫殑銆備笉璧烽偅錏嬬柤鐨別mulator瑕佸ソ寰堝氬緢澶氬暒錛屽ぇ瀹跺彲浠ヤ韓鍙椾簡銆

銆銆4銆佺綉緇滈厤緗

銆銆鎺ヤ笅鏉ュ綋鐒惰佽〢ndroid鑳藉熻窇璧鋒潵鎵嶅ソ銆傚埆嫻璐規椂闂村湪鉶氭嫙鏈洪噷闈㈤厤緗甒IFI絳夌綉緇滆劇疆錛岄偅鐜╂剰鍎挎牴鏈涓嶈搗浣滅敤銆傛ラゅ備笅錛

銆銆鍦ㄨ櫄鎷熸満鍚鍔ㄤ互鍚庣晫闈涓婃寜涓嬶細Alt+F1錛屽彲浠ュ垏鎹㈠埌鍛戒護琛屾ā寮忋傚懡浠よ屼笅鍐欏懡浠わ細netcfg鍙浠ョ湅鍒拌櫄鎷熸満涓鐨勭綉緇滆劇疆銆傛垜浠鍙浠ョ湅鍒頒竴涓127.0.0.1鐨勫湴鍧鍜屽彟澶栦竴涓璁懼囧悕縐頒負eth0錛孖P鍦板潃鏄0.0.0.0鐨勫湴鍧銆傛帴涓嬫潵鏁插叆鍛戒護錛歞hcpcd鍙浠ュ彟eth0璁懼囧惎鍔ㄩ厤緗甀P鍦板潃銆傚畬鎴愪箣鍚庡湪浣跨敤鍛戒護錛歴etprop net.dns1 8.8.8.8 鏉ヨ劇疆DNS鏈嶅姟鍣ㄤ負璋鋒瓕鐨凞NS鏈嶅姟鍣(鎴栦綘鎵鍦ㄥ湴鍖虹殑DNS鏈嶅姟鍣)銆傚湪鍛戒護琛屾寜涓嬶細Alt+F7鍒囨崲鍥炲浘褰㈢晫闈銆

銆銆5銆丒clipse閾炬帴VirtualBox
銆銆浠ヤ笂姝ラゅ畬鎴愪箣鍚庯紝鑻ユ兂瑕佽嚜宸辯殑紼嬪簭琚鍙戝竷鍒拌櫄鎷熸満涓錛岄渶瑕佷嬌鐢╝db閾炬帴鍒拌櫄鎷熸満涓銆傚湪涓婅堪榪囩▼涓閫氳繃DHCP鑾峰彇鍒扮殑鉶氭嫙鏈篒P鍦板潃涓猴細192.168.1.14銆傚垯闇瑕佸湪鍛戒護琛屼腑浣跨敤adb connect鍛戒護榪炴帴鍒拌櫄鎷熸満涓銆
銆銆Window錛氳繘鍏ュ埌Android SDK涓璦db鎵鍦ㄧ殑鐩褰曪紝騫惰繍琛岋細abc connect 192.168.1.14
銆銆Ubuntu錛氳繘鍏ュ埌Android SDK涓璦db鎵鍦ㄧ殑鐩褰曪紝騫惰繍琛岋細 ./adb connect 192.168.1.14

銆銆鐩鍓嶈繕涓嶇煡閬撶殑涓滆タ鏄錛屽備綍瀹炵幇灞忓箷鐨勫弽杞錛孏PS絳変竴浜涗俊鎮銆備絾鎴戝湪ROM涓鍙戠幇涓涓搴旂敤杈僃ake GPS搴旇ュ氨鏄鎻愪緵GPS淇℃伅鐨勶紝浣滀負嫻嬭瘯鏈哄凡緇忚凍澶熷暒銆

錛堟湜妤間富閲囩撼鍝︼級