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

Root giantpune's custom kernel

I also am unsure as to how we go about selecting governors, is there an interface we can use or can we run terminal codes....?


Set them in an app like setcpu or cpu master.
Also.. what would happen if I edited the value in scaling_max_freq and cpuinfo_max_freq to a higher number? Kernel panic? I wanna see if this thing can handle 2GHz.
 
Upvote 0
Sorry but I'm just confused...haven't flashed recovered backed up etc since the last big update from IHO.So my question is how in the hell do you Get the over clocked kernel and what file? Smh

Do you have ClockWorkMod? If not, follow these instructions:
http://androidforums.com/elite-all-things-root/620742-clockworkmod-optimus-elite-faq-guide.html

After you have CWM, download the latest update in the OP to your phone, boot in to recovery by powering on your phone while holding the down volume key, make a backup, and flash the new kernel by going to "install zip from sd card" in recovery.
 
Upvote 0
You're most likely right. Just a thought from seeing those values in those files. They were set to what the max is now. I could try it.. if I wanted to possibly brick my phone.. good thing I have my trusty nandroid :)

You can allow further overclocking by adding more values in acpuclock-7x30.c (in the kernel source) but you have to provide appropriate voltages as well. I wouldn't be surprised if this thing could overclock to 2.0GHz but it might be dangerous and would severely decrease the lifespan of the CPU.
 
  • Like
Reactions: landonh12
Upvote 0
There is a link to the source in the first post. And there is a table already of frequencies and voltages that goes up to 1.9GHz. Only certain frequencies are added to the list for scaling, with the highest one at 1.6Ghz. You should be able to tell it to use the 1.9GHz manually. I personally feel that 1.6 is already at the line, and never have tried any of the ranges above that.

This is the full table. Entries that start with a 1 as the first parameter are used for the auto-scaling governors.
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
	{ 0, 24576,SRC_LPXO, 0, 0,  30720000,  900, VDD_RAW(900) },
	{ 0, 61440,   PLL_3, 5, 11, 61440000,  900, VDD_RAW(900) },
	{ 1, 122880,  PLL_3, 5, 5,  61440000,  900, VDD_RAW(900) },
	{ 0, 184320,  PLL_3, 5, 4,  61440000,  900, VDD_RAW(900) },
	{ 1, 245760,  PLL_3, 5, 2,  61440000,  900, VDD_RAW(900) },
	{ 1, 368640,  PLL_3, 5, 1,  122800000, 900, VDD_RAW(900) },
	{ 1, 460800,  PLL_1, 2, 0,  153600000, 900, VDD_RAW(900) },
	{ 1, 576000,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 652800,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 768000,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 806400,  PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[0]},
	{ 1, 921600,  PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[1]},
	{ 1, 1024000, PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[2]},
	{ 1, 1113000, PLL_2, 3, 0, UINT_MAX, 1050, VDD_RAW(1050), &pll2_tbl[3]},
	{ 1, 1209600, PLL_2, 3, 0, UINT_MAX, 1100, VDD_RAW(1100), &pll2_tbl[4]},
	{ 1, 1305600, PLL_2, 3, 0, UINT_MAX, 1150, VDD_RAW(1150), &pll2_tbl[5]},
	{ 1, 1401600, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200), &pll2_tbl[6]},
	{ 1, 1516800, PLL_2, 3, 0, UINT_MAX, 1250, VDD_RAW(1250), &pll2_tbl[7]},
	{ 1, 1612800, PLL_2, 3, 0, UINT_MAX, 1300, VDD_RAW(1350), &pll2_tbl[8]},
	{ 0, 1708800, PLL_2, 3, 0, UINT_MAX, 1350, VDD_RAW(1350), &pll2_tbl[9]},
	{ 0, 1804800, PLL_2, 3, 0, UINT_MAX, 1350, VDD_RAW(1350), &pll2_tbl[10]},
	{ 0, 1900800, PLL_2, 3, 0, UINT_MAX, 1450, VDD_RAW(1450), &pll2_tbl[11]},
 
Upvote 0
There is a link to the source in the first post. And there is a table already of frequencies and voltages that goes up to 1.9GHz. Only certain frequencies are added to the list for scaling, with the highest one at 1.6Ghz. You should be able to tell it to use the 1.9GHz manually. I personally feel that 1.6 is already at the line, and never have tried any of the ranges above that.

