yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] BlueHarford:
I feel like a DOUCHE

Ok guys... IM SOO SORRY... the 004 hardware is completely MY fault!!!!!

Last time i flashed i used a old config... which didnt have the samsung drivers checked off... so it wasnt enabled...

its completely my fault and im sorry for the screw up, im compliing the builds with the drivers right now, and will post once the link is updated.... there was a couple of new minute CM kernel updates and i updated them... nothing that you would notice... so i would only reflash if your bored... or if you have 004 camera drivers..

Sorry again.
[EVO 4G Android Development] lafrad:
Camera on 1.6 freezes for me too...

CM6.1.2

freshly wiped.
[EVO 4G Android Development] luisrcastillo:
Please provide a logcat and we will review
[EVO 4G Android Development] gear.h34d.2012:
Hardware 003, wiping everything except ROM twice and getting stuck in a bootloop with 1.6 :(
[EVO 4G Android Development] jr19703:
Is the camera driver fixed now? Would like to try, thanks.
[EVO 4G Android Development] godfirst:
Yeah I've done that, camera app is just laggy.
[EVO 4G Android Development] BlueHarford:
New CFS

Im uploading the CFS with updated hardware... BFS i'll do in the AM.

Give it till 8:40pm EST till you try and download... same link as before.. please report back

Check back and front cam.
[EVO 4G Android Development] V1cmlb:
When I update the appmarket 2.2.6+ I get force close any suggestions
[EVO 4G Android Development] jr19703:
You did it! now I have camera! 003 with 004 cam
[EVO 4G Android Development] luisrcastillo:
What rom are you using? I don't think that's an issue with the kernel
[EVO 4G Android Development] luisrcastillo:
Great!!!! Thanks for the update
[EVO 4G Android Development] V1cmlb:
Cyanogenmod 6.1.1

$ent from my PC36100 + savage v1.6
[EVO 4G Android Development] conflikt:
Troll? Think not, but if it makes you feel better to blast someone over being curious/cautious then okay, whatever gets you off. Do some reading smart guy.

http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

Btw, thanks devs. Am using 1.5 and it is fast/stable. The problems I had with lag/ screen wake issues has now gone away with this kernel that is without setcpu, and just using OS monitor to change my profile to smartass. Think I'm going to backup and install savage mod :], thanks for the awesome work devs.
[EVO 4G Android Development] pardonmyownage:
Alright here we go, i understand this should be in the SBC thread, and i will post the same thing there. upon reading that site i'm assusming the main thing we are talking about is this...

No trickle charge is applied because lithium-ion is unable to absorb overcharge. A continuous trickle charge above 4.05V/cell would causes plating of metallic lithium that could lead to instabilities and compromise safety. Instead, a brief topping charge is provided to compensate for the small self-discharge the battery and its protective circuit consume. Depending on the battery, a topping charge may be repeated once every 20 days. Typically, the charge kicks in when the open terminal voltage drops to 4.05V/cell and turns off at a high 4.20V/cell.

But just to make sure that we are talking about the same thing, i checked out wikipedia

A float charger differs from a trickle charger in having circuitry to prevent overcharging. It senses when the battery voltage is at the appropriate float level and temporarily ceases charging; it maintains the charge current at zero or a very minimal level until it senses that the battery output voltage has fallen, and then resumes charging. It is important to note that the appropriate float voltage varies significantly with the construction of the battery and the ambient temperature. With the appropriate voltage for the battery type and with proper temperature compensation, a float charger may be kept connected indefinitely without damaging the battery. With a 6-cell (nominal 12V) lead-acid battery the correct float voltage drops by about 0.15 V for a 5°C rise in ambient temperature. Not compensating for this will shorten battery life either by over- or under-charging.

according to what i've read and what i see with my battery charging, the battery reaches a certain voltage and reduces the mA charging to almost 0. according to wikipedia, this seems MUCH more like float chargning, than actual trickle charging. maybe someone could back me up on this? so what we have is a miss use of terminology. according to the charging site, 4.2 is well inside the safe limits and if you dont overcharge or undercharge you are safe. since SBC doesnt over charge, but in a sense float charges, i think we are in the clear.

someone look over this and confirm my findings
[EVO 4G Android Development] mwielgosz:
Hello,

Please, before I say anything, do not mark me off as a troll. I'm simply posting a question and don't need to put a flame retardant suit on.

Thanks!

I've been testing a bunch of AOSP kernels and swapping back and forth. The main competition is obviously between Savage and ZenDroid. There is also a lot of discussion about SBC going on...some good, some bad. Now I've done my research, and personally I simply prefer not to use SBC. Even though the risks are low and batteries are affordable, I just would prefer to use the stock charging system built into the stock kernels...but stock kernels never perform well for me (when compared to kick ass kernels on these forums)

So why is it that neither of the kernel teams will release non SBC versions of their kernels? It seems that there is plenty of user support for both SBC and non SBC. IMO, if we can choose between CFS and BFS, why not swap the battery drivers out and allow a choice between SBC and non SBC? It would satisfy a lot of debate as those who prefer not to use SBC (for whatever reason), don't have to in order to get the great tweaks and other mods built into these kernels.

Thanks!
[EVO 4G Android Development] aimbdd:
They are releasing one for people that don't want it. (couple posts back they said so)
[EVO 4G Android Development] mwielgosz:
Awesome, this should stop alot of trolling and complaining. Sorry for asking a question thats been answered

---

Evolved into a higher form of communication
[EVO 4G Android Development] Envynet:
So it seems more reports coming in of battery's dying, one persons phone started smoking and Netarchy himself has pulled ALL SBC kernels :D:D

SBC Fail #1

SBC Fail #2

And straight from the kernel master himself...

Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, all SBC kernel build links have been removed from this post.

If you still wish to use SBC builds, being aware of any possible risks battery charger modifications may present,

you can access all previously available netarchy-toastmod SBC builds here,

or you can try ms79723's official SBC thread for one of his kernel builds, some of which are based on netarchy-toastmod.
[EVO 4G Android Development] rstuckmaier:
I find it funny people have no problem flashing a rom/kernel that is different from stock, that will over/underclock and undervolt the phone, potentially ruining a $450 phone (verified on sprint.com).

But they freak out and whine about flashing the same rom when it might make their $15-45 battery (pricing from how much I paid for my Hero battery online and Sprint.com).
[EVO 4G Android Development] Envynet:
Maybe because roms don't cause phones to smoke and destroy hardware lol
[EVO 4G Android Development] aimbdd:
pictures or it didnt happen.

Ahh. The one post he hasn't proven it yet. Also this is his first post here, and he signed up today. The second post the guy really has no clue what caused it. There is no evidence to shot it was the sbc, it could easily be many other things. There was no damage to anything besides a dead perfectly safe battery.
[EVO 4G Android Development] rstuckmaier:
Or maybe they did... I would think overclocking a phone could make it smoke and destroy hardware. And I can see how undervolting would accomplish the same thing.

Just because someone did A and B happened does NOT mean that A caused B.
[EVO 4G Android Development] pardonmyownage:
Why would this make you happy? I hate people sometimes...
[EVO 4G Android Development] mwielgosz:
It's my belief that you should be able to do whatever you want to your phone...as long as you accept responsibility for it if something goes wrong. Whether its underclocking/overclocking, using different prls, voiding your warranty, using hacked roms, or using the SBC battery mod, etc. the same rule applies. People have the choice to use any or none of these modifications. If something goes wrong, whether or not its the modifications fault...the blame actually goes on the user for installing it to begin with.

That being said, users of mods have choice...and should have choice. Like I stated earlier, I'm not into the SBC mod (although I used to be) and would simply like the choice of using these amazing kernels without it. IMO, the SBC mods are too new and untested for long term use.

But if user A fries his/her battery, it may not be mod XYZ's fault. They could have done any number of things to help that battery fail. They could have had their phone plugged in for a week running overclocked at fullbore CPU frequency with the phone on top of a heater. IMO, the "battery fail scare" is a little over-hyped and it seems to be breeding a semi-hysteria. Anything is possible though no one has put forth true data relating specifically to the Evo and trickle charging...everything is very general. Time will surely tell.

The SBC mod itself is really a great idea that works very well. If the fast battery % drop really bothers you, it fixes it wonderfully and gives you anywhere from 10 minutes to an hour of extra battery life. For myself, with an extended battery, scaled CPU frequencies, undervolting, and consciences use of radio settings, my battery will last 24 hours no problem with moderate use. If something happens to my battery or phone because of my modifications, I'm the one taking the loss.

Happy modding all, be responsible please ;)
[EVO 4G Android Development] BlueHarford:
Guys I'm going to ask the mod to clean the thread of all this SBC talk. Luis asked you nicely to stay on topic...

