vpnhide/docs
okhsunrog f543284ffb refactor(zygisk): persist debug_logging outside module dir
The Zygisk debug_logging flag lived only in the module dir
(/data/adb/modules/vpnhide_zygisk/), which KSU/Magisk wipe on every
module reinstall. Until the user next opened the app, all newly
forked target apps under that module would fall back to the OFF
default — even when the user had toggled debug logging ON. Same
problem the targets.txt file solved long ago by living in the
persistent dir; apply the same fix here.

- Canonical location: /data/adb/vpnhide_zygisk/debug_logging
  (alongside the existing targets.txt). Survives module reinstall.
- writeDebugFlagFiles writes BOTH the persistent file and the
  module-dir mirror on every toggle, so the .so still reads its
  current value via get_module_dir() fd at next fork.
- zygisk/module/service.sh copies persistent → module-dir at every
  boot, mirroring the existing targets.txt copy. Restores the
  module-dir mirror after a reinstall without needing the app
  to open.
- MainActivity.onCreate re-propagation comment updated: this call
  is now a safety-net for "reinstall mid-session, no reboot yet"
  rather than the only defence against module-dir wipe.
- docs/state.md sections 1, 2, 3 updated.

No changelog fragment — internal refactor; the user-visible effect
(less likely to need to re-toggle after zygisk reinstall) is too
subtle for a CHANGELOG line.
2026-04-28 00:12:58 +03:00
..
changelog.md fix(scripts): CHANGELOG.md at release time + Markdown fragments 2026-04-19 21:57:34 +03:00
development.md ci: shave another ~80s off lint/lsposed jobs 2026-04-27 00:28:25 +03:00
releasing.md build: align native cdylib on 16 KiB; unify kmod/zygisk build scripts 2026-04-26 23:26:30 +03:00
state.md refactor(zygisk): persist debug_logging outside module dir 2026-04-28 00:12:58 +03:00