• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [KERNEL] TheOC v1.7.20 kernel for MT Isaac & TG based CM7

Found a very nice post about overclocking. It is for another phone and slightly dated but was awesome in helping me understand the ins and outs of overclocking and Governors in general. Would definitely recommend for all of us OC noobs.

OverClocking 101

Made for an interesting read. I went ahead and installed the OC kernel. Not bad so far. I've found that at 122MHz, the phone its crazy slow, but works. Makes a weird noise though. I've been running antutu to test the voltages. I don't know how good of a test that, but its what I have.
 
linpack is good to use for stability testing. my current triumph doesn't scale nearly as well as my last one. but even still, i can hit some pretty impressive undervolts. even if it never freezes or crashes in real life use, repeated runs of linpack will result in inaccurate results. bump the voltage up a notch and try again.

wish there was a way to have it loop testing on its own, like intelburntest
 
linpack is good to use for stability testing. my current triumph doesn't scale nearly as well as my last one. but even still, i can hit some pretty impressive undervolts. even if it never freezes or crashes in real life use, repeated runs of linpack will result in inaccurate results. bump the voltage up a notch and try again.

wish there was a way to have it loop testing on its own, like intelburntest

In SetCPU on the Info tab, there's an option to do a CPU Stress test. I was using that when I was testing the voltage table. The Stress Test will run until you stop it. It seems to work ok.
 
In SetCPU on the Info tab, there's an option to do a CPU Stress test. I was using that when I was testing the voltage table. The Stress Test will run until you stop it. It seems to work ok.
I've gone an hour before without issues. Did three linpacks and 2 out of 3 failed. Stable enough but not truly stable.
 
I just downloaded linpak and I plan on doing my testing at each frequency again. Do y'all know if I can use this like I would use prime95 on windows?Also, is there a way to get the results sent to a log so I can see them in one place instead of making a bunch of pictures?
 
I just downloaded linpak and I plan on doing my testing at each frequency again. Do y'all know if I can use this like I would use prime95 on windows?Also, is there a way to get the results sent to a log so I can see them in one place instead of making a bunch of pictures?
there's no way to loop testing in the regular linpack. never looked in to the pay one. maybe that's the difference.

realistically speaking, just compile a command line linpack and run it over adb.
 
Question for undervolters:

How long did you run a stress test until you deemed a voltage/clock to be stable?
 
Question for undervolters:

How long did you run a stress test until you deemed a voltage/clock to be stable?

I'm impatient. I only ran each voltage drop in 25 increments at each frequency for about 5-10 minutes at each increment. I ran quadrants, linpacks, antutu benchmark and setcpu cpu stress tests. On my phone, when the voltage was too low, it would lock up and reboot fairly quickly in my testing.

So my methodology, which is probably kind of crappy... :)

1. Set governor to Performance so the phone would run at max speed all of the time.
2. I use a min of 245 which I wasn't planning on changing so I set my max to 245 also as a start -but obviously you can set your min to whatever and start your max at that same freq.
3. Lower voltage in Incredicontrol -25 and apply. DO NOT SET ON BOOT.
4. Run stress testing, quadrants, linpack, antutu benchmark until I get bored--usually about 5 - 10 minutes at each decrement. (I was doing this while watching tv so it wasn't as boring as it sounds.)
5. If the phone didn't lock up or reboot, repeat steps 3 and 4 until you get a voltage that causes your phone to be unstable then stick with the last good voltage.
6. Repeat steps 2 - 5 for the next higher clock frequency.
7. After I got my table set up the way I wanted, I still didn't set my voltages to be applied on boot until about a day after and it hadn't locked up or rebooted in that timeframe--but that's me.

I got tired of doing this at about 768 mHz so I kind of stopped trying to go much lower than just -25 figuring the phone spends most of its time at idle and lower frequencies anyways.
 
I'm used to 12-24 hour stress tests from undervolting pc's/laptops so I was curious what people did on phones.

I'm actually running 30 mins of stress tests at each step so I was wondering if that was too little. I'll probably run 1-2 hour ones to test my final stable voltages.

I'm leaving my governor alone and I'm actually just locking the phone to run at the specific clock I'm testing by setting it to the min/max. That way it never leaves that clock speed for any reason while im testing that specific clock.

I'm going to go all the way up to 1.4mhz so I'll report back here with my fully tested stable settings by the end of the week so people can use it as a reference in finding their own device's minimums.
 
I'm used to 12-24 hour stress tests from undervolting pc's/laptops so I was curious what people did on phones.

I'm actually running 30 mins of stress tests at each step so I was wondering if that was too little. I'll probably run 1-2 hour ones to test my final stable voltages.

I'm leaving my governor alone and I'm actually just locking the phone to run at the specific clock I'm testing by setting it to the min/max. That way it never leaves that clock speed for any reason while im testing that specific clock.

I'm going to go all the way up to 1.4mhz so I'll report back here with my fully tested stable settings by the end of the week so people can use it as a reference in finding their own device's minimums.

That would be great. It's a little easier on a pc because you can just run prime95 and let it go. There's not as convenient of a way to do it on the phone.

As for the governor, that's what the Performance governor does--it runs at the max clock that you have set all of the time and never drops down to the min; whereas min/max will still scale up and down based on load and a sampling frequency--which I suppose, if you're doing stress testing, your load should cause the clock frequency to be set at the max...
 
As for the governor, that's what the Performance governor does--it runs at the max clock that you have set all of the time and never drops down to the min; whereas min/max will still scale up and down based on load and a sampling frequency--which I suppose, if you're doing stress testing, your load should cause the clock frequency to be set at the max...

I meant for example I'm testing 368640hz, I'll set the minimum frequency to 368640hz and maximum frequency to 368640hz. I wasn't referring to the min/max governor. This should work, yes?
 
I meant for example I'm testing 368640hz, I'll set the minimum frequency to 368640hz and maximum frequency to 368640hz. I wasn't referring to the min/max governor. This should work, yes?

Ahh, yes, that works great. I misunderstood you. I apologize. :)
 
