MaxManager v1.0

What this is: the first release of MaxManager — a control panel for rooted Android phones.
Works on: Android 10 or newer · Magisk, KernelSU or KernelSU Next
Download: MaxManager-v1.0-module.zip — flash it in your root manager. Its checksums are the second file.
Since this is 1.0, everything below is new. There is no earlier version to compare against.

---

In one minute

MaxManager helps you make a rooted phone smoother, cooler, or longer-lasting — and it only offers
you settings your phone can actually do.

That sounds obvious, but it is the whole point. Most tuning apps give you hundreds of switches, and
half of them do nothing on your phone. MaxManager looks at your phone first, so:

• A setting your phone does not support simply is not shown. No dead switches.
• Every change is checked. If the phone did not accept it, you are told — not shown a green tick.
• When the app does not know a number, it says so. It never shows 0 to look tidy.
• Nothing runs until you turn it on. No hidden automation, and nothing is sent anywhere — ever.

---

What is inside 1.0 — the whole list

#	Area	In one line
1	Profiles	Five one-tap behaviours you can apply, tune, save and share — and switch from Quick Settings
2	Nine control areas	CPU, GPU, memory, display, responsiveness, thermal, power, storage & compiler, network
3	One app at a time	Give one app its own profile, refresh rate, resolution, thermal ceiling and governors
4	Charging & battery health	Charge ceiling, current limits, bypass charging, doze, battery health
5	The on-screen panel	FPS, frame time, CPU, RAM, power, battery heat and renderer over any game — four looks
6	What is running now	Process list with CPU and RAM per app, force-stop, SIGKILL, a floating panel
7	Logs & diagnostics	Live logs with search, route health for every control, a device blueprint, a report you choose to send
8	The tools shelf	Property editor, activity launcher, root file manager, permissions, backups, freezing, plugins, module health
9	Look and language	Themes, a colour scheme, 84 languages, real right-to-left support
10	Max Atlas	Finds what your phone supports — and proves what it does not have
11	Max AI	Off by default: changes one thing, measures whether it helped, remembers
12	The safeties	One write path, read-back verification, undo, and a list it never touches

---

Where to start

You do not need all 53 screens. These five cover what most people want:

If you are…	Open this	And you get
Just want a better phone	Profiles (home screen or Quick Settings)	Cooler and calmer, in one tap
Playing games	Apps → your game → Gaming	Its own settings; nothing else on the phone changes
Curious about the numbers	FPS panel and Home	Live readings over your game and inside the app
Charging overnight	Control → Power → charging	Less battery wear over time
Into the details	Control (the nine areas) and Control → Tools	Everything else

Everything else is there when you want it — nothing is missing, it is just not shouting at you.

---

Profiles — one tap, and what a profile really is

A profile is a named set of behaviour you can apply, tune, save and share:

• Power — cool and frugal.
• Balanced — the everyday baseline.
• Gaming — the GPU held in its upper range for steadier frame pacing.
• Performance — full capability, held as far as the hardware allows.
• Custom — yours.

Two things make profiles more than bookmarks:

• They are shareable, and the source travels with the number. On export, each value carries where it
  came from — a shipped default, a value you changed yourself, or a measurement claimed by whoever
  exported the file. On import the app says exactly what it accepted and what it refused, and a profile
  made on another chipset says so out loud: a value measured over there is not a measurement over here.
• They are reachable from Quick Settings. One tile switches the profile without opening the app, and
  a second tile drives bypass charging.

---

The nine control areas — everything you can change

Nine areas, each in its own hub. The line in italics is the app’s own one-line description of that area.

CPU — cores, governor, vendor boost and kernel preferences

• Turn individual cores on or off.
• Pin scheduling groups to clusters, and set a floor and a ceiling per cluster.
• Choose governors.
• Edit kernel preferences, and the vendor boost controls.

GPU — GPU frequencies and graphics-specific vendor parameters

