ARCHIVED: [OC Kernel] Xionia Kernel 2.6.32.33 (v013)

[zefie]

IMO overclocking is unnecessary (on the Optimus S) and kills battery. I underclock my CPU during normal usage. However it is nice for games like pissed off birds.

Underclocking (and even overclocking) really should have no effect on the battery since the voltage is the same.

600 is the same voltage as 825. And anything under 240 is pointless and somewhat dangerous. GetItNowMarketing explained this once somewhere, lol.

 

[erok910]

Thanks zefie and thanks shortie jacobs. I did everything w/o touching a computer. Phone has no issues so far. Its running thunderom 1.5 and the latest kernel on this thread. I still feel like a nanite

 

[Nick7]

Underclocking (and even overclocking) really should have no effect on the battery since the voltage is the same.

600 is the same voltage as 825. And anything under 240 is pointless and somewhat dangerous. GetItNowMarketing explained this once somewhere, lol.

Hmm I didn't know that, thanks zefie. Should we set the cpu governor to performance while the screen is on then?

 

[zefie]

Hmm I didn't know that, thanks zefie. Should we set the cpu governor to performance while the screen is on then?

well, voltage vs watts. i guess it could still save power to underclock. interesting test

 

[cordell]

I use interactive 24/7, overclock widget 245 low 806 high. Screen off 245 low 600 high, no battery issues at all. I find running interactive governor with OC widget takes any jitters the phone had away.

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

 

[quantum_futurist]

Running Higher than 600mhz

I've moved the scale in SetCpu to higher than 600 but it won't go any higher that.
Plus, when I use the widget it only shows my max as being 600 even though I have it set to 768. Should I maybe change the scaling?

LG Optimus

 

[moda.root]

How do I reboot into clockwork recovery and then flash cm6 please help thank a lot

 

[smccloud]

How do I reboot into clockwork recovery and then flash cm6 please help thank a lot

CM6 is still being worked on.

 

[J-I-N-X]

Hey everyone I an running thunderstorm v 1.5 and would like some info on how to flash xion carnal to my optimistic s robot phone please.

I am not picking on you and I'm sure you all know this has been poked at already but seeing this Auto-correction Fail just made my night alot less boring.

 

[Immersion]

Hey guys...quick question. Are there ANY issues with this latest kernel 2.6.32.26? any weird quirks?

and are there other OC kernels for the optimus s?

 

[simon.ponder]

Kernel needed

I've moved the scale in SetCpu to higher than 600 but it won't go any higher that.
Plus, when I use the widget it only shows my max as being 600 even though I have it set to 768. Should I maybe change the scaling?

LG Optimus

Have you made the app look for what the Kernel has available? I know with the OverClock widget, it is under Advanced Settings > Use your frequencies. I believe in setCPU, you need to define the frequencies in a text file in the root of your sd card. You can find the frequencies in setCPU on the INFO tab. Scroll down and you will see the freq's and the time spent on each freq. I would suggest not going over 768, if stability is important. I think the newer version's have an auto-detect feature, which allows the app to look at the kernel for speeds.

Also, don't tell the app to set the frequency on boot until you have tried the frequency and are sure it will not boot loop immediately, or else you will need to re-flash a stock kernel, a ROM that has a stock kernel in it(currently only ThundeRom), or a Nandroid backup.

All of this hinges on the kernel supporting the speeds, of course.

 

[shortyjacobs]

Have you made the app look for what the Kernel has available? I know with the OverClock widget, it is under Advanced Settings > Use your frequencies. I believe in setCPU, you need to define the frequencies in a text file in the root of your sd card. You can find the frequencies in setCPU on the INFO tab. Scroll down and you will see the freq's and the time spent on each freq. I would suggest not going over 768, if stability is important. I think the newer version's have an auto-detect feature, which allows the app to look at the kernel for speeds.

Also, don't tell the app to set the frequency on boot until you have tried the frequency and are sure it will not boot loop immediately, or else you will need to re-flash a stock kernel, a ROM that has a stock kernel in it(currently only ThundeRom), or a Nandroid backup.