Stability Test 2.3 will run through all available clock speeds between your min and max, by controlling the governor itself. It may, in fact, leave your governor set wrong if it crashes while testing. I have verified that it does indeed hit them all, in System Tuner. You could verify this in SetCPU as well, I think. Anyway, I found it to be helpful, and less of a PITA.

Edit:
Forgot to mention also that it will run indefinitely, until you stop it... The reason I posted about it to start with.
 
Has anyone verified hot spot in Mantera's kernel update? No go for me. Verified working in TG's b0.8 kernel. This one trys to work... Laptop connects, but the old limited connection error comes up. Flashed back to original that Mantera has posted, and hot spot worked fine again.
 
Has anyone verified hot spot in Mantera's kernel update? No go for me. Verified working in TG's b0.8 kernel. This one trys to work... Laptop connects, but the old limited connection error comes up. Flashed back to original that Mantera has posted, and hot spot worked fine again.

Laptop sees the hotspots and can connect but with "limited connectivity" meaning no internet access.

Short answer: No, its not working for me either. Original does.
 
Strange. It's working fine for me... I'm typing this message on my xoom tethered to my phone using this kernel right now.

Did you set any settings in the hot spot?

I'm using spa encryption and I changed the password.
 
Strange. It's working fine for me... I'm typing this message on my xoom tethered to my phone using this kernel right now.

Did you set any settings in the hot spot?

I'm using spa encryption and I changed the password.

Clean install of Beta 8 (factory reset, flash rom) fixed it!! :)
Working fine for me now with this kernel. Thankful for Titanium Backup
 
After 2 days of synthetic stress testing and 1 day of real world use (wifi on most of the time, browsing, maps to find a restaurant, phone calls, messaging, 15h on battery from 100% down to 23%), I've found the lowest 100% stable voltages for my Triumph. Thanks for this kernel, mantera :)

Synthetic Stress Test/Benchmark Tools
SetCPU's Stress Test
Stability Test - https://market.android.com/details?id=com.into.stability
Antutu - https://market.android.com/details?id=com.antutu.ABenchMark
Quadrant - https://market.android.com/details?id=com.aurorasoftworks.quadrant.ui.standard
Linpack - https://market.android.com/details?id=com.greenecomputing.linpack

Stock Voltages
122880: 900
245760: 900
368640: 900
460800: 950
576000: 1000
652800: 1050
768000: 1050
806400: 1100
921600: 1150
1024000: 1200

Mine - Hz / mV / Quadrant / Antutu / Linpack MFLOPS
122880: 750
245760: 750
368640: 750
460800: 875
576000: 875
652800: 875 2359 2492 32.306
768000: 875 2422 2485 32.281
806400: 900 2462 2558 34.499
921600: 950 2716 2798 38.368
1024000: 1000 2874 2952 41.729
1113000: 1050 3085 3102 44.007
1209600: 1100 3240 3293 46.445
1305600: 1150 3293 3436 49.054
1401600: 1200 3434 3565 51.463

As you can see 1.4ghz runs perfectly on the stock's voltage for 1ghz. Incredicontrol doesnt seem to let me go below 750mv so there may still be some room for improvement in the low frequencies unless 750mv is a hardware restriction.

Can someone walk me through or link to a guide on how to set voltages permanently without an app? mantera mentioned a script in init.d in the OP but I'm not familiar with scripts.
 
Back
Top Bottom