• Frequency presets and manual bounds.
• The GPU governor.
• Shader-core power policy.
• The vendor boost pipeline.
• A documented thermal-throttle bypass.

Memory — compression, VM behaviour and swappiness

• Size ZRAM or turn it off.
• Pick the compression engine.
• Tune swappiness and reclaim.

The engine reads memory stall pressure, not fill percentage: a nearly-full-but-idle phone and a phone
that is actually stalling need opposite responses, and the app tells them apart.

Display — refresh rate, colour and canvas scale

• Refresh rate.
• Colour channels, saturation, gamut and HDR response.
• Brightness curves and night light.
• Animation scales and screen timeout.
• Render resolution (its own screen).

Responsiveness — touch, frame pacing and scheduling latency

• Touch sampling rate and smoothing.
• Double-tap to wake.
• FPS GO / GED parameters.
• Frame-aware scheduling.

Thermal — temperatures, throttling and thermal parameters

• Live zone temperatures.
• Thermal policy, and what your device is throttling right now.

The safety limits themselves are never written — that is the one rule this project does not bend.

Power — charging, bypass, sleep and battery health

• Charge current limits.
• A charge ceiling to slow battery wear.
• Bypass charging, plus a separate check screen that confirms bypass is really working.
• Aggressive doze and the standby whitelist.
• Battery health.

Storage & compiler — compilation mode and storage health

• Re-run ART compilation with a filter you choose.
• Reset compiled state.
• Storage health.

Network — traffic scheduling and link state

• TCP congestion algorithm.
• Fast-open, SACK and ECN.
• SYN cookies and socket reuse.
• I/O scheduler tunables and link state.

Anything your device does not expose in one of these areas is simply not listed. No dead switches.

---

One app at a time — per-app control

Open Apps, pick an app, and give it its own treatment without touching the rest of the system:

• performance profile (Power / Balanced / Gaming / Performance / Custom)
• refresh rate
• render resolution
• thermal ceiling
• CPU governor and GPU governor — only the ones your kernel reports, and only governors supported
  by all CPU policies
• foreground priority lock
• I/O priority boost
• a per-app reset that puts just that app back

Every app shows its effective state in plain words: per-app control is off · using the global
profile · app override active. While a game with its own profile is in front, Max AI switches to
monitoring only and stops changing things.

There is also a screen for debloat and freeze, and “why didn’t it work?” for a per-app setting:
what it wanted, what the hardware is holding, and where to look next.

---

The panel over your game

A floating readout you can drag anywhere over any game. It does not cover your whole screen, and it does
not steal frames.

What it can show — you choose; only the fields you want appear:

• Frames per second, from the chosen source, with a fallback reading method when the first one
  cannot be read.
• Frame time in milliseconds — the number that tells you whether a game feels smooth. 60 and 55
  frames per second look close in a counter and are far apart in the hand (16.7 ms against 18.2 ms), and
  that difference is exactly what the eye catches when the picture stutters.
• CPU load and memory use.
• Power draw and battery heat.
• The renderer of the app in front — a real Vulkan / OpenGL label, not a guess.
• A live graph of the readings over the last few seconds.

Four looks, for four different kinds of player:

Look	What it is like
Strip	A thin single-line bar along the top or bottom edge
Pane	A small multi-line box, the classic “overlay in the corner”
Ring	A circular gauge with the headline number in the middle
Badge	The desktop-style look: one big number, its unit on the text baseline, frame time underneath

And three more things:

• A recorder that saves a real CSV session, so you can look at it afterwards in a spreadsheet.
• Line or stacked layout — stacked reads naturally in Arabic and other right-to-left languages — plus a
  preview inside the app that behaves exactly like the real panel, so you set it up before you are in a
  game.
• Two buttons on the panel itself. Hide folds it into a small touch capsule; the readings keep
  running and one tap brings it back — a capsule, not a full disappear, so the way back is something you
  know rather than something you hunt for in the notification shade. The folded state is a moment, not a
  saved set...