blocks|key|3057144|text|你提到的链接有答案。这是工具的最新版本中引入的一个错误。在下面的评论中，你可以看到一位谷歌代表说修复正在进行中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3057145|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The link which you referred to has the answer.
It is a bug introduced in the latest revision of the tools.
In the followup comments you can read that a google representative says a fix is on the way.

blocks|key|3057266|text|我也遇到了这个问题。作为一种解决方法，我在过滤器的by+Log+Message字段上使用以下表达式过滤LogCat输出：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3057267|%5E(?!.*(nativeGetEnabledTags)).*$+|code-block|syntax|javascript|3057268|否则，它几乎是无用的垃圾邮件。|3057269|遵循Laksh的建议，如果您希望始终过滤此内容，而不必始终将其写入Search+for+messages字段：|3057270|转到左侧的Logcat|3057271|In+|unordered-list-item|3057272|
|3057273|+Saved+Filters+part，单击Edit+selected+logcat+filter+(如果看不到保存的筛选器，则单击Logcat)|3057274|3057275|There，中的Display+Saved+Filters+Edit+selected+logcat+filter在by+Log+Message字段中输入%5E(?!.*(nativeGetEnabledTags)).*$.|3057276|3057277|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/1737392/laksh^0|P|E|1F|6|0|0|0|X|J|2|5|0|0|5|6|0|0|0|1|D|M|R|0|0|U|R|25|W|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1F|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|O|3|P|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1P|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|V|3|W|5|S|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|X|3|U|5|6|7|1W|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|S|7|1X|8|@$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|22|8|@]|D|@]|E|$]]|$1|11|3|-4|5|6|7|23|8|@]|D|@]|E|$]]]|12|$13|$5|14|15|16|E|$17|18]]]]

I just ran into this problem, too. As a workaround I'm filtering the <code>LogCat</code> output with the following expression on the <code>by Log Message</code> field of the filter: 

<pre><code>^(?!.*(nativeGetEnabledTags)).*$ 
</code></pre>

Otherwise it is so spammed it's almost useless.

Following <a href="https://stackoverflow.com/users/1737392/laksh">Laksh</a> suggestion, if you want to filter this always without having to always write it on the <code>Search for messages</code> field:

<ol>
<li>Goto your <code>Logcat</code></li>
<li>In the <code>Saved Filters</code> part on the left, click on the <code>Edit selected logcat filter</code> (If Saved Filters is not visible then click on Display Saved Filters View in the Logcat)</li>
<li>There, in the by Log Message field, enter <code>^(?!.*(nativeGetEnabledTags)).*$</code>. </li>
</ol>

blocks|key|205022|text|这是API+17的仿真器系统映像中的一个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|205023|目前，您的变通方法如下：|205024|如果不需要API+level+17，则使用|205025|使用带有API+16+(或更高版本的lower)...|offset|length|style|BOLD|205026|...or+)的仿真器(例如API+19，经过测试也可以解决该问题)。|unordered-list-item|205027|。|205028|205029|205030|如果您确实需要API+level+17，请使用|205031|205032|使用真实设备:Nexus4、Nexus7、Nexus10。|205033|使用亨德里克建议的LogCat过滤器。不过，您必须编辑您拥有的每个过滤器(如果您想要全部修复它们)。|205034|205035|entityMap^0|0|0|0|0|R|0|0|Z|0|0|1|0|0|0|0|J|0|0|0|T|0|0|1E|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@$H|16|I|17|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|18|8|@$H|19|I|1A|J|K]]|9|@]|A|$]]|$1|O|3|P|5|N|7|1B|8|@$H|1C|I|1D|J|K]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1G|8|@$H|1H|I|1I|J|K]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|V|3|W|5|N|7|1K|8|@$H|1L|I|1M|J|K]]|9|@]|A|$]]|$1|X|3|Y|5|N|7|1N|8|@$H|1O|I|1P|J|K]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|11|$]]

It's a bug in the emulator System Image for API 17.

At the moment, your workarounds are the following:

If you DON'T need API level 17

<ul>
<li>Use an emulator with API 16 (or lower)...</li>
<li>...or higher (API 19 for instance, tested to solve the problem too).</li>
</ul>

