yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] ms79723:
I have an idea here...you know how when you set the governor to Conservative and go to advanced, there's that option for frequency step? Most kernels usually have that at like 10 or 15, but I think we need to bump it up to like 50. I think that because if its at 10 or 15, whenever the workload exceeds the value thats assigned in advanced, it'll scale up to the max by 10-15%...but thats no good. In theory that should save power, but not really because we've only been looking at that one way..and that way is scaling up. So yeah, it "may" save power while scaling up but it takes longer to scale down as well. But I for one dont think that slowly scaling up saves power at all. I also dont think that setting screen off profiles are that beneficial either...so I think that if we set that value to 50% we should see better battery life because the processor only has to make two jumps scaling up and down. And by only needing to make two jumps there will be no lag at all and you get to finish your tasks quicker..and once the task is done it only takes two jumps to go back to the minimum frequency...which is why I think that that will save battery a lot better than having to make 10 or so jumps.
[EVO 4G Android Development] xlGmanlx:
Ms, good ideas for sure.
[EVO 4G Android Development] :
The thing is I hardly ever see kernels on here taking advantage of "Race-To-Idle". Scaling by 50 instead of 10 would increase life because the phone could get to Sleep mode quicker and save oodles of more battery. This was a key principal over at the Pre forums for saving battery life.

