Database Users

[Kernel] - 3-23-11 - v.5b - Impressive Sounding Name Kernel

Most of what is below is still accurate, but see this post for links to the kernel download and important infoshttp://forum.xda-developers.com/showpost.php?p=12397646&postcount=580
1-18-11
v.4 - GB’s Impressive Sounding Name Kernel
* As always, many, many thanks to xcaliburinhand.
* Consolidating Steam and Voodoo/CWM kernels into one thread. The two kernels are the same except for recovery, and jfs support in the Steam kernel.
* Started using a proper changelog
* Implemented Impressive Sounding Name Technology AND Dynamic Naming Technology patches; next update to include Dramatic Use of Imagery, with possible Reference to Mythical Creatures patch.
* Cherry-picked some recent commits not included in JPX source. (Will post source this evening, I hadn’t planned on releasing this just yet, but it seems as though it’s already being packaged into a ROM so might as well, right?)
* CONFIG_ARM_THUMBEE=y, enables ThumbEE processor mode, should give some minor JIT performance improvement.
* config_hz=100. With this value, kernel hz = user hz which eliminates HZ <--> USER_HZ conversions. It should also slightly increase battery life without affecting performance.
* Increased default overclock to 1280 MHz. Your may want to revise your undervolt settings, 1280MHz runs at the same voltage as 1200MHz did/does, so you **may** not be able to undervolt as much at 1280. (Yes, I previously said I wouldn’t go past 1200MHz, but, I feel ok going to 1280 since the voltage hasn’t changed and it’s still well below the max vdd_arm.) Use voltage control or setCPU to limit clock speed if you don’t want to use this. Delete your Voltage Control boot settings before booting this kernel. I’m currently using Voltage Control 3.0a.
* Added Voodoo Sound. I hadn’t really planned on it but there were a lot of requests for it.
* Removed i9000 splash screen and replaced with an old familiar one.
* Want lower screen brightness? I know Hardcore did tinkering with the kernel source to do this, but I really like Screen Filter, it even has a Tasker plugin.
* From previous versions: Backlightnotification 2.3, Voodoo color/video fixes re-enabled against my better judgment and even though single-blind testers couldn't tell me which kernels had it and which did not. .
Downloads of v.4 - The file you want is something like rGB-v.4-011811-XXXXX.zip/tar
By clicking any of these links, you agree to flash delete your Dalvik cache and remove any oc/uv boot settings you have before booting. v.4 ClockworkMod zip at the bottom of this post, tar files of Voodoo5/CWM and Steam below for those of you who like to use Odin.
tar of v.4 with Voodoo5 & CWM recovery
tar of v.4 with Steam recovery
Credits
Xcaliburinhand, supercurio, raspdeep, SztupY, sorry if I forgot anyone else.
Stuff I wrote a while ago and may or may not be accurate any more.
1-6-11
This seems to be stable again. Started over from scratch and added in BLN 2.3. Everyone who was affected by charging problems with the previous kernels has not had a shutdown over the last two days of testing. Hopefully we're good again.
1-4-11
Closed testing on newer kernels until I'm fairly confident the issue is resolved again. I had still been getting intermittent reports of charger instability from the reoriented-balls-1-3-11-ocuv-bln23.zip (#47) kernel. Anyone affected by this please switch back to the 'f' builds below, which is the last known rock solid (I think) version.
-----------------------------------------------------------------------------------------------
This kernel is fast, and this kernel is stable. It's overclocked by default to 1.2GHz, but if you don't want to overclock at all, just install either setCPU or download xan's app which I have attached to this post and set the max clock speed to 1.0GHz. This kernel supports init.d scripts, so you have save your settings and have them load at boot.
1100-1200+ Quadrant score on RFS at 1GHz. 1500-1700+ on /data, /dbdata, and /cache on ext4. ~14.1 Linpack at 1GHz. Compare that to any other kernel available here at the same speed and I think you'll see this one comes out on top. I'm not doing this for donations, I just want to my experience with the phone as good as possible. Since this is a Voodoo 5 kernel, you can also make /system ext4 as well for an even smoother experience. This kernel has great battery life and is very stable as well. And when I say stable, I mean, you can use the phone however you want to, you don't have to do any workarounds to keep it from freezing. (edit - as long as you're using one of the build f kernels it seems...) Although, as always, if you aren't 100% satisfied with any of my products, I will give you a full refund.
What this kernel is -
Kernel for 2.2.1 ROMs, (may work on 2.2, but I haven't personally tested it), built from JPX source, with Supercurio's Voodoo 5, overclocked by default to 1.2GHz with raspdeep's code, and Neldar's backlight notification enabled, and re-oriented with xcaliburinhand's code. The undervolting code has been fixed to keep your phone from dying while charging. I'll not be supporting anything beyond 1.2GHz. I hardly use 1.2GHz myself, and from what I've read, many users (but obviously not all) have stability issues with anything much beyond that. This post from one of the senior Android engineers at Google also struck a nerve with me, and is also part of the reason I'll not support anything past 1.2GHz. Samsung actually wrote most of the code for 1.2GHz into the kernel source but had it commented out, so I don't have a problem providing software that will allow users to push it to that level.
Again, for voltage control, use xan's app. I've attached an older version of the app as I'm not sure if the newer one is backwards compatible with the 'older' methods of power management.
Also, standard disclaimers about how if this blows up your phone or tells your girlfriend she's getting fat, it's not my fault. I've had this kernel on my phone for a couple days, so none of that should happen.
How to install - Either flash in ClockworkMod, or use Neldar's really awesome kernel flashing app.
gb-reorient-12-23-build-f.zip is a zip tarred zImage. Unzip, then flash the tar with Odin, or extract the zImage and flash it with Heimdall or Neldar's kernel flashing app.
gb-reorient-fixed-ocuv-f-cwm.zip is a ClockworkMod flashable kernel.
Some thoughts on undervolting
The whole point of undervolting is to safely do the same amount of work with your CPU while using less energy (ie more battery life). Your phone is idle most of the time, so you can the most from undervolting lower frequencies more. Undervolting is safe WHEN you find the settings that work for your phone. Generally, -75mV seems to be stable for everyone. If you want to push it further, go ahead, but realize that if you push it too far, you phone will freeze, and you'll have to pull the battery. Relatively harmless, but, be aware it can happen. Personally, my phone is perfectly stable at the following settings (from 100MHz to 1000MHz) -125mV, -100mV, -100mV, -100mV, -75mV. These settings may not work for your phone. You might find that you can get by with undervolting a little more, but your system will freeze randomly, so if that happens, don't undervolt as aggresively. So, for example, I found that I can usually get by with -150, -125, -125, -125, -100, but every once in a while the phone will freeze up. And since I want a stable system, I've backed down from that. I can't tell you what to do though, but keep in mind that undervolting too much may lead to system instability.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.

Thanks. Going to try it now.

I flashed 'em at 94%, so we'll see.
But FWIW- I think I've had MAYBE 2 charge deaths when I was on perception. But I was using Setiron's kernels, so I dunno...
I'll report back in a bit.. gonna let it over-charge for a bit and see what happens.

Darky 7.0.1 with your kernel and 100% battery power for 2.5 hours plugged in to the wall and no power off yet. Hopefully this is the fix, I am tired of leaving my computer on all night to charge on usb

thank you so much for this...been looking for something exactly like this, and seems sleep death is gone

darky 7.0.1 here also.
I had it charge around an hr and a half past 100% and no death!
So we'll see how it does overnight

I'll try it out and let you know how it goes, i charge by ac overnight so I should have the results of it to you by morning I'm using it with Assonance 5.2 by the way.

Well no charge death for me last night...
Sent from my GT-I9000 using XDA App

Absolutely no problem, left on ac all night with an undervolt and everything. Great job with this, it made oc/uv usable for me.

Doc's 6.1.3 + your kernel = 100% joy
I found your thread last night after a long and happy Christmas day with the family. Followed your instructions to the letter. Charged overnight from 45% and woke up to find the phone operating fine. This might be the answer to all our prayers!! Thank you so much!

Runs great with eugenes ginger clone. Slightly better benchmarks than other rom/kernel combos. I peak out at 1.3ghz so 1.2 seems like a good medium. One request though is to look into changing the divider for the gpu. I know we don't need it but its good for bragging. Unhelpful had this and I could set the gpu down to 166.750 For lower clocks to save battery and up to 222.334 (stable) for benchmarks. I never tried other clocks so I don't know if it would work on other settings. It depends on how his code works. but it seems by my math the gpu is divided off a 2000 or 2001mhz frequency. There is a margin of error I guess. and stock is divided by 10. In unhelpfuls code it is divided by 9 (222.334) default but could be set to 10 or 12. If we bump that up to 15 or 20 we might reduce battery consumtion with a gpu clock at 133 or even 100mhz. Id also like to try the divider at 8 for 250mhz. Im curious as to how that would benchmark if its stable.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Ive been charging since 2pm yesterday and its still on. I think you got the fix

No problems here charging overnight. For those who care about quadrant scores, mine was about 250 points higher than the other 1.2ghz kernel I was using.

I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.

opcow said:
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
Click to expand...
Click to collapse
Same here, battery life seems better..I've noticed it not draining so quickly, im at 85% when usually id be at 50-60%
Sent from my Captivate

I've found Darky's 7.01 works best on my phone, could it be true this makes it run faster? Do I need to have full charge or can i flash this at any battery level?

I didn't look at the actual quadrant score. But my fps is on average about 2-3 greater. Similar to running at 1300 on other kernels. Battery life is much improved over the kernel in eugenes ginger clone rom.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

I just flashed it over SetiroN 1.5.6 and can see a speed difference already. 1200 O/C is perfect, I really like the kernel. Working great on Darkys 7.0.1

I too just installed over Darky's 7.0.1, bit more speed is noticable but i mainly did it for the possibility of better battery because right now thats all i am after.

i just installed but i want some more about voltage control
how can i modified that option?
thx a lot!

set cpu

OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.

btucker2003 said:
OK for those that boast supreme bat life and performance please share your "EXACT" setup for set CPU, rom, kernel etc. Pretty please.
Click to expand...
Click to collapse
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.

The best thing I did was uninstall setcpu and let the custom kernel work,
Sent from my Nexus S 4G using xda premium

Currently running Taboonay 2.1b with rtrip's custom kernel 3.4 - it had issues with setcpu so I uninstalled it and am letting the kernel do it's thing - OC'd t 1.4 and it's smooth and fast but still has a decent battery life despite running a bunch of stuff, games, music, email and navigation - wifi on always...
Standby is about 3.5 days / on constantly about 7.5 hour life, so..yeah...Me likey..
YMMV

kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.

kjy2010 said:
I'm guessing you're looking to underclock your CPU right?
Because "supreme bat life" and overclocking in the same sentence is an oxymoron.
Click to expand...
Click to collapse
_motley said:
LOL, I was wondering the same thing about "boast supreme bat life and performance". This reminded me of my days of tuning cars and we we used to say "Fast, cheap, and reliable. You can have 2 of the 3."
OP, all machines won't react exactly the same way and people use their tablets for difference purposes, so having others post exactly what they have setup probably isn't the best way to go. First, you need to find a kernel that works and is stable for everything you need. Kernels are changing all the time, sometimes they move two steps forward and 1 step back before they are stable again and support everything a user needs (docking, NTFS mount, cifs, 3G etc.). After you find a kernel that is stable and suits your needs using the defaults, then you can take it a step further if you wish.
If you want a performance minded setup, setup a profile (in setcpu or one of the others) using the desired clock speed. Try 1.4 or 1.5 Ghz to start as that seems to work for most. Use the governor recommended by the kernel developer for best results. The more you over-clock, the more battery you will consume.
If things are stable with the default voltages, then experiment with under-volting to get the best battery life you can for your performance profile. Start with the recommended voltages with your kernel and adjust down -10uV at your max CPU frequency to find out how much voltage you can reduce and still have a stable system. Make sure you run through all the things you typically do and give it a good workout before moving down to another voltage. Using benchmarks can be helpful for finding stability, but may not match how you use the tablet in the real world.
If you want the best battery life, then experiment with under-clocking to 912MHz and then try under-volting that clock speed to find your stable point. You could then setup a setup "battery mizer" profile for that.
If this sounds too difficult and time consuming for you, then do as the others have stated and just install a custom kernel that does what you need and let it work for you. It should give you a good "in-between" setup. For me, I am addicted to 1.5GHz as the increased smoothness from stock is very noticeable for me. I can recharge every night after 6 hrs or so, so this works great for me. If I go on the road and need to take it easy on the battery, I use another profile to get better battery life for the time being.
Hope this helps you out.
Click to expand...
Click to collapse
Hah! Well thanks but I'm pretty sure I didn't say "overclocking" but gotcha thanks for the feedback and answers. I was merely looking for setups compared to what I'm running now. TIA

[Q] No 'Battery Life' ROM for the Nexus 7?

Correct me if I'm wrong, but I've seen loads of ROMs all about adding speed to the Nexus 7, and most of these ROMs also advertise better battery life, but I've not found any that actually have better battery life than stock, and I haven't seen any ROMs with a main purpose of increasing the battery life.
Also, it might be just me but I'm really satisfied with the speed of the stock ROM so I don't see much need to speed it up!
Franco Kernel did increase my battery life but I can't use it on 4.2.2 as it locks up my device into deep sleep. Other kernels I've tried have increased performance but not battery life. I have tried Elite Battery Saving kernel but that's for an old version of android, so to revert back in kernel would be reverting lots of the changes in kernel that have been done by Google I think (I know there were a lot of changes from 4.2.1 to 4.2.2?)
So my question is, is there a ROM / Kernel combination out there that is just trying to increase the battery life?
Thanks a lot. No disrespect to the hardworking devs that work on speeding up the Nexus 7; it's just my personal opinion.

Roms have little impact on battery life. Its primarily going to be a combo of the kernel and your own unique settings. Want to see anecdotes regarding other users' results with different kernels? There a thread for that.
Sent from my Nexus 7 using Tapatalk HD

As najaboy stated, it's a combination of kernel and user settings.
Note that custom kernels have governors, which regulate cpu core active states, and mhtz. Suggest you read up on custom kernel governors to get the most.
Also, we have a thread pertaining to this;
http://forum.xda-developers.com/showthread.php?p=38092846#post38092846
As "Best Rom-Kernel" threads are not allowed, however, that thread is dedicated to it.
Thread Closed.
MD

[Q] Best Kernel to UV, reduce heat and extend battery life

I have been testing different Kernels and settings on my fast binned Nexus 4, what I am trying to achieve is a similar experience to stock kernel and being able to undervolt and maybe even have sweep2wake.
In my experience AK and NEO gave me the best results in Antutu (which I don’t care much about) but I am not sure if they respect the thermal throttling settings, I don’t feel good knowing that my phone will be producing more heat than on stock so the questions are:
What kernels respect the thermal throttling settings as the stock kernel?
Some kernels allow you to set some SOC temperature settings in “Trickster”, what are does? Is that only for the maximum temperature before the phone shuts down?
Thank you guys.

theres no such thing as a best kernel. all our devices react differently with every kernel, and we all have differing needs. try them all out, thats the only way that you will find the best lernel for your device.

simms22 said:
theres no such thing as a best kernel. all our devices react differently with every kernel, and we all have differing needs. try them all out, thats the only way that you will find the best lernel for your device.
Click to expand...
Click to collapse
My questions where a bit more specific than just “whats the best kernel” as I said in the frist post:
*What kernels respect the thermal throttling settings as the stock kernel?
*Some kernels allow you to set some SOC temperature settings in “Trickster”, what are does? Is that only for the maximum temperature before the phone shuts down?
I want a kernel that has similar or same thermal throttling settings as the stock kernel, I don’t want my phone making more heat and I want to be able to undervolt and maybe even use sweep2wake, all this was said in the original post but thanks.
I have tested franco kernel, AK and NEO but I am not sure about theyr thermal throttling criteria and/or settings, I have tried researching but I cant come to the conclusion if they produce more heat than stock or not.

simms22 said:
theres no such thing as a best kernel. all our devices react differently with every kernel, and we all have differing needs. try them all out, thats the only way that you will find the best lernel for your device.
Click to expand...
Click to collapse
Nice post.
We don't want to hurt any developers feelings by saying who's work is better. lol
thread closed.

[Q] [L4-II] Weird Governor Behaviour

Hello guys, i have a small problem with my rooted L4-II, i've searched the web and the forums and i can't seem to find anything on the subject.
I noticed for the last couple of days that my CPU governor changes itself to "performance" whenever it feels like... I use SetCPU to manage my CPU and created a profile to try and force it to stay in "hybrid" (the default governor on this LG Rom), but it still happens.
I already tried other programs (Andromizer, Rom Toolbox, Antutu CPU Master), but the governor seems to have a will of its own and it randomly switches to performance by itself, changing back to the default "hybrid" when i set it again manually, and it stays there for a couple of hours (only to switch again to "performance" later on)
I've tried to find if this was related to some app, but nothing. I'm starting to think that the stock LG/MediaTek kernel has some weird bug that makes the governor switch when it detects a sudden demand for full CPU load, even if it's just for a few seconds. Just a guess.
Has anyone encoutered this problem? Any ideias? Any way to eliminate the "performace" governor from the system or prevent it from being set?
Thank You.

Hello mate! I'm sorry, my post may be won't help you much, but I wanted to share some of my experience too. I have unrooted, fabric LG L5 II phone. It gives me average battery life of around 2 days - 2 days and a half with heavy usage and up to 5-6 days with only 2G/GSM/SMS usage.
This is why I've never needed to change my CPU governor. Excuse me for asking, but what is your battery life and why have you decided to change your governor? In my case I don't need to think about it, don't know how it is with you.
My advice is to clean the cache of your device and if you have rooted it to try Greenify app. It is a new breed of Task-killer and may be it will help you reach better performance/battery life ratio.
Don't mind me asking, but do you have root privilleges on your phone? And if you have can you share your "rooting steps", because I want to root successfully my LG L5 II phone.
Cheers!

mutha88 said:
Hello mate! I'm sorry, my post may be won't help you much, but I wanted to share some of my experience too. I have unrooted, fabric LG L5 II phone. It gives me average battery life of around 2 days - 2 days and a half with heavy usage and up to 5-6 days with only 2G/GSM/SMS usage.
This is why I've never needed to change my CPU governor. Excuse me for asking, but what is your battery life and why have you decided to change your governor? In my case I don't need to think about it, don't know how it is with you.
My advice is to clean the cache of your device and if you have rooted it to try Greenify app. It is a new breed of Task-killer and may be it will help you reach better performance/battery life ratio.
Don't mind me asking, but do you have root privilleges on your phone? And if you have can you share your "rooting steps", because I want to root successfully my LG L5 II phone.
Cheers!
Click to expand...
Click to collapse
Hello there.
My battery life is very good, 2 and a half days minimum, and up to 4 days without charging, but that's not the point. I don't want to change the CPU governor, i just want it to stay in the stock setting, instead of changing itself to "performance" without me doing anything. The only reason i use a CPU manager is to downclock to 500Mhz when the battery is below 15% when i'm at work because i can't charge it there.
I've already cleaned cache and dalvik but all is the same.
I had a Xperia for 3 years and used a ton of different Roms, from 2.3.7 all the way to JB 4.1.2 and never saw such behaviour from the CPU governors.
I've rooted my phone using V-Root and MtkTools as suggested in a thread here on the forums made for the L5-II, it worked perfectly, it's the easiest way to do it.
http://forum.xda-developers.com/showthread.php?t=2343579

JBolho said:
Hello there.
My battery life is very good, 2 and a half days minimum, and up to 4 days without charging, but that's not the point. I don't want to change the CPU governor, i just want it to stay in the stock setting, instead of changing itself to "performance" without me doing anything. The only reason i use a CPU manager is to downclock to 500Mhz when the battery is below 15% when i'm at work because i can't charge it there.
I've already cleaned cache and dalvik but all is the same.
I had a Xperia for 3 years and used a ton of different Roms, from 2.3.7 all the way to JB 4.1.2 and never saw such behaviour from the CPU governors.
I've rooted my phone using V-Root and MtkTools as suggested in a thread here on the forums made for the L5-II, it worked perfectly, it's the easiest way to do it.
http://forum.xda-developers.com/showthread.php?t=2343579
Click to expand...
Click to collapse
Thank you for the information, JBolho! My previous phone is Samsung Galaxy Spica and I was using modes since forever, because my original Android was 1.6 :laugh: and it was quite laggy on my phone. So I know what you mean.
I wish you good luck.