If you DO need API level 17

<ul>
<li>Use a real device: Nexus 4, Nexus 7, Nexus 10.</li>
<li>Use the LogCat filter suggested by Hendrik. You'll have to edit every single filter you have, though (If you want to fix them all).</li>
</ul>

blocks|key|207735|text|从Android+SDK+Manager更新ARM+EABI+v7a+System+Image，警告将不会再出现。!！:)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|207736|是。这仅适用于ARM+EABI系统映像，而不适用于英特尔映像。|207737|更新|BOLD|207738|似乎有一个API18的Intel+x86+Atom+System+Image更新可以修复这个问题(我还没有尝试过)。手动安装系统映像的link。当然，它也可以在Android+SDK管理器中使用。|207739|但它只适用于Android4.3。4.2.x开发人员可能还需要等待修复！|207740|entityMap|0|LINK|mutability|MUTABLE|url|http://software.intel.com/en-us/articles/intel-atom-x86-image-for-android-jelly-bean-43-installation-instructions-manually^0|1|J|M|P|0|0|0|2|0|B|R|1V|4|1V|4|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|M|3|N|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Update the <code>ARM EABI v7a System Image</code> from <code>Android SDK Manager</code> and the warning wont be seen any more .. !! :)

Yes. This works only for ARM EABI System Image and not for Intel image.

Update

Seems like there is a Update available for the <code>Intel x86 Atom System Image</code> for API 18 which fixes the issue (I have not tried it though). A <a href="http://software.intel.com/en-us/articles/intel-atom-x86-image-for-android-jelly-bean-43-installation-instructions-manually"><code>link</code></a> to manually install the system image. Ofcourse its also available in Android SDK Manager.

But its only for Android 4.3. The 4.2.x developers might still have to wait for a fix..!

blocks|key|2844551|text|英特尔x86凌动镜像和"nativeGetEnabledTags:+0“的问题已在安卓4.3+(API+18)英特尔x86凌动镜像的发布中修复。我刚测试过，可以确认这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2844552|有了手臂图像，我知道这是一段时间前修复的.|2844553|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The problem with Intel x86 Atom images and "nativeGetEnabledTags: 0" is fixed with the release of the Android 4.3 (API 18) Intel x86 Atom image. I just tested it and can confirm that.

With ARM images this was fixed some time ago, I know ...

blocks|key|209437|text|由于这些消息是用Trace标签标记的，因此您可以使用更简单的表达式来过滤它们的by+Log+Tag字段：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|209438|%5E(?!Trace)|code-block|syntax|javascript|209439|就这样。|209440|顺便说一句，我也在真实设备上看到了这些消息(Fly+IQ4410)。|209441|entityMap^0|8|5|13|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

Since these mesasages are tagged with the <code>Trace</code> tag, you can use simpler expression to filter them <code>by Log Tag</code> field: 

<pre><code>^(?!Trace)
</code></pre>

That's it.

Btw, I also see these messages on the real device (Fly IQ4410).

