Use the information in this page to create the makefiles for your device and product.
Each new Android module must have a configuration file to direct the build system with module metadata, compile-time dependencies, and packaging instructions. Android uses the Soong build system. See Building Android for more information about the Android build system.
Understanding build layers
The build hierarchy includes the abstraction layers that correspond to the physical makeup of a device. These layers are described in the table below. Each layer relates to the one above it in a one-to-many relationship. For example, an architecture can have more than one board and each board can have more than one product. You may define an element in a given layer as a specialization of an element in the same layer, which eliminates copying and simplifies maintenance.
|myProduct, myProduct_eu, myProduct_eu_fr, j2, sdk
|The product layer defines the feature specification of a shipping product such as the modules to build, locales supported, and configuration for various locales. In other words, this is the name of the overall product. Product-specific variables are defined in product definition makefiles. A product can inherit from other product definitions, which simplifies maintenance. A common method is to create a base product that contains features that apply to all products, then create product variants based on that base product. For example, two products that differ only by their radios (CDMA versus GSM) can inherit from the same base product that doesn't define a radio.
|marlin, blueline, coral
|The board/device layer represents the physical layer of plastic on the device (that is, the industrial design of the device). This layer also represents the bare schematics of a product. These include the peripherals on the board and their configuration. The names used are merely codes for different board/device configurations.
|arm, x86, arm64, x86_64
|The architecture layer describes the processor configuration and application binary interface (ABI) running on the board.
Using build variants
When building for a particular product, it's useful to have minor
variations on the final release build. In a module
definition, the module can specify tags with
which can be one or more values of
If a module doesn't specify a tag (by
tag defaults to
optional. An optional module is installed only if
it's required by the product configuration with
These are the currently defined build variants.
This is the default flavor.
The variant intended to be the final release bits.
The same as
user, with these exceptions:
Guidelines for userdebug
Running userdebug builds in testing helps device developers understand the performance and power of in-development releases. To maintain consistency between user and userdebug builds, and to achieve reliable metrics in builds used for debugging, device developers should follow these guidelines:
- userdebug is defined as a user build with root access enabled, except:
- userdebug-only apps that are run only on-demand by the user
- Operations that run only during idle maintenance (on charger/fully
charged), such as using
dex2oatfor background compiles
- Don't include features that are enabled/disabled by default based on the build type. Developers are discouraged from using any form of logging that affects battery life, such as debug logging or heap dumping.
- Any debugging features that are enabled by default in userdebug should be clearly defined and shared with all developers working on the project. You should enable debugging features only on a limited-time basis until the issue you're trying to debug is resolved.
Customizing the build with resource overlays
The Android build system uses resource overlays to customize
a product at build time. Resource overlays specify resource
files that are applied on top of the defaults. To use resource overlays, modify the project
buildfile to set
PRODUCT_PACKAGE_OVERLAYS to a
path relative to your top-level directory. That path becomes a shadow root searched along with
the current root when the build system searches for resources.
The most commonly customized settings are contained in the file frameworks/base/core/res/res/values/config.xml.
To set up a resource overlay on this file, add the overlay directory to the project buildfile using one of the following:
PRODUCT_PACKAGE_OVERLAYS := device/device-implementer/device-name/overlay
PRODUCT_PACKAGE_OVERLAYS := vendor/vendor-name/overlay
Then, add an overlay file to the directory, for example:
Any strings or string arrays found in the overlay
config.xml file replace
those found in the original file.
Building a product
You can organize the source files for your device in many different ways. Here's a brief description of one way to organize a Pixel implementation.
Pixel is implemented with a main device configuration named
marlin. From this device configuration, a product is created with a
product definition makefile that declares product-specific information about
the device such as the name and model. You can view the
device/google/marlin directory to see how all of this is set up.
Writing product makefiles
The following steps describe how to set up product makefiles in a way similar to that of the Pixel product line:
- Create a
device/<company-name>/<device-name>directory for your product. For example,
device/google/marlin. This directory will contain source code for your device along with the makefiles to build them.
- Create a
device.mkmakefile that declares the files and modules needed for the device. For an example, see
- Create a product definition makefile to create a specific product based on the device. The
following makefile is taken from
device/google/marlin/aosp_marlin.mkas an example. Notice that the product inherits from the
vendor/google/marlin/device-vendor-marlin.mkfiles through the makefile while also declaring the product-specific information such as name, brand, and model.
# Inherit from the common Open Source product configuration $(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk) $(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base_telephony.mk) PRODUCT_NAME := aosp_marlin PRODUCT_DEVICE := marlin PRODUCT_BRAND := Android PRODUCT_MODEL := AOSP on msm8996 PRODUCT_MANUFACTURER := Google PRODUCT_RESTRICT_VENDOR_FILES := true PRODUCT_COPY_FILES += device/google/marlin/fstab.common:$(TARGET_COPY_OUT_VENDOR)/etc/fstab.marlin $(call inherit-product, device/google/marlin/device-marlin.mk) $(call inherit-product-if-exists, vendor/google_devices/marlin/device-vendor-marlin.mk) PRODUCT_PACKAGES += \ Launcher3QuickStep \ WallpaperPicker
See Setting product definition variables for additional product-specific variables that you can add to your makefiles.
- Create an
AndroidProducts.mkfile that points to the product's makefiles. In this example, only the product definition makefile is needed. The example below is from
device/google/marlin/AndroidProducts.mk(which contains both marlin, the Pixel, and sailfish, the Pixel XL, which shared most configuration):
PRODUCT_MAKEFILES := \ $(LOCAL_DIR)/aosp_marlin.mk \ $(LOCAL_DIR)/aosp_sailfish.mk COMMON_LUNCH_CHOICES := \ aosp_marlin-userdebug \ aosp_sailfish-userdebug
- Create a
BoardConfig.mkmakefile that contains board-specific configurations. For an example, see
- For Android 9 and lower only, create a
vendorsetup.shfile to add your product (a "lunch combo") to the build along with a build variant separated by a dash. For example:
- At this point, you can create more product variants based on the same device.
Setting product definition variables
Product-specific variables are defined in the product's makefile. The table shows some of the variables maintained in a product definition file.
aapt configurations to use when creating packages.
|The brand (for example, carrier) the software is customized for.
aapt characteristics to allow adding variant-specific resources to a package.
List of words like
source_path:destination_path. The file at the source path
should be copied to the destination path when building this product. The rules for the copy
steps are defined in
Name of the industrial design. This is also the board name, and the build system uses it
A space-separated list of two-letter language code, two-letter country code pairs that
describe several settings for the user, such as the UI language and time, date, and
currency formatting. The first locale listed in
PRODUCT_LOCALES is used as
the product's default locale.
|Name of the manufacturer.
|End-user-visible name for the end product.
|End-user-visible name for the overall product. Appears in the Settings > About screen.
|List of over-the-air (OTA) public keys for the product.
|List of the APKs and modules to install.
|Indicates whether to use default resources or add any product specific overlays.
List of the system property assignments in the format
"key=value" for the
system partition. System properties for other partitions can be set via
PRODUCT_<PARTITION>_PROPERTIES as in
PRODUCT_VENDOR_PROPERTIES for the vendor partition. Supported partition
Configuring the default system language and locale filter
Use this information to configure the default language and system locale filter, then enable the locale filter for a new device type.
Configure both the default language and the system locale filter using dedicated system properties:
ro.product.locale: for setting the default locale. This is initially set to the first locale in the
PRODUCT_LOCALESvariable; you can override that value. (For more information, see the Setting product definition variables table.)
ro.localization.locale_filter: for setting a locale filter, using a regular expression applied to locale names. For example:
- Inclusive filter:
^(de-AT|de-DE|en|uk).*- allows only German (Austria and Germany variants), all English variants of English, and Ukrainian
- Exclusive filter:
^(?!de-IT|es).*- excludes German (Italy variant), and all variants of Spanish.
- Inclusive filter:
Enabling the locale filter
To enable the filter, set the
ro.localization.locale_filter system property string value.
By setting the filter property value and the default language through
factory calibration you can configure restrictions without baking the filter into the system image.
You ensure that these properties are picked up from the OEM partition by adding them to the
PRODUCT_OEM_PROPERTIES variable as indicated below:
# Delegation for OEM customization PRODUCT_OEM_PROPERTIES += \ ro.product.locale \ ro.localization.locale_filter
Then in production the actual values are written to
oem/oem.prop, to reflect the target
requirements. With this approach, the default values are retained during the factory reset, so the
initial settings look exactly like a first setup to the user.
Setting ADB_VENDOR_KEYS to connect over USB
ADB_VENDOR_KEYS environment variable enables device manufacturers to access
debuggable builds (-userdebug and -eng, but not -user) over adb without manual authorization.
Normally adb generates a unique RSA authentication key for each client computer, which it will send
to any connected device. This is the RSA key shown in the adb authorization dialog. As an
alternative you can build known keys into the system image and share them with the adb client.
This is useful for OS development and especially for testing because it avoids the need to manually
interact with the adb authorization dialog.
To create vendor keys, one person (usually a release manager) should:
- Generate a key pair using
adb keygen. For Google devices, Google generates a new key pair for each new OS version.
- Check the key pairs in, somewhere in the source tree. Google stores them in
vendor/google/security/adb/, for example.
- Set the build variable
PRODUCT_ADB_KEYSto point to your key directory. Google does this by adding an
Android.mkfile in the key directory that says
PRODUCT_ADB_KEYS := $(LOCAL_PATH)/$(PLATFORM_VERSION).adb_key.pub, which helps ensure that we remember to generate a new key pair for each OS version.
Here's the makefile Google uses in the directory where we store our checked-in key pairs for each release:
PRODUCT_ADB_KEYS := $(LOCAL_PATH)/$(PLATFORM_VERSION).adb_key.pub ifeq ($(wildcard $(PRODUCT_ADB_KEYS)),) $(warning ========================) $(warning The adb key for this release) $(warning ) $(warning $(PRODUCT_ADB_KEYS)) $(warning ) $(warning does not exist. Most likely PLATFORM_VERSION in build/core/version_defaults.mk) $(warning has changed and a new adb key needs to be generated.) $(warning ) $(warning Please run the following commands to create a new key:) $(warning ) $(warning make -j8 adb) $(warning LOGNAME=android-eng HOSTNAME=google.com adb keygen $(patsubst %.pub,%,$(PRODUCT_ADB_KEYS))) $(warning ) $(warning and upload/review/submit the changes) $(warning ========================) $(error done) endif
To use these vendor keys, an engineer only needs to set the
environment variable to point to the directory in which the key pairs are stored.
adb to try these canonical keys first, before falling back to the generated
host key that requires manual authorization. When
adb can't connect to an unauthorized
device, the error message will suggest that you set
ADB_VENDOR_KEYS if it's not
Tumia habari katika ukurasa huu kuunda makefiles kwa kifaa chako na bidhaa. Kila moduli mpya ya Android lazima iwe na faili ya usanidi kuelekeza mfumo wa kujenga na metadata ya moduli, utegemezi wa wakati wa kukusanya, na maagizo ya ufungaji. Android hutumia mfumo wa kujenga wa Soong. Angalia kujenga Android kwa habari zaidi kuhusu mfumo wa kujenga Android. Kuelewa kujenga tabaka kujenga hierarchy ni pamoja na tabaka abstraction kwamba inalingana na fizikia makeup ya kifaa. Tabaka hizi zimeelezwa katika jedwali hapa chini. Kila safu inahusiana na moja juu yake katika uhusiano wa moja-kwa-wengi. Kwa mfano, usanifu inaweza kuwa na bodi zaidi ya moja na kila bodi inaweza kuwa na bidhaa zaidi ya moja. Unaweza kufafanua kipengele katika safu fulani kama utaalam wa kipengele katika safu hiyo hiyo, ambayo huondoa kunakili na kurahisisha matengenezo. "Mfano: ""MyProduct"" (J2S) ni sehemu ya ""Product"" (J2S) ambayo inaonyesha vipengele vya bidhaa, kama vile modules za kujenga, maeneo yanayoungwa mkono, na usanidi kwa maeneo mbalimbali." Kwa maneno mengine, hii ni jina la bidhaa ya jumla. Bidhaa maalum vigezo ni maalum katika bidhaa ufafanuzi makefiles. Bidhaa inaweza kurithi kutoka ufafanuzi mwingine wa bidhaa, ambayo kurahisisha matengenezo. Njia ya kawaida ni kuunda bidhaa ya msingi ambayo ina sifa ambazo zinatumika kwa bidhaa zote, kisha kuunda aina za bidhaa kulingana na bidhaa hiyo ya msingi. Kwa mfano, bidhaa mbili ambazo hutofautiana tu na redio zao (CDMA dhidi ya GSM) zinaweza kurithi kutoka kwa bidhaa moja ya msingi ambayo haijabaini redio. "Mapendekezo ya ""Marlin"" na ""Blueline"" ni ""mfano wa vifaa vya plastiki"" na ""kiwango cha vifaa vya plastiki"" ni ""kiwango cha vifaa vya plastiki.""" Safu hii pia inawakilisha schematics wazi ya bidhaa. Hizi ni pamoja na vifaa vya nje juu ya bodi na Configuration yao. Majina kutumika ni tu codes kwa ajili ya bodi tofauti / kifaa Configurations. "Archive: ""Archive"" ni ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive"" ya ""Archive""" Kutumia kujenga variants Wakati wa kujenga kwa ajili ya bidhaa fulani, ni muhimu kuwa na tofauti ndogo juu ya mwisho kutolewa kujenga. Katika ufafanuzi moduli, moduli inaweza kutaja tags ambayo inaweza kuwa moja au zaidi ya maadili ya Kama moduli haina kutaja tag (kwa tag defaults kwa hiari. Moduli ya hiari ni imewekwa tu kama ni required na Configuration bidhaa na Hizi ni sasa kufafanuliwa kujenga variants. Hii ni ladha default. Tofauti iliyokusudiwa kuwa bits ya mwisho ya kutolewa. "Kama vile mtumiaji, na tofauti hizi: Miongozo kwa ajili ya userdebug: Kuendesha userdebug inajenga katika kupima husaidia watengenezaji kifaa kuelewa utendaji na nguvu ya in-kuendeleza releases. """ Ili kudumisha uthabiti kati ya mtumiaji na userbug, na kufikia vipimo vya kuaminika katika ujenzi unaotumiwa kwa debugging, watengenezaji wa kifaa wanapaswa kufuata miongozo hii: - userbug hufafanuliwa kama ujenzi wa mtumiaji na upatikanaji wa mizizi, isipokuwa: - programu za userbug tu ambazo zinaendeshwa tu kwa mahitaji ya mtumiaji - Uendeshaji unaofanyika wakati wa matengenezo ya idle (kwa chaja au kulipwa kabisa), kama vile kutumia dex2oat kwa mkusanyiko wa nyuma. Watengenezaji ni kukatishwa moyo kutoka kwa kutumia aina yoyote ya kurekodi kwamba huathiri maisha ya betri, kama vile debug kurekodi au rundo dumping. - yoyote debugging vipengele ambayo ni kuwezeshwa kwa default katika userdebug lazima wazi kufafanuliwa na kushiriki na watengenezaji wote kufanya kazi kwenye mradi. Unapaswa kuwezesha vipengele vya debugging tu kwa msingi wa muda mdogo mpaka suala unajaribu debugging ni kutatuliwa. Customizing kujenga na rasilimali overlays mfumo wa kujenga Android hutumia rasilimali overlays kubadili bidhaa wakati wa kujenga. Rasilimali overlays kutaja rasilimali faili ambayo ni kutumika juu ya defaults. Kwa kutumia overlays rasilimali, kurekebisha mradi kujenga faili kuweka PRODUCT_PACKAGE_OVERLAYS kwa njia jamaa na directory yako ya ngazi ya juu. Njia hiyo inakuwa shadow mizizi searched pamoja na mzizi wa sasa wakati kujenga mfumo inatafuta rasilimali. Mipangilio ya kawaida customized ni zilizomo katika faili frameworks / msingi / msingi / resres / resres / maadili / config.xml. Kuongeza faili ya overlay kwenye faili ya ujenzi wa mradi kwa kutumia moja ya zifuatazo: PRODUCT_PACKET_OVERLAYS: = kifaa_IMPLAYER: = jina la kifaa: = overlay PRODUCT_PACKET_OVERLAYS: = muuzaji: * jina la muuzaji: * juu ya faili: * kuongeza faili ya overlay kwenye faili ya ujenzi wa mradi: * yoyote ya safu au safu ya safu zilizopatikana katika faili ya config.xml Kuunda bidhaa Unaweza kupanga faili chanzo kwa ajili ya kifaa chako katika njia nyingi tofauti. Hapa ni maelezo mafupi ya njia moja ya kuandaa utekelezaji Pixel. Pixel ni kutekelezwa na msingi kifaa Configuration aitwaye Marlin. Kutoka kwa muundo huu wa kifaa, bidhaa huundwa na faili ya ufafanuzi wa bidhaa ambayo inatangaza habari maalum ya bidhaa kuhusu kifaa kama vile jina na mfano. Unaweza kuangalia orodha ya kifaa na Google ili kuona jinsi ya kufanya kazi. Kuandika bidhaa makefiles Hatua zifuatazo kuelezea jinsi ya kuanzisha bidhaa makefiles kwa njia sawa na ile ya Pixel bidhaa mstari: - Kuunda kifaa <name> kampuni <name> <name> kifaa <name> directory kwa ajili ya bidhaa yako. Kwa mfano, kifaa cha Google. Mwongozo huu itakuwa na chanzo code kwa ajili ya kifaa chako pamoja na makefiles kujenga yao. - Kuunda device.mkmakefile ambayo inatangaza faili na modules zinahitajika kwa ajili ya kifaa. Kwa mfano, angalia - Kuunda bidhaa ufafanuzi makefile kuunda bidhaa maalum kulingana na kifaa. Makefile yafuatayo inachukuliwa kutoka kifaa / google / marlin / aosp_marlin.mkas mfano. Kumbuka kwamba bidhaa inarithi kutoka kwa muuzaji / google marlin au kifaa-muuzaji-marlin.mk faili kupitia faili ya kufanya wakati pia kutangaza habari maalum ya bidhaa kama vile jina, brand, na mfano. "Kama ilivyoelezwa hapo juu, ""Msingi wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo wa Mfumo.""" - Kuunda AndroidProducts.mkfile kwamba inaonyesha bidhaa ya makefiles. Katika mfano huu, tu bidhaa ufafanuzi makefile inahitajika. "Kama ilivyoelezwa hapo juu, ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google"" na ""Mapato ya Google"" ni ""Mapato ya Google.""" Kwa mfano, angalia - Kwa Android 9 na chini tu, kuunda vendorSetup.shfile kuongeza bidhaa yako (mlo mchana combo) kwa kujenga pamoja na kujenga tofauti kutenganishwa na dash. Kwa mfano: - Katika hatua hii, unaweza kuunda aina zaidi ya bidhaa kulingana na kifaa hicho. Kuweka bidhaa ufafanuzi vigezo Bidhaa maalum vigezo ni kufafanuliwa katika bidhaa ya makefile. Jedwali inaonyesha baadhi ya vigezo kudumishwa katika faili ya ufafanuzi wa bidhaa. Apt Configuration - Fanya kazi kwa kuunda vifurushi <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> < aapt sifa kuruhusu kuongeza rasilimali tofauti-maalum kwa mfuko. Orodha ya maneno kama chanzo_njia: malengo_njia. Faili katika njia ya chanzo inapaswa kunakiliwa kwa njia ya marudio wakati wa kujenga bidhaa hii. Sheria kwa ajili ya hatua ya nakala ni kufafanuliwa katika Jina la muundo wa viwanda. Hii pia ni jina la bodi, na mfumo wa kujenga hutumia orodha iliyogawanywa na nafasi ya nambari ya lugha ya herufi mbili, jozi za nambari za nchi za herufi mbili ambazo zinaelezea mipangilio kadhaa kwa mtumiaji, kama vile lugha ya UI na wakati, tarehe, na muundo wa sarafu. Mfumo wa eneo wa kwanza ulioorodheshwa katika PRODUCT_LOCALES hutumiwa kama eneo la default la bidhaa. < start=""102.0" dur=""0.0""> Jina la mtengenezaji. _Mtumizi wa mwisho-kuonekana jina kwa ajili ya bidhaa ya mwisho. |Mtumizi wa mwisho-kuonekana jina kwa ajili ya bidhaa ya jumla. Inaonekana katika mipangilio > Kuhusu screen. OTA (Over-the-Air) Funguo za Umma "Mfano wa ""APK"" ni APKs na modules ambazo zinapaswa kuunganishwa na programu." |Inaonyesha kama kutumia rasilimali default au kuongeza yoyote ya bidhaa maalum overlays. Orodha ya mfumo mali mgawo katika muundo "key=thamani" kwa ajili ya mfumo wa mgawanyiko. Vipengele vya mfumo kwa ajili ya partitions nyingine inaweza kuweka kupitia PRODUCT_PARTITION_PROPERTIES kama katika PRODUCT_VENDOR_PROPERTIES kwa ajili ya sehemu ya muuzaji. Kuanzisha lugha ya default ya mfumo na filters eneo: Kuanzisha lugha ya default ya mfumo na filters eneo, kisha kuwezesha filters eneo kwa ajili ya aina mpya ya kifaa. Configure wote lugha default na mfumo wa eneo kichujio kutumia kujitolea mfumo mali: ro.product.locale: kwa ajili ya kuweka default eneo. Hii ni awali kuweka kwa eneo la kwanza katika PRODUCT_LOCALESvariable; unaweza kufuta thamani hiyo. (Kwa habari zaidi, angalia Setting bidhaa ufafanuzi vigezo meza.) ro.localization.locale_filter: kwa ajili ya kuweka kichujio eneo, kwa kutumia usemi wa kawaida kutumika kwa majina ya eneo. Kwa mfano: - Filter ya kujumuisha: ^(de-AT|de-DE|en|uk). *- inaruhusu tu Kijerumani (Austria na Ujerumani variants), wote Kiingereza variants ya Kiingereza, na Kiukreni - Exclusive filter: ^(?!de-IT|es). *- haijumuishi Kijerumani (tofauti ya Italia), na tofauti zote za Kihispania. - Inclusive filter: Kuwezesha eneo filter Kuwezesha chujio, kuweka ro.localization.locale_filter mfumo mali string thamani. Kwa kuweka thamani ya mali ya kichujio na lugha default kupitia kiwanda calibration unaweza configure vikwazo bila kuoka kichujio katika picha ya mfumo. "Kama vile ilivyoelezwa hapo juu, bidhaa hizi zinapaswa kuunganishwa na sehemu ya OEM kwa kuongeza ""OEM"" kwa ""OEM"" kama ilivyoelezwa hapa chini: ""Ujumbe kwa ajili ya Customization OEM"" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Product-OEM) "" (Properformance) "") " Kwa njia hii, maadili default ni kuhifadhiwa wakati wa kiwanda reset, hivyo mipangilio ya awali kuangalia hasa kama kuanzisha kwanza kwa mtumiaji. "Kuweka ""ADB_VENDOR_KEY"" kuunganisha kupitia USB ""ADB_VENDOR_KEY"" mazingira variable inawezesha wazalishaji wa kifaa kupata debuggable kujenga (userdbug na -eng, lakini si -mtumiaji) juu ya adb bila ruhusa ya mkono." Kwa kawaida adb inazalisha ufunguo wa kipekee wa uthibitisho wa RSA kwa kila kompyuta ya mteja, ambayo itatuma kwa kifaa chochote kilichounganishwa. Hii ni ufunguo RSA kuonyeshwa katika adb idhini mazungumzo. Kama mbadala unaweza kujenga funguo inayojulikana katika picha ya mfumo na kushiriki nao na mteja adb. Hii ni muhimu kwa ajili ya maendeleo ya OS na hasa kwa ajili ya kupima kwa sababu inaepuka haja ya manually kuingiliana na adb idhini mazungumzo. Kuunda funguo muuzaji, mtu mmoja (kwa kawaida meneja wa kutolewa) lazima: - kuzalisha jozi muhimu kwa kutumia adb keygen. Kwa vifaa vya Google, Google inazalisha jozi mpya ya ufunguo kwa kila toleo jipya la OS. - Angalia jozi muhimu katika, mahali fulani katika mti chanzo. Google ni moja ya makampuni ya kuhifadhi data katika tovuti ya Google, kama vile Google Security, Google Security, na Google Adwords. - Kuweka kujenga variable PRODUCT_ADB_KEYS kwa uhakika kwa directory muhimu yako. "Kufanya hivyo, Google inaongeza faili ya Android.mk kwenye orodha ya funguo ambayo inasema ""Product_ADB_Key"" (PRODUCT_ADB_KEY) = ""PLATFORM_VERSION"" (PLATFORM_VERSION) ""adb_key"" (pub) ambayo inasaidia kuhakikisha kwamba tunakumbuka kuzalisha jozi mpya za funguo kwa kila toleo la OS." "Kama ilivyoelezwa hapo juu, ""Kuchukua"" ni jina la kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo cha kiungo." "Kama ilivyoelezwa hapo juu, ""Platform_VERSION"" ni ""Platform_VERSION"" katika ""build_core_version_defaults_mk"" na ""Platform_VERSION"" ni ""Platform_VERSION"" katika ""build_core_version_defaults_mk"" na ""Platform_version_defaults_defaults_mk"" ni ""Platform_version"" katika ""Platform_version_defaults_defaults_mk""" "Kama unavyoona, ""Kumbuka"" ni moja ya vichwa vya habari vya Google, na ""Kumbuka"" ni moja ya vichwa vya habari vya Google, na ""Kumbuka"" ni moja ya vichwa vya habari vya Google, na ""Kumbuka"" ni moja ya vichwa vya habari vya Google." adb kujaribu hizi funguo canonical kwanza, kabla ya kuanguka nyuma ya kuzalisha ufunguo mwenyeji ambayo inahitaji idhini ya mkono. Wakati adb haiwezi kuunganisha kwa kifaa unauthorized, ujumbe wa kosa itaonyesha kwamba wewe kuweka ADB_VENDOR_KEYS kama si