[BUG] CPU Clock Mismatch between real clock frequency and apparent on Raspberry Pi

Describe the bug

the clock-speed that is shown in the upper right corner is the "apparent" or "should-be" (apparently from /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq) - value but in fact the pi I am using is throttling due to insufficient power and that is not represented correctly

you can see it in the attached screenshot that the frequency is dipping, but btop shows 2Ghz constantly

you can check the real value via vcgenmod vcgencmd measure_clock arm

https://www.raspberrypi.com/documentation/computers/os.html#vcgencmd

To Reproduce

compare cpu freq in btop to vcgencmd measure_clock arm

Expected behavior

the dips in frequency should be represented accordingly

Screenshots

Info (please complete the following information):

btop++ version: 1.2.7
Binary: self compiled
(If compiled) Compiler and version:
Architecture: aarch64
Platform: Linux - Debian GNU/Linux 11 (bullseye)
(Linux) Kernel: 5.15.32-v8+
Terminal used: bash
Font used: (does not matter IMO)

Possible solution/Feature Request

change the get_cpuHz() function to get the current frequency via the vcgencmd measure_clock arm command

you could even add a warning if it is throtteling due to temperature or undervoltage

if i don't forget this issue, i could write a PR - concerning this issue

aristocratos / btop

[BUG] CPU Clock Mismatch between real clock frequency and apparent on Raspberry Pi #379