Please try to stay on topic
[EVO 4G Android Development] EJerVJerO:
I blame all the people having issues with the SBC kernels on them overclocking as this seems to be the trend of why people are having heat issues. I personally have multiple EVOS and all running CM7 with SBC and sit on the character for about 10 hours a night.
[EVO 4G Android Development] EJerVJerO:
I have also reviewed my temp on my phones and none of them have gone over 77 degrees F
[EVO 4G Android Development] Tyzing:
No kidding...I'm not sure how fast you REALLY need your ROM to be...I'm on MIUI underclocked to the 700s and it's still so quick with amazing battery life
[EVO 4G Android Development] EJerVJerO:
Exactly every person I know have had issues with SBC had their phones overclocked to over 1ghz up to including 1.2ghz and they complained and wondered why their battery got hot LOL

Especially when they had their phone set to CPU profile performance.
[EVO 4G Android Development] nosfanatic2006:
I've been using SBC for about a month, overclocked to 1113, and never had heat issues. Unless its on my car dock and I have the heater running (sits right in front of the vent). Other than that, zero issues
[EVO 4G Android Development] :
People sure like a good controversy.

Personally, if someone is worried about SBC then use a different kernel. There are many out there.

Back on topic. I'm loving 1.6 CFS. I'm getting the best battery life since I bought the phone! To run the conservative governor and still have amazing performance is just incredible. And no explosions, implosions or incinerations to speak of. :)
[EVO 4G Android Development] EJerVJerO:
I agree I have 1.6 CFS on multiple devices and yet none of them have caught on fire exploded or turned into some mutant :)
[EVO 4G Android Development] Lento10:
I just flashed cm 7 kang,

