CPU / GPU policy
Governor, frequency and scheduling changes can alter how aggressively a device uses available compute. A higher ceiling is not the same thing as a guaranteed higher sustained FPS.
cpufreq · schedutil · DVFS
Magisk · KernelSU · APatch · AxManager
Android
performance, engineered.
A polished technical hub for exploring TerX projects, release notes, compatibility context, and the system layers these tools are designed to interact with.
OPEN SOURCEROOT ECOSYSTEMTECHNICAL DOCUMENTATION
ROOTMagisk · KSU · APatch
PLUGINAxManager on listed builds
OPEN SOURCEPublic GitHub repository
TERX OFFICIAL✦ROOTED ANDROID✦PERFORMANCE✦BATTERY✦CHARGING✦OPEN SOURCE✦TERX OFFICIAL
01 / MODULE INDEX
The current grimoire
Publicly documented TerX projects, with the marketing layer stripped back so the important details are easy to inspect.
02 / TECHNICAL RESEARCH
What these modules actually touch
Performance modules live close to Android’s kernel, compositor, power and thermal layers. The same category can produce very different results on different devices.
SurfaceFlinger & display
Frame pacing depends on the display pipeline, compositor timing, refresh-rate policy and the game’s own renderer. A module can expose or tune these controls without creating unsupported display modes.
VSync · refresh rate · compositor
Thermal control
Thermal policy is a hardware-protection mechanism. Public TerX releases explicitly describe thermal changes; those changes should be treated as device-specific rather than as a universal performance upgrade.
thermal · temperature · throttling
Charging & battery
Charging-current, voltage and temperature controls depend on the PMIC, kernel interfaces and vendor implementation. A module cannot safely invent a charging limit that the hardware does not expose.
PMIC · current · voltage · temperature
Systemless deployment
Root modules generally place scripts and files under the module framework rather than directly replacing the read-only system image. Manager support and the exact module format still matter.
/data/adb/modules · boot scripts
Device variance
MediaTek, Qualcomm and other platforms expose different sysfs nodes, governors, thermal zones and vendor services. Compatibility must therefore be checked per module and device.
SoC · kernel · vendor HAL
Research ruleClaims on this page are separated into documented project features and general Android engineering context. Performance percentages are intentionally not fabricated.
03 / INSTALLATION
Choose the path that matches your setup
Installation instructions are kept deliberately explicit. The module’s own release notes remain the authority for version-specific requirements.
ROOT
Magisk / KernelSU / APatch
- Download the release asset from the official repository or its documented distribution page.
- Open your root manager and install the module ZIP from storage.
- Reboot, then inspect the module’s own logs or WebUI if provided.
- If behavior is unstable, disable the module from the manager or use its documented uninstall path.
PLUGIN
AxManager route
- Use AxManager only for builds that explicitly document plugin support.
- Install the module/plugin from storage through the manager’s Plugin interface.
- Reboot if the release instructions require it.
- Verify the result on your own device instead of assuming another phone’s settings apply.
COMPATIBILITY MATRIX
Support is module-specific
Root managerAxManagerDevice scopeRuby HoshinoDocumentedDocumentedAndroid hardware dependentSilly BillyDocumentedDocumentedAndroid hardware dependentAtmosphere Battery UIRelease says supportedRelease says supportedVendor / kernel dependentPhoenix AMagisk / KSU / APatchNot statedPerformance / thermal dependent
04 / RELEASE INTELLIGENCE
A project that keeps changing
The public GitHub release archive currently exposes multiple generations of the project, from gaming optimizers to battery tooling and larger performance suites.
CURRENT ARCHIVE
Null Universe
Listed at the top of the repository’s public release archive, alongside the project’s newer performance work.
Open release archive ↗BATTERY / v4.5.0
Atmosphere Battery UI
The release page documents AxManager and root-manager support, selectable watt flashing, battery-life features, temperature optimization, SurfaceFlinger and schedutil-related changes.
Source on GitHub ↗GAMING / PRE-RELEASE
Phoenix A
The public pre-release summary describes extreme performance mode, thermal changes, RAM/cache cleanup, maximum FPS/refresh-rate goals and Magisk, KernelSU and APatch support.
Read release notes ↗GAMING / AI
Ton618
The release notes describe performance mode, FPS/refresh-rate changes, background cleanup, touch/GPU/process-priority tweaks and an AI system that monitors FPS and temperature.
Read release notes ↗GAMING
TerX Gaming Optimizer 1.5
Listed in the repository’s release archive as a dedicated gaming optimizer release.
View archive ↗EARLIER PROJECT
TerX Galaxy V1
A pre-release entry in the same public archive, showing the project’s broader history beyond the newer performance and battery releases.
View archive ↗TX
05 / ABOUT THE PROJECT
TerX Official
The public repository identifies the project with Salen, Niño / TerX Official and describes it as supporting rooted Android platforms. The repository is public and carries a GPL-2.0 license listing.
MagiskKernelSUAPatchAndroid moddingOpen source
06 / RESEARCH SOURCES
Read the primary material
Use these links when a module version, compatibility claim or implementation detail matters. Third-party pages are included only where they provide additional module-specific documentation.
PRIMARYTerX Official GitHub repositoryRepository structure, license, topics and project identity.↗
PRIMARYGitHub release archivePublic release names, versions, changelogs and feature summaries.↗
THIRD-PARTYRuby Hoshino module pagev2.0 listing, 7.1 MB size and documented root/AxManager installation path.↗
THIRD-PARTYSilly Billy module pagev1.0 listing, 2.44 MB size and documented installation path.↗
07 / FAQ
Before you flash
Does a higher FPS claim mean my phone will actually run at that FPS?
No. The display refresh rate, game engine, SoC/GPU load, thermal state and game-side frame cap all matter. A module can change system policy without creating frames the hardware or game cannot produce.
Are all TerX modules compatible with every Android phone?
No universal compatibility should be assumed. Vendor kernels expose different controls, and the public release pages themselves describe support on a per-module basis.
Why does the redesigned site avoid performance percentages?
Because the public material reviewed here does not provide a controlled benchmark methodology for figures such as “98% smoothness” or “−32% battery drain.” The new site labels documented features instead of presenting invented measurements.
Where should I get the authoritative release?
Start with the official TerX Official GitHub repository and its Releases page. A third-party module index can be useful for discovery, but the project’s own release archive is the primary reference.