Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to build an Android development environment in Linux

2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/01 Report--

Linux how to build an Android development environment, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

1. System environment

[android@localhost] $uname-a

Linux localhost.localdomain 2.6.32-71.el6.i686 # 1SMP Wed Sep 1 01:26:34 EDT 2010 i686 i686 i386 GNU/Linux

[android@localhost] $lsb_release-a

LSB Version:: core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch

Distributor ID: RedHatEnterpriseServer

Description: Red Hat Enterprise Linux Server release 6. 0 (Santiago)

Release: 6.0

Codename: Santiago

[android@localhost ~] $

2. Prepare the software

Java

Eclipse

Android-sdk

ADT

These softwares can be downloaded from the official website.

3. Construction process

(1) install java

[android@localhost ~] $rpm-qa | grep java

Eclipse-mylyn-java-3.3.2-4.5.el6.i686

Java-1.6.0-openjdk-devel-1.6.0.0-1.21.b17.el6.i686

Java-1.6.0-openjdk-1.6.0.0-1.21.b17.el6.i686

Tzdata-java-2010l-1.el6.noarch

Gcc-java-4.4.4-13.el6.i686

Java-1.5.0-gcj-1.5.0.0-29.1.el6.i686

Subversion-javahl-1.6.11-2.el6.i686

Ooobasis3.3-javafilter-3.3.0-9567.i586

Libvirt-java-0.4.5-2.el6.noarch

Lpg-java-compat-1.1.0-4.1.el6.noarch

Libvirt-java-devel-0.4.5-2.el6.noarch

Mysql-connector-java-5.1.12-2.el6.i686

Ant-javamail-1.7.1-13.el6.i686

Java-1.6.0-openjdk-javadoc-1.6.0.0-1.21.b17.el6.i686

Java_cup-0.10k-5.el6.i686

[android@localhost ~] $

Use the command to see the relevant jdk that currently has java installed, and you can proceed to the next step.

(2) install eclipse

Eclipse downloaded from the official website does not need to be installed and can be used by decompressing it directly. Such as:

[android@localhost Base Env] $ls

ADT-18.0.0.zip

Android-sdk_r18-linux.tgz

Android development environment building (Linux). Doc

Eclipse

Eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

Build Linux environment .doc

Build Android development environment under Linux. Doc

[android@localhost Base Env] $rm-R eclipse

[android@localhost Base Env] $ls

ADT-18.0.0.zip

Android-sdk_r18-linux.tgz

Android development environment building (Linux). Doc

Eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

Build Linux environment .doc

Build Android development environment under Linux. Doc

[android@localhost Base Env] $tar-zxfeclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

[android@localhost Base Env] $ls

ADT-18.0.0.zip

Android-sdk_r18-linux.tgz

Android development environment building (Linux). Doc

Eclipse

Eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

Build Linux environment .doc

Build Android development environment under Linux. Doc

[android@localhost Base Env] $cd eclipse

[android@localhost eclipse] $ls

About_files configuration eclipse.ini icon.xpm p2

About.html dropins epl-v10.html libcairo-swt.so plugins

Artifacts.xml eclipse features notice.html readme

[android@localhost eclipse] $ll

Total dosage 540

Drwxrwxr-x. 2 android android 4096 February 17 03:06 about_files

-rw-rw-r--. 1 android android 18909 February 8 21:55 about.html

-rw-rw-r--. 1 android android 88246 February 17 03:06 artifacts.xml

Drwxrwxr-x. 5 android android 4096 February 17 03:06 configuration

Drwxrwxr-x. 2 android android 4096 February 17 03:06 dropins

-rwxr-xr-x. 1 android android 62814 February 8 22:16 eclipse

-rw-rw-r--. 1 android android 407 February 17 03:06 eclipse.ini

-rw-rw-r--. 1 android android 16536 February 8 21:36 epl-v10.html

Drwxrwxr-x. 46 android android 4096 February 17 03:06 features

-rw-rw-r--. 1 android android 9022 February 8 21:54 icon.xpm

-rwxr-xr-x. 1 android android 266168 February 8 21:54 libcairo-swt.so

-rw-rw-r--. 1 android android 8951 February 8 21:36 notice.html

Drwxrwxr-x. 5 android android 4096 February 17 03:05 p2

Drwxrwxr-x. 10 android android 36864 February 17 03:06 plugins

Drwxrwxr-x. 2 android android 4096 February 17 03:06 readme

[android@localhost eclipse] $. / eclipse

After launching eclipse, eclipse will automatically create and find the workspace folder, you can directly click the ok button. The startup process of eclipse is shown in the following figure:

Eclipse can also double-click the eclipse executable file directly under the gnome desktop to start.

(3) install android-sdk

[android@localhost Base Env] $tar-zxfandroid-sdk_r18-linux.tgz

[android@localhost Base Env] $ls

ADT-18.0.0.zip

Android-sdk-linux

Android-sdk_r18-linux.tgz

Android development environment building (Linux). Doc

Eclipse

Eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

Build Linux environment .doc

Build Android development environment under Linux. Doc

[android@localhost Base Env] $cdandroid-sdk-linux/

[android@localhost android-sdk-linux] $ls

Add-ons platforms SDK Readme.txt tools

[android@localhost android-sdk-linux] $cd tools/

[android@localhost tools] $ll

The total dosage is 6772

-rw-rw----. 1 android android 323 March 30 23:20 adb_has_moved.txt

-rwxrwx---. 1 android android 3491 March 30 23:19 android

Drwxrwx---. 2 android android 4096 March 30 23:19 ant

-rwxrwx---. 1 android android 30 March 1977 23:19 apkbuilder

Drwxrwx---. 3 android android 4096 March 30 23:19 apps

-rwxrwx---. 1 android android 3116 March 30 23:19 ddms

-rwxrwx---. 1 android android 46724 March 30 23:19 dmtracedump

-rwxrwx---. 1 android android 1940 March 30 23:19 draw9patch

-rwxrwx---. 1 android android 24828 March 30 23:19 emulator

-rwxrwx---. 1 android android 2814128 March 30 23:19 emulator-arm

-rwxrwx---. 1 android android 2765428 March 30 23:19 emulator-x86

-rwxrwx---. 1 android android 136860 March 30 23:19 etc1tool

-rwxrwx---. 1 android android 3282 March 30 23:19 hierarchyviewer

-rwxrwx---. 1 android android 9680 March 30 23:19 hprof-conv

Drwxrwx---. 6 android android 4096 March 30 23:19 lib

-rwxrwx---. 1 android android 30 March 2015 23:19 lint

-rwxrwx---. 1 android android 9676 March 30 23:19 mksdcard

-rwxrwx---. 1 android android 3169 March 30 23:19 monkeyrunner

-rw-rw----. 1 android android 379587 March 30 23:20 NOTICE.txt

Drwxrwx---. 7 android android 4096 March 30 23:19 proguard

-rw-rw----. 1 android android 66 March 30 23:19 source.properties

-rwxrwx---. 1 android android 613856 March 30 23:19 sqlite3

Drwxrwx---. 2 android android 4096 March 30 23:19 support

-rwxrwx---. 1 android android 3044 March 30 23:19 traceview

-rwxrwx---. 1 android android 46784 March 30 23:19 zipalign

[android@localhost tools] $. / android update sdk

The upgrade and update interface of android simulator opens here, as shown in the following figure:

The next operation is mainly to download and upgrade the relevant packages in the simulator, which may take a long time (I will basically keep the boot on at night when upgrading, because of the incompatibility between Android systems. Of course, if you are only targeting a particular version of the Android system, it will be much faster. However, you can also download and install it later. ):

You can choose Aceept all:

After clicking the Install button, you will jump to the following interface, where, at the bottom of the dialog box, you will see the download speed and progress of the current package:

AndroidSDK Manager sometimes pops up the following log dialog box, where you can see more detailed information (you can close the dialog box. If you do need to see it next time, you can click the button behind the back color button, and the manager will open the log dialog box):

After the android-sdk installation is successful, under this directory, Android SDK Manager creates a platform-tools folder that contains android commands such as adb that you will already use.

