![]() |
Re: Pybattery - battery statusbar applet with candies
Quote:
|
Re: Pybattery - battery statusbar applet with candies
Quote:
Is there a way to check what the CPU is at without Advanced Battery? Some cli method? I'd be curious to know what it's at with Advanced Battery disabled. |
Re: Pybattery - battery statusbar applet with candies
Quote:
|
Re: Pybattery - battery statusbar applet with candies
Quote:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq |
Re: Pybattery - battery statusbar applet with candies
xterm gave output: 165000.
Can I assume this is less than when Advanced Battery reports 400MHz? |
Re: Pybattery - battery statusbar applet with candies
Nope. Advanced Power reads its frequency from that file. If you choose (with sound off) e.g. powersave governor in AP and wait a while it gonna show 165MHz.
|
Re: Pybattery - battery statusbar applet with candies
So, AP is set to "On Demand" and reads "CPUFreq: 400Mhz". But cli method outputs 165000.
I've tried it three times. Same divergent results. |
Re: Pybattery - battery statusbar applet with candies
But, you're right, if I change to powersave, both say 165000. Why is this?
|
Re: Pybattery - battery statusbar applet with candies
lm2, running ondemand will speed the cpu up to 400 as demand increases over some present %age.
running a python GUI app tiself may trigger the increase and push cpu to 400mhz for reading the value. using the command line is typically a LOT less strain on the system so the cpu will sit idle and be on slowest speed. powersave should show 165 all the time, on demand should be variable, perforance should show 400 all the time. |
Re: Pybattery - battery statusbar applet with candies
Thanks. Which setting does the tablet use default out of the box. I had assumed it was Ondemand, simply because qole's turbo debian gives two options: ondemand and performance.
|
All times are GMT. The time now is 00:41. |
vBulletin® Version 3.8.8