![]() |
end of phone call sets minimum cpu frequency to 125Mhz
I noticed this strange and very annoying behavior - is it possible to tweak it?
|
Re: end of phone call sets minimum cpu frequency to 125Mhz
Yes, of course it is.
React with dbus-settings to the end of call and reset lower limit to 250/500. But it is not needed as this frequency is blocked in kernel settings and therefore not taken into account. Speaking about kernel-power. |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
i will use dbus if i'll have no other choice, but i'm looking for a "cleaner" solution |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
Code:
echo 125000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
But as it is blocked, your min freq will still be 250 MHz. For that, the new min. value of 125 MHz is bogus. Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
|
Re: end of phone call sets minimum cpu frequency to 125Mhz
The only time I've seen anything do this was in early versions of speedpatch. If you're running and older version of that, do update it (or remove it). 125Mhz is unstable, and doesn't allow transition fast enough to handle all cases (missed calls, etc) which is why Nokia avoided using it in the first place.
Personally, I run 0/500/900 with a large step threshold and have no issues with low battery or lack in usability. |
Re: end of phone call sets minimum cpu frequency to 125Mhz
"Correct Frequencies" can all depend on usage and the device, it's been covered lots of times before.
While I wouldn't recommend it to all, after long periods of testing different frequencies with my device and usage. I run 125-600 and have no issues with low battery or lack in usability. I have never experienced any issue with 125Mhz being unstable. Bear in mind that since the "125Mhz unstable issue" was reported, smartreflex has been fixed and also there have been new releases of KP. For reference this is the bugzilla link:- https://bugs.maemo.org/show_bug.cgi?id=7116 |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
if no other choice, i guess i'll be executing my kernel power command to set a profile after each call end with dbus... |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
|
Re: end of phone call sets minimum cpu frequency to 125Mhz
Quote:
Quote:
'kernel-config show' will report 125 as Minimum, but this is not used! See here some extract of TIME_IN_STATE ANALYSING SCRIPT Quote:
|
Re: end of phone call sets minimum cpu frequency to 125Mhz
Guys, this bug really iritates me and I don't know what to do. I have tried to set "avoid 125" from a fiew post earlier but my output is like this.
BusyBox v1.23.0 (Debian 1.23.0power1) built-in shell (ash) Enter 'help' for a list of built-in commands. Nokia-N900:~# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/ time_in_state 1150000 0 1100000 0 1000000 0 950000 0 900000 0 850000 47010 805000 1644 720000 2309 600000 35952 550000 2420 500000 57200 250000 113621 125000 14373 Nokia-N900:~# What am I doing wrong? What to do (keep in mind that I'm quite a noob)? It is really frustrating to enter x-term and load a config every time after a phone call... |
Re: end of phone call sets minimum cpu frequency to 125Mhz
What bug?
What post? What info (we could help you on)? |
Re: end of phone call sets minimum cpu frequency to 125Mhz
Doesn't matter..it looks like that it wasn't a big thing after all, and that 125MHz lock after a call was a bogus as someone wrote in this thread already.
Sorry for bothering you all cheers |
All times are GMT. The time now is 10:54. |
vBulletin® Version 3.8.8