During the download process, SDK Menager will pop up the site authentication information shown in the figure below, which can be ignored:

After the download and installation is complete, the Android SDK Manager pops up the following dialog box:

At this point, you can check the relevant packages labeled Not installed, and click Install*package to install the relevant packages that you choose not to install, but most of the installed packages need you to provide site authentication information. Screenshots of related information are as follows:

At this point, Android SDK Manager is installed.

(4) install the ADT plug-in

First, you need to start eclipse

Click Help- > Install New Software... in IDE Open the Install dialog box for eclipse, as shown in the following figure:

Click Add... Button to open the Add Repository dialog box:

In this week, you can fill in the Location input box with the URL of the ADT you downloaded. But at this point, in order to speed up the installation, you can download ADT locally, and then click Archive... Button:

At this point, you need to select the ADT you just downloaded (remember, do not extract it):

Here, just click ok:

Check Developer Tools in Name, click Next directly to install:

At this point, you need to accept the terms of the agreement, and then click the Finish button:

In the installation interface, you can click the Details > > button to view the current details, and a progress prompt will also be given in the lower right corner of Eclipse's IDE interface:

During the installation of the plug-in, the following warning message may pop up. After reading the message, you will click the OK button like me:

After the installation is complete, Eclipse will let you choose whether or not to restart Eclipse to apply the new changes you just brought to IDE, which varies from time to time:

After restarting to enter Eclipse, normally, the dialog box of Welcome to Android Development will pop up:

If the dialog box does not pop up, you can make the necessary settings in Android in Window- > Perferences

This setting item is located under SDK Location.

What needs to be set here is Target Location. You can click Browse.... To browse and select the path address of your previously installed Android-sdk-linux:

Click OK:

Next, a simple Next:

Next, you need to select an installable package, generally click Accept All:

After this process is installed, you can open Android Virtual Device Manager through Window- > AVD Manager in Eclipse. It can also be opened through the android bash file under tools, but it may be a little difficult and should not be recommended.

Set the tablet "driver" of Skyworth M6