This is the full table. Entries that start with a 1 as the first parameter are used for the auto-scaling governors.
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
	{ 0, 24576,SRC_LPXO, 0, 0,  30720000,  900, VDD_RAW(900) },
	{ 0, 61440,   PLL_3, 5, 11, 61440000,  900, VDD_RAW(900) },
	{ 1, 122880,  PLL_3, 5, 5,  61440000,  900, VDD_RAW(900) },
	{ 0, 184320,  PLL_3, 5, 4,  61440000,  900, VDD_RAW(900) },
	{ 1, 245760,  PLL_3, 5, 2,  61440000,  900, VDD_RAW(900) },
	{ 1, 368640,  PLL_3, 5, 1,  122800000, 900, VDD_RAW(900) },
	{ 1, 460800,  PLL_1, 2, 0,  153600000, 900, VDD_RAW(900) },
	{ 1, 576000,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 652800,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 768000,  PLL_1, 2, 0,  153600000, 950, VDD_RAW(950) },
	{ 1, 806400,  PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[0]},
	{ 1, 921600,  PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[1]},
	{ 1, 1024000, PLL_2, 3, 0, UINT_MAX, 1000, VDD_RAW(1000), &pll2_tbl[2]},
	{ 1, 1113000, PLL_2, 3, 0, UINT_MAX, 1050, VDD_RAW(1050), &pll2_tbl[3]},
	{ 1, 1209600, PLL_2, 3, 0, UINT_MAX, 1100, VDD_RAW(1100), &pll2_tbl[4]},
	{ 1, 1305600, PLL_2, 3, 0, UINT_MAX, 1150, VDD_RAW(1150), &pll2_tbl[5]},
	{ 1, 1401600, PLL_2, 3, 0, UINT_MAX, 1200, VDD_RAW(1200), &pll2_tbl[6]},
	{ 1, 1516800, PLL_2, 3, 0, UINT_MAX, 1250, VDD_RAW(1250), &pll2_tbl[7]},
	{ 1, 1612800, PLL_2, 3, 0, UINT_MAX, 1300, VDD_RAW(1350), &pll2_tbl[8]},
	{ 0, 1708800, PLL_2, 3, 0, UINT_MAX, 1350, VDD_RAW(1350), &pll2_tbl[9]},
	{ 0, 1804800, PLL_2, 3, 0, UINT_MAX, 1350, VDD_RAW(1350), &pll2_tbl[10]},
	{ 0, 1900800, PLL_2, 3, 0, UINT_MAX, 1450, VDD_RAW(1450), &pll2_tbl[11]},

In other words, when you made/edited the kernel, you chose what would be the greatest yield when combining speed, stability, and compatibility? You're awesome, man.
 
Upvote 0
Anyone having issues with phone not entering Deep Sleep?

Noticed my battery was dropping quick so I checked all the usual and cpuspy shows it's staying at 245 and not entering deep sleep. No apps are running that would prevent thing and I'm pretty sure it was before.

I'm not so sure I've checked it on newest kernel but I know on previous it would hit Deep Sleep... Just wondering if anyone else is having issues

Depending upon which app you have to control your governors, that could be influencing it. The app I'm using requires the deep sleep mode to be check marked in settings to include it.
 
Upvote 0
rumor has it that the boot image from the VM phone will work on the Sprint one, but wifi doesn't work. I compared the source for the Sprint v9 and VM v5 kernels, and the only functional changes I saw were having to do with the diag interface. You may be able to stick the stock Sprint ramdisk into the boot image and magically fix the wifi.
 
Upvote 0
Yeah, I'm a bit new to the Android Forums but am more non-new-ish over at Android Central. I plan to get the Optimus Elite one of these days. Then, I wanted to see if I could flash one of the custom roms here in the forum and a custom kernel, too, as soon as I get set up.

Anyway, how would I go about getting the Sprint ramdisk into the boot image of the kernel?
 
Upvote 0
For those of you overclocking to 1.5/6 how has the battery life been?

It can be good if you use an app or some other way to change the scaling. If you leave it set to ondemand (default), it will stay at 1.6 most of the time, which certainly lessens the battery life. I use smartassV2 scaling via the SetCPU app and the battery life is pretty good.
 
  • Like
Reactions: mcgraham89
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones