blocks|key|1010992|text|引用myself|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1010993|按照谷歌用于M+Developer预览的方法，您可以选择Build.VERSION.CODENAME：|blockquote|style|CODE|1010994|public+static+boolean+iCanHazN()+{
++return("N".equals(Build.VERSION.CODENAME));
}|code-block|syntax|javascript|1010995|我没有像may+7009的评论所暗示的那样，看Build.VERSION.RELEASE，尽管这也是可能的。|1010996|另外，如果你阅读这篇文章是从遥远的未来(+Android已经以最终形式发布)，那么你应该能够使用Build.VERSION.SDK_INT和Build.VERSION_CODES.N。上面的攻击是由于Google处理这些开发者预览的独特之处。|1010997|entityMap|0|LINK|mutability|MUTABLE|url|https://commonsware.com/blog/2016/03/17/backwards-compatibility-n-developer-preview.html^0|2|6|0|0|S|M|0|0|N|L|0|1C|L|1Y|L|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|F|7|13|8|@$A|14|B|15|G|H]]|9|@]|C|$]]|$1|I|3|J|5|K|7|16|8|@]|9|@]|C|$L|M]]|$1|N|3|O|5|6|7|17|8|@$A|18|B|19|G|H]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1A|8|@$A|1B|B|1C|G|H]|$A|1D|B|1E|G|H]]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]]]

Quoting <a href="https://commonsware.com/blog/2016/03/17/backwards-compatibility-n-developer-preview.html">myself</a>:

<blockquote>
 Following the approach that Google used for the M Developer Preview,
 you can check <code>Build.VERSION.CODENAME</code> instead:
</blockquote>

<pre><code>public static boolean iCanHazN() {
 return("N".equals(Build.VERSION.CODENAME));
}
</code></pre>

I haven't looked at <code>Build.VERSION.RELEASE</code>, as suggested by zgc7009's comment, though that too may be a possibility.

Also, if you are reading this from the far future, where Android N has shipped in final form, you should be able to use <code>Build.VERSION.SDK_INT</code> and <code>Build.VERSION_CODES.N</code>. The above hack is due to the idiosyncrasies of how Google handles these developer previews.

blocks|key|1011053|text|我建议使用Integer值来检查Android版本，而不是字符串。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1011054|public+boolean+isAndroidN()+{
++++++++return+Build.VERSION.SDK_INT+==+Build.VERSION_CODES.N;
++++}|code-block|syntax|javascript|1011055|请记住，compileSdkVersion必须在manifests.xml中达到24或更高版本：|1011056|compileSdkVersion+24|1011057|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I would recommend using Integer value for checking Android version rather than String

<pre><code>public boolean isAndroidN() {
 return Build.VERSION.SDK_INT == Build.VERSION_CODES.N;
 }
</code></pre>

Just remember it's necessary to have compileSdkVersion to 24 or higher in manifests.xml:

<pre><code>compileSdkVersion 24
</code></pre>

blocks|key|248964|text|方法1：(推荐)使用支持库android.support.v4.os.BuildCompat.isAtLeastN。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|248965|方法2:将其用作“真实”版本代码：Build.VERSION.SDK_INT+<+23+%7C%7C+Build.VERSION.PREVIEW_SDK_INT+==+0+?+Build.VERSION.SDK_INT+:+Build.VERSION.SDK_INT+%2B+1。|248966|entityMap^0|D|18|0|H|38|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Approach 1: (recommended) Use support library <code>android.support.v4.os.BuildCompat.isAtLeastN</code>.

Approach 2: Use this as the "real" version code: <code>Build.VERSION.SDK_INT &lt; 23 || Build.VERSION.PREVIEW_SDK_INT == 0 ? Build.VERSION.SDK_INT : Build.VERSION.SDK_INT + 1</code>.

blocks|key|1011108|text|我发现Build.VERSION.RELEASE和Build.VERSION.CODENAME的行为是完全不同的，这取决于它是一个完整的Android版本还是一个开发者预览版。我们采用了以下机制。如果您想要解释多个场景，就不能只依赖一个值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1011109|这就是我发现的情况，一个GalaxyNexus5X运行的是一个生产版本的S7和一个运行O+DP1的Nexus5X。|1011110|Galaxy+S7本体+Build.VERSION.BASE_OS:+Build.VERSION.CODENAME+Build.VERSION.INCREMENTAL:+G930FXXU1DQB3+Build.VERSION.PREVIEW_SDK_INT:+0+Build.VERSION.RELEASE:+7.0+Build.VERSION.SDK_INT:+24+Build.VERSION.SECURITY_PATCH:+2017-01-01|offset|length|style|BOLD|1011111|Nexus+5X+O+Build.VERSION.BASE_OS:+Build.VERSION.CODENAME:+o+Build.VERSION.INCREMENTAL:+3793265+Build.VERSION.PREVIEW_SDK_INT:+1+Build.VERSION.RELEASE:+O+Build.VERSION.SDK_INT:+25+Build.VERSION.SECURITY_PATCH:+2017-03-05|1011112|//+release+builds+of+Android+(i.e.+not+developer+previews)+have+a+CODENAME+value+of+"REL"
++++//+check+this.+if+it's+REL+then+you+can+rely+on+value+of+SDK_INT+(SDK_INT+is+inaccurate+for+DPs
++++//+since+it+has+the+same+value+as+the+previous+version+of+Android)
++++//+if+it's+not+REL,+check+its+value.+it+will+have+a+letter+denoting+the+Android+version+(N+for+Nougat,+O+for...+er...+O+and+so+on)