(please allow to call it this, only because it is similar to the drive effect under Windows. After this setting, you can open Skyworth M6's adb to use.)

1. Use the lsusb command to view the USB devices of the system:

[android@bogon ~] $lsusb

Bus 002 Device 005: ID 0bb4:0c02 High Tech ComputerCorp. Dream / ADP1 / G1 Phone (Debug)

Bus 002 Device 003: ID 093a:2510 Pixart Imaging,Inc. Optical Mouse

Bus 002 Device 002: ID 8087:0020 Intel Corp.Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation2.0 root hub

Bus 001 Device 002: ID 8087:0020 Intel Corp.Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation2.0 root hub

[android@bogon ~] $

It can be seen that the 0bb4 in Debug mode is the ID of Skyworth M6.

2. Under the tools directory of the switched android-sdk-linux, update adb:

[android@bogon tools] $. / androidupdate adb

Adb has been updated. You must restart adb with thefollowing commands

Adbkill-server

Adbstart-server

[android@bogon tools] $

3. Try to view Android devices:

[android@bogon platform-tools] $. / adb devices

* daemon not running. Starting it now on port 5037 *

* daemon started successfully *

List of devices attached

? No permissions

[android@bogon platform-tools] $

It can be seen that the execution of the command failed and returned results that I do not know.

4. Add the ID of Skyworth M6 to the adb_usb.ini file (you must have root permission, and the file exists in the hidden .Android folder):

[android@bogon ~] $suroot

Password:

[root@bogon android] # ls-al

Total dosage 200

Drwx-. 34 android android 4096 April 13 09:10.

Drwxr-xr-x. 5 root root 4096 April 13 08:57..

Drwx-. 3 android android 4096 April 13 09:01. Adobe

Drwxrwxr-x. 3 android android 4096 April 13 09:18. Android

Drwxrwxr-x. 4 android android 4096 April 13 09:13 Base Env

-rw-r--r--. 1 android android 18 June 22 2010. Bash _ logout

-rw-r--r--. 1 android android 176.22 2010. Bash _ profile

-rw-r--r--. 1 android android 124 June 22 2010. Bashrc

Drwxr-xr-x. 3 android android 4096 April 13 08:58. Cache

Drwxr-xr-x. 6 android android 4096 April 13 09:13 .config

Drwx-. 3 android android 4096 April 13 08:58 .dbus

-rw-r--r--. 1 android android 500 January 24 2007. Emacs

-rw-. 1 android android 16 April 13 08:58. ESD _ auth

Drwx-. 4 android android 4096 April 13 08:59 .gconf

Drwx-. 2 android android 4096 April 13 09:09 .gconfd

Drwxr-xr-x. 7 android android 4096 April 13 09:07. Gnome2

Drwx-. 2 android android 4096 April 13 08:58. Gnome2 _ private

Drwxrwxr-x. 3 android android 4096 April 13 08:58 .gnote

Drwx-. 2 android android 4096 April 13 08:58. Gnupg

Drwxrwxr-x. 2 android android 4096 April 13 08:58 Gstreamer-0.10

-rw-rw-r--. 1 android android 200 April 13 08:58. Gtk-bookmarks

Drwx-. 2 android android 4096 April 13 08:58 .gvfs

-rw-. 1 android android 310 April 13 08:58. ICE authority

-rw-r--r--. 1 android android 794 April 13 08:58 .imsettings.log

Drwx-. 3 android android 4096 April 13 09:09 .kde

-rw-r--r--. 1 android android 121 June 29 2010. Kshrc

Drwxr-xr-x. 3 android android 4096 April 13 08:58 .local

Drwx-. 3 android android 4096 April 13 09:01. Macromedia

-rw-r--r--. 1 android android 124 June 25 2010. Mkshrc

Drwxr-xr-x. 5 android android 4096 April 13 08:58. Mozilla

Drwxr-xr-x. 2 android android 4096 April 13 08:58. Nautilus

Drwx-. 2 android android 4096 April 13 08:58. Pulse

-rw-. 1 android android 256 April 13 08:58. Pulse-cookie

-rw-. 1 android android 218 April 13 09:07. Recently-used.xbel

Drwxrwxr-x. 3 android android 4096 April 13 08:58 .redhat

Drwx-. 2 android android 4096 April 13 08:58 .ssh

Drwx-. 3 android android 4096 April 13 09:10.

Drwxrwxr-x. 3 android android 4096 April 13 09:10 workspace

-rw-. 1 android android 50 April 13 08:57. XauthoxIGCv

-rw-. 1 android android 4401 April 13 09:26. Xsession-errors

-rw-r--r--. 1 android android 658 December 9 2009 .zshrc

Drwxr-xr-x. 2 android android 4096 April 13 08:58 Public

Drwxr-xr-x. 2 android android 4096 April 13 08:58 template

Drwxr-xr-x. 2 android android 4096 April 13 08:58 video

Drwxr-xr-x. 2 android android 4096 April 13 08:58 Picture

Drwxr-xr-x. 2 android android 4096 April 13 08:58 document

Drwxr-xr-x. 2 android android 4096 April 13 09:13 download

Drwxr-xr-x. 2 android android 4096 April 13, 08:58 Music

Drwxr-xr-x. 2 android android 4096 April 13 08:58 desktop

[root@bogon android] # cd.android/

[root@bogon .android] # ls

Adb_usb.ini avd

[root@bogon .android] # vimadb_usb.ini

[root@bogon .android] # lsusb

Bus 002 Device 008: ID 0bb4:0c02 High Tech ComputerCorp. Dream / ADP1 / G1 Phone (Debug)

Bus 002 Device 003: ID 093a:2510 Pixart Imaging,Inc. Optical Mouse

Bus 002 Device 002: ID 8087:0020 Intel Corp.Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation2.0 root hub

Bus 001 Device 002: ID 8087:0020 Intel Corp.Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation2.0 root hub

[root@bogon .android] # gvimadb_usb.ini

# ANDROID 3RD PARTY USBVENDOR ID LIST-DO NOT EDIT.

# USE 'android updateadb' TO GENERATE

# 1 USB VENDOR ID PERLINE.'

0x0bb4# the content in front of this paragraph is the original saved content of the file, just add the ID of Skyworth M6 at the end.

5. Create a file / etc/udev/rules.d/im-android.rules file with root permissions, and add the following red and bold text to it, the meaning of which you can guess. Remember to give the file readable executable permissions.

[root@bogon .android] # cd..

[root@bogon android] # cd..

[root@bogon home] # gvim/etc/udev/rules.d/imx-android.rules

SUBSYSTEM== "usb", SYSFS {idVendor} = = "0bb4", MODE= "0666"

[root@bogon home] # gvim/etc/bash.bashrc

[root@bogon home] # exit

Exit

[android@bogon ~] $cdBase\ Env/

[android@bogon Base Env] $ls

ADT-18.0.0.zip eclipse

Android-sdk-linux eclipse-cpp-indigo-SR2-incubation-linux-gtk.tar.gz

Android-sdk_r18-linux.tgz

[android@bogon Base Env] $cd android-sdk-linux/

[android@bogon android-sdk-linux] $ls

Add-ons docs platforms platform-tools SDK Readme.txt temp tools

[android@bogon android-sdk-linux] $cd platform-tools/

[android@bogon platform-tools] $. / adb devices

List of devices attached

? No permissions

[android@bogon platform-tools] $. / adb kill-server

[android@bogon platform-tools] $. / adb start-server

* daemon not running. Starting it now on port 5037 *

* daemon started successfully *

[android@bogon platform-tools] $. / adb devices

List of devices attached

? No permissions

[android@bogon platform-tools] $cd / etc/udev/rules.d

[android@bogon rules.d] $ll

Total consumption 76

-rw-r--r--. 1 root root 6627 June 24 2010 40-hplip.rules

-rw-r--r--. 1 root root 226 August 18 2010 51-dlm.rules

-rw-r--r--. 1 root root 495 June 24 2010 56-hpmud_support.rules

-rw-r--r--. 1 root root 1652 August 26 201060-fprint-autosuspend.rules

-rw-r--r--. 1 root root 1060 June 29 2010 60-pcmcia.rules

-rw-r--r--. 1 root root 452 August 13 2010 60-raw.rules

-rw-r--r--. 1 root root 292 July 17 2010 70-cups-libusb.rules

-rw-r--r--. 1 root root 788 February 21 02:41 70-persistent-cd.rules

-rw-r--r--. 1 root root 460 February 21 01:49 70-persistent-net.rules

-rw-r--r--. 1 root root 1914 January 13 2010 85-pcscd_ccid.rules

-rw-r--r--. 1 root root 320 May 15 2009 90-alsa.rules

-rw-r--r--. 1 root root 83 July 28 2010 90-hal.rules

-rw-r--r--. 1 root root 359 August 18 2010 90-rdma.rules

-rw-r--r--. 1 root root 53 April 19 2010 91-drm-modeset.rules

-rw-r--r--. 1 root root 2486 June 30 201097-bluetooth-serial.rules

-rw-r--r--. 1 root root 292 August 30 2010 98-kexec.rules

-rw-r--r--. 1 root root 54 April 9 2010 99-fuse.rules

-rw-r--r--. 1 root root 53 April 13 09:39 imx-android.rules

[android@bogon rules.d] $su root

Password:

[root@bogon rules.d] # chmod+rx imx-android.rules

[root@bogon rules.d] # ll

Total consumption 76

-rw-r--r--. 1 root root 6627 June 24 2010 40-hplip.rules

-rw-r--r--. 1 root root 226 August 18 2010 51-dlm.rules

-rw-r--r--. 1 root root 495 June 24 2010 56-hpmud_support.rules

-rw-r--r--. 1 root root 1652 August 26 201060-fprint-autosuspend.rules

-rw-r--r--. 1 root root 1060 June 29 2010 60-pcmcia.rules

-rw-r--r--. 1 root root 452 August 13 2010 60-raw.rules

-rw-r--r--. 1 root root 292 July 17 2010 70-cups-libusb.rules

-rw-r--r--. 1 root root 788 February 21 02:41 70-persistent-cd.rules

-rw-r--r--. 1 root root 460 February 21 01:49 70-persistent-net.rules

-rw-r--r--. 1 root root 1914 January 13 2010 85-pcscd_ccid.rules

-rw-r--r--. 1 root root 320 May 15 2009 90-alsa.rules

-rw-r--r--. 1 root root 83 July 28 2010 90-hal.rules

-rw-r--r--. 1 root root 359 August 18 2010 90-rdma.rules

-rw-r--r--. 1 root root 53 April 19 2010 91-drm-modeset.rules

-rw-r--r--. 1 root root 2486 June 30 2010 97-bluetooth-serial.rules

-rw-r--r--. 1 root root 292 August 30 2010 98-kexec.rules

-rw-r--r--. 1 root root 54 April 9 2010 99-fuse.rules

-rwxr-xr-x. 1 root root 53 April 13 09:39 imx-android.rules

[root@bogon rules.d] #

6. Start / etc/init.d/udev-post service:

[root@bogon rules.d] # / etc/init.d/udevrestart

Bash: / etc/init.d/udev: there is no such file or directory

[root@bogon rules.d] # cd/etc/init.d/

[root@bogon init.d] # ls | grep udev

Udev-post

[root@bogon init.d] # / etc/init.d/udev-postrestart

Usage: / etc/init.d/udev-post {start | stop | reload}

[root@bogon init.d] # / etc/init.d/udev-postreload

Refire failed udev events [OK]

[root@bogon init.d] # / etc/init.d/udev-poststart

Refire failed udev events [OK]

[root@bogon init.d] # cd/home/android/Base\ Env/android-sdk-linux/platform-tools/

[root@bogon platform-tools] #. / adb kill-server

[root@bogon platform-tools] #. / adb devices

* daemon not running. Starting it now on port 5037 *

* daemon started successfully *

List of devices attached

0123456789ABCDEF device

[root@bogon platform-tools] #

[root@bogon platform-tools] #. / adb shell

# pwd

/

# ls

Config

Cache

Udisk

Flash

Sdcard

Acct

Mnt

Vendor

D

Etc

Ueventd.rk29board.rc

Ueventd.rc

Ueventd.goldfish.rc

System

Sys

Sbin

Proc

Init_battery.sh

Init.rk29board.rc

Init.rc

Init.goldfish.rc

Init

Default.prop

Data

Root

Dev

# exit

[root@bogon platform-tools] #

7. In order to run adb like other bash commands, that is, do not add ". /" before, you need to modify the corresponding environment variable configuration file, which you can do as follows:

[root@bogon platform-tools] # vim / etc/profile

...

Export Android_HOME=/home/android/Base\ Env/android-sdk-linux

Export PATH=$PATH:$Android_HOME/platform-tools

[root@bogon platform-tools] # source / etc/profile

[root@bogon platform-tools] # exit

[android@bogon ~] $

[android@bogon ~] $echo$PATH

/ usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/android/bin

In order to leave the environment variables you set, you can source the file as follows:

[android@bogon ~] $source/etc/profile

[android@bogon ~] $echo$PATH

/ usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/android/bin:/home/android/BaseEnv/android-sdk-linux/platform-tools

[android@bogon ~] $adbdevices

List of devices attached

0123456789ABCDEF device

[android@bogon ~] $adbshell

# pwd

/

#. / data/grip/ids

1. Wlan0

(no description available)

2. Any

(Pseudo-device that captures on all interfaces)

3. Lo

(no description available)

Input an interface: (1-3) 1

Dev:wlan0

-ethernet protocol (phydical layer)-

MAC source Address:

78:d6:f0:25:af:a9

MAC destination Address:

00:26:9e:6f:cc:e3

Protocol:0806

This is an ARP protocol

-ARP Protocol-

-ethernet protocol (phydical layer)-

MAC source Address:

00:26:9e:6f:cc:e3

MAC destination Address:

78:d6:f0:25:af:a9

Protocol:0806

This is an ARP protocol

-ARP Protocol-

^ C

# [android@bogon ~] $

[android@bogon ~] $

After reading the above, have you mastered how to build an Android development environment in Linux? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report