All of this hinges on the kernel supporting the speeds, of course.

SetCPU has an autodetect function too, worked great for me. When it first starts up, there's a dialog that asks you if you want to autodetect. If you want to do it again, hit the Menu button then click "device selection".

Edit: Ugh, reading comprehension fail....you said right in your post that it can autodetect, sorry! Also, never realized all the cool stuff under the Info tab. I'm surprised to see that my phone spends the vast majority of it's time, (around 75% at a guess), at 806 MHz...I figured it would have been far less with all my fancy profiles...

 

[quantum_futurist]

Have you made the app look for what the Kernel has available? I know with the OverClock widget, it is under Advanced Settings > Use your frequencies. I believe in setCPU, you need to define the frequencies in a text file in the root of your sd card. You can find the frequencies in setCPU on the INFO tab. Scroll down and you will see the freq's and the time spent on each freq. I would suggest not going over 768, if stability is important. I think the newer version's have an auto-detect feature, which allows the app to look at the kernel for speeds.

Also, don't tell the app to set the frequency on boot until you have tried the frequency and are sure it will not boot loop immediately, or else you will need to re-flash a stock kernel, a ROM that has a stock kernel in it(currently only ThundeRom), or a Nandroid backup.

All of this hinges on the kernel supporting the speeds, of course.

Yeah, I got it to work, finally! As you mentioned I can't get past 729(I think) on mine without it rebooting. You think it'll be able to go higher any time soon? Just a thought.

QuFu

 

[weenerdog3443]

Yeah, I got it to work, finally! As you mentioned I can't get past 729(I think) on mine without it rebooting. You think it'll be able to go higher any time soon? Just a thought.

QuFu

I run mine at 806 daily and occasionally crank it up to 864 with put too many problems. I also have a xouple profiles set up. Runnimg setcpu sry forgot to mention

 

[quantum_futurist]

I run mine at 806 daily and occasionally crank it up to 864 with put too many problems. I also have a xouple profiles set up. Runnimg setcpu sry forgot to mention

You probably did something with the buildprop files or something like that. If you didn't I'd be interested in knowing how you run it so high without rebooting.

 

[shortyjacobs]

You probably did something with the buildprop files or something like that. If you didn't I'd be interested in knowing how you run it so high without rebooting.

It's a hardware thing. Some phones are capable of higher speeds than others, simply because their individual processor chip is a bit more well built than others. It's the luck of the draw where your chip maxes out.

 

[dirtygreek]

Yeah, I got it to work, finally! As you mentioned I can't get past 729(I think) on mine without it rebooting. You think it'll be able to go higher any time soon? Just a thought.

QuFu

Same.

 

[KSmithInNY]

It's a hardware thing. Some phones are capable of higher speeds than others, simply because their individual processor chip is a bit more well built than others. It's the luck of the draw where your chip maxes out.

Yep. My phone can only do 806 and i get occassional reboots but Beezy's can rock 864 without a single issue. He can even benchmark that high

Happens with every phone. When Beezy and I were working on our EVO ROM series, his phone could clock to like 1.2 while mine could only do 1.15.

Come to think of it .... why does his phone always beat mine?!?!? I'll be back, I have to come up with a plan to go jack B's phone

 

[quantum_futurist]

Yep. My phone can only do 806 and i get occassional reboots but Beezy's can rock 864 without a single issue. He can even benchmark that high

Happens with every phone. When Beezy and I were working on our EVO ROM series, his phone could clock to like 1.2 while mine could only do 1.15.

Come to think of it .... why does his phone always beat mine?!?!? I'll be back, I have to come up with a plan to go jack B's phone

I'm so upset mine can't go any higher than 729 Someone wanna trade?

 

[gilbequick]

OK so what's the verdict on running this with ThunderROM? With ThunderROM 1.6.2 is this kernel an improvement over the kernel that comes with ThunderROM?