do you have any problems with this kernel on cm7?

Before I flashed wanted to get an opinion.

Thanks
[EVO 4G Android Development] Lento10:
I have been using this kernel since the beginning on cm 6.1.1 and my battery is in great condition.
[EVO 4G Android Development] EJerVJerO:
I personally have multiple 002 hardware EVO's running my own compile of CM7 and when I can't get to a computer to compile use Lithd's CM7 compile with 1.6 CFS Savage Kernel. I have had 0 issues with running any of Savage's kernels on the phones since I been running CM7 which has been a couple weeks when the source was put up on github for CM7.
[EVO 4G Android Development] Lento10:
Thank you, I am using lithids compile version.
[EVO 4G Android Development] Dozenboy0012:
Can you plz consider implamiting ondemand govenor into a future release?
[EVO 4G Android Development] sracercelica:
For some reason my phone is not charging after flashin this kernel
[EVO 4G Android Development] jxs1984:
just reached near the end of the battery life. result: 2d 8h 12m with 6% left. :eek:
[EVO 4G Android Development] :
What weather widget is that? I like.

Sent from my HTC EVO.
[EVO 4G Android Development] BlueHarford:
On demand only really caused problems and we saw no benefit or practical reason to keep it in. Any specific reason you'd like to have it back?
[EVO 4G Android Development] nosfanatic2006:
That's insane haha
[EVO 4G Android Development] jxs1984:
beautiful widget
[EVO 4G Android Development] -viperboy-:
How?????? Ugh, CM7 is great on my phone but battery life is garbage. Not even lasting a full day. No apps causing wake locks, no apps causing excessive battery drain. Wifi, BT, GPS all off, good service area all day. I don't get it :(
[EVO 4G Android Development] kdbrown5:
CFS or BFS ?
[EVO 4G Android Development] jxs1984:
calibrate your battery? my wife's evo with cm was having the same issue until i calibrated her battery.

cfs
[EVO 4G Android Development] BlueHarford:
Future of Savage

We should have an announcement next week about v2 and other issues.

