blocks|key|2566558|text|有关这里的概述，请参阅Build.FINGERPRINT：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2566559|android.os.Build.FINGERPRINT:唯一标识此构建的字符串。它应该是人类可读的。它必须遵循以下模板：
$(BRAND)/$(PRODUCT)/$(DEVICE)/$(BOARD):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS)
例如:+acme/mydevice/generic/generic:2.1-update1/ERC77/3359:userdebug/test-keys
指纹不能包括空格。如果模板中包含的其他字段有空格，则应将它们替换为指纹中的ASCII下划线("_")字符。|blockquote|2566560|我知道你确实需要你的平台认证+(是的，包括提供指纹以便市场只显示那些你的设备能够运行的应用程序)，然后才能获得使用市场的许可。|2566561|entityMap|0|LINK|mutability|MUTABLE|url|http://chall32.blogspot.com/2010/06/android-market-fingerprints-demystified.html|1|http://source.android.com/faqs.html^0|2|2|0|0|0|C|2|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

See <a href="http://chall32.blogspot.com/2010/06/android-market-fingerprints-demystified.html" rel="noreferrer">here</a> for an overview of Build.FINGERPRINT:

<blockquote>
 android.os.Build.FINGERPRINT: A string
 that uniquely identifies this build.
 It SHOULD be reasonably
 human-readable. It MUST follow this
 template:
 
 $(BRAND)/$(PRODUCT)/$(DEVICE)/$(BOARD):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS)
 
 For example:
 acme/mydevice/generic/generic:2.1-update1/ERC77/3359:userdebug/test-keys
 
 The fingerprint MUST NOT include
 spaces. If other fields included in
 the template above have spaces, they
 SHOULD be replaced with the ASCII
 underscore ("_") character in the
 fingerprint.
</blockquote>

I do know that you do need to have your platform <a href="http://source.android.com/faqs.html" rel="noreferrer">certified</a> (which yes, includes providing your fingerprint so that Market can display only those apps that your device is able to run) before being licensed to use the Market.

blocks|key|2207747|text|build/core/Makefile:++BUILD_FINGERPRINT+:=+$(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2207748|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>build/core/Makefile: BUILD_FINGERPRINT := $(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)
</code></pre>

blocks|key|2566607|text|注意，最近的AOSP删除了$(BOARD)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2566608|现在看起来是这样的：$(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BF_BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)|2566609|指纹%2520：%253D%2520$|2566610|构建/制造/核心/syspro.mk|2566611|#+BUILD_FINGERPRINT+is+used+used+to+uniquely+identify+the+combined+build+and
#+product;+used+by+the+OTA+server.
ifeq+(,$(strip+$(BUILD_FINGERPRINT)))
++ifeq+($(strip+$(HAS_BUILD_NUMBER)),false)
++++BF_BUILD_NUMBER+:=+$(BUILD_USERNAME)$$($(DATE_FROM_FILE)+%2B%25m%25d%25H%25M)
++else
++++BF_BUILD_NUMBER+:=+$(file+<$(BUILD_NUMBER_FILE))
++endif
++BUILD_FINGERPRINT+:=+$(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BF_BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)
endif|code-block|syntax|javascript|2566612|所以正确的指纹就像：|2566613|象素|BOLD|2566614|google/shamu/shamu:5.1.1/LMY48Y/2364368:user/release-keys|2566615|三星S9|2566616|samsung/starqlteue/starqlteue:10/QP1A.190711.020/G960U1UEU9FUE4:user/release-keys|2566617|三星S10|2566618|samsung/beyond2qlteue/beyond2q:11/RP1A.200720.012/G975U1UEU5GUE4:user/release-keys|2566619|entityMap|0|LINK|mutability|MUTABLE|url|https://cs.android.com/android/platform/superproject/%2B/master:build/make/core/sysprop.mk;l=170?q=BUILD_FINGERPRINT%2520:%253D%2520$^0|D|8|0|A|44|0|0|D|0|0|0|0|0|0|2|0|0|0|4|0|0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1J|8|@]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|J|3|K|5|6|7|1N|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1O|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|1P|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1Q|8|@$9|1R|A|1S|B|U]]|D|@]|E|$]]|$1|V|3|W|5|N|7|1T|8|@]|D|@]|E|$O|P]]|$1|X|3|Y|5|6|7|1U|8|@$9|1V|A|1W|B|U]]|D|@]|E|$]]|$1|Z|3|10|5|N|7|1X|8|@]|D|@]|E|$O|P]]|$1|11|3|12|5|6|7|1Y|8|@$9|1Z|A|20|B|U]]|D|@]|E|$]]|$1|13|3|14|5|N|7|21|8|@]|D|@]|E|$O|P]]|$1|15|3|-4|5|6|7|22|8|@]|D|@]|E|$]]]|16|$17|$5|18|19|1A|E|$1B|1C]]]]

Note that the recent AOSP remove the <code>$(BOARD)</code>
Now it looks like this:
<code>$(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BF_BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)</code>
<a href="https://cs.android.com/android/platform/superproject/+/master:build/make/core/sysprop.mk;l=170?q=BUILD_FINGERPRINT%20:%3D%20$" rel="nofollow noreferrer">https://cs.android.com/android/platform/superproject/+/master:build/make/core/sysprop.mk;l=170?q=BUILD_FINGERPRINT%20:%3D%20$</a>
build/make/core/sysprop.mk
<pre><code># BUILD_FINGERPRINT is used used to uniquely identify the combined build and
# product; used by the OTA server.
ifeq (,$(strip $(BUILD_FINGERPRINT)))
 ifeq ($(strip $(HAS_BUILD_NUMBER)),false)
 BF_BUILD_NUMBER := $(BUILD_USERNAME)$$($(DATE_FROM_FILE) +%m%d%H%M)
 else
 BF_BUILD_NUMBER := $(file &lt;$(BUILD_NUMBER_FILE))
 endif
 BUILD_FINGERPRINT := $(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BF_BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)
endif
</code></pre>
So a correct fingerprint is like:
Pixel
<pre><code>google/shamu/shamu:5.1.1/LMY48Y/2364368:user/release-keys
</code></pre>
Samsung S9
<pre><code>samsung/starqlteue/starqlteue:10/QP1A.190711.020/G960U1UEU9FUE4:user/release-keys
</code></pre>
Samsung S10
<pre><code>samsung/beyond2qlteue/beyond2q:11/RP1A.200720.012/G975U1UEU5GUE4:user/release-keys
</code></pre>

Android documentation refers to <a href="http://developer.android.com/reference/android/os/Build.html#FINGERPRINT" rel="noreferrer">Build.FINGERPRINT</a> as a way to uniquely identify the build. I'd like to know how this property is generated. I'm compiling whole framework on my board and it's set by default to unknown. Another question is if Market uses this identifier as some kind of validation?

Creating Build.FINGERPRINT on Android

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

Android文档将作为唯一标识构建的一种方式。我想知道这个属性是如何生成的。我正在我的板上编译整个框架，默认设置为未知。另一个问题是，市场是否使用此标识符作为某种验证？

问在Android上创建Build.FINGERPRINT
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Android上创建Build.FINGERPRINTEN