NoWakeLock
com.js.nowakelock
Zapstore _@zapstore.dev Republished from GitHub / F-Droid by the Zapstore main account.
Github: https://github.com/Jasper-1024/NoWakeLock With the update of Android version, doze mode is enough to suppress the power consumption of the background of the application, but some advanced users still hope to be able to control the wakelock by themselves. Amplify is good enough to meet the needs of most people, but after Android N, Amplify stops updating. So NoWakeLock expects to achieve the same function as Amplify does on Android N and later. NoWakeLock is available for Android N and later. For previous versions of Android N, please use Amplify. Serious warning: 2.0-alpha data is not compatible with 1.x, you need to clear the application data before use, if you mind, please don't use 2.x version for now, we will try to solve this problem later.
First release: Jul 26, 2025, 4 total releases.
Most recent release: Mar 15, 2026.
Appears in 0 app stacks.
0 sats / 0 zaps received in the past year.
Sats Received
Underlying data available via MCP: app_zaps, app_releases.
Zap Count
Underlying data available via MCP: app_zaps, app_releases.
Releases
- Mar 15, 2026 3.0.9- Fix cross-app minimum-interval state collisions for same-name WakeLock/Alarm entries - Fix the Service-domain screen-off-only blocking rule not taking effect - Fix timeout field clipping in the DA control section on narrow widths
- Feb 22, 2026 3.0.8- Fix crash in multi-user app list on Android 16 - Improve Samsung/OneUI compatibility (OEM fallback + Nest accessor support for hooks) - Remove `com.android.settings.provider` from the recommended LSPosed scope list - Shorten fastlane metadata `short_description` to avoid truncation/warnings