[OC] Tegrak Overclock for Galaxy S II v0.7.0.5

Search This thread

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Tegrak:

I have a feature request: Anyway we can do app specific profiles? For instance, for the games that really heat up the CPU and drain battery quick, I like to scale only to 1000 MHz or so. It would be great if Tegrak OC Ultimate could assign profiles to each app so that when the app is launched, the app would automatically set a (lowered/throttled) profile, and once the app closes, the default OC profile is reset.

Chainfire3D PRO allows for app specific driver settings, so I'm thinking this has to be possible with your OC app as well.

Many thanks!
 

lpsi2000

Senior Member
Jan 16, 2004
2,479
156
TriState
Tegrak:

I have a feature request: Anyway we can do app specific profiles? For instance, for the games that really heat up the CPU and drain battery quick, I like to scale only to 1000 MHz or so. It would be great if Tegrak OC Ultimate could assign profiles to each app so that when the app is launched, the app would automatically set a (lowered/throttled) profile, and once the app closes, the default OC profile is reset.

Chainfire3D PRO allows for app specific driver settings, so I'm thinking this has to be possible with your OC app as well.

Many thanks!

Great idea, I was thinking the same this weekend. It would also be nice scale based on condition similar to SetCPU. Using the SetCPU you can say to scale the CPU back if temp is greater than 40 degree Celcius. Or set a profile when using the phone that min and max are 200 - 500 mhz. These features would be great to add to this application.
 

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Great idea, I was thinking the same this weekend. It would also be nice scale based on condition similar to SetCPU. Using the SetCPU you can say to scale the CPU back if temp is greater than 40 degree Celcius. Or set a profile when using the phone that min and max are 200 - 500 mhz. These features would be great to add to this application.

Yep, that would be great as a later add-on, but for now, app driven profile settings would be a great first step. I'm currently manually stepping down for the games that cause "excessive heat," would like that to be more automated.
 

crypticc

Senior Member
Aug 22, 2009
1,249
174
London
Great idea, I was thinking the same this weekend. It would also be nice scale based on condition similar to SetCPU. Using the SetCPU you can say to scale the CPU back if temp is greater than 40 degree Celcius. Or set a profile when using the phone that min and max are 200 - 500 mhz. These features would be great to add to this application.

Tegrak had said he doesn't like profiles. Also per app doesn't mean so much on a multi taking environment

Sent from my GT-I9100 using Tapatalk
 

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Tegrak had said he doesn't like profiles. Also per app doesn't mean so much on a multi taking environment

Sent from my GT-I9100 using Tapatalk

You're clearly not understanding this request. Please try and understand what I'm asking for before responding:

1) Throttled/lower frequency makes a HUGE difference. In some games that overheat the SGS2 (especially at a OC'd max frequency), if I cap the highest frequency to only 800 MHz or 1000 Mhz, there is a huge reduction in heat output with no difference in performance. So your "multi tasking" bit is irrelevant.

2) Tegrak Ultimate already has profiles... just right now, you have to manually select them. I just want to see if Tegrak can assign them to only trigger per app like Chainfire3D Pro. So your "Tegrak doesn't like profiles" bit, also irrelevant.
 
Last edited:

crypticc

Senior Member
Aug 22, 2009
1,249
174
London
You're clearly not understanding this request. Please try and understand what I'm asking for before responding:

1) Throttled/lower frequency makes a HUGE difference. In some games that overheat the SGS2 (especially at a OC'd max frequency), if I cap the highest frequency to only 800 MHz or 1000 Mhz, there is a huge reduction in heat output with no difference in performance. So your "multi tasking" bit is irrelevant.

2) Tegrak Ultimate already has profiles... just right now, you have to manually select them. I just want to see if Tegrak can assign them to only trigger per app like Chainfire3D Pro. So your "Tegrak doesn't like profiles" bit, also irrelevant.


cf3d is different because it redirects specific open gl calls per app. Cpu is different.

