Database Info

Can't overclock my Nexus S

Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.

Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.

I've tried this already dude, probably should of mentioned it in my steps cheers anyhows

risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?

kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )

risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon

I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.

Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.

What the heck? I keep hitting edit but it keeps quoting =( please delete.

sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!

Blah please delete.

I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.

sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?

I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App

sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.

Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.

Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.

[KERNEL][28 APR]LorDMod|SMARTASS|BFSv400|CFS|SLQB|UV|1.99GHz|VOL|V DD|SQ LITE3|

http://forum.xda-developers.com/showthread.php?t=1020637
DON'T USE THE ROM, IT IS OUTDATED AND HAS BEEN DISCONTINUED!
DO NOT USE THE "PUV" (Pinky UnderVolt) VERSION, IT WILL CAUSE YOUR DEVICE TO GET STUCK AT THE SPLASHSCREEN! (POSSIBLY)
I DID NOT MAKE THIS KERNEL, I'M JUST POSTING IT HERE FOR YOU ALL.
THIS IS NOT FOR ANY OTHER ROMS BESIDES CM7 (AND CM7-BASED ROMS) AND MIUI, SO DON'T ASK!
I'm using the UUV CFS version. It is very fast and smooth, I urge you not to have an OC past 1.3GHz as a daily driver, unless you want horrible battery life.
Any option below PUV is safe (UUV, -50mV, and -25mV all work, but every device varies).

i didnt think my phone could ever sh*t itself until i flashed this kernal.

dethpikil said:
i didnt think my phone could ever sh*t itself until i flashed this kernal.
Click to expand...
Click to collapse
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?

vln004 said:
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
Click to expand...
Click to collapse
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.

Been running his kernels for a couple of weeks, no issues. It is nice to be able to choose from different undervolt versions. Helps battery life a little, around 5%-10% in my experience.

NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.

henrybravo said:
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
Click to expand...
Click to collapse
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk

dethpikil said:
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Click to expand...
Click to collapse
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.

rasroygbiv said:
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Careful, the PUV version softbricked my device. Easily fixable through reflashing your ROM or just a new kernel.
It may not brick yours because some devices can handle it, some can't.

helushune said:
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
Click to expand...
Click to collapse
+1. Not "iffy" at all.

I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App

TheBassman369 said:
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm currently pulling two days at 64% with the same kernel but my CPU settings are 122 min - 1075 max.

So what's everyone recommendations for the best version of this Kernel in terms of both optimum battery and performance?
Additionally... what kinds of CPU governors and max-min frequencies are you using? I've seen a few post what their using in this thread, but I'd like to get some more opinions.

I've been using this Kernel for a few weeks now with no issues. The UUV had some slight hesitation when scrolling so now I'm running 4.3 CFS with the -50 UV and it's absolutely perfect. Fantastic battery life running at 122/1305 MHz with the -50 UV.

i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.

substance12 said:
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
Click to expand...
Click to collapse
Default is no undervoltage.
Cell Standby and Phone Idle are my two biggest "battery killers" but that's normal operation.

henrybravo said:
+1. Not "iffy" at all.
Click to expand...
Click to collapse
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.

Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?

dethpikil said:
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Click to expand...
Click to collapse
I sure did. Pardon.
sugardaddy1979 said:
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
Click to expand...
Click to collapse
Check these two posts: Post 1, Post 2. Looks like BFQ is the standard scheduler and VIO is quicker on paper (kind of like BFS vs CFS).

Thanks for the explanation. The bfqhs seems much smoother than the io. I am running it with the uuv.

[Q] Fix for G2X sleep of death?

The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!

I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.

No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.

Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.

You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.

I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.

I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.

For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.

viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.

I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App

regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?

I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.

viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.

What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk

noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App

If missing with software and settings dont work you may just have a bad phone.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.

I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.

For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA

[Q] Noob questions on G2X OC/UV...

I recently rooted my P999/G2x and installed CM7.1.0.1, and am extremely happy with it. Am looking to tinker just a *little* bit more, but have some questions... I have LOTS of answers on the forums, but am somewhat skeptical about the currency of some of the information out there (let's face it, stuff changes fast!). So, down to it:
Kernels:
- Did CM7 overwrite the stock kernel?
- I understand the benefits to changing the kernel; what about drawbacks?
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
- Recommendations on a good, reliable kernel to use w/ CM7? I am looking at faux123's CM and morific's Trinity. Thoughts?
OC/UV:
- Can you OC on stock/CM7 kernel?
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
Thx in advance!

- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!

Using eagle blood (cm7 based) with faux kernel.
I heard trinity kernels may have random reboot but don't quote me on that.
Try faux kernel with oc/uv. Its very good, latest is 0.48. But if you go with the ds version (debaouch?) The battery percentages are all over the place... Lol one minute its 50% the next it may be 34%...
Use set cpu. I've uv additional 25mv across the board with no I'll effects. Screen off profile at 503 mhz max and some other profiles will have you getting 24hours easily with normal usage.
Make sure test it out before you "set on boot"...
Sent from my LG-P999 using XDA App

I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?

Trinity ELPmax with Phoenixblood is the best combo. Trinity batterylife is amazing. When i leave the house my phones battery is 100%. 11 hours later (I when i make it home) my battery is always under 60% but never less then 40%. I play music as soon I leave the house, and till I get in the house. I also turn of data when not using and have setscpu set to 900mhz max and screen off profile set to 432 max 216 min.
Just my personal results

e4e5nf3nc6 said:
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Click to expand...
Click to collapse
+1 to everything you said
just to add if you want to over clock then go with faux or trinity. the cm7 kernel is faster then both @1000mhz, if speed is what your looking for without the dangers of oc. The stock cm7 kernel also lacks the ability to under volt soo battery life might not be as good though

Rbern144 said:
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Click to expand...
Click to collapse
Format data/ factory reset.
Wipe all cache.
Format system. (don't forget)
Flash cm.
Flash kernel.
It may take a while for the system to boot, 5 min. Let it load, and reboot, enjoy.
Sent from my LG-P999 using XDA App

[kernel][TW][ML1 v4.0, 1/11/14] Leankernel: Minimalistic Kernel by Imoseyon

Imoseyon gave me permission to link his kernel here on XDA. Please thank Imo on here or RootzWiki, and please donate to him if u can.
ICS and JB kernels are available.
v 4.0 is the newest version for TW JB 4.3 ML1 only.
Older versions are available (4.1.2)
Experimental builds are also posted on RW. I personally dont want to link them here since I cannot help if something goes wrong. So keep an eye on the RW thread if you can help in testing.
Link to OP/ICS kernel http://rootzwiki.com/topic/31329-ke...el-minimalistic-kernel-ics-v13-jb-v03-112512/
Link to JB kernel changelog https://github.com/imoseyon/leanKernel-d2vzw/wiki/TW-ChangeLog
Link to source https://github.com/imoseyon/leanKernel-d2vzw
All credit goes to Imoseyon
Please feel free to post results from Roms.

OK so running this on jelly beans b 4 and it is super fast. Works like a champ! Great work imoseyon. I tried ktoonsez and this way smoother on touchwiz. Like butter baby!
Sent telepathically

Are there any custom governors with this kernel?
Sent from my SCH-I535 using Tapatalk 2

No just three. Not as many options but already set out of the box so to speak. Changed my io scheduler to deadline and let her rip.
Sent telepathically

I hope to have interactiveX running on it before the 1.0 release.
Also, you can find the change logs here: http://revision.io/embeds/leanKernel-galaxys3-tw

Thanks for sharing.

Running fine on clean Rom 5
Sent from my SCH-I535 using Tapatalk 2

does not work with Taste of Beans 3.5k at all..
color flux
removed boot animation
reboots
battery gets SUPER HOT!
had to do a batt pull, boot into recovery, and go from there.

Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean

Metfanant said:
Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Click to expand...
Click to collapse
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.

Imoseyon said:
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
Click to expand...
Click to collapse
So it would be "stress" related sorta...but more heat related specifically?...its a bummer because my phone does not like 1900mhz at all...and really starts to heat up/lag at that clock speed...
So if the kernel is going to "reset" all the time I'm gonna have to stick with 747 because its the only one (except stock vzw jb) that sticks no matter what I throw at it
Edit: I will however say...the kernel is completely compatible with Synergy 118...and like I said before...when it initially booted the phone was screaming...and performing better than ever...
So keep up the good work and I'll keep my eye on things...
I didn't run your kernel on ICS...wishing I had tried it out now lol
sent from my VZW Galaxy S3 running Synergy Jelly Bean

Despite what a previous user said I'm running this on tasteofbeans 3.5 with no issues. I've ran both 0.2 and now 0.3
Sent from my SCH-I535 using Tapatalk 2

Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2

TheGman125 said:
Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This is for TW roms not for aosp roms, imos has his aosp kernel in rootz
Sent from my SCH-I535 using xda app-developers app

Sorry to hear Met. My phone has never run so well. I'm not experiencing any heat ups or problems set at 1700mzh. When I I run Vellamo it lists the kernel max at 1900mhz but when I check setCPU its locked at 1700mzh. I ran LK on ICS and it was simply amazing. It was the only thing I missed moving to JB. Plz remember that this kernel is just days old and it will continue to get better with updates from Imo. Keep the reports coming guys, it's the best thing to do to help.

What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically

Any chance of Call Recorder kernel support Imo? I only ask becaues several of your kernels for other phones I have owned did support it.

jdub251 said:
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically
Click to expand...
Click to collapse
I would not use KTweaker with this kernel. I remember reading some where its specific for KT kernel. I have had issues using Android Tuner and system tuner on previoulsy used Rom/Kernels as well. I use SetCPU and it works great, I know its a paid app but its so worth it especially if you plan on using custom kernels. Theres a free setCPU version floating around but that app isnt supported anymore.

V.3 locks my cpu to 1900mhz...so i reverted back to v.2 and all is well. 11180 antutu bench mark @ 1520mhz, 10080 @1900mhz

For the ppl not needing to OC try v.2, u might have better results.