Nuke adds a settings layer to WeChat, QQ and Douyin on Android

A module that lives inside three Chinese apps

Nuke is an Android Xposed module that targets three applications, and the support table in the README gives the package names so there is no ambiguity about what gets patched. WeChat is com.tencent.mm and is described as the current main platform, with a settings entry, chat and Moments menu extensions and interface customisation. QQ is com.tencent.mobileqq, where module loading and a menu entry are in place and further adaptation is still being worked on. Douyin is com.ss.android.ugc.aweme, with a settings entry, filtering of the recommendation feed and some basic experience options. The project notes are explicit that the coverage differs per platform and that the in-app settings screen of the current version is the authority on what is actually available. That is a useful warning, because a module that hooks into three very different applications and hosts versions has to be re-adapted whenever one of them updates, and the docs say so directly: after WeChat, QQ or Douyin update, some features may need to be adapted again.

What the module actually adds to WeChat

The WeChat feature list is the most developed of the three, and it reads as a set of interface and quality-of-life changes rather than new capability. A Nuke entry is added to the WeChat settings page, the long-press menus on chat messages and on Moments posts are extended, and tablet mode can be forced on, which is useful if you use a phone with a large screen or want the two-column layout on a tablet. There are cosmetic extras too, including round avatars, the ability to rotate chat avatars and a setting for the rotation period. The general capabilities listed apply across hosts: features can be enabled, disabled and configured from inside the host application, there is light and dark theme support with a custom theme colour, and the interface is available in Simplified Chinese, Traditional Chinese and English. There is also a set of support affordances, with function status, exception records and the ability to restart the host app, which tells you the module expects to be restarted after configuration changes rather than hot reloading.

Douyin filters the feed, QQ is still a work in progress

The Douyin list is short and concrete. A Nuke entry is added to the Douyin settings page, live streams and advertisements are filtered out of the recommendation feed, the update check is blocked, the high picture quality mode is preserved, and the teen mode pop-up is hidden. Each of those is a decision about what the host app shows you, and the update check one has an obvious side effect: the module keeps the app on the version you have rather than letting it upgrade itself, which also means it is the version you have to re-check for compatibility after each host update. The QQ support is described more cautiously. The module can be loaded inside QQ and a menu entry is provided, and the documentation says the remaining features and adaptation are being completed. If QQ is the app you actually use, the honest reading is that Nuke today is a WeChat and Douyin tool with a QQ foothold.

Two installation routes, and only one of them needs root

The framework support table splits the install by whether the device is rooted. In a root environment, Nuke works with Vector, LSPosed and other Xposed compatible frameworks, so the sequence is: install Nuke, enable the module in the framework, add WeChat, QQ or Douyin to the module scope, force stop the target app, reopen it, and then enter the Nuke entry from inside the host app to switch features on. In a non-root environment the module is injected into a copy of the target application using NPatch, FPA or LSPatch. You prepare the Nuke package and the target app package, follow the injection flow for whichever tool you use, install and launch the patched app, and then configure from the Nuke entry inside it. The documentation also states plainly that actual availability depends on the Android version, the host app version and the framework, and that support for a given framework does not mean every host version or every function works.

The runtime requirements and the Dex analysis step

The runtime target is Android 8.1 and above on ARM64 devices, which is stated as the environment for running the module. There is one operational wrinkle that will catch you out. On first load in WeChat and Douyin, some features require a Dex analysis to complete first, and the analysis can cause the app to exit or restart, after which you reopen it and carry on. A separate Nuke app exists for checking module status and for usage guidance. The FAQ section names the two failure messages you are most likely to hit. A Dex analysis failure with NameNotFoundException is fixed by adjusting the Hide My Applist configuration so that it does not hide Nuke from WeChat, then restarting WeChat. A failure with IllegalStateException is attributed to the device being unable to download runtime files from the server, and the suggested fix is to connect a VPN and try again.

Closed source, and a script API documented elsewhere

The repository holds a README and a .github directory, and that is essentially all of it. The project states in an important note that Nuke is closed source and that this repository is for project presentation only, with no source code published. The licence field carries no identified licence, which follows from that, so there is no permission text to read and no way to check what the module does to your chat application before you install it. There is one part of the project that is open in practice. Script development documentation is maintained in a separate repository, NukeDevelopers/NukeJsDocs, which the documentation says contains a quick start, the permission model, an API reference and migration notes. The feature overview also mentions script extension capability, so the intended model is that the closed binary is a host for scripts whose API is documented. That is a workable arrangement for the author and an awkward one for you, since a script you can read is a script you can trust, while the module that hosts it is not open. The releases page is the distribution point, with versions v1.0.9, v1.1.0 and v1.1.1 shipped between late September and mid October 2026.

Where Nuke is the wrong choice

There are three situations where this is not a fit. The first is a device you do not control or cannot patch. The non-root route is not a convenience path, it requires repacking the host application and reinstalling it, which breaks on managed devices, on work profiles, and wherever the original app signature matters for login or push notifications. The second is anyone who needs to know what the module does. Because the code is closed and the licence unstated, you are trusting a binary that has full access to three applications that hold your messages, your contacts and your feed. The third is a device that is neither rooted nor patchable, which is most of them. Nuke is not a general enhancement to WeChat, it is a modification of WeChat, and the value it adds is real but narrow: extra menus, a settings entry, a filter on the recommendation feed and a few cosmetic options. The most relevant comparison is with the host apps' own settings, and if what you want is mostly to remove noise from the feed, the Douyin options are modest enough that you should weigh them against simply not using the app for the hour.

Editorial conclusion

Adopt Nuke if you run WeChat, QQ or Douyin on a rooted or patched Android device and you want the extra menus and interface options without waiting for the host apps to offer them, and you are comfortable with a closed source binary that patches other applications. Skip it if your device is unrooted and you refuse to repack the host app, if you need to audit what the module does to your chat client, or if your organisation blocks app injection. Before you install, read the compatibility notes for the host app version you run, and check the Dex analysis errors in the FAQ, because a module that cannot read the host classes will appear to install correctly and then do nothing.

Frequently asked questions

Official sources

1. dartcv/Nuke on GitHub
2. Issues
3. README
4. Releases