@2disbetter I added the gpu frequency module, please update to play with it.
I think this will save some measurable energy, I’ll do some tests this week and try to get numbers.
2 Likes
ok, I updated, and I have it in psuspend now. Thanks! I will let you know if I feel the back of the display cool down some.
I let a full battery discharge, and unfortunately it took the same time to discharge than without this latest addition.
Minute explained me on IRC that this frequency was not the GPU, but another component of the computer.
We at least tried.
2 Likes
Psuspend has started causing the system to stop responding when wanting to resume. The system will get into a state where they keyboard does not respond, and you can’t access the LPC.
I have tried with the previous OG Sysctrl firmware and the most current. Same problem on both firmwares.
Has anyone else who has been using this regularly had any similar issues?
This is a pretty integral piece of software to me. I use it like suspend. When I am not using my Pocket, psuspend is active. Previously I went days and even weeks with psuspend being used when I finished using it. It worked flawlessly.
What is everyone else doing? Are you turning off your pocket when you are not using it?
1 Like
I have been turning it off when using it. It’s not ideal. I haven’t ever tried Psuspend, but will see if I can get it running as I would love the option.
Just wanted to add that @amospalla is reviewing my psuspend logs and hopefully we will make some progress there. Amos is a rock star!
2 Likes
Some research into with @amospalla as lead to us disabling the CPU module in the script. However talks on IRC are also showing that there is an issue with the keyboard / sysctrl disconnecting. Light is being shed on the problem, and the good news is that we have a direction to go. Really appreciate all the work on this!
PSA for all using the awesome psuspend, if you have moved to the new keyboard firmware from @minute, please make sure you update psuspend via amospalla’s github repo.
The great news is that the new keyboard firmware seems to keep the keyboard from disconnecting and therefore psuspend is once again reliably saving some power.
1 Like
@amospalla I wanted to change the trigger key combo for psuspend to something like left ctril + left alt + 1. However, it doesn’t seem to work. I used the evdev labels of KEY_LEFTCTRL, KEY_LEFTALT, and KEY_1.
I made this change in psuspend.conf. Saved it and reloaded psuspend. Didn’t work, so I rebooted. Still didn’t work.
DO you have any ideas on why the new keyboard combo isn’t working?
Edit: Disregard. It seems to work but you have to push ctrl and alt at the same time and then push 1.
Hi, psuspend detects in a very rudimentary way the keyboard combo. It expects the keys to be pressed exactly in the order you put in the configuration, so alt+control+a means pressing alt, then pressing control and finally pressing a, in that exact order. If you press control before alt it is not detected. Hope this is what was happening to you.
2 Likes
That is actually a very good thing! I think it is good that it works that way! And yes I think this is why it appeared to not be working. It is working perfectly now. Really appreciate your efforts in making psuspend.
1 Like
@amospalla I have noticed some peculiarities with the script, and I wonder if you have experienced anything like this as well? Basically, sometimes when activating psuspend with the key combo I’ll see the wifi drop, and I know the script is active, BUT the display does not turn off. It freezes on the desktop as it was before the script was active. To get it out of this you have to “wake” it from psuspend using the key combo. Then the screen will go black, and swaylock happens. I have to sometimes psuspend several times to get the display to actually turn off.
I am using the swayidle signal instead of the display modules, as the display modules sometimes leaves the display out with no way to bring it back.
Any ideas?
My own idea is that the key combo actually writes something if you are in a text app. So now I use shift alt 1 and that seems to have improved the issue.
I’ve experienced that too myself, and I end suspending and resuming again until it works.
Unfortunately I am barely using my pocket and have no time to debug this at this moment.
1 Like
So far I think it has to do with whatever application might be active when you push the command. If I am in a terminal it has worked so far EVERY time. If I am instead in a browser or a chat application it might not work and have the glitch described above.
Seems to be fixable with this kind of tweak to using it. Nothing big. The other good news, is that even though it glitches, it doesn’t freeze or anything. So no worries there. Whew!
Yes, the script should not break anything, but the display module is a bit of a hack and probably needs some attention to ensure it does the correct thing with the adequate timings.
I have found things more stable when setting the trigger keys to something that do not typically send a character and is not in itself a command. SO I set mine to use left alt, shift, and left ctrl. This has made it much stabler when activating and deactivating psuspend. YMMV but I thought I would share.
2 Likes
Good to know, thank you for sharing. Let’s see if it keeps like this.
I have to thank you for this solution because even though the power savings with this are not as much as real suspend they are very close.
Real suspend gets me around .450A whereas psuspend gets me on average .550A. It doesn’t help you eek a ton of battery life out there because it does give you a few more hours, and that is great.
So you can do real a suspend then?
You can do it too. Just type sudo systemctl suspend.
It will suspend BUT you CANNOT resume or wake from that state.
1 Like