http://www.lesswatts.org/projects/applications-power-management/race-to-idle.php
[EVO 4G Android Development] luisrcastillo:
That is a great idea which I personally like. Right now we are deep working on the .37 kernel. We're ironing out a few issues but I will definitely give this a try. Thank you very much for your suggestion and idea. This community needs more people like you
[EVO 4G Android Development] bbedward:
we have a fully working 2.6.37 base, the only thing that doesn't work is the accelerometer :cool:
[EVO 4G Android Development] halorin:
That's awesome. I'm really looking forward to this. Ldey me know our you guys need a guinea pig. I was a beta tester got like a day but I got removed for some reason. :(
[EVO 4G Android Development] xx5352:
Hello I'm new to rooting and all but I have been messing with some things anr I am running a MIUI rom on an evo. The battery is good but not great and I want to know if I should try this one. Can anyone help? Thank you in advance! :)
[EVO 4G Android Development] paranoid android85:
Go for it! :D
[EVO 4G Android Development] xx5352:
I want to but I was reading this thread and not sure which one to go for. If I get the zip at the beginning of the thread will thy be the most updated kernel? And idk which to chose out of the CFS or BFS?
[EVO 4G Android Development] luisrcastillo:
Suggest you start with CFS
[EVO 4G Android Development] xx5352:
Ok and thank you so much! I have it and going to flash it now. Should I do a cache wipe first?
[EVO 4G Android Development] paranoid android85:
You can if you want, but I think it does that already when you flash this kernel
[EVO 4G Android Development] merkindude:
so i was reading through a different thread and read that some people's phones were getting messed up due to the trickle charging. Is this true? I want to flash it to give this thing a try (using cm 6.1.2) and see how great the battery life is on this kernel.
[EVO 4G Android Development] xx5352:
It is now installed and I am restoring my apps. Are there any tweaks I need to or should add? I read that setpcu isn't needed short to make surethe governor is set to conservative. And can anyone suggest a good battery monitor. I was using some widget called battery life lol.
[EVO 4G Android Development] ms79723:
There's a voltage limit set on those kernels. Once the voltage reaches 4.228V, the charger shuts off. Now in order for visible damage to happen (i say that because this fix does cause wear and tear on the battery, but one post was talking about a smoking battery..which is why i said "visible damage") is if you exceed that limit. Now, once you exceed the limit, the charger turns off but once the voltage is lower than the limit it turns back on and bla bla...it's a cycle. The charger will keep turning on and off at 4.228V...which will cause an increase in temperature and you'll see visible damage. Now, how often does that happen? One case that I've seen. But (this is a big one), the only way you can even charge up to that limit is if you have charger that is stronger than the stock charger...or you are constantly doing heavy duty work on the charger (and when i say heavy duty, i mean HEAVY DUTY. Its possible that you also have an app running wild in the background, and overtime that can wreak havoc).

So after saying that, this kernel is safe. I use it all the time no problems whatsoever. Those that have problems have got to be doing the two things I've mentioned in the previous paragraph. As long as you dont do those two things, this kernel will be insane for you and you will have the Evo you always wanted (charging aside this kernel is monster).

tl;dr. You have to do something extra to cause this kernel to mess up your phone. This kernel and its charging method by itself shouldnt mess up your phone. If this were an experiment and we pulled the statistics from it, it would show that there are other factors that cause users phones to mess up (ive only heard about 2 people's phones messin up btw..both had other factors at play). Since more than the majority (close to a good 95% I think..) has success, then you should have success too. So download it up and enjoy ya self! Its a celebration!

Edit: I also like to type out everything I'm thinking until I feel that I've made my point...sorry for the long post haha
[EVO 4G Android Development] ms79723:
I say just get battery indicator pro just to look at the percentage. I wouldnt necessarily advise monitoring the battery because that would mess up your battery life because of all the work in the background. As for setcpu...if you wanna test a theory with me then set the governor to conservative then go to the advanced tab. Once there, set the up threshold to 95, the down threshold to 93, and freq step to 50. Apply and hit "set on boot." I have a feeling that those options will help prevent unnecessary battery drainage.
[EVO 4G Android Development] matt2053:
This is very exciting to me. I am constantly flashing back and forth between your kernels, now I can finally stop!
[EVO 4G Android Development] xx5352:
Ok made the changes in setpcu. What should indoor with the bar on the main page? Set the min to the lowest and the high to the highest? And thank you all so much for the help!!!
[EVO 4G Android Development] aimbdd:
I made those changes too, will see how it helps.
[EVO 4G Android Development] merkindude:
Ms-thanks for clearing that up. How is your battery life on this?
[EVO 4G Android Development] ms79723:
lost 2% in about an hour (63 - 61%). Been listening to music the whole time, I'm lovin this. I've been unplugged since 11am too btw (it's 11:26 PM right now where I'm at).
[EVO 4G Android Development] merkindude:
Wow thats insane. Are you using setcpu with that as well?
[EVO 4G Android Development] ms79723:
yup. No profiles though. I'm against setCPU profiles (well, screen off profiles).
[EVO 4G Android Development] xx5352:
Im getting nothing like that. I am going to give it a full charge and take it out for a real test tomorrow. Got my fingers crossed!!
[EVO 4G Android Development] ms79723:
Did you use the setCPU settings that I posted on the previous page?
[EVO 4G Android Development] xx5352:
Yes. I set everything the way you suggested and my scaling is set to 860 max and 245 min and set the governor to conservative. I left the sampling rate alone. No profiles set on setpcu. And the main screen isn't set to start on boot, should that be as well as the advanced settings?
[EVO 4G Android Development] pardonmyownage:
MS, it might be advantageous to add those two things to all the openings of threads of kernels that use SBC. just so everyone is on the same page before they download the kernel.
[EVO 4G Android Development] ms79723:
meh, people will always find something to pick at. They'll find something wrong with it, there probably is something wrong with it (probably something talkin about how the battery wont be able to last 3 years, it'll only last 2 or some bull -.-)...I wouldnt know because I'm not an engineer of sorts...I'm a future med student.
[EVO 4G Android Development] nosfanatic2006:
MS, could you explain how that freguency and those thresholds are supposed to work better? I feel like I'm not fully understanding the concept.

Btw, just changed my settings to what you recommended. I'll report back with my results tomorrow
[EVO 4G Android Development] Smac7:
Kernel is working great for me except there is one problem. Once I am fully charged and on the charger for a bit the phone will be extremely sluggish while still on the charger. Once I pull it off it works fine again. I am not overclocking or using setcpu.

Sent from the xda app on my htc evo
[EVO 4G Android Development] xx5352:
The kernel and settings seem to be working fine. Though when I use the phone, i.e. talking, facebook, or net, the battery goes down about 1% every 3 minutes. Is this good desired results? Though it is noticeably better than when I was using the stock everything, it doesn't seem to be its full potential.
[EVO 4G Android Development] paranoid android85:
so do you recommend the threshold up/down and freq steps on all kernels or just the sbc ones?
[EVO 4G Android Development] Tyzing:
Donation sent....not much but I will try to do this once a week or so. Confirmation number: 3SY17588KU663063X

I encourage everyone to do the same...if everyone that uses this kernel sends just a few bucks it'll help keep these dev's positive and wanting to continue to offer their services....b/c Lord knows I'd get pissed off from time to time reading some of these yahoos post and complain.
[EVO 4G Android Development] BlueHarford:
Thank you very much. Donations are great as this is how we hope to pay for our site www.savaged-zen.org

we are looking to open a fourm on there as well, and our gerrit is up. Since from the PM i got lastnight from toast... XDA is forcing us to take down all kernels with SBC in them unless someone can provide concrete proof that it doesnt do any harm...

I dont agree with this, as no one has provided concrete proof that it does harm... just speculation, as well i would expect XDA to remove any kernel that over clocks, as you can fry your phone overclocking over 1113mhz...

Anyway... once our fourm is up we will re-post future SBC links... as .35 development is now stopped now that we have .37 all but working.

We have 1 issue left... its small but big... once we get it nailed down we will release a base code... and then our first HAVS, SVS, SBC, BFS, CFS and all the good stuff, in a new thread.
[EVO 4G Android Development] bigj225:
Camera

I have one of the rev 003 with the new camera and hboot 2.02. I can not get your the camera to work with any ASOP rom using your kernel.

Any suggestion???
[EVO 4G Android Development] Tyzing:
You have got to be kidding me. XDA is actually listening to this nonsense???? Are you serious? Thousands of people are using SBC and there's been a handful of reports....wow, talk about an over reaction.

Please tell me that this wont mean you'll stop updating them like King did after he was banned from XDA (not to mention charging for his website).

This is not good...
[EVO 4G Android Development] BlueHarford:
Were going to come out with a non-SBC version of 1.6 for everyone.

We are not going to stop updating but we are done with .35. We will continue in a new thread sometime this week with our 2.6.37 kernel. If XDA is really going to enforce the no SBC, then we will just have to keep those versions off this site and put them on our website.

We want to obied by the rules of XDA, its a great community... even if we personally dont agree with decisions made... its not really our site... so we cant throw a huge stink about it...

I expect a reply from toast before he takes any action, i'll keep you guys apprised... he's the mod of the fourm... so i dont know what the reasoning is, or what, doesnt look like XDA has made a formal announcement either... so im pretty confused by the email that i got.

Anyway SBC links will be removed soon.. and replaced by non-SBC... SBC development going forward from the looks of it will have to be off of XDA.

Thanks for your support.
[EVO 4G Android Development] BlueHarford:
Oh and BTW we will NEVER charge for our kernel or access to our site!!!

We however would appreciate donations, for the sole purpose of paying for the site, but will NEVER require it. We do this development for free because we enjoy it and we like to contribute to the open source world.
[EVO 4G Android Development] luisrcastillo:
To add to Josh's comment, I am pretty upset about the drama and all the fuzz going around about SBC. I've seen people in threads and twitter saying "Why do you think HTC developed the driver this way?" HTC this, HTC that. Did everyone forget that when the Evo came out it had a 30 FPS lock which was horrible? Did everyone forget HTC said "This is a hardware limitation and cannot be done"? Did everyone forget about all the hard work Netarchy, AssasinsLament and all other developers heavily involved in breaking the 30 FPS barrier put into it to accomplish that? At the time, I remember people were afraid about frying their LCD display, at first I was one of them but I believed in the devs and gave it a try. Just the same way I decided to root, flash a custom ROM and custom kernels, and overclocking, and using different schedulers, etc.

I think people should stop and think before making the comments they make. Some people really need to learn how to express themselves better. I have been using SBC since day 1 and I have not had any issues with it. I have had issues running other kernels in XDA which made my phone unreliable. No one is saying anything about underclocking, undervolting, overclocking, overvolting but yet are bashing MS' hard work. It's a great community with its pros and cons but damn, people are overreacting and making it sound like MS' goal is to fry everyone's phone.

I respect everyone's opinion and point of view. From now on, this will be my last post about SBC and discussion about other kernels. When I first started this project I decided to contribute to the community and I will keep doing that. From now on I will just continue to do my work and contribute in any way I can until I lose my motivation. I teamed up with Josh initially and after leaving the drama behind we have teamed up with bbedward, developer of the zendroid kernel to bring you a better experience and a new kernel base (2.6.37) faster. And by the way, we are very close to getting that finished. Like Josh said, just have one small thing to fix and we are golden. I hope no one calls us "wannabes" because we are working on .37, well, I think we are the first to have it fully functional and just need one sensor fixed.

Sorry for the long post guys, just had to let it out.
[EVO 4G Android Development] thedarksavant:
Is there anyone we can appeal to to stop this nonsense. I mean, everything we do in these threads could damage our phones, but we do them because the risk is low and the reward is high.

Seems ridiculous to take something down with only reports of correlation and no evidence of causation. I can see them wanting more of a warning on the front page, but banning a mod? SERIOUSLY?

Anyway, glad to hear you're teaming up with bbedward. I've been using the Zendroid kernel since .4 :)