++++boolean+laterThanNougat+=+false;

++++if(Build.VERSION.CODENAME.equals("REL"))+{
++++++++Log.i(TAG,+"This+is+a+release+build");

++++++++//+since+this+is+a+release+build,+we+can+rely+on+value+of+SDK_INT
++++++++if+(android.os.Build.VERSION.SDK_INT+>+25)+{
++++++++++++Log.i(TAG,+"This+is+later+than+Nougat");
++++++++++++laterThanNougat+=+true;
++++++++}+else+{
++++++++++++Log.i(TAG,+"This+is+Nougat+or+before");
++++++++}
++++}+else+{
++++++++Log.i(TAG,+"This+is+NOT+a+release+build");

++++++++//+since+this+is+not+a+release+build,+we+can't+rely+on+value+of+SDK_INT.+must+check+codename+again
++++++++if(Build.VERSION.CODENAME.compareTo("N")+>+0)+{
++++++++++++Log.i(TAG,+"This+is+later+than+Nougat");
++++++++++++laterThanNougat+=+true;
++++++++}+else+{
++++++++++++Log.i(TAG,+"This+is+Nougat+or+before");
++++++++}
++++}|code-block|syntax|javascript|1011113|entityMap^0|0|0|0|B|0|0|A|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|L|3|M|5|N|7|10|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I found that the behaviour of Build.VERSION.RELEASE and Build.VERSION.CODENAME is quite different depending on whether it's a full production release of Android OS or a developer preview. We went with the following mechanism. You can't rely on just one value if you want to account for more than one scenario.

This is what I found was the case for a Galaxy S7 running a production release of Nougat and a Nexus 5X running O DP1.

Galaxy S7 Nougat
Build.VERSION.BASE_OS: 
Build.VERSION.CODENAME: REL
Build.VERSION.INCREMENTAL: G930FXXU1DQB3
Build.VERSION.PREVIEW_SDK_INT: 0
Build.VERSION.RELEASE: 7.0
Build.VERSION.SDK_INT: 24
Build.VERSION.SECURITY_PATCH: 2017-01-01

Nexus 5X O
Build.VERSION.BASE_OS: 
Build.VERSION.CODENAME: O
Build.VERSION.INCREMENTAL: 3793265
Build.VERSION.PREVIEW_SDK_INT: 1
Build.VERSION.RELEASE: O
Build.VERSION.SDK_INT: 25
Build.VERSION.SECURITY_PATCH: 2017-03-05

<pre><code>// release builds of Android (i.e. not developer previews) have a CODENAME value of "REL"
 // check this. if it's REL then you can rely on value of SDK_INT (SDK_INT is inaccurate for DPs
 // since it has the same value as the previous version of Android)
 // if it's not REL, check its value. it will have a letter denoting the Android version (N for Nougat, O for... er... O and so on)

 boolean laterThanNougat = false;

 if(Build.VERSION.CODENAME.equals("REL")) {
 Log.i(TAG, "This is a release build");

 // since this is a release build, we can rely on value of SDK_INT
 if (android.os.Build.VERSION.SDK_INT &gt; 25) {
 Log.i(TAG, "This is later than Nougat");
 laterThanNougat = true;
 } else {
 Log.i(TAG, "This is Nougat or before");
 }
 } else {
 Log.i(TAG, "This is NOT a release build");

 // since this is not a release build, we can't rely on value of SDK_INT. must check codename again
 if(Build.VERSION.CODENAME.compareTo("N") &gt; 0) {
 Log.i(TAG, "This is later than Nougat");
 laterThanNougat = true;
 } else {
 Log.i(TAG, "This is Nougat or before");
 }
 }
</code></pre>

Is it possible to detect if an user is running Android N?

I have a Nexus 6 with the Android N Developer Preview. If I try to get the build version with <code>Build.VERSION.SDK_INT</code>, it returns 23 which is equal to Android Marshmallow.

Detect Android N version code

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

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

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

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

社区新版编辑器体验调研

是否有可能检测用户是否在运行Android？我有一个带有Android N开发者预览的Nexus 6。如果我尝试使用Build.VERSION.SDK_INT获得构建版本，它将返回23，相当于Android。

问检测Android版本代码
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问检测Android版本代码EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问检测Android版本代码
EN