blocks|key|207850|text|我已经添加了%5E(?!.*(nativeGetEnabledTags)).*$过滤器，但您可以看到它对我的帮助有多小：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|207851|​|207852|📷|atomic|207853|207854|从1157中过滤了几个，799绕过了相同的比率，但数字更大：|207855|207856|207857|207858|我需要添加"SpamFilter“才能使用日志猫：|207859|207860|207861|207862|按日志标签：|207863|+%5E(?!Trace%7CADB_SERVICES%7CBufferQueue%7Cwpa_supplican%7CSurfaceFlinger%7CSettings/BW%7CBluetooth+HS/HF)|code-block|syntax|javascript|207864|按应用程序名称：|207865|%5E(?!com.android.systemui%7Csystem_process)|207866|对我来说，它让Logcat变得有点实用。|207867|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1e2a75ba39bfba12aa3f79751297a701.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/a25b90156484412ab58c6250aa99f1ef.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/e70c6ab5ea4c60ad0c8da255dc14b284.png^0|6|W|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1O|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|K|3|G|5|6|7|1T|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1U|8|@]|D|@]|E|$]]|$1|N|3|G|5|6|7|1V|8|@]|D|@]|E|$]]|$1|O|3|I|5|J|7|1W|8|@]|D|@$9|1X|A|1Y|1|1Z]]|E|$]]|$1|P|3|G|5|6|7|20|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|21|8|@]|D|@]|E|$]]|$1|S|3|G|5|6|7|22|8|@]|D|@]|E|$]]|$1|T|3|I|5|J|7|23|8|@]|D|@$9|24|A|25|1|26]]|E|$]]|$1|U|3|G|5|6|7|27|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|28|8|@]|D|@]|E|$]]|$1|X|3|Y|5|Z|7|29|8|@]|D|@]|E|$10|11]]|$1|12|3|13|5|6|7|2A|8|@]|D|@]|E|$]]|$1|14|3|15|5|Z|7|2B|8|@]|D|@]|E|$10|11]]|$1|16|3|17|5|6|7|2C|8|@]|D|@]|E|$]]|$1|18|3|-4|5|6|7|2D|8|@]|D|@]|E|$]]]|19|$1A|$5|1B|1C|1D|E|$1E|1F|1G|-4]]|1H|$5|1B|1C|1D|E|$1E|1I|1G|-4]]|1J|$5|1B|1C|1D|E|$1E|1K|1G|-4]]]]

I have added the <code>^(?!.*(nativeGetEnabledTags)).*$</code> filter, but you can see how few it helps me:

<img src="https://i.stack.imgur.com/7KPYK.png" alt="enter image description here">

from 1157 is filtered a few and 799 bypassed same ratio, but a bit bigger numbers:

<img src="https://i.stack.imgur.com/yWSBp.png" alt="enter image description here">

I needed to add the "SpamFilter" to be able to use the Logcat:

<img src="https://i.stack.imgur.com/Tod40.png" alt="enter image description here">

by Log Tag:

<pre><code> ^(?!Trace|ADB_SERVICES|BufferQueue|wpa_supplican|SurfaceFlinger|Settings/BW|Bluetooth HS/HF)
</code></pre>

by Application Name: 

<pre><code>^(?!com.android.systemui|system_process)
</code></pre>

For me it made a bit usable the Logcat.

blocks|key|205175|text|我收到了很多类似的消息，所以我需要更好的过滤器。将这些过滤器添加到LogCat：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|205176|按日志标签的：|offset|length|style|BOLD|205177|%5E(?!.*(GN_FW_TextView%7CGN_FW_Editor%7CSurfaceTextureClient%7Cskia%7CAbsListView%7CProvider/Settings%7CInputMethodManager%7Cjdwp)).*$|code-block|syntax|javascript|205178|按日志显示的消息：|205179|%5E(?!.*(nativeGetEnabledTags)).*$|205180|entityMap^0|0|6|1|0|0|6|3|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I was getting lots of similar messages, so I needed better filters. Add these filters to the LogCat:

By log tag: 

<pre><code>^(?!.*(GN_FW_TextView|GN_FW_Editor|SurfaceTextureClient|skia|AbsListView|Provider/Settings|InputMethodManager|jdwp)).*$
</code></pre>

By log message:

<pre><code>^(?!.*(nativeGetEnabledTags)).*$
</code></pre>

I installed the latest version of the SDK (r21) and ADT 21.0.0. I tried simple code, and it works well, but now I get a warning in <a href="https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file">LogCat</a> that did not appear in the previous versions:

<blockquote>
 Unexpected value from nativeGetEnabledTags: 0
</blockquote>

I googled it, and I found <a href="http://code.google.com/p/android/issues/detail?id=39723">Issue 39723: Emulator spams LogCat with "Unexpected value from nativeGetEnabledTags: 0" message</a>.

What does it mean?

Unexpected value from nativeGetEnabledTags: 0

软件开发

Android

我安装了最新版本的软件开发工具包(r21)和ADT21.0.0。我尝试了简单的代码，它工作得很好，但现在我在中收到了以前版本中没有的警告：来自nativeGetEnabledTags的意外值:0我用谷歌搜索了一下，找到了什么意思？

问来自nativeGetEnabledTags的意外值:0
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问来自nativeGetEnabledTags的意外值:0EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问来自nativeGetEnabledTags的意外值:0
EN