On a side note... Savage will continue to come with SBC, as we can find no proof of harm to your battery, actually its the opposite. (I'd be glad to share my battery monitory)

With that said, we may decide to release two versions in the future for those who believe the hype... as we are here to support the community not our own personal desires.

Hope everyone is enjoying the weekend!
[EVO 4G Android Development] PCap79:
Please explain...
[EVO 4G Android Development] aimbdd:
here you go.

http://www.nexusoneforum.net/forum/nexus-one-faq-how-tos/5625-calibrate-your-battery.html

the phones software needs to be re calibrated for the battery. The phones software tells it when to shut off not the battery, hence your problem.
[EVO 4G Android Development] fsalazar504:
Anyone using the latest miui rom (12.31) having trouble flashing CFS 1.6? I get stuck on spalsh screen and yes I did wipe cache and dalvik. I also tried fresh install to test it out.
[EVO 4G Android Development] InfidelForLife:
I'm running 12.31 but still with 1.34. I see no need of upgrading to 1.6 when I am getting 30hrs, fast, and no rebooting. What's the difference with 1.6 now?

Sent from my Supersonic EVO 4Gees
[EVO 4G Android Development] jcrabapple:
I had a version 4 that I returned for screen separation. Savage kernel worked fine on that one. I got a new one that is also version 4 but this time my camera doesn't work with Savage kernel. Only works with CM 6.1.2 kernel. It also won't overclock. You think they changed the hardware again?
[EVO 4G Android Development] BlueHarford:
Re download 1.6cfs and it will work fine
[EVO 4G Android Development] jcrabapple:
I tried it already. Camera just shows a black screen and FCs. Has 1.6 been updated since yesterday?
[EVO 4G Android Development] bwcorvus:
Same happens to me. HW 0004 with SK 1.6 BFS
[EVO 4G Android Development] BlueHarford:
1.6 CFS was re-uploaded with the new drivers, the BFS version has not been updated yet. we've confirmed with numerous users that it works.

please try re-downloading CFS and try again
[EVO 4G Android Development] bwcorvus:
CFS does work...guess i'll have to wait on BFS
[EVO 4G Android Development] newone757:
Is it possible to get a non havs version? My phone doesn't charge with any havs kernal and just dies overnight on the charger.
[EVO 4G Android Development] jcrabapple:
Thanks I downloaded it. Will try flashing when I get home. In my previous experience this kernel has much better battery life than stock CM so I am looking forward to getting it working.
[EVO 4G Android Development] BlueHarford:
thats a very unusual reaction to HAVS.

We will on our v2 version.

The plan is to put out 3 types

1 Full Savage

1 No SBC

1 No HAVS

CFS/BFS version of each.
[EVO 4G Android Development] jcrabapple:
I tried it. No luck. Causes all kinds of problems. I think this phone is just not very flexible. It won't run any other kernel besides HTC and CM6. It also won't overclock. And it was a pain in the ass to root. I'm still within my 30 days so I might just return it again and tell them that it is randomly rebooting or something. That will be my 4th one. :confused:
[EVO 4G Android Development] EndlessDissent:
Not to make you guys work harder (I'm gonna use the full savage kernel, personally), but in order to make everyone happy, wouldn't you have to make a fourth version with no SBC and no HAVS?
[EVO 4G Android Development] InfidelForLife:
1.6 Does have SBC in it correct?

Sent from my Supersonic EVO 4Gees
[EVO 4G Android Development] InfidelForLife:
Cool, thanks

Sent from my Supersonic EVO 4Gees
[EVO 4G Android Development] gear.h34d.2012:
To confirm, you don't have to be on CM 6.1.2 to flash 1.6 CFS aye? I'm on 6.1.1 and keep getting a bootloop. Going to keep trying.
[EVO 4G Android Development] itlnstln:
I don't think so. I have used 1.6 on MIUI 12.24 and 12.31 as well as Salvage Mod .9.5.1, and it's been all good. Any problems I have had have been ROM-related. The Kernel has been as solid as my **** at strip club (VIP room, of course).
[EVO 4G Android Development] locozildjiangodx:
has anyone else had any issues with this kernel and some hang ups? Sometimes, on this kernel only, I get launcherpro force closes, app drawer 3 or 4 second hang ups (comes up but cant scroll/select apps), browser lag, and sometimes hang ups in apps (gmail specifically)? For the most part the kernel is fantastic, but any suggestions for those problems?

I have done a full wipe and refresh on it, it has happened on cfs and bfs (it was a little better on bfs so I stuck with it), it has happened on smartass and conservative as well (both with screen off settings in place).

Any ideas?
[EVO 4G Android Development] itlnstln:
Try not using SetCPU. I have had no problems with any ROM I have tried, but I don't use SetCPU. The big question would be if you have determined if the ROM (what ROM are you using?) or the kernel is causing the problem.
[EVO 4G Android Development] phyba:
I had the same issue....I just flashed bfs version and it worked fine. Never had issues with cfs builds before but 1.6 would boot up the first time and then hang on a reboot at the splash screen. Not sure why.
[EVO 4G Android Development] locozildjiangodx:
Im using the latest stable CM rom. 6.1.2 i believe. And I have tried both bfs and cfs. I can try using no setcpu and let ya know
[EVO 4G Android Development] thenags:
Gonna try 1.6 CFS on CM 6.1.1 right now.
[EVO 4G Android Development] thenags:
Flashed with no problems. So far so good.
[EVO 4G Android Development] thenags:
Well that was short lived. Just rebooted the phone and it now wont boot past the white EVO screen
[EVO 4G Android Development] BlueHarford:
Web Designer /Graphics Guru needed!!

Looking for a Web designer / Graphics guru to join our team and donate his.her time.

We are creating a website for the kernel, and some graphics for another surprise. Please shoot me a PM if you would like to get the requirements and submit your idea.
[EVO 4G Android Development] Mac N Ts Daddy:
Love to the Devs!

Thank you guys for this amazing work. If there was such a thing as a "God Kernel" this would be right there at the top. I have been using the SBC kernels since CMtrickle.zip and have noticed nothing but goodness. Keep up the good work.
[EVO 4G Android Development] system60:
Been running cfs 1.5.2 for over a week now and it has been nothing short of stellar on CM6.1.1, which had flaky wifi with the stock kernal.

Keep up the good work.
[EVO 4G Android Development] newone757:
That's great news for me. U guys are the best
[EVO 4G Android Development] jr19703:
Have issue with my computer reconizing phone with 1.6. Charges but no option to mount sd card? i have to go into recovery to connect and push files.

Jason
[EVO 4G Android Development] aimbdd:
No problems here on any version
[EVO 4G Android Development] suavestats718:
can i use 1.6 on the cm7 build?
[EVO 4G Android Development] Tyzing:
Same thing happened to my buddies phone while mine works perfectly...
[EVO 4G Android Development] BlueHarford:
Make sure you try cfs
[EVO 4G Android Development] ms79723:
Which rom are you using? I've noticed the same thing with MIUI but that only happened once I flashed another kernel right after flashing MIUI then flashing back to 1.6. Flash a previous build and see if that gets it working, if so, flash 1.6 right over that and see how that goes.
[EVO 4G Android Development] thenags:
So now that I got my issues fixed my phone is running great. So I had my coworker flash it on his phone that is also running CM 6.1.1. Wiped cache and dalvik.. Flashed Salvage. Booted up great. Ran it for an hour. And after a reboot his phone got stuck at the white Evo screen as well.
[EVO 4G Android Development] mykenyc:
Don't know if your saying the issue is fixed or not, but sometimes i get white screens when my usb is plugged in don't know why, and few times when it's not, but mostly when it's plugged in. I just do a battery pull.
[EVO 4G Android Development] thenags:
To fix the issue on my phone I did a nandroid backup from a week earlier. I still wasn't able to boot until I wiped cache and dalvik again. Then I flashed savage AGAIN and it finally worked.

Now flashing it onto a friends phone he's having the exact same issue. Won't boot past the white Evo screen... Trying to wipe cache and dalvik now.

EDIT; After the 3rd wipe it seems to be booting up.
[EVO 4G Android Development] FlowingAway:
Hey all what's the proper settings to overclock this kernel a lil and not flip it out? I'm running CM 6.1.1 and flashed this kernel and set the MAX to 1.19 and almost instantly the phone froze and rebooted and continued doing that until I flashed another kernel.
[EVO 4G Android Development] luisrcastillo:
Savage Kernel Users:

Today has been a great day for the community specially the savage kernel. A few days ago we joined forces with a great developer. We stopped the beef and drama and we are working to deliver the best kernel for you. See the screenshot to see what's coming....

Doing closed testing but an alpha version may be coming your way very soon. Stay tuned!!!
[EVO 4G Android Development] nosfanatic2006:
Try lowering your max to 1113. Any higher and my phone starts freaking out too. Just keep lowering your max till your phone calms down. Possibly try rewiping dalvick and cache, or even redownload the kernel and flash it again.
[EVO 4G Android Development] Lento10:
Looking forward to the new kernel, if you need another tester let me know.