🚀 AXPerformanceEngine — NEW FULL UPDATE

After initial testing and feedback, AXPerformanceEngine has undergone a deep revision focused on one thing: making the functions actually do what they promise.

The goal of this revision wasn't simply to add more options to the interface, but to overhaul the architecture, commands, permissions, result validation, and compatibility across different Android versions and manufacturers.

📱 No ROOT — Using ADB + Shizuku

AXPerformanceEngine uses the Shizuku UserService as an authorized backend to execute operations. The app does not rely on root and does not use a silent fallback for arbitrary command execution.

Furthermore, there is a command allowlist, package validation, and blocking of unauthorized commands or parameters, making execution much more controlled and secure.

🎮 GAME PROFILE — REVISED

The Game Profile was one of the areas that received the most attention.

Functions are now handled according to what Android actually allows to be executed, and the app attempts to validate the result whenever there is a reliable way to do so.

• 🔕 Auto DND: Now uses the official Android API to apply Do Not Disturb mode. Before executing, the app checks if the user has granted Notification Policy Access. The previous DND filter is saved, and when the profile is removed, the app tries to restore the previous state. If the permission is revoked or the system rejects the operation, the function will be presented as an error—and not as "activated" just because the button was pressed.
• ⚡ Game Mode Performance: A new Game Mode Performance has been added. When supported, the app requests: cmd game mode performance <game_package>. The function depends on the Android/OEM and the game's own support, requiring API 31 or higher. When the game does not support Performance mode, the app will inform you that the operation is unsupported instead of presenting a fake success.
• 💡 Brightness Lock: The old Brightness Lock has been removed. Instead of keeping a function that couldn't be guaranteed across all devices, it was dropped from the Game Profile. Global brightness changes via settings put system screen_brightness can be blocked, overwritten, or controlled by the manufacturer and automatic system policies. Therefore, the decision was to eliminate the function rather than keeping an option that only appeared to be functional.
• 🖥️ Keep Screen On: Now alters screen_off_timeout with backup and readback. The app verifies if the value was actually applied and tries to restore it later. Even so, specific manufacturer policies might override this setting.
• 🔄 Refresh Rate: The app tries to use the keys available on the device and verifies which changes were actually accepted. This avoids simply stating that the refresh rate was changed without confirmation.
• 👆 Touch Optimization: Applies only settings that are available on the device and verifies the outcome of accepted changes.
• 🧹 Background Cleanup: Configures the process limit when Android/the device allows this change.
• 🧠 Memory Cleanup: Uses am kill-all as a best-effort operation via Shizuku. The function doesn't promise a specific amount of freed RAM, because the recovered memory depends on the actual state of the system.
• 🚀 Quick Boost on Launch: When enabled, the service applies the profile upon launching the game.
• 🔊 Audio Boost: Now treated as unsupported when there isn't a portable API to apply this type of change per game.
• 🛑 Kill Apps Before Launch: The function does not try to kill arbitrary apps. When the operation cannot be performed safely and compatibly, it is reported as unsupported.
• 🧩 CPU Governor: There is no longer a fake promise of application. CPU Governor depends on kernel/OEM control and is not a universal setting available to standard apps via ADB/Shizuku.
• 🌡️ Thermal Protection: Thermal control remains under Android/OEM authority. The app does not try to impose a kernel thermal policy that it cannot guarantee.
• 🌐 Network Monitoring: Treated as an informational feature, not as a promise of a universal network performance boost.

⚙️ APP STANDBY — RESTRUCTURED

App Standby has also been revised.

Instead of using "global mode" concepts that don't match how Android actually works, the app now works with Standby Buckets on a per-package basis.

You can select an installed game and use:

• active — fewer restrictions while the app is in use
• working_set — mild restrictions
• frequent — heavier restrictions
• rare — strong restrictions
• restricted — even stronger restrictions, when supported

The application uses:
am set-standby-bucket <package> <bucket>

And verifies it afterward with:
am get-standby-bucket <package>

Important: App Standby is not a boost mode. It controls background activity restrictions and can affect synchronization, alarms, and network connectivity.

📡 WI-FI OPTIMIZER

The Wi-Fi Optimizer also received a more accurate implementation.

When available, it uses the Android Wi-Fi service:
cmd wifi set-scan-always-available enabled|disabled

And verifies it through:
cmd wifi get-scan-always-available

