hyperswitch VS System76 Power Management

Similarly there is https://hyperswitch.io/ open source written in Rust.

Lago is written in Ruby.

I found few others opens source billing systems written in Java.

Anyone knows anything written in nodeJS?

Read and understand the general guidelines on contributing to Hyperswitch

🚨 BTW we are hiring for several roles, apply here.

Ultimately, we believe that payments should be a basic utility like water or air. This is important because the payment ecosystem is full of closed systems and walled gardens. It is also extremely diverse (as it should be). In order to enable this diversity, payments need a trusted unifier like Linux. The road to commoditize payments will not be easy and we are looking for engineers that can make it happen. If this vision resonates with you, consider applying for Hyperswitch and we’d love to work with you! 🌟🔧🌈

See: https://github.com/pop-os/system76-power

Also refer to https://github.com/pop-os/system76-power/issues/153 for setting environment variables and making simple scripts with it.

One example would be, I had problems with running native version of Substance Designer. And it had something to do with always using GPU or setting environment variables(https://github.com/pop-os/system76-power/issues/153). But I wouldn't know what to look for if a random guy on a forum didn't tell me to use it with NVIDIA Graphics.

[Update 2022-02-21] It appears that there are two packages, System76-io-dkms and System76-power. From what I gather only the first is necessary. I'm not sure how to install third-party DKMS modules that are not in the official repos. The official Void documentation on this topic is sparse, is there somewhere I can look this up?

Initially it only worked with Intel CPUs but it seems it supports AMD APUs now according to this Github issue https://github.com/pop-os/system76-power/issues/73

system76-power

The performance modes are going to affect how much power the system is using (and thus how much heat it's generating), not the fan curves directly. Those profiles are defined in the system76-power application, source code here: https://github.com/pop-os/system76-power/blob/master/src/daemon/profiles.rs

The script uses udev rules that are run at specific kernel events. It creates one rule for when the Laptop switches to battery power and another for when the Laptop switches to wall power. Both rules run system76-power while providing one of the available power profiles as an argument. I went with battery and balanced respectively.

Try the fix listed here: https://github.com/pop-os/system76-power/issues/358