E.g lets imagine this function is working. i have feedr, text messaging, weather and facebook running in background to riptide in foreground. Which profile should tegrak use? I'd say riptide profile. Then i close riptide, what then? Default profile. The issue then is that tegrak will need to monitor for active apps at any time to detect which apps are running and prioritise the profile and he said he didnt want active cpu throttling to do that. If you can grab a moment and read back it is there somewhere.

You can always setup and pick your own profiles. Maybe a widget to set them manually is a better idea.

Regards
Chris

P.s. Less rude next time please
 

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
cf3d is different because it redirects specific open gl calls per app. Cpu is different.

E.g lets imagine this function is working. i have feedr, text messaging, weather and facebook running in background to riptide in foreground. Which profile should tegrak use? I'd say riptide profile. Then i close riptide, what then? Default profile. The issue then is that tegrak will need to monitor for active apps at any time to detect which apps are running and prioritise the profile and he said he didnt want active cpu throttling to do that. If you can grab a moment and read back it is there somewhere.

You can always setup and pick your own profiles. Maybe a widget to set them manually is a better idea.

Regards
Chris

P.s. Less rude next time please

I'm not being rude, you're just being argumentative for the sake of argument. You're still not getting it: I already throttle the ENTIRE SYSTEM when I play a game that gets really hot (ie, Riptide)... the process is just manual. So, this doesn't need to be tied to the app as it is running real time, I just need it to throttle the entire system and revert to default OC upon open/close of a specific app. Yes, event based. This is not hard to do... in fact, if I had the source, I could probably do this rather easily.

Anyway, doesn't matter. I bought Tegrak Ultimate, I've asked for a feature add, and I'll wait for Tegrak's response.
 

adit17

Senior Member
Sep 3, 2011
128
7
my device is not available

model number : GT - I9100
Android version : GINGERBREAD_MR1 2.3.5 (SDK 10)
Kernel version : 2.6.35.13
Firmware version : XXKI3

thank you for assistant
 

beaver2233

