MAN_NFC_1105-267 Open NFC - Android Gingerbread 2.3.3 - SDK v0.1
Sofia3gr平台_Android5.1_CTS_产品测试环境搭建V1
福州瑞芯微电子有限公司密级状态：绝密( ) 秘密( ) 内部( √ ) 公开( )Sofia3GR平台A ndroid5.1_CTS产品测试说明（系统产品二部）文件状态：[ ] 正在修改[√] 正式发布当前版本：V1.1作者：hxw完成日期：2015-09-03审核：完成日期：福州瑞芯微电子有限公司Fuzhou Rockchips Semiconductor Co . , Ltd(版本所有,翻版必究)1简述本文档介绍Sofia3GR平台Android 5.1 的GMS测试，包括Android 5.1工程配置，CTS、GTS、Verifier测试fail项补丁，GMS要求相关细节说明，以及测试环境搭建及机器配置，若有存在其他问题，欢迎反馈，我们会尽快进行补充。
2Android 5.1 GMS 工程配置2.1集成DRM、GMS 包1)确保widvine level3 drm包被编译diff --git a/device.mk b/device.mkindex 7df0cb7..5d794b6 100755--- a/device.mk+++ b/device.mk@@ -16,9 +16,26 @@# Oct 20, 2013: Initial Creation for Sofia3G# May 27 2014: IMC: add IMC test tools for engineering build+$(call inherit-product-if-exists, vendor/widevine/widevine.mk)# Screen size is "normal", density is "mdpi"PRODUCT_AAPT_CONFIG := normal large mdpi tvdpi hdpi2)确保GMS 包编译：GMS 包SDK 默认是不带的，请向认证公司索取最新的GMS 包，解压后放在：vendor/google 目录下在/device/rockchip/sofia3gr/BoardConfig.mk 中将以下两项设为true# google appsBUILD_WITH_GOOGLE_MARKET ?= trueBUILD_WITH_GOOGLE_MARKET_ALL ?= true2.2合并分区、hardware features配置1)合并分区，在/device/rockchip/sofia3gr/BoardConfig.mk 中#if set to true m-user would be disabled and UMS enabled, if set to disable UMS would be disabled and m-user enabled-BUILD_WITH_UMS := true+BUILD_WITH_UMS := false2)Sensor编译配置，根据产品sensor list在/device/rockchip/sofia3gr/BoardConfig.mk 如下代码块中做正确配置：# Enabling sensorsBOARD_SENSOR_MPU := false #if use mpuBOARD_USES_GENERIC_INVENSENSE := false #if use mpuBOARD_SENSOR_ST := trueifeq ($(BOARD_SENSOR_ST),true)BOARD_GRAVITY_SENSOR_SUPPORT := trueBOARD_COMPASS_SENSOR_SUPPORT := falseBOARD_GYROSCOPE_SENSOR_SUPPORT := falseBOARD_PROXIMITY_SENSOR_SUPPORT := trueBOARD_LIGHT_SENSOR_SUPPORT := trueBOARD_PRESSURE_SENSOR_SUPPORT := falseBOARD_TEMPERATURE_SENSOR_SUPPORT := falseBOARD_SENSOR_COMPASS_AK8975 := falseBOARD_SENSOR_COMPASS_AK09911 := falseBOARD_SENSOR_COMPASS_AK8963 := falseBOARD_COMPASS_ARCH_ARM=falseBOARD_COMPASS_ARCH_X86_32=trueBOARD_COMPASS_ARCH_X86_64=falseendif另外需要在framework/native/data/etc目录下的xml文件中，根据产品hardware features 进行配置。
安卓手机adb驱动安装失败的解决方法
安卓手机adb驱动安装失败的解决方法看到很多朋友的安卓手机在安装驱动的时候出现ADB Interface黄色感叹号，造成手机管理软件无法使用。
网上也有很多文章说解决方案，不过都不是很详细，我在这边详细介绍下这个问题的原因和解决方案，有几种不同的原因，解决方案也不相同。
由于碰到问题基本都是XP系统，所以这里全部以XP为例子。
1、系统已经存在相同的WDF版本引起。
这个情况是最常见的，电脑已经存在一个相同的WDF版本的时候，而又缺少相关的卸载项就会出现这个问题，表现是提示安装致命错误。
解决方案：a、添加一个相关版本的卸载项，以wdf1005版本为例，导入注册表卸载项。
Wdf01005.rar (1 K) ；然后再安装次即可。
b、或者升级一个1.9版本的驱动也可以解决此问题。
下载驱动：Android.rar (3888 K) 下载次数:176542、系统缺少Cryptographic Services服务造成驱动安装失败在个别XP系统上有碰到因为Cryptographic Services服务缺失造成驱动最后安装失败，这是因为wdf驱动的安装依赖Cryptographic Services。
解决方案：导入服务的注册表键值，然后重启电脑再安装即可。
注册表信息：Cryptographic Services.rar (2 K) 下载次数:41003、与农行网银U-KEY存在冲突已经发现安卓的ADB驱动跟个别网银的U-KEY存在冲突，造成adb interface驱动无法安装，显示错误10。
更新解决方案：如果碰到错误10提示设备有问题的情况，查看下c:\WINDOWS\system32\drivers 目录下有WdfDynam.sys和WdfLdr.sys没。
如果存在这两个文件，就是老版本的WDF 驱动引起了驱动安装失败。
a、先删除WdfDynam的服务，开始-运行-cmd，输入“sc delete WdfDynam”b.、删除c:\WINDOWS\system32\drivers目录下WdfDynam.sys和WdfLdr.sysc、重新安装驱动即可。
adb-Android Debug Bridge version 1.0.26
Android Debug Bridge version 1.0.26-d - directs command to the only connected USB devicereturns an error if more than one USB device is present. -e - directs command to the only running emulator.returns an error if more than one emulator is running.-s <serial number> - directs command to the USB device or emulator withthe given serial number. Overrides ANDROID_SERIALenvironment variable.-p <product name or path> - simple product name like 'sooner', ora relative/absolute path to a productout directory like 'out/target/product/sooner'.If -p is not specified, the ANDROID_PRODUCT_OUTenvironment variable is used, which mustbe an absolute path.devices - list all connected devicesconnect <host>[:<port>] - connect to a device via TCP/IPPort 5555 is used by default if no port number is specified. disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.Port 5555 is used by default if no port number is specified.Using this ocmmand with no additional argumentswill disconnect from all connected TCP/IP devices.device commands:adb push <local> <remote> - copy file/dir to deviceadb pull <remote> [<local>] - copy file/dir from deviceadb sync [ <directory> ] - copy host->device only if changed(-l means list but don't copy)(see 'adb help all')adb shell - run remote shell interactivelyadb shell <command> - run remote shell commandadb emu <command> - run emulator console commandadb logcat [ <filter-spec> ] - View device logadb forward <local> <remote> - forward socket connectionsforward specs are one of:tcp:<port>localabstract:<unix domain socket name>localreserved:<unix domain socket name>localfilesystem:<unix domain socket name>dev:<character device name>jdwp:<process pid> (remote only)adb jdwp - list PIDs of processes hosting a JDWP transportadb install [-l] [-r] [-s] <file> - push this package file to the device and install it('-l' means forward-lock the app)('-r' means reinstall the app, keeping its data)('-s' means install on SD card instead of internal storage)adb uninstall [-k] <package> - remove this app package from the device('-k' means keep the data and cache directories)adb bugreport - return all information from the devicethat should be included in a bug report.adb help - show this help messageadb version - show version numDATAOPTS:(no option) - don't touch the data partition-w - wipe the data partition-d - flash the data partitionscripting:adb wait-for-device - block until device is onlineadb start-server - ensure that there is a server runningadb kill-server - kill the server if it is runningadb get-state - prints: offline | bootloader | deviceadb get-serialno - prints: <serial-number>adb status-window - continuously print device status for a specified deviceadb remount - remounts the /system partition on the device read-writeadb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program adb reboot-bootloader - reboots the device into the bootloaderadb root - restarts the adbd daemon with root permissionsadb usb - restarts the adbd daemon listening on USBadb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port networking:adb ppp <tty> [parameters] - Run PPP over USB.Note: you should not automatically start a PPP connection.<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1[parameters] - Eg. defaultroute debug dump local notty usepeerdnsadb sync notes: adb sync [ <directory> ]<localdir> can be interpreted in several ways:- If <directory> is not specified, both /system and /data partitions will be updated.- If it is "system" or "data", only the corresponding partitionis updated.environmental variables:ADB_TRACE - Print debug information. A comma separated listof the following values1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given. ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.。
mini2440 开发板之 andriod 说明书
mini2440开发板之andriod使用手册潘应云（南京师范大学，panyingyun@，QQ:29548754，848682821）提供第一部分：内核映像及文件系统介绍 (1)第二部分：使用说明 (1)开发平台：RedHat 9.0 ＋ mini2440开发板使用内核版本类型：linux-2.6.25-android-1.0_r1.tar.gz下载地址：/p/android/downloads/list交叉编译器：arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2下载地址：/sgpp/lite/arm/portal/release642或者直接复制下面地址/sgpp/lite/arm/portal/package3686/public/arm-none-eabi/arm-2 008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2第一部分：内核映像及文件系统介绍1、zImage：andriod内核映像文件。
支持触摸屏（目前没有校屏程序，点击不太准），支持nfs文件系统启动，支持RTC(可以正确显示google时钟)，支持DM9000网卡，支持yaffs文件系统，电源管理等。
2、nfs_root_andriod.tar.gz：nfs方式启动文件系统，可以看到很绚丽的google大钟和google浏览器。
3、final_config.rar：内核配置文件（可以自己用命令mv final config .config 放到内核下进行编译）。
（为何不提供yaffs文件系统而采用NFS启动方式：主要原因是mini2440开发板提供的nand flash太小，只有64M空间，这里需要至少80M的空间）第二部分：使用说明（注意：开发环境和redhat9.0系统的安装大家可以参考mini2440开发板手册。
安卓SDK Windows版 资源包下载地址全集
A.用迅雷下载以下链接；B.把下载的压缩包放到你安装sdk的temp这个文件夹里，再启动SDKManager安装它们；C.不要修改Hosts文件，否则安装会不完全或者无法安装；D.本文适用于Windows系统，如果你是其他平台，请参考本文和此博客：/gyming/article/details/8168166；本文更新于2014年7月4日1.Toolshttps:///android/repository/tools_r23.0.2-windows.ziphttps:///android/repository/platform-tools_r20-windows.ziphttps:///android/repository/build-tools_r17-windows.ziphttps:///android/repository/build-tools_r18.0.1-windows.ziphttps:///android/repository/build-tools_r18.1-windows.ziphttps:///android/repository/build-tools_r18.1.1-windows.ziphttps:///android/repository/build-tools_r19-windows.ziphttps:///android/repository/build-tools_r19.0.1-windows.ziphttps:///android/repository/build-tools_r19.0.2-windows.ziphttps:///android/repository/build-tools_r19.0.3-windows.ziphttps:///android/repository/build-tools_r19.1-windows.ziphttps:///android/repository/build-tools_r20-windows.zip2.Android L（API 20, L Preview）https:///android/repository/docs-L_r01.ziphttps:///android/repository/android-L_r01.ziphttps:///android/repository/samples-L_r01.ziphttps:///android/repository/sys-img/android/sysimg_armv7a-L_r01.ziphttps:///android/repository/sys-img/android-tv/sysimg_tv_x86-L_r01.ziphttps:///android/repository/sys-img/android/sysimg_armv7a-L_r01.ziphttps:///android/repository/sys-img/android/sysimg_x86-L_r01.zip3.Android4.4W（API 20）https:///android/repository/android-20_r01.ziphttps:///android/repository/samples-20_r01.ziphttps:///android/repository/sys-img/android-wear/sysimg_wear_arm-20_r01.ziphttps:///android/repository/sys-img/android-wear/sysimg_wear_x86-20_r01.ziphttps:///android/repository/sources-20_r01.zip4.Android 4.4.2 (API 19)https:///android/repository/docs-19_r02.ziphttps:///android/repository/android-19_r03.ziphttps:///android/repository/samples-19_r05.ziphttps:///android/repository/sys-img/android-wear/android-wear-sysimg-1077298.zip/android/repository/sysimg_armv7a-19_r02.zip/android/repository/sys-img/x86/sysimg_x86-19_r02.zip https:///android/repository/sys-img/x86/google_apis_x86-19_r06.zip https:///android/repository/google_apis-19_r06.ziphttps:///glass/xe18.3/google-gdk.ziphttps:///android/repository/sources-19_r02.zip5.Android 4.3 (API 18)https:///android/repository/android-18_r02.ziphttps:///android/repository/samples-18_r01.zip/android/repository/sysimg_armv7a-18_r02.zip/android/repository/sys-img/x86/sysimg_x86-18_r01.zip https:///android/repository/google_apis-18_r03.ziphttps:///android/repository/sources-18_r01.zip6.Android 4.2.2 (API 17)https:///android/repository/android-17_r02.ziphttps:///android/repository/samples-17_r01.zip/android/repository/sysimg_armv7a-17_r02.zip/android/repository/sys-img/x86/sysimg_x86-17_r01.zip /android/repository/sys-img/mips/sysimg_mips-17_r01.zip /android/repository/sys-img/mips/sysimg_mips-17_r03.zip https:///android/repository/google_apis-17_r03.ziphttps:///android/repository/sources-17_r01.zip7.Android 4.1.2 (API 16)https:///android/repository/android-16_r04.ziphttps:///android/repository/samples-16_r01.ziphttps:///android/repository/sysimg_armv7a-16_r03.ziphttps:///android/repository/sys-img/x86/sysimg_x86-16_r01.zip /android/repository/sys-img/mips/sysimg_mips-16_r04.zip https:///android/repository/google_apis-16_r03.ziphttps:///android/repository/sources-16_r02.zip8.Android 4.0.3 (API 15)https:///android/repository/android-15_r03.ziphttps:///android/repository/samples-15_r02.ziphttps:///android/repository/sysimg_armv7a-15_r02.ziphttps:///android/repository/sys-img/x86/sysimg_x86-15_r01.zip /android/repository/sys-img/mips/sysimg_mips-15_r01.zip https:///android/repository/google_apis-15_r02.ziphttps:///android/repository/sources-15_r02.zip9.Android 4.0 (API 14)https:///android/repository/android-14_r03.ziphttps:///android/repository/samples-14_r02.ziphttps:///android/repository/sysimg_armv7a-14_r02.zip https:///android/repository/google_apis-14_r02.ziphttps:///android/repository/sources-14_r01.zip10.Android 3.2 (API 13)https:///android/repository/android-3.2_r01-linux.zip https:///android/repository/samples-3.2_r01-linux.zip https:///android/repository/google_apis-13_r01.ziphttps:///android/repository/google_tv-13_r01.zip11. Android 3.1 (API 12)https:///android/repository/android-3.1_r03-linux.zip https:///android/repository/samples-3.1_r01-linux.zip https:///android/repository/google_apis-12_r01.ziphttps:///android/repository/google_tv-12_r02.zip12. Android 3.0 (API 11)https:///android/repository/android-3.0_r02-linux.zip https:///android/repository/samples-3.0_r01-linux.zip https:///android/repository/google_apis-11_r01.zip13. Android 2.3.3 (API 10)https:///android/repository/android-2.3.3_r02-linux.zip https:///android/repository/samples-2.3.3_r01-linux.zip /android/repository/sys-img/x86/sysimg_x86-10_r02.zip https:///android/repository/google_apis-10_r02.zip14. Android 2.2 (API 8)https:///android/repository/android-2.2_r03-linux.zip https:///android/repository/samples-2.2_r01-linux.zip https:///android/repository/google_apis-8_r02.zip15.Android 2.1 (API 7)https:///android/repository/android-2.1_r03-linux.zip https:///android/repository/samples-2.1_r01-linux.zip https:///android/repository/google_apis-7_r01.zip16. Android 1.6 (API 4)https:///android/repository/android-1.6_r03-windows.zip https:///android/repository/google_apis-4_r02.zip17. Android 1.5 (API 3)https:///android/repository/android-1.5_r04-windows.ziphttps:///android/repository/google_apis-3-r03.zip18.Extrashttps:///android/repository/android_m2repository_r06.ziphttps:///android/repository/support_r20.ziphttps:///gaformobileapps/GoogleAnalyticsAndroid_2.0beta5.ziphttps:///android/repository/google_play_services_3265130_r12.ziphttps:///android/repository/google_play_services_5077000_r18.ziphttps:///android/repository/google_m2repository_r09.ziphttps:///android/repository/market_apk_expansion-r03.ziphttps:///android/repository/play_billing_r05.ziphttps:///android/repository/market_licensing-r02.ziphttps:///android/repository/usb_driver_r10-windows.ziphttps:///android/repository/webdriver_r02.ziphttps:///android/repository/extras/intel/haxm-windows_r04.ziphttps:///googleadmobadssdk/googleadmobadssdkandroid-6.4.1.ziphttps:///android/repository/gcm_r03.zip中央民族大学在校生整理。
openOCD安装及配置
openOCD安装及配置RISC-V openOCD安装及配置本⽂介绍openocd开源软件的安装和配置⼯作OS: Ubunto20.04openOCD version: openocd v0.10.01、什么是open OCD ?open OCD (Open On-Chip Debugger) 是⼀个运⽤于PC上的开源调试软件，它可以控制⼤多数JTAG硬件设备。
openOCD的功能需要在调试⼯具（例如GDB）的协同下完成。
openOCD主要是对⾼级指令进⾏解析，转换。
对于RISC它可以进⾏指令转换配合debug调试。
2、open OCD 的下载openocd可以通过进⾏下载，但官⽹下载版本较⽼暂不⽀持RISC-V的调试，要获取⽀持RISC-V版本可通过进⾏获取3、安装准备⼯作提前安装好以下合适版本的软件- make- libtool- pkg-config >= 0.23 (or compatible)- autoconf >= 2.64- automake >= 1.14- texinfo可通过运⾏脚本install进⾏安装（⾃⼰编写）#!/bin/shsudo apt-get install make -ysudo apt-get install libtool -ysudo apt-get install pkg-config -ysudo apt-get install autoconf -ysudo apt-get install automake -y4、编译与安装4.1、解压tar -xzvf riscv-openocd.tar.gz4.2、进⼊riscv-openocd⽂件执⾏bootstrap⽣成configure⽂件./bootstrap4.3 通过configure配置openOCD通过 --prefix=/../../../来指明安装路径，此路径为绝对路径通过 --enable-ftdi 等来配置调试器，此处可根据需要⾃⾏添加（通过./configure --help获取帮助）./configure --prefix=/home/dong/tools/openocd --enable-jlink --enable-remote-bitbang看到⽣成Makefile⽂件或者下列代码说明配置成功OpenOCD configuration summary--------------------------------------------------MPSSE mode of FTDI based devices nocJTAG OSCAN1 tunneled thru MPSSE noST-Link Programmer noTI ICDI JTAG Programmer noKeil ULINK JTAG Programmer noAltera USB-Blaster II Compatible noBitbang mode of FT232R based devices noVersaloon-Link JTAG Programmer noTI XDS110 Debug Probe noOSBDM (JTAG only) Programmer noeStick/opendous JTAG Programmer noAndes JTAG Programmer noUSBProg JTAG Programmer noRaisonance RLink JTAG Programmer noOlimex ARM-JTAG-EW Programmer noCMSIS-DAP Compliant Debugger noNu-Link Programmer noCypress KitProg Programmer noAltera USB-Blaster Compatible noASIX Presto Adapter noOpenJTAG Adapter noLinux GPIO bitbang through libgpiod noSEGGER J-Link Programmer yes如需添加FTDI相关配置需安装 libusb-1.xsudo apt-get install libusb-1.0安装成功后运⾏configure进⾏配置⼯作./configure --prefix=/home/dong/tools/openocd --enable-ftdi配置成功后相应端⼝会开启Enabled transports:- USB ............................ yes- TCP ............................ yesOpenOCD configuration summary--------------------------------------------------MPSSE mode of FTDI based devices yescJTAG OSCAN1 tunneled thru MPSSE yes (auto)ST-Link Programmer yes (auto)TI ICDI JTAG Programmer yes (auto)Keil ULINK JTAG Programmer yes (auto)Altera USB-Blaster II Compatible yes (auto)Bitbang mode of FT232R based devices yes (auto)Versaloon-Link JTAG Programmer yes (auto)TI XDS110 Debug Probe yes (auto)OSBDM (JTAG only) Programmer yes (auto)eStick/opendous JTAG Programmer yes (auto)Andes JTAG Programmer yes (auto)USBProg JTAG Programmer noRaisonance RLink JTAG Programmer noOlimex ARM-JTAG-EW Programmer noCMSIS-DAP Compliant Debugger noNu-Link Programmer noCypress KitProg Programmer noAltera USB-Blaster Compatible noASIX Presto Adapter noOpenJTAG Adapter noLinux GPIO bitbang through libgpiod noSEGGER J-Link Programmer yes配置成功后进⾏编译安装make -j4(可根据电脑配置进⾏多线程选择)make install安装完成后通过指令查看open OCD是否安装成功➜ ~ openocd --versionOpen On-Chip Debugger 0.10.0+dev-01406-gdd17f7cca (2021-02-07-23:43) Licensed under GNU GPL v2For bug reports, read/doc/doxygen/bugs.html⾄此openocd安装⼯作结束。
Android_CTS_test(安装和命令)
一、Android CTS测试简介CTS 全称 Compatibility Test Suite 兼容性测试工具。
当电子产品开发出来，并定制了自己的 Android 系统后，必须要通过最新的 CTS 检测，以保证标准的 android application 能运行在该平台下。
通过了 CTS 验证，需要将测试报告提交给 Google，已取得 android market的认证。
CTS 是一款通过命令行操作的工具。
目前 cts 没有提供 windows 版本，只能在 Linux 下测试。
本文将详细介绍在ubantu系统上如何搭建CTS环境，以及运行测试计划和分析测试结果。
二、Android CTS测试环境搭建1.下载android-SDK linux版本，下载地址：/sdk/index.html步骤：1.安装android-sdk2.2 解压下载所得的android-sdk到安装的目录（任意），如：/home/tester/cts/ android-sdk-linux_86。
进入/home/tester/cts/ android-sdk-linux_86/tools，运行android可执行文件：双击，点击“在终端运行”，出现在左菜单中选择“Installed package”选项，点击下方“update All…”按钮，进入更新界面：选择左边的的package，选择“Reject”，不会更新该package，点击Install。
进入更新状态。
2.将platfrorm-tools目录下的adb文件拷贝到tools目录下（安装CTS时会用到）安装完成。
在Linux Command窗口输入以下命令：env可查看到当前PATH的值为：PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/ga mes:/home/username/bin:再输入以下命令，将Android SDK路径加入到环境变量中：exportPATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin :/usr/games:/home/username/bin:/home/username/android-sdk-linux_86/platform-tools:/h ome/username/android-sdk-linux_86/toolsNote：1> 各环境变量之间用冒号隔开2> 如果PATH中已添加了Android SDK路径，默认即可2.下载android-cts包,下载地址：/compatibility/downloads.html根据手机系统版本下载对应版本的cts包，否则将无法运行测试a．配置CTS：进入/home/username/CTS/android-cts/tools目录，打开/home/username/CTS/android-cts/tools/startcts脚本进行编辑，找到脚本中第一次出现SDK_ROOT的地方(注释了的片段不算)，将Android SDK的根目录路径赋值给“SDK_ROOT”，如下:# Add SDK_ROOT to the PATH for backwards compatibility with prior startcts# commands that required SDK_ROOT to find adb.if [ -n "${SDK_ROOT=/home/username/android-sdk-linux_86}" ]; thenPATH=${SDK_ROOT}/platform-tools:${SDK_ROOT}/tools:${PATH}fi然后保存编辑。
自己动手编译Android（LineageOS）源码
⾃⼰动⼿编译Android（LineageOS）源码⼀、编译LineageOS源码准备设备：⼩⽶ MIX2设备代号：chironAndroid版本：9.0PC配置：系统：Ubuntu18.04⾄少12G RAM⾄少200GB 剩余硬盘空间良好的⽹络环境1.下载并解压SDKsdk中包含fastboot和adb下载wget https:///android/repository/platform-tools-latest-linux.zip解压unzip platform-tools-latest-linux.zip -d ~添加到环境变量gedit ~/.profile输⼊：# add Android SDK platform tools to pathif [ -d "$HOME/platform-tools" ] ; thenPATH="$HOME/platform-tools:$PATH"fi保存。
使改动⽣效:source ~/.profile2.安装依赖安装必要库和⼯具sudo apt-get install bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev安装openjdk-8-jdksudo apt install -y openjdk-8-jdk3.配置源创建repo存放⽬录mkdir -p ~/bin创建源码存放⽬录mkdir -p ~/android/lineage× 注：请确保该⽬录所在的磁盘有⾜够的空间（⾄少200G）安装repocurl https:///git-repo-downloads/repo > ~/bin/repochmod a+x ~/bin/repo将~/bin放⼊环境变量gedit ~/.profile加⼊：# set PATH so it includes user's private bin if it existsif [ -d "$HOME/bin" ] ; thenPATH="$HOME/bin:$PATH"fi使改动⽣效:source ~/.profile初始化repocd ~/android/lineagerepo init -u https:///LineageOS/android.git -b lineage-16.0× 注：这⾥的lineage-16.0是分⽀名,对应Android 9.0。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Check document version before use. Copyright © 2011 Inside Secure Open NFC - Android Gingerbread 2.3.3 - SDK
Document Type: Manual Reference: MAN_NFC_1105-267 Version 0.1 (10371) Release Date: May 25, 2011 File Name: MAN_NFC_1105-267 Open NFC - Android Gingerbread 2.3.3 - SDK v0.1.pdf
Security Level: Public
Open NFC - Android Gingerbread 2.3.3 - SDK Public
Page : 2/21 Date : May 25, 2011 Ref. : MAN_NFC_1105-267 v0.1(10371)
Check document version before use. Copyright © 2011 Inside Secure Disclaimer
Copyright © 2011 Inside Secure
Licensed under the Apache License, Version 2.0 (the "License");you may not use this file except in compliance with the License.You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.
Content of the NOTICE file:
Open NFC and the Open NFC logo are trademarks or registered trademarks of Inside Secure.
Other brand, product and company names mentioned herein may be trademarks, registered trademarks or trade names of their respective owners.
Open NFC - Android Gingerbread 2.3.3 - SDK Public
Page : 3/21 Date : May 25, 2011 Ref. : MAN_NFC_1105-267 v0.1(10371)
Check document version before use. Copyright © 2011 Inside Secure History
Version Date Comments 0.1 May 25, 2011 First Release Open NFC - Android Gingerbread 2.3.3 - SDK Public
Page : 4/21 Date : May 25, 2011 Ref. : MAN_NFC_1105-267 v0.1(10371)
Check document version before use. Copyright © 2011 Inside Secure Summary of Contents 1 Introduction ........................................................................................................ 5 2 Delivery Description .......................................................................................... 6 2.1 Delivery contents ................................................................................................. 6 2.2 SDK add-on ......................................................................................................... 6 2.3 Documentation of the Open NFC for Android API ............................................... 6 2.4 Application examples ........................................................................................... 6
3 Installation .......................................................................................................... 8 3.1 Installation............................................................................................................ 8 3.2 Checking the installation ...................................................................................... 8 3.3 Creation of the AVD ............................................................................................. 9 3.4 Launching of the AVD and starting of the Open NFC stack ............................... 11
4 Development of applications .......................................................................... 18 4.1 Generalities........................................................................................................ 18 4.2 Examples ........................................................................................................... 19 4.2.1 Reading Mode ................................................................................................ 20 Open NFC - Android Gingerbread 2.3.3 - SDK Public
Page : 5/21 Date : May 25, 2011 Ref. : MAN_NFC_1105-267 v0.1(10371)
Check document version before use. Copyright © 2011 Inside Secure 1 Introduction This document is the developer’s manual for the NFC software stack “Open NFC v4.3 (Build 10378)”.
This document describes the installation of the Open NFC for Android SDK add-on and gives some hints about the development of Open NFC applications.
The revision of this delivery is Open NFC v4.3 (Build 10378) This product was tested and SHALL be used under the following environment: NFC Controller Hardware: Firmware Loader: Firmware: Error! Unknown document property name. Android AOSP Gingerbread branch (Android 2.3.x series)