If you want to force your PI4 to run at 1500Mhz in constant ways, you need to change the ‘Scaling governor’ from ‘ondemand’ to ‘Performance’ !
This is explained a few posts above :
sudo apt -y install cpufrequtils
sudo sh -c "echo 'GOVERNOR=\"performance\"' > /etc/default/cpufrequtils"
sudo systemctl restart cpufrequtils
For my part I did it on my PI4 because it changed every second between the values of 600Mhz and 1500Mhz, so let him turn permanently at 1500Mhz !
You can probably reduce power usage and temperature setting it at 1200 MHz or something.
Should still be plenty fast.
Or i suppose instead of forcing the performance governor, you could change the minimum frequency:
arm_freq_min 900
That might be enough to prevent it from changing to maximum clock all the time, but would still go to maximum clock i you need it.
Thanks for the info. I learn something here every day.
I can’t install it. Going through the steps in the guide…
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 2C0D3C0F
Executing: /tmp/apt-key-gpghome.AMDrj7MC4X/gpg.1.sh --recv-keys --keyserver keyserver.ubuntu.com 2C0D3C0F
gpg: keyserver receive failed: Connection timed out
Has anyone with an N2 got an answer for this on yet???
Maybe try again? Server hiccup perhaps.
I’ve been trying for a few days but it’s still the same. Sadly, there’s no way I can see to contact the author.
Try this:
sudo sed -i -e '0,/nameserver/{s/nameserver.*/nameserver 8.8.8.8/}' /etc/resolv.conf
Then check if the gpg stuff still fails.
You could also try a different keyserver:
sudo apt-key adv --recv-keys --keyserver pgp.mit.edu 2C0D3C0F
Thanks guys.
I’ve been trying all afternoon and have got a bit further with my investigations.
It’s something to do with the Pi image I’m using which is stopping it. I’ve just tried on another Pi and it’s installing perfectly well. I’m using a Pi-Star image which is based on Buster but there’s clearly something within the image that’s blocking it. It’s not the DNS server (I’m using my own DNS and I could see nothing is being blocked) and other keyservers are giving the same error.
I’ll probably put this on the Pi4 when it goes up but I wanted to monitor this other Pi as well.
Well it’s not about anything being blocked.
The GPG software for a timeframe used a stupid way do to DNS queries which some DNS servers don’t answer due to configuration.
If you really wanted to install this, you could also put the IP address / domain name for the keyserver in the /etc/hosts file.
Well it installed on another Pi using my own DNS so that’s not stopping it and one of the things I had tried this afternoon was doing exactly what you’ve suggested - I added
162.213.33.8 keyserver.ubuntu.com
to the hosts file.
Still trying other methods.
Is it the same software version of the gpg thing that tries to talk to the key server is the question.
Nope, the working one is running 2.1.18 and the one which won’t work is on 2.2.12
Time to upgrade, yay!
Downgrade, surely? The one which works is on an older version!
Is one of the systems Buster? 
Pretty sure the issue is fixed on buster.
But yeah i misread the version numbers.
The one that’s working is Stretch, the one that’s not working is Buster.
Can’t you just:
sudo apt-key adv --recv-keys --keyserver 162.213.33.9 2C0D3C0F
Or does that give an error as well?
Same error 