View Poll Results: What up_threshold gets you the best performance/battery combo?

Voters
2. You may not vote on this poll
  • 20

    0 0%
  • 25

    1 50.00%
  • 30

    0 0%
  • 35

    0 0%
  • 40

    0 0%
  • other

    1 50.00%
Results 1 to 11 of 11
  1. seekis's Avatar
    Posts
    59 Posts
    Global Posts
    64 Global Posts
       #1  
    if you just installed the 800MHz patch installed, you may want to use the following script to help CONSERVE BATTERY LIFE when you don't need the phone running at full blast

    just got cpu scaling via onDemand working with the new 800MHz patch...now just trying to make sure it never touches 125MHz (pandora ALWAYS freezes)...

    this is what i got so far

    Code:
    # Enables cpu scaling
    
    start on stopped finish
    stop on runlevel [!2]
    
    console none
    
    script
    echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
    echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
    echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
    echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
    echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
    end script
    i will upload the above script as well as one at 20, 30, 35, and 40 up_threshold all zipped together so that you it will stick after a reboot

    us WOSQI to send file to /etc/event.d/

    and then reboot

    then in WOQSI use linux commandline and use the following command to see how its working

    Code:
    cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    im a newb at this stuff. all i did was piece it all together.

    PLZ let me know if this is wrong and how to fix it. i don't know how to make it into a patch for WOSQI or Preware, but if you do, be my guest

    these are my results so far

    Code:
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in
    _state
    800000 8778
    720000 2495
    600000 301
    550000 99
    500000 695
    250000 24149
    125000 0
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in
    _state
    800000 8778
    720000 2495
    600000 301
    550000 99
    500000 695
    250000 24199
    125000 0
    
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in
    _state
    800000 8778
    720000 2495
    600000 301
    550000 99
    500000 695
    250000 24293
    125000 0
    my biggest question is if i should actually lower the up_threshold so that it utilizes the midrange frequencies as well as the high end?

    the following is with many apps open and pandora running in the back ground @ 25 up_threshold after a half-ish hour

    Code:
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 40783
    720000 17159
    600000 9311
    550000 12592
    500000 86496
    250000 44696
    125000 0
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 40841
    720000 17159
    600000 9311
    550000 12592
    500000 86523
    250000 44696
    125000 0
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 40882
    720000 17323
    600000 9311
    550000 12592
    500000 86523
    250000 44696
    125000 0
    now to test at 30 up_threshold...

    Code:
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 32720
    720000 8943
    600000 3508
    550000 4399
    500000 25915
    250000 9100
    125000 0
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 32720
    720000 8943
    600000 3508
    550000 4399
    500000 25962
    250000 9100
    125000 0
    root@palm-webos-device:/# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    800000 32720
    720000 8943
    600000 3508
    550000 4399
    500000 26006
    250000 9100
    125000 0
    now at 35...
    Attached Files Attached Files
    Last edited by seekis; 03/25/2010 at 08:21 AM. Reason: more results
  2. #2  
    Does the 80MHz kernel patch need to be installed for this?
  3. seekis's Avatar
    Posts
    59 Posts
    Global Posts
    64 Global Posts
       #3  
    yes if you want to use the higher 720 and 800MHz settings

    which i would recommend HIGHLY
  4. #4  
    Stupid comment ignore me....its been a busy morning here in the UK
  5. #5  
    it does run on boot (ondemand)

    event.d folder runs the scripts upon bootup
  6. #6  
    You all are using the wrong governor if you are worried about battery life.
    Live free or DIE!
  7. #7  
    if you dont want a patch installed and hidden from you, try my app. It lets you choose any speed or scaling option you want with the touch of a button:

    alpha testing---
    CPUScalerUber
    http://forums.precentral.net/webos-a...-unixpsyc.html
    Internet Radio - the best beats on the web

    CPUScaling app L337Tech post

    Super PreKernel app

    If you appreciated any of my help, enjoy any of my apps that I give away for free, or want to see more development from me, think about making a donation. Thanks!
  8. seekis's Avatar
    Posts
    59 Posts
    Global Posts
    64 Global Posts
       #8  
    You all are using the wrong governor if you are worried about battery life.
    what should i use instead?
  9. billfold's Avatar
    Posts
    35 Posts
    Global Posts
    44 Global Posts
    #9  
    Apart from battery life, will this improve temp. spikes, etc? That would be the main reason I would use this script. Also, how would you remove it? Would it be as simple as going in and using an rm command? What type of strain do you place on the processor with it scaling throughout that range?
  10. #10  
    Quote Originally Posted by seekis View Post
    what should i use instead?
    The governors compiled into the stock kernel arent the best for scaling. Palm wants to control battery life via power domains. Thats why they use "userspace". Also why enabling SmartReflex will hang your phone in random times or at boot. CPU scaling wont necessarily save battery life, but it will cut down on heat.

    So if you use the phone alot and using scaling having a faster ramp up will defeat the purpose. when the phone is idle the kernel timer does nothing and the power state can go to almost 0V. The ondemand governor ramps up to 100% too quickly by default. yes you can tweak it but other governors already have powersaving in mind.
    Live free or DIE!
  11. kevank#AC's Avatar
    Posts
    67 Posts
    Global Posts
    73 Global Posts
    #11  
    Quote Originally Posted by unixpsycho View Post
    The governors compiled into the stock kernel arent the best for scaling. Palm wants to control battery life via power domains. Thats why they use "userspace". Also why enabling SmartReflex will hang your phone in random times or at boot. CPU scaling wont necessarily save battery life, but it will cut down on heat.

    So if you use the phone alot and using scaling having a faster ramp up will defeat the purpose. when the phone is idle the kernel timer does nothing and the power state can go to almost 0V. The ondemand governor ramps up to 100% too quickly by default. yes you can tweak it but other governors already have powersaving in mind.
    Agreed. Unfortunately, the only governors available to us are ondemand and userspace. Correct?

    Kevan

Tags for this Thread

Posting Permissions