Senior Member
Feb 19, 2011
2,099
494
Sydney
I was wondering if there is any way in obtaining the ultimate version without going through the market (don't have credit card). I'd rather pay via paypal directly, is this possible ?

Sent from my GT-I9100 using Tapatalk
 
Last edited:

cmd512

Senior Member
Aug 25, 2009
3,348
841
Shanghai
Latest update says support for more kernels... Mind clarifying which new kernels are now supported? Thanks!

Sent from my GT-I9100 using Tapatalk
 

NoPompem

Senior Member
Jul 22, 2011
111
11
Tegrak. I cannot wait to get 5mv and 1mhz increments. :D Seriously, I would really like to have that for when I am at work with nothing to do but tune my clocks. Consider it please.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 55
    Hello,

    After some day to day testing, here is what I think are the best methods to tune Tegrak Overclock :
    sorry for my poor english, I am french :)


    ADVICES
    • First of all, no matter how high your max frequency is, you have to put a low voltage @200Mhz. This is for battery life when your screen is off.
      You can try 800mV@200Mhz but on my device 825mV@200Mhz is 100% stable (I mean never EVER crash with no reason)
    • When your screen is on, most of the time (if using it), the frequency will be at max. So, if you plan on high frequency (like 1500+), your battery WILL drain faster.
      At high voltages (IE high frequencies), the difference is easily noticeable.
    • More than 1500Mhz is almost useless. The phone is already smooth at 1200-1300 and there are no lag at all. You will drain your battery for nothing more than your happiness to be at that frequency.
    • For games, prefer tweaking the max frequency of the GPU. Tegrak permit it, so use it ! It will be better for battery life when you are not playing games.
    • Don't forget to unlock your GPU freq after playing games like Asphalt 6. GPU drain more battery when locked at 267Mhz.
    • About Internal Voltage. I recommend to not scale it like Core Voltage because the difference between 850 and 1100mV is low on battery (I didn't notice a difference).
      For my device, I permit 25mV difference between each frequencies (950->1075). Also, it's easier to crash your phone at low frequencies.

    SETTINGS

    CPU Level 4 - 200 Mhz
    This is the critical setting of your phone because it will be most of the day at it (when your screen is off).
    No matter what are your other settings, I recommend 825mV but you can try 800mV. Most of the phones will crash at less.

    (Note : I have seen that if your max frequency is very high (1500+), it will be more difficult to put 825mV@200Mhz. I don't know why but on my phone, I had to put between 850 and 900mV when max frequency were more than 1500Mhz. If you are experiencing the same thing, please share !)

    Naphtaline recommends : 825mV@200Mhz



    CPU Level 3, 2 and 1 - 500, 800 and 1000 Mhz
    500, 800 and 1000 Mhz are frequencies who are used when you are using your smartphone normally : sending sms, using web browser, using home screen, etc.
    But, in fact, the max frequency is more often used.
    You can see that by yourself with a cpu frequency monitor (setcpu can do that). Just put your finger on the screen and you'll see that the frequency go max just for getting your finger position (like crypticc said, this is visible only for "on demand" governor).

    Anyway, theses frequencies are important because the phone will grind on them very often. So the voltage have to be low but not as accuracy as @200Mhz.

    With a calculator, you can scale the voltage on frequencies and then adjust for your device.

    Just remember that trying to put the lowest voltages on theses frequencies is pointless because you will increase your chance of crash.

    Naphtaline recommends : 900mV@500Mhz, 975mV@800Mhz and 1100mV@1000Mhz



    CPU Level 0 - 1200 Mhz and higher
    This CPU level is for overclocking. If you just want to stay at stock clock, you'll have to do the same as @200Mhz : As low as possible.

    So, there are three school for tuning here.

    School of battery life
    You want the best battery life no matter what the max frequency you can get.
    First, you have to find your lowest voltage @1200Mhz. Mine is 1200mV 100% stable (1175Mhz is ok but crashed one time on testings)
    Then, you can try to increase your frequency to find what is your max frequency for this voltage.
    As 1Mhz is nothing in performance, add 10Mhz every morning until you got a crash and go back to last frequency until it never crash anymore.

    For my device, it's 1200mV@1270Mhz.



    School of performance
    You want really noticeable better performance than stock and don't want your phone to overheat.
    In my opinion, 1500Mhz is the point.
    So, method is the same. Put 1500Mhz and try at 1350mV first. If it's okay after a day, try to lower the voltage 1325, 1300 (if your device is ok at less than 1300mV@1500Mhz, you got a gold CPU^^)
    When you got a crash, go back to last voltage until it never crash anymore.



    School of the biggest
    You want :
    - A kickass smartphone no matter battery consumption is AND no matter your cpu life will suffer
    - The best frequency your smartphone can beat

    Start by putting 1500mV at the Core Voltage. DO NOT try to do the same with Internal Voltage. 1100mV~1150mV is good.
    Next, try to start at 1700Mhz and increase by 100Mhz every hour. Between each test, do not keep your screen off. You can run a benchmark or playing games.
    Your phone will heat so be careful ! At this point, this is a little risky. You cpu may burn and die (I am not responsible blah blah...). Normally he can't (he will crash before) but who knows.
    When your phone crash, just go back to last frequency until it never crash anymore.
    Later, you can tune the frequency by steps of 10Mhz but well... Does it really matter ?

    I didn't tune a lot on this, but for my device, I can raise at 1500mV@1700Mhz with no errors.


    Naphtaline recommends : 1200mV@1250Mhz
    50
    *NOTICE*

    zelendel said:
    It has come to our attention that you have been asked to give access to the source code for your tegrak_overclock_galaxys_gingerbread.ko that is in your app. As this modual is covered under the GPL you are required to post the source code for this. IF you refuse to post the code for this modual (only one that needs to be posted) then you are breaking the GPL licence and I will be forced to move further on this. I look forward to hearing back from you

    I got this message from zelendel, a moderator of xda.
    I don't have knowledge enough about GPL, so I didn't what he said.
    My job is a Windows programmer and I've never concern about the license except Microsoft Visual Studio and Windows.

    I'll start to study GPL deeply. then I'll open my source if I broke the rules.
    I think this post will be removed by him very soon.
    I'll send him links (that I posted) about this app.
    I'm sorry to developers who felt unpleasant by this thread like zelendel.

    Thanks to all for helping this thread.

    Regards & Thanks,
    Tegrak

    ------------------------------------------------------

    NEED ROOT!
    Overclock can be harm to your hardware.
    Use at your own risk.


    *Galaxy Tab Gingerbread 2.3.3 is available!
    *GPU optimization is available! (Galaxy S II only)
    *GT-I9000 leaked 2.3.4 and Gingerbread 2.3.3 is available!
    *Galaxy S II in Europe is available! (confirmed by blaaez at xda)
    *Galaxy S II in Korea is available!

    Please!
    Check available models and use free version first before you buy.

    I want to share settings in this dev thread.
    Stable maxinum overclocked setting
    Stable undervoltage setting
    ..etc...

    Links
    Free version
    Web: https://market.android.com/details?id=com.tegrak.overclock
    Mobile: market://details?id=com.tegrak.overclock
    Ultimate version
    Web: https://market.android.com/details?id=com.tegrak.overclock.ultimate
    Mobile: market://details?id=com.tegrak.overclock.ultimate
    I'll upload free version here if you want.

    Best Quandrant Score of Galaxy S II
    6229 MZWiZard's thread. @1.66GHz 1400mV
    http://xdaforums.com/showpost.php?p=14403392&postcount=191

    Wonderful Guide
    Naphtaline's school of overclocking
    http://xdaforums.com/showpost.php?p=14973796&postcount=531

    What is this?
    This is for family of Galaxy S devices and Galaxy S II devices.
    You can set maximum CPU frequency of your device on available models EASILY.
    This works with STOCK kernel, STOCK rom, (x)custom kernels and roms(x).
    You just need to rooting.

    (x) The latest kernel source of Galaxy S II on Samsung Opensource Release Center is not compatible with latest rom's kernel. So, this time, this app can't be used with kernels that built from source code.

    Features on Ultimate
    Try free version first!
    Then try this if you like free version, want more professional control or want to help me! :D
    *Profile management
    - profiles are stored in /sdcard/tegrak/overclock/*.oc
    *Lock GPU clock to 267MHz (Galaxy S II only)
    - see details, http://xdaforums.com/showpost.php?p=14733638&postcount=384
    *Set customized GPU clock. (Galaxy S II only)
    *Set customized GPU voltage. (Galaxy S II only)
    *Set scaling governor and min/max frequency.
    *2x1 and 3x1 home screen widgets
    *Set customized frequency (1.0 ~ 2.0 GHz)
    *Set customized voltage (750 ~ 1400 mV, OV or UV available)
    *Available set last settings on boot automatically.
    - Stability checking background service is turned on about 5 minutes every time when you change settings.
    - If your device freeze or shutdown while it is running, app will show you popup to apply the last setting on boot.
    *Show ARM core voltage at max frequency.
    *Show your device information
    *Free from Advertisement
    *Tweaks (Io Scheduler)

    Features on Free
    *Lock GPU clock to 267MHz (Galaxy S II only)
    - see details, http://xdaforums.com/showpost.php?p=14733638&postcount=384
    *Set scaling governor and min/max frequency.
    *Set cpu max frequency
    -- Galaxy S: 1.0 ~ 1.3GHz
    -- Galaxy S II: 1.2 ~ 1.452GHz
    *Show ARM core voltage at max frequency.
    *Show your device information
    *Tweaks (Io Scheduler)

    About voltage control
    Galaxy S II Gingerbread: +-25 step
    Galaxy S Froyo: +-25 step
    Galaxy S Gingerbread: +-1 step

    About IO Scheduler in Tweaks
    CFQ scheduler: http://en.wikipedia.org/wiki/CFQ
    Deadline scheduler: http://en.wikipedia.org/wiki/Deadline_scheduler
    Noop scheduler: http://en.wikipedia.org/wiki/Noop_scheduler
    Summary by neilix http://xdaforums.com/showpost.php?p=14684673&postcount=353

    How to use?
    First, click "Load overclock module.
    Second, click "CPU max frequency" and choose one frequency from preset options.
    You can control more detailed option in "Optimization" menu.

    More features will be added :)

    Available Galaxy S II Family
    *Galaxy S II (GT-I9100, Gingerbread)
    *Galaxy S II, Bell (GT-I9100M, Gingerbread)
    *Galaxy S II (GT-I9100T, Gingerbread)
    *Galaxy S II, NTT Docomo (SC-02C, Gingerbread)
    *Galaxy S II (SHW-M250S, Gingerbread)
    *Galaxy S II (SHW-M250K, Gingerbread)
    *Galaxy S II (SHW-M250L, Gingerbread)

    Available Galaxy S Family
    *Captivate (SGH-I897, Gingerbread / Froyo)
    *Captivate, Rogers (SGH-I896, Gingerbread / Froyo)
    *Epic 4G (SPH-D700, Gingerbread / Froyo)
    *Fascinate (SCH-I500, Gingerbread / Froyo)
    *Fascinate, Telus (SGH-T959D, Gingerbread / Froyo)
    *Galaxy S (GT-I9000, Gingerbread / Froyo)
    *Galaxy S (GT-I9000B, Gingerbread / Froyo)
    *Galaxy S, Bell (GT-I9000M, Gingerbread / Froyo)
    *Galaxy S (SHW-M110S, Gingerbread / Froyo)
    *Galaxy K (SHW-M130K, Gingerbread / Froyo)
    *Galaxy U (SHW-M130L, Gingerbread / Froyo)
    *Galaxy Player (YP-GB1, Froyo)
    *Galaxy Player (YP-GB70, Froyo)
    *Galaxy S Hoppin (SHW-M190S, Gingerbread / Froyo)
    *Giorgio Armani Galaxy S (GT-I9010, Gingerbread / Froyo)
    *Mesmerize (SCH-I500, Gingerbread / Froyo)
    *Vibrant (SGH-T959, Gingerbread / Froyo)
    *Vibrant Plus (SGH-T959V, Gingerbread / Froyo)

    Available Galaxy Tab Family
    *Galaxy Tab (GT-P1000, Gingerbread)
    *Galaxy Tab (GT-P1000N, Gingerbread)
    *Galaxy Tab (SHW-M180S, Gingerbread)
    *Galaxy Tab (SHW-M180K, Gingerbread)
    *Galaxy Tab (SHW-M180L, Gingerbread)
    *Galaxy Tab (SHW-M180W, Gingerbread)
    *Galaxy Tab, Sprint (SPH-P100, Gingerbread)

    If you are using Galaxy S or Galaxy S II and your device is not in available models
    please let me know your device's model number.

    Update History
    [ v0.7.0.5 ]
    *improved app responsiveness
    *deleting a profile with long clicking

    [ v0.7.0.2 ]
    *supports GT-I9100M Galaxy S II, Bell, Canada

    [ v0.7.0.0 ]
    *added "Profile" menu. you can manage your profiles.
    *supports GT-P1000N Galaxy Tab, Latin

    [ v0.6.3.7 ]
    *supports SHW-M190S Galaxy S Hopping Gingerbread.
    *fixed an error of "Lock to 267MHz" in GPU Optimization (Free, Galaxy S II)

    [ v0.6.3.6 ]
    *for Lulz Kernel Beta

    [ v0.6.3.4 ]
    *fixed a driver error on Epic 4G Gingerbread
    *supports GT-I9100T Galaxy S II, Australia

    [ v0.6.3.3 ]
    *supports SPH-P100 Galaxy Tab, Sprint

    [ v0.6.3.2 ]
    *supports SC-02C Galaxy S II, NTT Docomo, Japan

    [ v0.6.0.9 ]
    *minor bug fix

    [ v0.6.0.2 ]
    *Galaxy S and Galaxy Tab - supports chaging frequencies over 1.0GHz
    *Galaxy S II - supports changing frequencies over 1.004GHz

    [ v0.5.1.4 ]
    *fixed an error on boot when cpu level is changed

    [ v0.5.1.3 ]
    *added "Set GPU settings on boot" menu. (Galaxy S II)
    *added "Reset to default GPU settings" menu. (Galaxy S II)

    [ v0.5.1.0 ]
    *fixed a bug of 3x1 widget.

    [ v0.5.0.9 ]
    *fixed a widget bug.

    [ v0.5.0.6 ]
    *supports 3x1 widget. this shows internal voltage.
    *fixed text alignment of widget.
    *Please remove old widgets and use new.

    [ v0.5.0.2 ]
    *supports Vibrant Plus Gingerbread
    *supports Galaxy Tab SHW-M180S, SHW-M180L

    [ v0.5.0.0 ]
    *New menu! GPU clock and voltage (Galaxy S II only)
    *Galaxy Tab GT-P1000, SHW-M180S, SHW-M180L beta

    [ v0.4.3.1 ]
    *added "Reset default" menu. Optimization > Reset default
    *fixed minor bugs

    [ v0.4.2.9 ]
    *added option. Stability watcher off. Menu key > Settings

    [ v0.4.2.7 ]
    *added Tweaks menu. (Io shceduler available)
    *added options that excludes scaling settings from "set on boot". Press menu key > Settings (for SetCPU users)

    [ v0.4.2.5 ]
    attachment.php

    *added a attractive notification icon (I believe)
    *improved codes. more stable.

    [ v0.4.2.3 ]
    *improved stability service

    [ v0.4.2.2 ]
    *fixed a problem (custom scaling was not appplied on boot)

    [ v0.4.2.1 ]
    *fixed a bug (time goes fast when stability service restarts)

    [ v0.4.1.8 ]
    *fixed a bug of "stability service". (stopped timer when screen off)
    *improved stability service

    [ v0.4.1.7 ]
    *Stability checking background service is turned on about 5 minutes when you change settings every time. (ultimate only)
    *"Set on boot" popup never shows if it passed the stability service. (ultimate only)

    [ v0.4.1.5 ]
    *support GT-I9000 Gingerbread.

    [ v0.4.1.1 ]
    *apply your scaling options on boot.

    [ v0.4.1.0 ]
    *added "Scaling" menu. can change scaling governor and min/max frequency.
    *fixed blank error message problem.

    [ v0.4.0.3 ]
    *GalxyS2 in Europe is available!! (GT-I9100)

    [ v0.4.0.1 ]
    *Galaxy S II is available!!! (SHW-M250S, SHW-M250K, SHW-M250L)
    *added model - Galaxy S Hoppin (SHW-M190S)
    *added model - Galaxy Player (YP-GB1, YP-GB70)

    [ v0.3.1.0 ]
    *support Galaxy Player YP-GB1, YP-GB70
    *support Galaxy S Hoppin SHW-M190S
    *fix minor bugs

    [ v0.3.0.3 ]
    *modified clock preset (more stable values)

    [ v0.3.0.2 ]
    *fixed insmod failure who installed busybox.

    [ v0.3.0.1 ]
    *fixed "not available" problem on GT-I9000 Gingerbread

    [ v0.3.0.0 ]
    *support Galaxy S Gingerbread!! SHW-M110S, SHW-M130K, SHW-M130L, GT-I9000, GT-I9010
    *add internal voltage control.
    *more powerful and stable overclock driver. (re-created)
    *stablelized application algorithm.

    [ v0.2.0.5 ]
    *added 2x1 size widget.

    [ v0.2.0.3 ]
    *changed minimum core voltage 900mV to 750mV

    [ v0.2.0.1 ]
    *added available model Giogio Armani Galaxy S (GT-I9010)

    [ v0.2.0.0 ]
    *fixed core voltage control. it doesn't work before this version. UV(under voltage) and OV(over voltage) works correctly now.
    *removed internal voltage control. this is unnecessary for overclock.

    [ v0.1.7.7 ]
    *added feedback url link.

    [ v0.1.7.5 ]
    *more stable
    *insert Ultimate version link.

    [ v0.1.7.3 ]
    *fix bug at 0.1.7.1, not work to change frequency.

    [ v0.1.7.1 ]
    *display freq, core volt, internal volt in "Optimization" menu.
    *added available models. Captivate Rogers, Fascinate Telus

    [ v0.1.6.2 ]
    *display ARM core voltage.
    *fixed a problem that Captivate isn't recognized by app.
    *improved overclocking routine. more efficient.

    [ v0.1.6.0 ]
    *added available models. U.S. Cellular Mesmerize

    [ v0.1.5.7]
    *fixed scaling freq bug with SetCPU and CPU Master Free app.
    *fixed "unavailable" problem who use custom rom.

    [ v0.1.5.0 ]
    *more stable preset with S5PC110 data sheet.

    [ v0.1.4.7 ]
    *added available models. Epic 4G, Captivate
    *fix some codes.

    [ v0.1.4.0 ]
    *added available models. Vibrant, Vibrant Plus, GT-I9000B
    *modified preset voltage for each devices.

    [ v0.1.3.5 ]
    *set preset voltage to stock voltage.
    *fixed error -102
    *improved preset frequency settings.

    [ v0.1.3.2 ]
    *add detailed error code for "unmatched driver version" problem. please send me error code when you failed to run.
    *modified voltage in preset table.

    What comes next?
    *Reset values to default
    *No popup on boot by adding stability test service
    *Reflect your opinion...

    Do you have any question or opinion?
    Leave a comment.
    Contact me luciferanna@gmail.com
    Follow me http://twitter.com/tegrak
    5
    Ok, just ran the following through 20 minutes of stress test with Stability Test v1.5 (hammers both cores + memory simultaneously) with no failures. Max temp = 39C.

    Again, courtesy of Major_Sarcasm for his settings from Levels 1 ~ 4.

    CPU Level 0
    Frequency: 1308Mhz
    Core Voltage: 1225mV
    Internal Voltage: 1050mV

    CPU Level 1
    Frequency: 1000Mhz
    Core Voltage: 1150mV
    Internal Voltage: 1075mV

    CPU Level 2
    Frequency: 800Mhz
    Core Voltage: 1025mV
    Internal Voltage: 1050mV

    CPU Level 3
    Frequency: 500Mhz
    Core Voltage: 875mV
    Internal Voltage: 900mV

    CPU Level 4
    Frequency: 200Mhz
    Core Voltage: 850mV
    Internal Voltage: 875mV

    ===============================

    Could I have squeezed more out of the frequency at Level 0? Probably, but I got the phone to crash after 12 minutes with 1 notch lower on the voltage (-25) at 1308MHz, so I figured for ensured stability, 1308 at the current voltage will do.

    Could I have undervolted more on the other frequencies? Probably so as well, but that would take a whole lot of testing one parameter at a time, and I just can't be bothered. At the current settings, phone is going to and coming out of sleep, syncing up to my car's bluetooth with screen off, etc with no issues. So, it's good to go. :)

    Again, like I mentioned above, my goal is complete stability with a small overclock + some undervolting. Increased performance + lower temps sound like a win-win to me.

    Hope this helps. :)
    4
    ok I have tried some UV settings and tested the settings with Quadrant and played Tekken 3 (FPse)

    I only use 1GHz max so I have not touched 1.2GHz or more UV settings, CV=Core Voltage, IV=Internal Voltage

    1GHz: CV:1125mV,IV:1075mV
    800MHz: CV:950mV,IV:1050mV
    500MHz: CV:875mV,IV:975mV
    200MHz: CV:800mV,IV:925mV

    These settings seems to work good atm, I think I can lower some more, but I will try these settings for a couple of days and see... btw, what is Internal Voltage?
    4
    Hi Tegrak, what about setting I/O scheduler setting in next version... I managed to get 5200 in quadrant ay only 1280 MHz using deadline scheduler (400 points more than default cfq)

    Sent from my Galaxy SII

    If you find this post usefull please press the "Thanks" button