Device Watch Files

What's changed

• Kernel page on rooted phones. The Device tab starts with a KERNEL band; Open leads to a page that shows what this phone's kernel itself reports: each group of processor cores with its speed now, its limit and range and the phone's own limit where it differs, heat throttling in plain words, the graphics processor's speeds, compressed memory (zRAM), the kernel version, SELinux and the storage queue, and every named temperature sensor. Nothing is assumed from the phone's model.
• Processor profiles (root). Power saving holds the faster cores to about 60 % of their top speed, Balanced to about 80 %; the slowest group stays free. Custom sets each group yourself, from half its top speed up. Stock (full speed) returns the phone's own limits. Only scaling_max_freq is ever written, only to speeds the kernel lists and never above what the phone allows; heat protection keeps working as before, and the page says when it holds a group lower.
• The limit stays. Android's power management can write the same limit itself; the monitor sets yours again within five seconds while the screen is on and counts how often. When Android holds a group lower than your profile, the app leaves that alone. A limit the kernel refuses is undone, not left behind.
• Safe ways back. The phone's own limits are saved before anything is written and come back on Stock, when root is switched off (or Shizuku takes its place) and at every restart; switch on Apply after restart too to have the profile set again after a restart. If root stops answering while a limit is held, Settings says the limits stay until the next restart.

Root is needed for the Kernel page and the profiles; Shizuku cannot write kernel values. Everything else in the app is unchanged. More in the FAQ.

Installing

Updates cleanly over v1.4.x and later. If you are coming from v1.3.1 or older (package com.example.modernwidget), uninstall the old app first — it is a different package and will not update.

APK SHA-256: 8c8c3bb5201be5aa61e760f1e665119bc695cfec1e5699b0c4e3c5e96d910e88 Signing cert SHA-256: a787d3be1fa4d58751e246dba9b8f1ded5b6a00ab2675367bf49420928e1a51a