[barchamb]

abqnm, on 06 July 2012 - 08:38 AM, said:

I know for certain that Jelly Belly/leankernel combo supports it as I am running it right now.

Okay, then can you help me figure out what I'm doing wrong here? If I run CPU Spy, for Kernel Info, it says "Linux version 3.0.36-leanKernel-4.0.0-04197-gf36ff07-dirty...", so I know I'm running the right kernel, right? And, it shows my "Time in State" as 1200 MHz, 920 MHz, 700 MHz, 350 MHz, and Deep Sleep, with some time spent in each of them.

Next, I open Terminal Emulator, type su, then type lt. If I choose the "Current Frequencies at Boot" option, it tells me Max is 1200000 and Min is 350000. Does that sounds right? I thought flashing LeanTweaks was support to set it to 1350000/350000 automatically? Anyway, I use the menus to set my max to 1650000 with Highspeed_freq set to Max Freq With Input Boost. Exit out of lt menus and Terminal Emulator. Run CPU Spy again, and it now shows "Time in State" as 1650 MHz, 1200 MHz, 920 MHz, 700 MHz, 350 MHz, and Deep Sleep, with some time spent in each, with unused states of 1520 MHz and 1350 MHz. Then I go back into Terminal and run lt again and can confirm that "Current Frequencies at Boot" is still 1650000 / 350000. Everything looks good, right?

Now I reboot. Bring up CPU Spy and crap. Now it's working. :-) I have no idea what I did differently this time, but it looks like it stuck. Thanks for listening to me ramble...

[abqnm]

barchamb, on 06 July 2012 - 09:03 AM, said:

Okay, then can you help me figure out what I'm doing wrong here? If I run CPU Spy, for Kernel Info, it says "Linux version 3.0.36-leanKernel-4.0.0-04197-gf36ff07-dirty...", so I know I'm running the right kernel, right? And, it shows my "Time in State" as 1200 MHz, 920 MHz, 700 MHz, 350 MHz, and Deep Sleep, with some time spent in each of them.

Next, I open Terminal Emulator, type su, then type lt. If I choose the "Current Frequencies at Boot" option, it tells me Max is 1200000 and Min is 350000. Does that sounds right? I thought flashing LeanTweaks was support to set it to 1350000/350000 automatically? Anyway, I use the menus to set my max to 1650000 with Highspeed_freq set to Max Freq With Input Boost. Exit out of lt menus and Terminal Emulator. Run CPU Spy again, and it now shows "Time in State" as 1650 MHz, 1200 MHz, 920 MHz, 700 MHz, 350 MHz, and Deep Sleep, with some time spent in each, with unused states of 1520 MHz and 1350 MHz. Then I go back into Terminal and run lt again and can confirm that "Current Frequencies at Boot" is still 1650000 / 350000. Everything looks good, right?

Now I reboot. Bring up CPU Spy and crap. Now it's working. :-) I have no idea what I did differently this time, but it looks like it stuck. Thanks for listening to me ramble...

Glad it is working now. No idea what was going on that it wasn't working though. Also since you are on leankernel, leantweaks has an init.d "Dr" that should get things working again if it stops for some reason.

Sent from my brain using human to phone transport technology.

[icebear]

i noticed that when i enable fast charge it wont let me use PDAnet or even mount to my computer, is it suppose to do this?

[sonicxml]

icebear, on 06 August 2012 - 10:10 PM, said:

i noticed that when i enable fast charge it wont let me use PDAnet or even mount to my computer, is it suppose to do this?

Yes that happens, the phone cant keep a connection to the computer if its using the whole port for charging

Sent from my Galaxy Nexus using RootzWiki

[Reno Skyy]

If I flash this will I get better battery life?

Sent from my Galaxy Nexus using Tapatalk 2

[icebear]

Ok so I flashed the scripts and for some reason the set on boot option won't stick when I reboot my phone on anything. I am running on the jelly belly 6.0 ROM

[blaksmyth]

The download link appears to be down.

Edit: nevermind it just worked

Edited by blaksmyth, 12 August 2012 - 03:47 AM.

[midnight assassin]

Reno Skyy, on 09 August 2012 - 09:11 PM, said:

If I flash this will I get better battery life?

Sent from my Galaxy Nexus using Tapatalk 2

not if you don't know what to do with it.

Sent from my cm_tenderloin using Tapatalk 2

[moosez3]

icebear, on 10 August 2012 - 03:18 AM, said:

Ok so I flashed the scripts and for some reason the set on boot option won't stick when I reboot my phone on anything. I am running on the jelly belly 6.0 ROM

Same thing is happening with me on JB AOKP...

[icebear]

anyone know a fix to fix the set on boot for CPU overclock? GPU does not stick on boot to running Jelly belly 6.4

Edited by icebear, 19 August 2012 - 04:06 AM.