If the service doesn't offer the command, there is a fallback via wifi_scan_always_enabled, but the app only shows success when the SettingsProvider confirms the value.

The function specifically controls the availability of Wi-Fi scanning when Wi-Fi is turned off.

It does NOT promise to:

• ❌ Increase internet speed
• ❌ Magically reduce ping
• ❌ Increase radio power
• ❌ Improve the Wi-Fi channel
• ❌ Increase FPS

BLE Scan Always Available remains unsupported on generic Android without system privileges, so no fake changes are made.

🔔 NOTIFICATION OPTIMIZER

This part has also been fixed.

Android does not provide a standard app with a universal API to mute notification channels of other apps. Because of this, the old switch has been removed.

Now, the app directs the user to the official Android settings related to notifications and Notification Policy Access. The final decision remains with the user and the Android system itself.

⚙️ SYSTEM OPTIMIZER

The System Optimizer now only works with operations that Android actually exposes through Settings or the shell, and that can be verified.

Among the revised functions:

• 🔹 Private DNS: Uses a valid hostname and performs a readback of the settings.
• 🔹 Background Process Limit: Applies the setting and verifies the value afterward.
• 🔹 GPU Rendering: Uses setprop only when the change is accepted and verifies it through getprop.
• 🔹 Battery Saver: Checks the actual state through PowerManager.
• 🔹 Data Saver: Uses cmd netpolicy set/get restrict-background.
• 🔹 Adaptive Battery: Uses the setting only when available and performs a readback.
• 🔹 App Standby: Works per-package and confirms the applied bucket.
• 🔹 Wi-Fi Scan: Uses WifiService or a fallback via SettingsProvider, always with validation.
• 🔹 Notifications: Opens the official Android settings.
• 🔹 Memory Boost: Executes am kill-all as a best-effort operation, without promising a specific amount of freed RAM.

🛡️ MORE RELIABLE QUICK PRESETS

Quick Presets have also been revised.

The visual state should now only update after the corresponding operations return success. If an operation fails, the previous selection is preserved, and the user receives a message detailing the error or stating that a specific feature is unsupported.

This means the interface should not simply show:
✅ "Activated"
when the command wasn't actually executed.

🔐 SECURITY

The app uses the Shizuku UserService to send commands to the authorized backend.

The remote executor has an allowlist and blocks:

• Unknown commands
• Dangerous characters
• Unauthorized Settings keys
• Invalid packages
• Arbitrary shell operations

Per-package operations only accept names in a valid Android package name format. Furthermore, protected packages cannot be killed through cleanup operations.

📱 COMPATIBILITY

The goal is not simply to say: "Android 12 = works."

Compatibility is analyzed by the actual observed capability of the device. Two devices using the same Android version can behave differently due to the manufacturer, ROM, security services, and power-saving policies.

Different environments were considered, including:

• AOSP / Pixel
• Samsung / One UI
• Xiaomi / HyperOS / MIUI
• ASUS ROG / ZenUI
• OnePlus / OPlus
• Other manufacturers

When an operation is not exposed by the device, the app will inform you that it is unsupported.

📝 A Note from the Developer (VOID)

Sorry for the long text, but it is necessary that you read it. Well, this update took a long time, and I hope you like it! Please let me know if there are any bugs, errors, or any other issues.

It took a lot of work to do all of this. I've been working from midnight until now, 5:03 AM. Basically, I haven't slept. I did my absolute best to get everything working as smoothly as possible. 🙏❤️

🚀 AX Performance Engine — New Update

AX Performance Engine has received an update bringing several improvements to Game Turbo, Game Profile, Display, and Shizuku. 🔥

🎮 Game Profile

• Removed the Profile Type preset system.
• Configurations are now fully manual and saved individually on a per-game basis.

📱 Game Identification

• Fixed game names, now using the official name provided by Android.
• The package name remains available for technical identification.

🖼️ Game Turbo

• Each game now displays its actual icon, using the generic icon only as a fallback.

⚡ Display

• Improved refresh rate (Hz) detection.
• The system now identifies the highest rate supported by the device, preventing it from showing only the active 60 Hz rate when the device supports 90/120/144 Hz.

🔧 Shizuku

• More detailed diagnostics.
• Improved retry mechanism.
• Better connection and reconnection handling for UserService.
• Clearer error messages.

⚙️ Profiles

• The application of settings is now more deterministic, preventing old values from another game from being mixed into the current profile.

🔥 More precision, organization, and stability for the AX Performance Engine.