Files

T

Claude Sonnet 5 328237d722 Add release/build tooling and README

- Real release build type: R8 shrinking + shrunk resources, with a keep
  rule for VeilHook specifically — LSPosed finds it by exact class name via
  the plaintext xposed_init asset, which R8 can't see, so obfuscating it
  would silently break module loading with no build error to point at why.
- Signing config that reads keystore.properties if present (gitignored,
  generated via scripts/generate-keystore.sh), falling back to debug
  signing otherwise so assembleRelease always produces something
  installable.
- scripts/release.sh builds and copies a version-stamped APK into dist/.
- GitHub Actions workflow building and publishing a release on any tag
  matching *.*.* (bare semver, e.g. 1.2.0 — no v prefix required), optionally
  using repo secrets for real release signing in CI.
- README covering setup, the feature table, and the DenyList gotcha.

No native code in this module, so a single APK already covers every
architecture — no per-ABI splitting needed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-06 21:46:16 +06:00

2.6 KiB

Raw Permalink Blame History

Veil

An LSPosed module that hides accessibility, debugging, and root/hook state from specific apps, per app, without changing the actual state of the device.

Important

Built entirely by AI in one evening to fix a personal problem. YMMV — it works for me and hasn't been audited beyond that.

Requirements

Rooted device with a working Zygisk implementation and LSPosed (or an LSPosed-compatible framework such as Vector).
Android 8.1+.

Setup

Build (below) or grab a release APK from the repo's Releases page.
Enable the module in LSPosed Manager and scope it to the target app.
Open the target app once — it appears in Veil's own settings screen automatically.
Uncheck anything you don't want hidden for that app.

If the target app still won't launch, check whether it's on your root manager's DenyList (e.g. KernelSU: app profile → "Umount modules"). An app on that list never gets Zygisk modules injected at all, Veil included. The settings screen's help panel covers this and a few other gotchas.

Features

Per app, per feature — anything not listed gets everything hidden by default.

Feature	Hides
Accessibility services	Any accessibility service running
USB / wireless debugging	`adb_enabled` / `adb_wifi_enabled`
Developer options	Developer Options enabled state
Mock location	Legacy pre-Marshmallow flag only
Root / manager apps	Configurable package list (default: KernelSU, Magisk)
Build tags/type	Real build swapped for `release-keys` / `user`

Doesn't cover native-level root/hook detection or remote attestation (Play Integrity, SafetyNet) — that's your Zygisk implementation's job, not Veil's.

Building

Requires JDK 17 and Android SDK (platform 35, build-tools 35.0.0).

./gradlew assembleDebug       # debug-signed APK
./gradlew assembleRelease     # minified release build, debug-signed unless keystore.properties exists
scripts/generate-keystore.sh  # create a personal release-signing keystore
scripts/release.sh            # build + copy signed release APK into dist/

CI releases

Pushing a tag matching *.*.* (e.g. 1.2.0) triggers .github/workflows/release.yml. For a properly signed CI build, set repo secrets: KEYSTORE_BASE64 (base64 of your release.jks), KEYSTORE_PASSWORD, KEY_ALIAS, KEY_PASSWORD.

2.6 KiB Raw Permalink Blame History