Oh well, SBC or no SBC, looking forward to your work. I guess in a community forum, mobs rule :(
[EVO 4G Android Development] EVO-lution of Man:
That sucks. I respect toastcfh 100% for all he's done for the EVO and android period so he must have his reason for saying that but damn! I think we could all use a more detailed explanation as to why sbc kernels have to be removed. A handful of borked devices shouldn't warrant removal of a great mod. If I'm not mistaken everything on this site is flash at your own risk. The only thing I can think of being the reason is a scare of batteries exploding but that's silly. Screens can spontaneously shatter from overclocking if your willing to feed into that type of thinking. Undervolting could cause major, irrepearable instability. That's the kind of thought that's happening right now. Maybe more devs should look into this more thoroughly before they decide to start a witch hunt. Good investigative science with rock solid facts is always better then just pointing a finger. Nothing is definite. The thought of because of this then this isn't really any evidence of anything. Just saying.
[EVO 4G Android Development] ms79723:
Well if we were lookin at this from a statistical point of view (i think i said that right) then there is no way SBC should be removed. Looking at hard facts is way different than looking at the experiment and its results. But this has only been a month or so though, so we can't draw any conclusions yet (only assumptions)....but if my battery is still working well in a few months (which it will be) and nothin bad has happened (nothing bad will happen)..then that says a lot.
[EVO 4G Android Development] pardonmyownage:
i love you man... i love you all! keep up the good work. i think its great you guys are working together now. GL
[EVO 4G Android Development] BlueHarford:
Update from Toast

Ok guys i got a PM from toast... he has stated that in fairness due to the non concrete evidence of harm or no harm, we may post SBC versions of the kernel but we MUST post a nonbias disclaimer/warning to any users that download it...

With this said... the 3 of us will talk today about putting SBC back in for those who wish to use it. with a approved warning, so XDA is happy as well as the users of the community.

As of now the SBC links have been removed UNTIL ALL 3 of us talk together about it.
[EVO 4G Android Development] xlGmanlx:
thanks for the update, and dude........how about slinging some of that hash on sense??? I would like to see that same warning applied to every ROM/Kernel/MOD/RADIO/NV/WIMAX etc on XDA if that is the case
[EVO 4G Android Development] thedarksavant:
I'm so glad cooler heads prevailed on this. I've seen so many posts saying that SBC kernels will damage your battery. I guess it's true that geeks sometimes are bad communicators ;)
[EVO 4G Android Development] BlueHarford:
he stated that apparently all of the fried battery posts people have targeted savage as the kernel... which is funny because all other kernels out there that had SBC... were using the exact same mod as us.. anyway its a mute point.

I'll talk with the guys tonight and we'll let you all know... another thing toast said was "users come to xda trusting the devs and what they are doing to not brick break or burn there phone"(no verbatim) This is true... i just personally cant see the harm... i mean maybe it wears at your battery, but over heat it or over charge it no way.. i see clear evidence on my battery monitor that when it hit 100% there is no more positive mA therefore not charging. My temp is actually lower since SBC came about... so its not even warm...

I dunno. but the point is dead, we'll let you guys know later.
[EVO 4G Android Development] BlueHarford:
I cant speak for all devs, but i am passionate about my work, and have a high ego about my work, i research before i open my mouth, but i dont speak unless im firm about something...

It does get you in trouble sometimes... even at work :-p. But it also gets you respect. stand by your work and your beliefs.

There is ALLOT of drama on XDA, that happens when allot of hard headed people talk to each other...

Do i think the ridiculous tweets about "Wannabe snap kernels" and low blows on SBC from some of the snap members is appropriate? NOPE... to some people twitter and forums are there life so they "Act cool" on them...

Savaged-Zen team is here to give you all a good solid stable kernel that has the best performance, stability and compatibility. We have fun doing it... we enjoy the community of users that support us. and we try our hardest to not involve ourselves in post wars or twitter banter...

I'mm off this forum i gotta get back to work ;-) lol.

Stay tuned for our new thread and show your love there. dont hate on toast he's not being a jerk just has to be careful as the mod... the other smack talking devs or whatever they want to call themselves... whatever....

BTW please from now on post to the SBC thread about SBC, and if you have a problem with the other devs post on theirs, we dont want our thread to fill up with hate or banter.
[EVO 4G Android Development] xlGmanlx:
sooo...........whats up with a sense .37 kernel? is that even possible haha?
[EVO 4G Android Development] BlueHarford:
lol i have no idea... i personally dont want to mess with sense. I will never go back to that... cant speak for Luis or Brandon though
[EVO 4G Android Development] xlGmanlx:
ok, i rock sense because i like RLS5 and sense is the only ROM's that work with my work exchange account. Right now there is only two dev's that make sense based kernels
[EVO 4G Android Development] pardonmyownage:
only 2 different AOSP kernels right now...
[EVO 4G Android Development] luisrcastillo:
I loved Myn's ROMs when I used sense. I know what you mean on exchange. For me, exchange works in AOSP but I can't any html images in the email so I have to click the download button which I don't really enjoy. Then I tried out Touchdown and it is a good app and does it's thing. I can search on the exchange server and search the email app like sense does. Could use improvements and a visual overhaul but it does the job. Long story short....I may get into developing a sense kernel but that depends on other things.
[EVO 4G Android Development] luisrcastillo:
+1. Toastcfh is a great developer and mod and this community is in debt with him. I never got upset with his desicion because he's just looking out for users. Also, he did get back to us with a fair statement so I appreciate it and I thank him.

In regards to other devs and kernels, lets try to all stay on topic and not talk about other devs and their work. Two teams have combined forces so Zendroid and Savage became Savaged-Zen and will be better than ever.
[EVO 4G Android Development] ms79723:
Mass hysteria is what I like to call it. The code is the same but yet people have problems...I wonder if any MIUI users have a problem with it..because its the default kernel for that rom. I check those forums and I havent seen any issues. All positive comments...but once people know what they are flashing then read someoen say "blu blu blu I was using savagekernel then my battery messed up blu blu blu" then thats when they start seeing invisible sht: "oh yeah, my phone is burning up today even though for the past few days it wasnt burning up...it must be the kernel and not the fact that today ive made 3 calls, streamed some videos online and sent mass amounts of text!"

Some people are sheep. This kernel runs great, it's my go-to kernel. Its the reason why I can't run Sense roms anymore..no problems whatsoever. Until the people having issues post every single factor that was at play when something went wrong..we can't really trust 'em.