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!
Related
Ok so I have searched all over the forums and through google to find an answer to this and I can't any where so here goes. I am currently running the syndicate rom with the extreme kernal installed and when I go to use set cpu I have it set to conservative but any time I try to limit the cpu speed with the sliders it doesn't tae effect. The green numbers above the sliders will change stating my preferences but the white numbers that show the actual speed of the processor will continue to climb past my desired bottleneck. It looks like thecpu always stays between a range of 200 mhz and 1.2 ghz no matter what I set it at. If I change the style to something other than conservative it will change the behavior like performance will keep it at 1.2 or what I select and battery saver will keep it at the minimum. On demand and interactive seem to respond as well but are a little buggy and any little touch on the screen will make the processor jump straight to the maximum and stay there fr a bit which I would assume would kill my battery quite a bit faster. Does any one know if this is an issue with the phone, rom, kernal and if there is maybe a better settng than conservative or a different kernal I could use I was looking into the phoenix or fluff kernal. Any help or recomendations would begreatly appreciated. Thanks
Sent from my SPH-D700 using XDA App
Its been a long time since Ive used it (2.2.1 scales pretty good) if I remeber right,interactive is what you want to select,but on some kernels conservtive is what you want to select.I never used the profiles,I think they dont work all the time.
That's odd I never had that problem with syndicate. And I know for sure that almost every overclocking kernel recommends conservative, for some reason the other profiles can cause problems. There's a couple things that I've learned.
Conservative, for one thing, is never going to be an on demand setting. Typically it will just up the cpu to the max you set it at whenever there is some sort of activity on the phone. Which begs the question, what do you have the max set at? if its 1ghz, remember that the kernel is overclocked, so a setting of 1ghz will allow you to go to 1.2ghz. (I'm almost positive you don't want to set it at 1.2, because then it will peak higher than that) I think the max you set it to should be the listed physical limit of the processor (ours is 1ghz obviously), and the overclocking handles it from there (at least that's been my experience).
Also, remember that when there is no activity (your phones in your pocket), the cpu will be at your minimum. So you save battery in that regard, because with out setting cpu limits, like if you're running stock, I think it might run at the max all the time. (I don't that for a fact tho) again, we pretty much have to run conservative, (I've read its something to do with these hummingbirds and setcpu and overclock widget aren't built fot them) so its an all or nothing deal, you can't get "just enough" processor setting.
Try creating different conditions to help yourself out. When I had syndiccate I had a different setting for the screen being off, for being plugged in to a wall, for being plugged in to a computer, and for being below a certain battery %. Those are really cool features and help out a lot.
And as far as other roms...I use baked snack right now with his ultimate kernel. Its only sllliggghttly less stable than syndicate (but most most most defintly stable enough for a daily driver), and I get much better battery life and performance. He recommends using overclock widget, which isn't as flexible as setcpu, but defintly gets the job done. You'll have to google baked snack and find his website since they kicked him off of here.
Hope that helps, let me know if I didn't quite answer your question correctly.
Sent from my baked and emotionless SPH-D700
From my experience,you need to set it to 1.2 to activate OC...That being said,there are some kernels that need the interactive setting to work right...and 2.2.1 scales to the lowest setting when screen off even without setcpu,thats why I dont use it anymore.I will again once we have an official OC kernel for 2.2.1.
Sent from my SPH-D700 using XDA App
I actually used to have bakedsnacks rom and I liked it but it became a bit glitchy on me but I did think the battery life was a bit better. I only am using eclair as I want to wait for a final build of froyo to come out from sprint so the developers can utilize it better. I tried some of the leaked ones but I prefered the 2.1 better, all of the 2.2 ones were missing minor things that I used so I switched back. Also interactive setting just keeps the processor at max clock for a really long time before it scales back down and I didn't like that. Has anyone used the fluff ondemand kernal that is supposed to be for bettery battery life with syndicated 2.1? So I have deleted setcpu but it seemed to eat my battery faster so I put it back on. Maybe I will try some other kernal configurations since I was told that I can swap kernals without looseing data.
Sent from my SPH-D700 using XDA App
Fluff was glitchy for me,I liked Xtreme kernel the best.
Not sure if this was asked before but what is the difference between the Netarchy Toastmod Kernel Builds (cfs-nosbc) , (cfs-sbc) and (bfs-nosbc), (bfs-sbc).. and which is the best?
http://en.wikipedia.org/wiki/KERNAL
Nellyboy555 said:
Not sure if this was asked before but what is the difference between the Netarchy Toastmod Kernel Builds (cfs-nosbc) , (cfs-sbc) and (bfs-nosbc), (bfs-sbc).. and which is the best?
Click to expand...
Click to collapse
This should help you out a bit.
http://forum.xda-developers.com/showthread.php?t=894880&highlight=kernels
While I could link, I'll throw a few quick comments up for quick reading...please note that generally I follow the following pattern when chosing a kernerl
First
SBC or No SBC - SBC gets alot of bad rap, all I'm going to say is that I've been using SBC kernels only for months and haven't had a single issue. I've found that actually having my phone at 100% when I take it off the charger really makes a difference during my daily usage. However do your own research and make your own decisions on this.
SBC kernels have a trickle charge tweak that powers on and off to keep the battery at 100% instead of the stock kernel which considers "Full Battery" to be between 90% and 100%, this is why when you plug in your phone from a full nights charge, that it may discharge 5-10% within an hour. No SBC would be stock charging
Second BFS/CFS (I don't really know how these function, but my lamens take is below...)
CFS (Completely Fair Scheduler) - Use this one, it's the most friendly and stable and is my preferred choice just for stability reasons
BFS (Brain **** Scheduler) - Faster burst readings on various speed tests, but often doesn't play well with many phones, less stable but possibly faster.
Third (Havs, Less Havs, More Havs)
Havs or Hybrid Adaptive Voltage Scaling - adjust voltage to cpu depending on certain conditions of the phone, this generally helps battery life as it won't provide full voltage to the cpu when not needed. SVS which is not usually listed in kernels would be standard or stock, and if no HAVS or other Under Voltage is listed then this is likely the case. Less havs, means "Less aggressive scaling, More would be more aggressive scaling. It is not suggested using a overclock program as this can cause worse battery life as havs may work harder when you fluctuate the cpu speed with a program like setCPU. Go with less havs if unsure.
Optional
UV - Undervolt - a static undervolt that does not fluctuate.
Smartass Kernel - basically lowers cpu when the screen is off, this would help battery life, Less/More applies similiarly to havs.
Enjoy, Net's new 4.3.4 is very stable - I'm currently using 4.3.4 - cfs - nohavs - suv - sbc, with Koni III rom. I've had a couple of random reboots but otherwise it's sittin pretty. I'm going to try a less havs tonight to see how it affects battery. I try to carry and extra battery or charger so I don't have to stress and can use my phone to the fullest enjoyment. Stressing over to many little things ruins the fun. Don't worry about everyone else, flash away, almost all mistakes are fixable.
Since we are all wondering what is responsible for this rash of bricks I thought I would start a topic about it. I'm hoping some of our electrical engineering crowd will pipe in on this.
First of all I'm not an engineer and all my knowledge of electronics comes from the practical and theory side of being an amateur radio licensee and a tinkerer of electronic devices.
I think that undervolting is just plain crazy. Our phones are devised to perform in a certain manner at a specific range of voltages. Circuits that are under volted tend to destabilize and do strange things. Resistors change the circuit and the wrong input voltage can change eveything downwind so to speak. Capacitors that are undervolted may not even fire at all. With the advent of LSI's a component may get smoked and you won't even get the satisfaction of smelling the magic smoke (acrid burned smell)
Now over volting definitely has much more applicability here because it's just a plain fact that juicing the cpu results in higher clock speed. Problem here is how to dissipate the heat generated. If we were talking about a desktop we could put on a big heatsink and fan and get decent results. If we wanted to go faster we could do liquid cooling and direct freon injection (phase change) on cpu if we really want to have some fun (if anyone is interested in a world record Epic OC attempt on liquid nitrogen send me a PM). However, none of these methods is going to work well on a phone if you want to keep using it to make phone calls.
From my perspective we can easily OC any processor 10-15% without worrying about heat problems and no under/over volting needed for most phones. As mentioned in another thread, to paraprase Duracell, some can take a licking and some will quit ticking. However, outside of this narrow range we are literally asking for odd kinds of trouble. Just like what we have seen of late...
Sent from Bonsai 7.0.3
Well there is nothing wrong with undervolting..we just need to take things a step at a time...instead of undervolting everything doing 1 change at a time would be much more ideal as its easier to root out problems. One thing I notice is lately these things are released in form of 10-20 changes to try to get better then the kernel before it..instead I would rather see isolated test kernels of 1 thing at a time...so lets say UV ram was the culprit(not saying it is)...but maybe LCD UV is ok..and thats probably what most of us wanted
In my case I was running Genocide and was getting really good underclocks(better then most people) and things were stable..when I saw LCD underclocking on the Vision I just couldn't resist...even though I noticed problems from the get go and my intuition was telling me to go back to Genocide as I had better undervolts there anyways the greed of having LCD undervolt was too much to give up.
What ultimately got me was when I saw the thread about the issue in the kernel...I paniced as I have been having issues and proceeded to shut down my phone to get back into clockworkmod...if I didnt do that my phone would probably still be alive...
So ironically what bricked my phone was not only the kernel itself but the warning about the possible brick lol...thats why I quickly put up the warning to others not to panic and shut down their phones following my footsteps...I dont blame anyone but myself..
There will always be sacrifices along the way..thats just how development is...
I agree,I think we are going down the wrong road when it comes to kernels,but everything is trial and error,just wish more time was spent testing; Not just "hey it boots,testers like it" 2 hours later its uploaded...
Sent from my SPH-D700 using XDA Premium App
ecooce said:
I agree,I think we are going down the wrong road when it comes to kernels,but everything is trial and error,just wish more time was spent testing; Not just "hey it boots,testers like it" 2 hours later its uploaded...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Well as I said it would have been nice if we got the kernel features separated...aka 1 kernel with UV ram, one kernel with UV CPU and one kernel with UV LCD..then 10 days later if there were no issues go to UV CPU + LCD kernel and UV RAM + UV LCD Kernel..and then if everything is ok 10 days later merge them all into one..
My regret is not bricking my phone but the fact that it was bricked without providing much use...at the very least if my phone was bricked during a UV ram only test for example we would know where the issue was and not go that road..instead we are now stuck guessing the possibilities...
I guess our ambition is getting the better of us :/..slow and steady wins the race...
I totally agree with you about all the changes at one time being detrimental to good development. I've brought this up several times with the Bonsai Team. The problem from my perspective is that if you change 20 things and you have a problem you have no clue about what screwed what. Making one change and making observations is the hallmark of scientific testing. Now sometimes doctors use the shotgun approach, but only when they don't know what will work and someones life is on the line.
Sent from Bonsai 7.0.3
Top Nurse said:
I totally agree with you about all the changes at one time being detrimental to good development. I've brought this up several times with the Bonsai Team. The problem from my perspective is that if you change 20 things and you have a problem you have no clue about what screwed what. Making one change and making observations is the hallmark of scientific testing. Now sometimes doctors use the shotgun approach, but only when they don't know what will work and someones life is on the line.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
Yeah I agree as well, however these are regular guys and gals that do this in their own free time and if they compile one thing at a time I believe it becomes way more time consuming. It could literally take months or even years to completely shake down a build, going one by one. Bleeding edge is the only way it can really be done in an open source/freelance environment like this.
epic4GEE said:
Yeah I agree as well, however these are regular guys and gals that do this in their own free time and if they compile one thing at a time I believe it becomes way more time consuming. It could literally take months or even years to completely shake down a build, going one by one. Bleeding edge is the only way it can really be done in an open source/freelance environment like this.
Click to expand...
Click to collapse
your not compiling line by line...your just compiling 1 feature at a time...it may take more time to compile, but you also end up saving time on debugging.
I mean its up to the devs to do their own thing, we can't exactly tell them what to do..but we can offer our suggestions..its up to them if they wish to try it that way or not.
And bleeding edge is not how its done in an open source environment..in an open source environment a feature is tested 1 at a time by forking the tree..then when its been properly finished and tested it gets merged back into the main tree for a release. If it fails to hit stable by time of main release it rolls over to the next release.
Of course everyone has different development policies but the above is a very common one.
Definitely agree about being real careful with undervolting just to squeeze a few percent out of the battery life. Top Nurse for not-an-engineer you are essentially correct about disrupting circuits especially transistors and diodes that function on a specified voltage drop. I, myself, thought I bricked twice only to find out I had undervolted my sleep speed of 200 Mhz by 125 mV essentially bringing it to 100Mhz. The interesting thing is Genocide has all this undervolting and 1.4Ghz speeds and yet I have not heard of any rash of bricks there. Maybe that kernel should be used as a comparison baseline.
Do you BONSAI?
If I remeber right Genocide dosnt UV the RAM...
Sent from my SPH-D700 using XDA Premium App
ecooce said:
If I remeber right Genocide dosnt UV the RAM...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Does it undervolt the display?
mattallica76 said:
Does it undervolt the display?
Click to expand...
Click to collapse
no it doesnt, but i dont think display is the issue..also genocide doesnt have BFQ..only CFQ
mattallica76 said:
Does it undervolt the display?
Click to expand...
Click to collapse
No vision kernel was the first kernel publicly released that uv the screen and ram
Sent from my SPH-D700 using Tapatalk
MysteryEmotionz said:
No vision kernel was the first kernel publicly released that uv the screen and ram
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I do believe the bonsai beta 4.1.0b9 kernel had the display undervolted as well, and I believe the BFQ was enabled by default...someone correct me if I'm wrong. More commonalities I'm sure.
mattallica76 said:
I do believe the bonsai beta 4.1.0b9 kernel had the display undervolted as well, and I believe the BFQ was enabled by default...someone correct me if I'm wrong. More commonalities I'm sure.
Click to expand...
Click to collapse
I found this changelog for bonsai:
- Voodoo color
- Undervolting in several modes including Screen and RAM at certain cpu frequencies
- Overclocking and underclocking configuration for 100mhz-1120mhz is now standard
- Read_ahead tuning to 4096 bytes
- Volume switch provides silent and vibrate control
- Upgrade to CWM 3.0.2.4
- Reduced battery % limit to 5% for Camera, VideoPlayer, and MusicPlayer.
- Increased windowsmgr refresh events_per_sec from 60 to 68
- Updated Maps.apk
---
I dont see BFQ..unless they always had it...
One thing I do notice with Genocide vs VisionKernel is on Genocide kernel 100mhz never really worked...and i odnt mean crashing...I used CPU Spy and it never showed 100mhz..on VisionKernel I did have it hit 100mhz a few times..
Edit: I see BFQ was added on the 31st - r458 - Add BFQ scheduler from Paolo Valente
gTen said:
I found this changelog for bonsai:
- Voodoo color
- Undervolting in several modes including Screen and RAM at certain cpu frequencies
- Overclocking and underclocking configuration for 100mhz-1120mhz is now standard
- Read_ahead tuning to 4096 bytes
- Volume switch provides silent and vibrate control
- Upgrade to CWM 3.0.2.4
- Reduced battery % limit to 5% for Camera, VideoPlayer, and MusicPlayer.
- Increased windowsmgr refresh events_per_sec from 60 to 68
- Updated Maps.apk
---
I dont see BFQ..unless they always had it...
One thing I do notice with Genocide vs VisionKernel is on Genocide kernel 100mhz never really worked...and i odnt mean crashing...I used CPU Spy and it never showed 100mhz..on VisionKernel I did have it hit 100mhz a few times..
Click to expand...
Click to collapse
On the stock Bonsai 4.0.1 kernel, it would not scale down to 100mhz with the conservative governor, but it would with interactive. The 4.1.0 b9 kernel fixed the issue and it would scale to 100mhz with no problem. (other than bricking your phone)
mattallica76 said:
On the stock Bonsai 4.0.1 kernel, it would not scale down to 100mhz with the conservative governor, but it would with interactive. The 4.1.0 b9 kernel fixed the issue and it would scale to 100mhz with no problem. (other than bricking your phone)
Click to expand...
Click to collapse
Hmm..does any other kernel achieve 100mhz?
When I was looking at CPU Spy usually at max it would be like a few seconds on the 100mhz frequency...I would think when shutting down a phone 100mhz frequency might be used during a short interval..the only other person who claimed he got same thing and not on power down but at lock screen..which I know after waking it hits 100mhz...there might be a pattern here :/
So there are a lot of similiarities between the 2 bricking kernels and differences to genocide. Since there is no charging light when plugged in, it is still some catastrophic failure. Would RAM or video failure be enough to prevent the phone from charging? Or turn on the charge light?
Do you BONSAI?
kennyglass123 said:
So there are a lot of similiarities between the 2 bricking kernels and differences to genocide. Since there is no charging light when plugged in, it is still some catastrophic failure. Would RAM or video failure be enough to prevent the phone from charging? Or turn on the charge light?
Do you BONSAI?
Click to expand...
Click to collapse
I find it very very very very unlikely that the screen would do this..usually the screen is a separate component..In a pc for example ive had pc not turn on due to bad ram though...
gTen said:
I find it very very very very unlikely that the screen would do this..usually the screen is a separate component..In a pc for example ive had pc not turn on due to bad ram though...
Click to expand...
Click to collapse
Wasn't thinking the screen, I was thinking the video components on the circuit board due to LCD undervolting. But was def thinking dead RAM as a possibility.
Do you BONSAI?
With just Voltage Control my phone would hit 100 every blue moon. In conjunction with SetCPU on conservative it now idles fine at 100mhz and UV'd by 125. It seems to automatically revert to noop whenever I set it to bpq.
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
GSF1200S said:
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
Click to expand...
Click to collapse
Did you try reflashing fresh? I'm currently runnin CK23's Urban Precision 1.1 with Samurai 3.0.4 and I'm OC'd to 1400/200. I honestly don't kno why its not working for you, I'll be sure ta mention it in the thread tho.
Sent from a Epic like no other usin XDA Premium....
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
kennyglass123 said:
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
Click to expand...
Click to collapse
Yes, Ive done it a third time just to make sure; 100% reproducible with 3.0.4. The first 2 times I booted ACS ICS 5.5 FIRST, then booted back into CWM to flash the kernel. This last time, I flashed the ROM, then flashed the kernel immediately after. Same result. I guess its just my device? Ive never had issues with this before, so..
Did you clear data in Voltage Control? Perhaps it's your governor.
hi
i have a htc evo 4g running android 2.3.5 and kernel 2.6.35.10-g4b48446 [email protected] #1 and i have a few questions on setcpu. its a stock rom and it is rooted.
I shut off my profiles and disabled the perflock - it said success. So i ran the long bench test and only got 2078 ms, not 5000. so i dont know if its really working. I reengaged the profiles and i think it works with the screen off. the rest of the time i am not so sure. in fact it seems to still drain fairly rapidly unless i turn on some battery saver or something. I have the following settings on my profile all are set to ondemand except charging which is set to performance. the only other setting i can choose is user
in call 998 max and 245 min priority 91
screen off 384 max and 245 min priority 88
charging any 998 max and 245 min priority 85
battery <25% 460 max 245 min priority 81
bbattery <50% 883 max 245 min priority 65
Temp> 42 C 614 max 245 min priority 50
what am i doing wrong? I have it enabled and i have notifications off
i have system panel to try and monitor but its not recording and it also drains the battery like crazy so i think thats set wrong as well but i dont know why.
i also tried juice defender but it doesnt work right because it says the AOSP file isnt found in the system/app folder. I looked there and also in teh data/app folder and its not there. So i dont know what to do about that.
thanks
stock sense is just not all that efficient really. (well thats my opinion) profiles seem to look ok but also finding a different kernel with different governors (smartass v2 is rather efficient and changing around the frequencies as needed)
auto sync settings as well? turning some stuff of that you dont use or look at and so on can help too
and calibrating battery a bit can help aka a full discharge a full charge and full discharge will sure help (also what i have found personally)
kernels
thanks for the reply. You mentioned different kernels. I understand about rooting my phone but not so much about how to load a different kernel or different rom. Where do i go to learn about that?
jjdonohue said:
thanks for the reply. You mentioned different kernels. I understand about rooting my phone but not so much about how to load a different kernel or different rom. Where do i go to learn about that?
Click to expand...
Click to collapse
look around in the development section as there are some great kernels available right now...Ca1ne just released a new version of the underworld SBC v6 that i personally like with great battery life ...Mason kernels are also great with great battery...just make sure u read the threads completely to make sure u are using the right kernel for the rom u are using...ie there are kernels for ics...sense....and so on......also the kernels load through recovery...just load kernel to sd and wipe cashe and dalvik and flash zip...hope this helps...Carp
Hi another question about kernels. I am a bit of a newbie other than rooting my phone so i want to understand what advantages/disadvantages different kernels have. You mentioned smartassv2. i have seen others like
chopsuey kernal
freedom kernel
golden monkey kernel
savaged-zen kernel
tiamat kernel
all of these i think support sense roms.
as i understand it , you have to go into the recovery screen and load hte zip file off the sd card and reboot with the new kernel. What are the risks/rewards of doing so? I guess i am trying to understand which one would suit me best.
i have the current sprint lovers rom i guess since it is factory stock so should i also be considering changing the rom? Maybe i am getting ahead of myself here.
thank you again.
which rom are u wanting to run....this will help us steer u in the right direction
im sorry your entire post didnt load on my end i see ur running sprint stock....that is a fine rom but i have not ran it myself....
---------- Post added at 01:53 AM ---------- Previous post was at 01:36 AM ----------
i personally have switched to sbc kernels when they came out with a sense version...i am addicted to sense 3.5...just my personal likings...sbc is superior battery charging whichcarp will give u better full charge on your battery so when the light turns green and u unplug it it wont drop down to like 90% battery in just a few mins....i can squeeze another couple hours out of my battery with sbc and even more depending on light usage....but u will stil need to play around with different cpu speeds like 786..921 and so on to see what your individual evo can stand....what works for 1 may or will not work for another....lags and bootloops etc...
You don't need to change Roms, you can if you want, but changing kernels will unleash new features. Some features are:
Full hdmi mirroring
The ability to over/under clock CPU
2 way call recording
Improve battery charging
Enable swap space
Improved performance of phone
Some kernels allow under volting CPU to further save battery (this can cause some stability issues so start slow with undervolting)
You may want to take a look at Lionfish kernel also, just note first boot may take a while.
Also ditch the profiles in set CPU, I tried profiles and it never seemed to work right. A good governor will handle all your profile settings.
I like smartass, and intellidemand the most on my set up.
As an idea ok the battery life I am getting, I streamed Pandora over 3g for about 8 hours not much other phone use, screen off most of the time, and my phone was at like 20 %. I thought that was pretty good.
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
thanks detcup4evr for helping out explaining that better...i blew out my back and between no sleep and pain meds the brain just dont want to fire...thanks for stepping in bro....carp
smartassV2 vs InteractiveX ... which one giver better performance AND battery life??? currently I am running LIONFISH 1.8 with interactive X
Using profiles in setcpu actually uses more battery life. Because it has to be running all the time and monitoring phone state to know when to change to a different profile.
interactiveX vs smartassv2 all depends on how you use the phone and really which kernel it is. I've noticed little things like on mason's I got better battery with smartassv2 but on other kernels I get better battery with interactiveX. As far as performance, you won't realize a difference.
ok so it sounds like i should try the sbc sense 3.5 kernel with the smartassv2 governor. Did i get that right? i will look around to see where i can download that.
Were you refering to this kernel?
Underworld Sense Kernel v0.6
yes this is the kernel i run with ODJDub HD Bliss!! Sense 3.5...if u choose to run this rom it will give u alot of different options of kernels and apps and other things from the installer....if i can help u more just feel glad to hit me up....carp
Ok so with lionfish 1.8 kernel and interactivex, I should not use a profile? What does CPU go to on screen off? also where does it mention profiles use battery? I'd like to read more into this..
Thanks
Sent from my PC36100 using Tapatalk 2
Sense rom with Underworld v 0.6
At Carp -
thank you for the advice. I was thinking maybe i would use my ROM still (its a sense i believe) and load the underworld v0.6 kernel with sbc and see how that goes. I havent done very much research on ROMs so i dont know that i want to get that deep into this just yet. It seems like underworld has alot of nice features. One thing that i am wonderig though is with the new kernel would have any further ability to unload some of the sprint bloatware or do i need a new rom to do that or is there another way to do it? Things like qik video , gmail, accuweather blockbuster etc all load themselves periodically. I kill them but then they come back like weeds. Even programs i do like , like pandora, wheres my droid etc come back also. But i dont want them to.
no u will be fine getting rid of apps and bloatware u dont wont...u wont need a special rom....i use a free app in the market called root uninstaller to get rid of useless bloatware,apps etc...then u can go in and manually uninstall what u don't want...be careful not to uninstall anything which the phone needs to boot and operate such as android system...you will see the things u are looking for when u load the app...hope this helps...carp
I actually did something unusual.
I have universal aggressive lionfish SBC 1.8, swagged out stock N, and smartassv2
I set the ideal, sleep, and wake freq for smartass v2 to 128, while setting the up rate to 245. I used set cpu to lower the min freq for my device to 128. I set max load to 100, and min load to 85, and down time to 0. I then set a profile for "ondemand" during screen off, of 128-384.
I actually have pretty awesome battery life (I'm an uber heavy user).
Sometimes it reads that I spend over 70% of my time at 128mhz.
I feel no lag. It clocks to 998mhz maybe 15% of the time, mainly when loading web pages.
flashed underworld v 0.6
Hi Carp,
well, i flashed the underworld v 0.6. So i see in set cpu that i can underclock to 128 and overclock to 1228. however, i slid the slider over to 1228 by accident and it froze the phone even though it says its still at 998 mhz. then it rebooted by itself. so i guess that wasnt a good idea. Anyway, theres a ton of governor choices now in the profiles section. i am not familiar with alot of them but i was wondering which of those would provide the most benefit. they are as follows -
ondemandx
interactive x
intellidemand
smartass
interactive
conservative
smartass 2v2
performance
along with ondemand and user space from before.
thanks
Good to hear....u will need to try different settings as each evo will be a little different...ie.. some can take alot of overclock and as u said when u went to high it locked up......my evo likes min 245 and i dont go very little over 998...mine does not like high overclock....i run between 768 and 998 or until i can see a lag or slow down in performance..depends on which rom i am running...i like ondemand x and smartass 2 on my evo but there is a good read in papa smurph's smurphed out v6.6 thread in development on governors and such...go to post #2....i wish there was a perfect setting i could give u but u will have to see what your evo can take...part of the fun of android.....carp
Governors
Thanks carp. I guess experimentation is the only way to know. i charged my phone last night ad i noticed that it does take alot longer to go from 100% charge to 90% but i also noticed that the phone temp was at like 110 deg F and a voltage around 4.263 or so. i have read some thread where they claim its bad for the Lithium ion batt to be over 4.2 V but as soon as i unplug it it drops to 4.1 something usually. I am using battery indicator app to measure it. i am using the underworld w/sbc kernal currently but the voltage being higher has me a bit concerned that i am damaging the battery kind of like pumping water into a jar with the the lid on tight til it bursts. Or in the batteries case - too hot i guess or until it plates.