Configuration

Configuration

UXTU4Linux stores its settings in Assets/config.ini, created automatically on first run.

Full path on a standard install:

/opt/uxtu4linux/src/Assets/config.ini

---

Example

[User]
mode = Balance
customargs =

[Settings]
time = 3
softwareupdate = 1
reapply = 0
applyonstart = 1
debug = 0

[Automations]
enabled = 0
onac =
onbattery =

[Info]
cpu = AMD Ryzen 5 7535HS with Radeon Graphics
signature = Family 25, Model 68, Stepping 1
architecture = Zen 3 - Zen 4
family = Rembrandt
type = Amd_Apu

---

[User]

Key	Type	Description
mode	string	Preset to apply. Use a built-in name, a custom preset name (without _custom_preset), or Custom to use customargs directly
customargs	string	Raw ryzenadj argument string, only used when mode = Custom

Built-in preset names (availability depends on your CPU family):

Preset	Description
Eco	Low power, quiet, cool, battery-friendly
Balance	Moderate power, good for daily use
Performance	Higher power limits for sustained workloads
Extreme	Maximum power limits, highest performance

Custom presets saved in the editor are stored in custom_presets.json and can be selected by name in the app. See Custom Presets.

---

[Settings]

Key	Default	Values	Description
time	3	integer (seconds)	How often the daemon re-applies the preset when reapply is on
softwareupdate	1	0 / 1	Check GitHub for updates on every launch
reapply	0	0 / 1	Keep re-applying the preset on a timer
applyonstart	1	0 / 1	Daemon applies the saved preset when the systemd service starts
debug	0	0 / 1	Show build info in the header and verbose ryzenadj output in daemon logs

How these interact:

• applyonstart: controls whether the daemon applies a preset when it first starts (e.g. after boot). The TUI always applies the selected preset when you open it.
• reapply: runs a background loop that re-applies the preset every time seconds. Useful for keeping limits active on systems that reset them.
• When reapply = 1 and [Automations] enabled = 1, the loop also handles switching between AC and battery presets automatically.

---

[Automations]

Key	Default	Values	Description
enabled	0	0 / 1	Whether the override is active
onac	(empty)	preset name	Preset to apply when plugged in to AC power. Leave empty to use [User] mode
onbattery	(empty)	preset name	Preset to apply when on battery. Leave empty to use [User] mode

Notes:

• Preset names here follow the same rules as [User] mode: built-in names or bare custom preset names (without _custom_preset).
• If both onac and onbattery are empty, enabled is automatically set to 0.
• The override works even with reapply = 0: a lightweight background thread watches for power state changes and applies the correct preset on each transition.
• Disabling the override from the Automations menu restores normal [User] mode behaviour.

---

[Info]

Populated automatically by dmidecode during first-run hardware detection. Only edit manually if detection produced wrong results.

Key	Description
cpu	Full CPU name string from dmidecode
signature	CPUID signature, Family, Model, Stepping
architecture	Zen generation string, e.g. Zen 3 - Zen 4
family	Codename, e.g. Rembrandt, PhoenixPoint, StrixPoint
type	Amd_Apu, Amd_Desktop_Cpu, or Intel

If your CPU shows an unrecognised codename, set cpu to a known model string that matches your hardware family and re-run hardware detection from Settings.

---

Resetting

From inside the app: Settings -> Reset all

Manually:

rm /opt/uxtu4linux/src/Assets/config.ini
uxtu4linux