Home » Android » android – Unexpected value from nativeGetEnabledTags: 0

android – Unexpected value from nativeGetEnabledTags: 0

Posted by: admin March 10, 2020 Leave a comment

Questions:

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 LogCat that did not appear in the previous versions:

Unexpected value from nativeGetEnabledTags: 0

I googled it, and I found Issue 39723: Emulator spams LogCat with “Unexpected value from nativeGetEnabledTags: 0” message.

What does it mean?

How to&Answers:

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

^(?!.*(nativeGetEnabledTags)).*$ 

Otherwise it is so spammed it’s almost useless.

Following Laksh suggestion, if you want to filter this always without having to always write it on the Search for messages field:

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

Answer:

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

  • Use an emulator with API 16 (or lower)…
  • …or higher (API 19 for instance, tested to solve the problem too).

If you DO need API level 17

  • Use a real device: Nexus 4, Nexus 7, Nexus 10.
  • 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).

Answer:

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.

Answer:

Update the ARM EABI v7a System Image from Android SDK Manager 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 Intel x86 Atom System Image for API 18 which fixes the issue (I have not tried it though). A link 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..!

Answer:

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 …

Answer:

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

^(?!Trace)

That’s it.

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

Answer:

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

By log tag:

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

By log message:

^(?!.*(nativeGetEnabledTags)).*$ 

Answer:

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

enter image description here

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

enter image description here

I needed to add the “SpamFilter” to be able to use the Logcat:

enter image description here

by Log Tag:

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

by Application Name:

^(?!com.android.systemui|system_process)

For me it made a bit usable the Logcat.