ShizuStore

WaffleBoost

WafflingNinja

0.1 · GitHub

Download APK
Games Android 11+ 5 days ago MIT
615 ShizuStore
1.1k GitHub
12 Stars
42 MB Size

More about this app

Free, open-source ADB game booster: 27 tweaks over wireless debugging, reverted when you stop playing. Optional Shizuku fallback (not yet tested on device).

WaffleBoost

Free, open-source game booster for Android. No root, no PC, no ads, no account.

WaffleBoost connects to your phone's own ADB daemon over wireless debugging and runs performance tweaks while you play. Pick a game, tap boost, the game launches. When you leave the game or close the app, every setting goes back to what it was.

Built mainly for Roblox, works with any installed game.

Download the APK (Android 11 or newer)

What it does

27 tweaks across six tabs. A few of them:

  • Render scale 90 / 80 / 70 % and an FPS target per game
  • Force the highest refresh rate your screen has (or cap at 60 Hz to save battery)
  • Pre-compile the game so it starts faster
  • Vulkan renderer, ANGLE, 4x MSAA
  • Turn off blur, shorten animations
  • Do not disturb, pause backups and background compiling during the match
  • Faster long-press and double-tap, rotation lock, no vibration

Four profiles: Extreme, Balanced, Battery, and Custom where you pick the cards yourself.

Auto-detect starts the boost on its own when a game from your list opens.

The full list, with the exact command behind every card, is in docs/SPEC.md.

Why it is free

Every command WaffleBoost runs is a stock Android shell command that anyone can type into adb shell. There is nothing secret in here, so there is nothing to sell. Read FunctionCatalog.kt and you have seen all of it.

What it does not promise

No FPS number. I have not measured FPS gains, and anyone who quotes you one for every phone is guessing.

What has been checked: each tweak was applied on a real phone, read back, reverted, and read back again. 24 of the 27 passed. Two did not apply (Roblox refuses the system "performance" game mode, and one alarm block did not stick) and one could not be confirmed either way. Those cards stay in the app and are labeled failed or untested, so you know what you are turning on.

So far that is one phone: a Xiaomi on Android 16 with a MediaTek chip. Other phones may behave differently. Results are in docs/DEVICE_TESTS.md, and reports from other devices are welcome in the issues.

The Shizuku connection path is written but has not been tested yet.

Install

  1. Download app-debug.apk from Releases and install it. Android will ask you to allow installs from your browser or file manager.
  2. Connect to Wi-Fi.
  3. Open WaffleBoost and tap Start pairing. Developer options open.
  4. Turn on Wireless debugging, open it, tap Pair device with pairing code.
  5. Pull down the notifications and type the 6-digit code into the WaffleBoost notification.

Developer options hidden? Settings → About phone → tap the build number seven times.

Pairing is needed once. After that, turn on wireless debugging and the app connects by itself.

Safety

  • The command list is fixed in the code. The app never runs text you type as a shell command.
  • Before each change the original value is saved to disk. Stop boost puts it back. If the app crashes mid-boost, the restore runs on the next launch.
  • Risky cards (system resolution, kill all background apps, GPS off) are off by default, carry a warning, and are in no preset.
  • No analytics, no ads, no network calls. The INTERNET permission is there only because the socket to the phone's own ADB daemon needs it.

Build

Android Studio ships the JDK and Gradle does the rest.

set JAVA_HOME="C:\Program Files\Android\Android Studio\jbr"
gradlew.bat assembleDebug

APK lands in app/build/outputs/apk/debug/app-debug.apk. Unit tests: gradlew.bat testDebugUnitTest.

Code layout is described in docs/ARCHITECTURE.md.

Languages

English and Czech. The app follows the phone's language.

License

MIT. See LICENSE.

Close

How Shizuku is used

Can boost games with graphics, display and system tuning via `shell commands` through Shizuku.

This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.

How this app uses Shizuku

Shizuku provides a fallback shell path that runs the same game booster tweaks as wireless debugging, with all changes reverted when the boost stops.

  • Tune game graphics: lower render resolution and cap frame rate for the selected game with the cmd game shell commands.
  • Speed up loading: precompile the game code with cmd package compile, free memory with am kill-all, and pause background compile and backup work with pm bg-dexopt-job and bmgr.
  • Control display refresh: lock the screen to its highest rate or to 60 Hz with settings put system settings read from dumpsys display.
  • Lower system resolution: shrink the whole display to 90, 80 or 70 percent and restore it afterwards with the wm size and wm density shell commands.
  • Refine visuals and UI: shorten animations, turn off window blur, switch system rendering with setprop and getprop, force 4x anti aliasing and assign the ANGLE driver with settings put.
  • Block interruptions: enable Do Not Disturb with cmd notification, toggle battery saver and location with settings put, limit game background timers and wake locks with cmd appops, and request steady performance with cmd power.
  • Improve touch response: shorten long press and double tap delays, lock rotation, turn off touch vibration and set pointer speed to maximum with settings put.
  • Auto boost games: detect the focused game with dumpsys window and automatically apply the chosen profile while playing, then restore original settings.

Android APIs or commands used

  • settings put
  • settings get
  • settings delete
  • cmd game mode
  • cmd game set
  • cmd game reset
  • cmd game list-modes
  • cmd game list-configs
  • cmd package compile
  • am kill-all
  • dumpsys display
  • wm size
  • wm density
  • setprop debug.hwui.renderer
  • getprop debug.hwui.renderer
  • setprop debug.egl.force_msaa
  • getprop debug.egl.force_msaa
  • cmd notification set_dnd
  • cmd power set-fixed-performance-mode-enabled
  • bmgr enable
  • bmgr enabled
  • cmd appops set
  • cmd appops get
  • pm bg-dexopt-job
  • dumpsys window

Notable details

The same tweaks also work over wireless debugging without Shizuku, with Shizuku used as fallback. All shell commands are fixed in the app, no free typed commands reach the privileged shell.

Close

Changelog

What's new for version 0.1

First release. Android 11 or newer.

Install the APK, then follow the pairing steps in the README.

Tested on one phone so far (Xiaomi, Android 16, MediaTek). 24 of 27 tweaks verified there, details in docs/DEVICE_TESTS.md. Reports from other phones are welcome in the issues.

This is a debug-signed build.

Close

Permissions

9 permissions requested

  • android.permission.INTERNET
  • android.permission.FOREGROUND_SERVICE
  • android.permission.FOREGROUND_SERVICE_SPECIAL_USE
  • android.permission.POST_NOTIFICATIONS
  • com.waffleboost.app.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
  • android.permission.WRITE_EXTERNAL_STORAGE
  • android.permission.READ_PHONE_STATE
  • android.permission.READ_EXTERNAL_STORAGE
  • moe.shizuku.manager.permission.API_V23
Close