安卓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淇℃伅鐨勶紝浣滀负娴嬭瘯鏈哄凡缁忚冻澶熷暒銆

锛堟湜妤间富閲囩撼鍝︼級