Akihiro HyperTune Universal

Give your device another life.

A non-root performance suite for Android. One module, any manufacturer, any chipset, any Android version from 8.0 onward. Nothing is hardcoded to a specific phone — the module reads your hardware at boot and tunes itself to it.

Built and maintained by Akihiro N. Masbate.

What it actually is

Most "booster" modules are a text file of properties copied from a decade-old forum thread. A large share of those properties have no reader anywhere in the Android source and do nothing at all. This module takes the opposite approach: every tweak in it was checked against AOSP, and the verified no-ops were deliberately left out and documented as such.

What remains is 14 modules covering rendering, memory, the runtime, display, game frame rate, input, audio, media I/O, network, power, ART compilation, debloat, and vendor-specific paths.

It is tuned for frame rate, not battery life. Governors get pinned high, frame rate ceilings get removed, battery savers get switched off. Expect the device to run warmer and to lose some screen-on time. That trade is the entire point.

Hardware adaptation

Nothing asks you which phone you have. At boot the module reads:

Detected	Used for
Total RAM	Five tiers drive every cache size, heap limit, process budget and buffer depth
SoC vendor	Qualcomm, MediaTek, Exynos, Unisoc, Tensor and Kirin each get their own performance daemon properties
GPU family	Adreno, Mali, PowerVR and Xclipse get their own rendering hints
Android API	Each module gates itself; unsupported keys skip silently instead of erroring
OEM skin	One UI, MIUI/HyperOS, ColorOS, FunTouch/OriginOS, HiOS/XOS, MyUX, EMUI and stock each get their own settings and debloat list
Display count	Every physical display is scaled independently from its own native resolution

A device the module has never seen falls back to the generic AOSP path. It never guesses.

Multi-display support

Resolution scaling is the largest genuine frame rate lever available without root — fewer pixels per frame is linearly less GPU work. Most modules implement it as a single wm size call, which only ever touches display 0. On a foldable that scales one panel and leaves the other at native.

This module enumerates every physical display and scales each from its own resolution, working on the short edge so portrait and landscape panels are treated identically. Dimensions are rounded to even numbers, because odd sizes break hardware composition on many encoders. A floor guard refuses to go below 540px on the short edge and raises the scale for that panel instead of applying a size that clips OEM system UI. A 480×960 entry phone is correctly left at native rather than being made unusable.

Expect the UI to look larger and softer. Density is intentionally left alone. This is the visible cost of the speed-up, not a bug.

Frame rate ceilings

Android 15 introduced a system-wide default that pins games to 60 Hz regardless of what the panel can do. On API 35+ the module disables it.

Honest scope: this only unlocks games that don't set their own cap internally, and an OEM Game Mode FPS intervention still takes priority. It is not a universal unlock, but where it applies it is the single largest frame rate ceiling added to Android in years.

Also removed: content-detection refresh downclocking, system-imposed game resolution downscaling, and any GPU validation layer left enabled — each of the latter wraps every GL and Vulkan call and is ruinous for frame time.

Safety

It cannot bootloop your device. Nothing touches a partition, a mount point, or a system file. Every change is a settings, device_config or setprop write through the normal shell interfaces.

Debloat is reversible and guarded. Packages are unlinked from user 0 with pm uninstall -k --user 0 — the APK stays in /system. A 35-entry protected list covering SystemUI, Settings, telephony, providers, GMS, WebView, the permission controller and the keyboard is refused unconditionally. Package matching is anchored to the end of the line, so com.miui.analytics cannot accidentally catch com.miui.analytics.extra. Only your manufacturer's list runs; an unrecognised brand gets the generic AOSP list only.

Restore any package:

pm install-existing com.example.package

The full removed list is written to /sdcard/HyperTune_RemovedPackages.txt.

Revert is exact, not approximate. Before the first write, every value the module is about to change is read and recorded. Uninstalling restores those originals. Settings that had no prior value are deleted so the framework falls back to its own default, rather than being left at a number the module invented.

What is deliberately not here

Being specific about this matters more than a longer feature list.

Thermal throttling is not disabled. It is not reachable from a non-root shell — the thermal daemon runs below it and the sysfs nodes are root-owned. Any non-root module advertising this is either writing to nodes that reject it, or toggling an OEM software flag and calling it thermal control. It is also a battery and silicon safety limit. What this module does instead is remove every artificial brake so the chip can sit at its real sustained ceiling, with hardware protection intact underneath.

ANGLE is not forced. angle_gl_driver_all_angle only takes effect on a rooted device — that limitation is stated in Google's own ANGLE documentation. It is a translation layer, not an optimisation.

No renderer is forced onto games. A game creates its own GL or Vulkan context and chooses its own API. No system property reaches inside it. Modules claiming to force OpenGL ES 1.0 or Vulkan on games are not doing that.

SkiaVK is not used for the UI. SkiaGL is the mature path that behaves identically across every GPU vendor. The Vulkan-backed UI renderer regularly regresses on mid-tier Mali, PowerVR and older Adreno parts, which makes it the wrong default for a module that has to work everywhere.

Verified no-op properties are excluded. debug.performance.tuning, video.accelerate.hw, ro.max.fling_velocity, ro.min.fling_velocity, windowsmgr.max_events_per_sec, hw3d.force, ro.fb.mode, persist.sys.ui.hw, dalvik.vm.verify-bytecode, ro.HOME_APP_ADJ and others have no reader in AOSP. Including them would make the module look larger without making a device faster.

ZRAM is only disabled above 12 GB. Turning it off on a low-RAM device removes compressed swap and the system starts OOM-killing instead. This is a common way these modules backfire.

Dex verification stays on. Disabling it would let corrupt dex crash the runtime, and the property usually cited for it was removed from AOSP years ago.

Installation

1. Remove any other tweak, GFX, thermal or optimiser module first. Two modules writing the same key is the most common cause of unexplained behaviour.
2. Flash in AxManager or Magisk.
3. Reboot.
4. The first 5–10 minutes will feel slow. ART is recompiling your apps in the background. Leave it alone, ideally on a charger. It settles.

Requirements: Android 8.0+ (API 26), arm / arm64 / x86 / x86_64.

Configuration

Two values at the top of service.sh:

HT_RES_PCT=60      # 100=off · 85=subtle · 75=balanced · 60=aggressive
HT_ANIM=0.0        # 0.0=instant · 0.5=fast · 1.0=stock

If the interface is too soft for you, raise HT_RES_PCT and press Action in AxManager. No reboot needed.

Files

module.prop          metadata
system.prop          static, device-independent properties
customize.sh         install banner, compatibility gate, warnings
post-fs-data.sh      early boot properties, RAM-tiered
service.sh           boot orchestrator
action.sh            re-apply on demand
uninstall.sh         backup-driven revert
lib/core.sh          detection, logging, backup-aware setters, guards
modules/             14 independent, failure-isolated tweak modules
webroot/             status interface

Each module runs in its own subshell. One failing cannot take down the rest, and a boot cannot be interrupted by any of them.

Log: /sdcard/HyperTune_Log.txt

Credits

Akihiro N. Masbate. Built on AOSP documentation and source verification rather than inherited forum lists.