People running 1.4+ OC please post setscaling.sh text


Last Updated:

  1. inssane

    inssane Well-Known Member This Topic's Starter

    Joined:
    Dec 17, 2009
    Messages:
    1,851
    Likes Received:
    156
    If that makes sense...

    I tried 1.4 and I know some phones just won't do it. I had the voltage all the way up to 82 on the 1400, and no go, freezes up, but not a total M lock.

    I just want to see the voltage on 1400 and the voltages on the scaled frequencies.
    Thanks
    N
     

    Advertisement
  2. Cilraaz

    Cilraaz Well-Known Member

    Joined:
    Sep 14, 2010
    Messages:
    156
    Likes Received:
    19
    Personally, my phone is stable 1200 @ 59, 1300 @ 66, and 1400 @ 75.

    [edit: I did have some fairly rare reboots at 1400 @ 75, so I would say it would likely be perfectly stable at 76.]
     
  3. braway

    braway New Member

    Joined:
    Oct 24, 2010
    Messages:
    2
    Likes Received:
    2
    I'm running stable at 300mhz@2.7v/1000mhz@5.6v/1300mhz@6.8v/1400mhz/7.1v

    which would be:
    Code (Text):
    1. echo 71 > /proc/overclock/max_vsel
    2. echo 1400000 > /proc/overclock/max_rate
    3. echo 1 300000000 27 > /proc/overclock/mpu_opps
    4. echo 2 1000000000 56 > /proc/overclock/mpu_opps
    5. echo 3 1300000000 68 > /proc/overclock/mpu_opps
    6. echo 4 1400000000 71 > /proc/overclock/mpu_opps
    7. echo 0 1400000 > /proc/overclock/freq_table
    8. echo 1 1300000 > /proc/overclock/freq_table
    9. echo 2 1000000 > /proc/overclock/freq_table
    10. echo 3 300000 > /proc/overclock/freq_table
    I'm using 300 for my profiles for battery saving (so if the screen is off the phone will underclock to 300mhz, same with battery > 50C and battery < 15% or so)

    Quadrant score of 2608 (with stagefright):
    [​IMG]

    PS: just ran 10 minutes setCpu stress test, cpu temp (NOT battery temp) went up to 43C (immediately went down afterwards)
     
    7S Troll likes this.
  4. Cilraaz

    Cilraaz Well-Known Member

    Joined:
    Sep 14, 2010
    Messages:
    156
    Likes Received:
    19
    Out of curiosity, what are you using to measure CPU temp? As far as I was aware, the D2 was unable to directly measure the CPU.
     
  5. braway

    braway New Member

    Joined:
    Oct 24, 2010
    Messages:
    2
    Likes Received:
    2
    The D2 has a CPU Temperature Sensor which you can register to...

    so I wrote a small widget to get the temperature, look for "CPU Temperature Widget" in the market ;)

    It's not great, but it works :)
     
    Cilraaz likes this.
  6. Cilraaz

    Cilraaz Well-Known Member

    Joined:
    Sep 14, 2010
    Messages:
    156
    Likes Received:
    19
    Awesome. Thanks!

    Also, I re-did my overclock setups a bit. Each profile uses 400/700/900 MHz for the lower three settings. All three use voltages of 27/38/50 respectively. The top values I've used are 1200 @ 59, 1300 @ 67, and 1400 @ 77.

    I've done a few stress tests to check temps now that I have braway's widget. Each test was done with the intention of achieving the highest temperature possible, creating a worst-case scenario, but without having each test interfere with each other's results. Each test was 2 minutes in length. Each test was performed with the charger plugged in. Between each test, the charger was unplugged and the phone allowed to cool. This should add the extra battery heat from charging, while not allowing latent heat to adversely affect the next test. Yeah, probably a little over the top, but hey, I'm a geek.

    Code (Text):
    1.  
    2. Speed   CPU Temp   Battery Temp   Quadrant Score
    3.  1200     39
     
  7. 7S Troll

    7S Troll Member

    Joined:
    Oct 25, 2010
    Messages:
    12
    Likes Received:
    0
    tried using this with apex as the custom setscaling.sh on the sd card, came up with errors.
    using droid x, tried

    echo 71 > /proc/overclock/max_vsel
    echo 1400000 > /proc/overclock/max_rate
    echo 1 300000000 27 > /proc/overclock/mpu_opps
    echo 2 1000000000 56 > /proc/overclock/mpu_opps
    echo 3 1300000000 68 > /proc/overclock/mpu_opps
    echo 4 1400000000 71 > /proc/overclock/mpu_opps
    echo 0 1400000 > /proc/overclock/freq_table
    echo 1 1300000 > /proc/overclock/freq_table
    echo 2 1000000 > /proc/overclock/freq_table
    echo 3 300000 > /proc/overclock/freq_table

    any suggestions?


    NVM...found out the cause...
     
  8. Cilraaz

    Cilraaz Well-Known Member

    Joined:
    Sep 14, 2010
    Messages:
    156
    Likes Received:
    19
    So, I tinker too much, though it turned out to be a good thing. I found that my voltages on the lower profiles were too low, and were the cause of a lot of my freezing or reboots. I'm not going to go into as much detail as my last post, as temps weren't an issue at any point for me.

    This time, I used SetCPU to lock into each speed level individually to ensure stability of each (ie. max 400/min 400 run stress test, max 850/min 850 run stress test, etc). Here are my three setscaling.sh scripts now:

    1200MHz
    Code (Text):
    1.  
    2. echo 60 > /proc/overclock/max_vsel
    3. echo 1200000 > /proc/overclock/max_rate
    4. echo 1 400000000 33 > /proc/overclock/mpu_opps
    5. echo 2 850000000 56 > /proc/overclock/mpu_opps
    6. echo 3 1000000000 56 > /proc/overclock/mpu_opps
    7. echo 4 1200000000 60 > /proc/overclock/mpu_opps
    8. echo 0 1200000 > /proc/overclock/freq_table
    9. echo 1 1000000 > /proc/overclock/freq_table
    10. echo 2 850000 > /proc/overclock/freq_table
    11. echo 3 400000 > /proc/overclock/freq_table
    12.  
    1300MHz
    Code (Text):
    1.  
    2. echo 68 > /proc/overclock/max_vsel
    3. echo 1300000 > /proc/overclock/max_rate
    4. echo 1 400000000 33 > /proc/overclock/mpu_opps
    5. echo 2 900000000 56 > /proc/overclock/mpu_opps
    6. echo 3 1000000000 56 > /proc/overclock/mpu_opps
    7. echo 4 1300000000 68 > /proc/overclock/mpu_opps
    8. echo 0 1300000 > /proc/overclock/freq_table
    9. echo 1 1000000 > /proc/overclock/freq_table
    10. echo 2 900000 > /proc/overclock/freq_table
    11. echo 3 400000 > /proc/overclock/freq_table
    12.  
    1400MHz
    Code (Text):
    1.  
    2. echo 77 > /proc/overclock/max_vsel
    3. echo 1400000 > /proc/overclock/max_rate
    4. echo 1 400000000 33 > /proc/overclock/mpu_opps
    5. echo 2 900000000 56 > /proc/overclock/mpu_opps
    6. echo 3 1100000000 57 > /proc/overclock/mpu_opps
    7. echo 4 1400000000 77 > /proc/overclock/mpu_opps
    8. echo 0 1400000 > /proc/overclock/freq_table
    9. echo 1 1100000 > /proc/overclock/freq_table
    10. echo 2 900000 > /proc/overclock/freq_table
    11. echo 3 400000 > /proc/overclock/freq_table
    12.  
    Temps were good and (for my specific device) each level was 100% stable. I completely suggest to anyone who seriously wants stability from their overclock to use SetCPU to test each individual speed level.

    Personally, I'm only using the 1200MHz overclock right now. I didn't find enough "real world" increase at 1300MHz or 1400MHz to invest in the additional heat and voltage. The 1200MHz profile above is actually lower voltage than stock (stock 1000MHz appears to be a voltage setting of 62).

    Anyway, hopefully my inner geek is done now. Man, you put a piece of electronic equipment in front of me and I just need to play.
     

Share This Page

Loading...