yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Congo123:
"As of now, it will always default to 364 when the screen is cycled. I'll talk to netarchy about changing this. What are you guys getting at the 364 kernel default setting? Also, what rom/radio are you guys using?"

@AssassinsLament

Hardware: 002 Nova

T2 at 364: FPS average 28 ; stdev=6.22

ROM: DC 3.2.3

Radio: 2.05.00.06.10
[EVO 4G Android Development] psychopsilocin:
I'm on the latest OTA, rooted. I'm getting 53fps average with about 10-12sdv. On performance setting, its about 4-5 sdv. Gears is seeing similar numbers, getting as high as 55. Kudos on the progression.
[EVO 4G Android Development] spiicytuna:
This works great for me. No tearing, no stuttering. What was your reported fps? How many times did you run fps2d?

I initially had the same findings as you. Couple questions; are you overclocked? Using setcpu? Do you run ondemand or performance? If you use ondemand what is your sampling rate and threshold under the advanced tab?

Same question as above: Are you overclocked? Do you run ondemand or performance? If you use ondemand what is your sampling rate and threshold under the advanced tab?

Care to give any more info? What ROM? 002? 003?

See post #491
[EVO 4G Android Development] AssassinsLament:
What netarchy kernel revision are you using?
[EVO 4G Android Development] netarchy:
Woops! Link should be fixed now
[EVO 4G Android Development] brol1k:
yes hell yes I sure do man, its eating my battery like crazy with launcher pro
[EVO 4G Android Development] deathsled:
what do I have to do to get CIFS working? You say support has been added in but I sure can't make it work the same way I had it working with an older king kernel. I'm just trying to mount a share using cifs manager, nothing I haven't done before. Should we still have to load the module manually? I could never get it working without using to option to manually load the cifs.ko from some place on my SD card vis insmod. That doesn't even seem to work here.

**nevermind I got it. Not sure why it's working now but I cleared all the settings and set it back up again and it's working. Craziness.
[EVO 4G Android Development] netarchy:
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, all SBC kernel build links have been removed from the first 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] Nutzy:
I didnt know there had been problems... you 4.3 CFS HAVS LESS AGRESSIVE SBC is the best battery life rom Ive ever used... You should bring them back
[EVO 4G Android Development] buck1623:
im with him.... i unplugged this morning at 630am, by mid day, i was down to 88 percent with couple of phone calls and texts and facebook browsing...
[EVO 4G Android Development] Compusmurf:
It was pulled because there is now multiple reports of battery charge fails and now a report of a battery venting.

Proof that all electronics run on "smoke". :) Once you let the smoke out, electronics fail!

Sorry, lame old EE joke.
[EVO 4G Android Development] BuddaBelly:
Did we lose 5 point multitouch with the latest kernels? I used to have 5 point and since going to the latest kernels I have seemed to have lost that. Dotty is only showing two points. Not a huge deal just wondering if it was the latest base.
[EVO 4G Android Development] freeza:
The one based on. havs... is it also based on aggressive?
[EVO 4G Android Development] netarchy:
Still tracking this one down. It doesn't affect everyone (for instance, 5point is working perfectly on my evo), so far it seems to only affect people with a nova panel, based on reports.
[EVO 4G Android Development] d0cx:
It's happening to me as well. Only 2 points. Nova screen. :(
[EVO 4G Android Development] BuddaBelly:
Thanks! I can tell you my wife's phone rev 003 Epson works fine so I would for sure think it's just Novas.
[EVO 4G Android Development] wfrandy:
As you already know, mine is a nova too.

Funny thing is, the main reason I use your kernels is because the 5 point is something that I actually use. Other than that I would just stay with the stock kernel. The funny part is, if it weren't for the 5 point I probably would never have tried this kernel, but 4.3 cfs/havs/less/nosbc is the first kernel I have used that gave me significantly noticeable battery life improvement over the stock kernel.

So, while I really miss the 5 point touch, this is, without a doubt the best kernel I have tried so far.
[EVO 4G Android Development] Product F(RED):
You guys should not be using the SBC kernels (trickle charge). It's killed peoples' batteries. Read this thread: http://xdaforums.com/showthread.php?t=904577
[EVO 4G Android Development] fixxxer2008:
5 point multitouch lost here too running a 004 evo. ill keep the kernel until a fix comes out though. if not it may be back to stock for me for awhile.
[EVO 4G Android Development] ryanalan82:
I've been trying all these net kernels lately, running mikfroyo 4.2. The smoothness is there but not the battery life. I'm on 4.3.1 bfs havs no sbc now and thats giving me the best results so far. I'll need more time to really see what the battery is like. At idle these kernels are awesome but as soon as I use the phone, it's just downhill n fast. And for the record I'm still comparing all other kernels to king's bfs 11, which is the smoothest, and gives me 12 or so hrs with moderate use. But I'm looking for that magic combination that gives me 20 hrs plus as is everyone else.

Swyped from my Evo
[EVO 4G Android Development] fixxxer2008:
ive noticed that too, sometimes it drains faster than the stock kernel does. it seems idle the battery is saved and that's it.

net will there be an update for some of us this weekend?
[EVO 4G Android Development] dglowe343:
0003 nova here with 5 point working. Running 4.3.1 bfs havs no sbc.

Sent from my HTC Supersonic
[EVO 4G Android Development] brol1k:
Ran an sbc kernel for a few days and felt battery disintegrate switched back to no sbc kernel and now don't intend to run it anymore. Battery does just fine with nets no sbc kernels. Only thing I wish is battery drained less when I'm using it but at least sleep/wake mode it does wonders.

Tapatalk'd on Evo
[EVO 4G Android Development] Adam1422:
With the 4.3 set are we back to wiping the battery stats?
[EVO 4G Android Development] netarchy:
When did we ever need to wipe battery stats?
[EVO 4G Android Development] jelive:
Believe so...that feature was in the SBC-Net versions.

Jim
[EVO 4G Android Development] jelive:
Answered apparently as you were...We don't ever need to wipe battery stats when flashing a new kernel? Is this another one of those urban legends :D

Jim
[EVO 4G Android Development] netarchy:
That's an urban legend. I have never advised wiping battery stats as a matter of course for updating a kernel.

There are some limited situations where one might want to wipe battery stats in the course of troubleshooting, but those situations are few and far between (not to mention unrelated to simply flashing a new kernel).

It's generally a good idea to wipe cache and dalvik-cache to be on the safe side, but that's it.
[EVO 4G Android Development] gpz1100:
First off, what are battery stats, besides the obvious. Meaning, yes, they're statistics for the battery, but specifically what statistics?

If we understand this, then it might be clearer what the results of wiping or not wiping them might be...
[EVO 4G Android Development] xlGmanlx:
its the metrics your phone uses to determine battery percentage is my understanding, once you change your kernel to me thats what folks mean by settling in, getting your phone normalized on the batt stats
[EVO 4G Android Development] fixxxer2008:
net there's alot of debate about the sbc mod, why did you pull it from your kernels? im just curious is all.
[EVO 4G Android Development] Diplomat2387:
Can anybody point me to the correct kernel that he is using..I am confused...I can't find the 1 he is referring to...I am running Fresh ROM and just want to try a custom kernel to try to improve battery life.
[EVO 4G Android Development] h3nG:
Anyone else notice their internet speed are slower after installing this kernel?
[EVO 4G Android Development] gpz1100:
From reading the different guides, it would appear that resetting the battery stats resets the 100% mark of the battery. All the guides i've been reading on this say something to the effect of charge the battery fully. Let it run down completely, recharge again (powered off, even after green light is on), then up on that first boot, clear the battery stats.

Similar to setting a throttle opening/closing points on a power commander so that the bike's throttle movement is in sync with the map installed. - (if you don't know what a power commander is, disregard this line).
[EVO 4G Android Development] ElAguila:
I have been using your kernels for a while now. I just wanted to make sure I didn't misread the change logs. The 4.3 beta uses the conservative govenor instead of smartass. Is this correct?
[EVO 4G Android Development] Wisiwyg:
Hi Net,

I haven't seen anything about this and have been following the thread since the start...and using your kernel. Wonderful stuff.

So my question, and let me apologize now if it's been covered somewhere, recall that 'ages' ago you would build ROM-specific kernels, i.e. 4.1.9.1 CFS Fresh Compatible, that had start-up scripts unique to the ROM. Lately, all of the kernels are Universal, which I assume don't have the start up scripts.

How should we address the scripts if we do a full wipe to try out another ROM? I guess the new ROM will always include a kernel with its own unique startup scripts and then we could flash over your latest Universal. What do you recommend?

Thanks.
[EVO 4G Android Development] netarchy:
It became far too much of a hassle to try and make individual builds with the tweak scripts for each of the various roms available (especially as the number of roms keeps growing), so I went with the universal build approach and put the scripts into burnt droid.

The universal approach is arguably better because it preserves any startup scripts a rom author has in their particular rom (this was actually the reason individual builds had to be made in the first place).
[EVO 4G Android Development] xlGmanlx:
Net any updates on your.35 kernels? You had them in beta a while back
[EVO 4G Android Development] Admiral2145:
undervolting

am I missing something or? no more less or more undervolting?

TIA
[EVO 4G Android Development] Adam1422:
Net, can I get the 4.3.1 cfs morehavs sbc kernel...pretty please! I must have missed it when you had it posted. my phone loves your kernels and I have had no problem with the sbc add on either.

PLEASE!
[EVO 4G Android Development] EJerVJerO:
People really ruined the development of SBC into other kernels with this battery talk :(
[EVO 4G Android Development] xlGmanlx:
people? we are talking about less than 10 people and only a few actual experiences
[EVO 4G Android Development] cheebahawk:
Sorry guys if this has already been posted and/or answered:

I am currently running Netarchy's CFS More Aggressive 4.2.1 (aka 131), I think this is the best kernel out for battery life on the Evo and wanted to know which version of netarchy's 4.3 kernels is most like 131?

I want to upgrade to the newest kernel but would prefer to go with the 131 upgrade (dont know if that sentence even makes sense).

Would it be correct to assume that Netarchy Toastmod - 4.3.1-cfs-havs-more-sbc is the 4.3.1. 131 version of 4.2.1. 131?
[EVO 4G Android Development] EJerVJerO:
Exactly I am sure you have seen my posts on the other posts. It only takes a few people to start a riot :) So far it seems like quite a few people who have no clue what is going on are joining the riot looking at the other threads :)

We still haven't even proved 1 single incident was from SBC yet as proven by netarchy's thread we just lost one kernel with the tweak that isn't even been proven to be at fault.
[EVO 4G Android Development] xlGmanlx:
check your PM
[EVO 4G Android Development] chogardjr:
Seriously these handful of "people" probably used some after market charger that was not rated for the crappy Evo batteries. Netarchy has some of the best kernels I've ever used. SBC mod or not. Who cares about SBC, we all eventually have to plug in our phones. What needs to happen is someone should make at least a lithium polymer battery for the Evo.

From a Super Baked Evo #0002
[EVO 4G Android Development] chogardjr:
It should be pretty much the same except its universal and has the #0004 camera build in it.

From a Super Baked Evo #0002
[EVO 4G Android Development] deathsled:
jesus you guys...

http://www.qap.la/~netarchy/

You can have all the SBC kernels you want, they're right there on his site just as he said, learn to read

And you know what? I'm sure netarchy is going to continue working on these kernels. I'm sure as a legit developer for this platform he will be interested in determining if his work really is the cause of some battery issues or not.

And you know what ELSE? I'm still running an SBC kernel. I loaded up 4.3.1 last night. I didn't tell people to stop running these kernels and I didn't even say I was going to stop necessarily. Now that my phone is back up (it was down for 3 whole days, the battery would not respond) I can start tinkering again. I'm not sure if I really want to try to duplicate the issue again because if I do that could mean another day or two down or worse, but I'm curious at least.
[EVO 4G Android Development] cheebahawk:
I agree it seems a lot of speculation on everyone's part and no solid evidence or direct link that it is ONLY the SBC mod that is causing the problems. I dont think anyone has isolated SBC as the sole issue in causing problems with their batteries.

Most people have had the Evo for almost a half a year now, which means some battery degradation is expected. Especially when you consider the fact that the Evo battery & charging method is a POS and ppl constantly charged their Evo all day (not going thru proper battery cycles, etc) . Also a lot of people purchased and use cheap $10 knockoff batteries and chargers from Ebay, which is probably worse than SBC in terms of problems that it can cause.

If there is proof, why not post it directly in this thread, instead of sending PMs? I'm sure everyone here would benefit from direct evidence that shows cause (SBC) and effect (dying batteries or worse), and something more than speculation or correlation.
[EVO 4G Android Development] xlGmanlx:
was totaly unrelated
[EVO 4G Android Development] cheebahawk:
ahhh gotcha. Sorry I saw your post right after his and figured you had proof of SBC problems.:D
[EVO 4G Android Development] EJerVJerO:
I wasn't quite directing it to you or anyone in general. I just don't understand how such claims started getting out of control and everyone blaming a tweak that was discovered by someone and used in a vast majority of kernels. I am all for finding out why the people who ended up in a very bad situation did but again we might not even be able to pin it exactly now that most didn't have anything on their phones to track battery voltages, heat, or what everyones setup was.

Development / running non standard software/hardware does sure sometimes cost you some money that you might not have planned on. This is proven by people who lost RSA keys up to including I believe Shinzul also went through it while developing the 4G for CM.

My responses are purely about how the issues went from a "possibly caused by SBC" to "it was 100% caused by SBC"
[EVO 4G Android Development] chogardjr:
I agree. It's out of control and ridiculous. We need to get back track like we use to and try new things and do our personal tests based on how we personally use our phone, LIKE WE USE TO. I think its funny really but really don't want to read anymore wasted thread space about it.

From a Super Baked Evo #0002
[EVO 4G Android Development] EJerVJerO:
+1

I wish there would be a thread started on trying to find out what causing the issue don't tag it as any kernel or sbc related just find out why these 10 people or however many people have come out of the woodwork to say their phone / battery blew up. Everyone needs to get to finding issues and improving the community and development instead of killing it off with unfounded claims against the same thing. Remember there is a gap between giving people a warning, trying to figure out why an issue is happening, and coming out saying something is at fault without any research or data backing it up.
[EVO 4G Android Development] cheebahawk:
It seems that 4.3.1. fixed the screen tearing issue that some experienced in 4.3.

I was wondering if you look at http://www.qap.la/~netarchy/ the following are listed:

4.3.1 CFS

SBC:

Netarchy Toastmod - 4.3.1-cfs-havs-sbc

Netarchy Toastmod - 4.3.1-cfs-nohavs-sbc

The 4.3.1. CFS has no CFS-HAVS-MORE-SBC but if you look at:

4.3 CFS

Netarchy Toastmod - 4.3.1-cfs-havs-more-sbc

It actually lists 4.3.1. version of HAVS-MORE...

My question is, is this a typo? Is 4.3.1. CFS-HAVS-MORE-SBC listed under 4.3. really a 4.3.1. version? I've flashed this version and in the software info it states 4.3 CFS-HAVS-MORE-SBC and not 4.3.1.

Can someone with 4.3.1. kernel flashed let me know if it says 4.3.1 or only 4.3?

if this is only 4.3 version of HAVS MORE:

Netarchy any plans on putting up a 4.3.1. CFS-HAVS-MORE-SBC version? I imagine you are busy as hell but I'd appreciate it!
[EVO 4G Android Development] jelive:
Well, another one of those misunderstandings that just spreads like wildfire...thanks for info.

Jim
[EVO 4G Android Development] SteelH:
You might want to read the numerours reports and PHOTOS of damages reported by using SBC kernels HERE
[EVO 4G Android Development] netarchy:
It was a typo, fixed now.

I have no plans currently to make any more SBC builds.
[EVO 4G Android Development] EricSS619:
Hi all, I'm on my phone and drunk so forgive me if I'm totally off, but is it possible that the under volt kernel could cause my camera to stop working? I flashed the new warm rom and this kernel and realized my camera no longer works, just a black screen pops up now. :(
[EVO 4G Android Development] dcharleyultra:
I do not know, but you can flash a stock kernel and find out yourself.

Swyped from my Evo 4G using Tapatalk
[EVO 4G Android Development] buck1623:
this is with your 4.3 havs bfs more sbc kernel.... no charge over night either...
[EVO 4G Android Development] cheebahawk:
Bummer... Since I love SBC and I think there is too much speculation on whether SBC is a problem but no concrete evidence. But I completely understand.

Any plans on putting out a 4.3.1. HAVS MORE CFS then?:D
[EVO 4G Android Development] buck1623:
honestly i think you should keep the sbc builds for the "selective" people... most of us still us sbc....
[EVO 4G Android Development] cheebahawk:
Agreed, I wanted to say it but I figured if he made up his mind, there is no point in trying to persuade him... But that would be sweet. Here is hoping that MS will keep putting out new SBC and kernels based on Netarchy's stable builds (which he seems to be doing).
[EVO 4G Android Development] matthewjulian:
2.2.1 cfs havs-less is running great on myns RLS5, oc'd + screen off profile for uc...just wiped battery stats so I can't speak on batt life yet...

Sent from my White Warm Evo!
[EVO 4G Android Development] netarchy:
Here's what I'll do. I'm still not going to post more SBC builds in the forum thread.

I'll grant that nothing has been 100% conclusively linked to SBC in regards to any of the battery stories going around, but I am not going to put builds in the thread if there is any possibility they can cause actual -harm- to the phone.

I don't need a newcomer on their first custom to lose their battery or worse on the off chance that the mod happened to damage their hardware (and we all know that many people are initially unsure what build suits them so they try one at random or on advice, hence removing them from the thread).

What I will do is keep some SBC builds on my website for those of you who are -aware- of any possible risks that using the mod may or may not present, and consciously make the choice to use those builds bearing that in mind.
[EVO 4G Android Development] stricklerjosh:
What setcpu setting are you guys using with 4.3.1 havs no sbc?

mikfroyo evo!
[EVO 4G Android Development] Agfadoc:
Thanks!

That's fair.
[EVO 4G Android Development] buck1623:
NOW THATS COOL! so one more question, when you do make the sbc builds, could you update the first page here stating you made an update? if u do that, it'll be AMAZING!
[EVO 4G Android Development] ryanalan82:
4.3.1 cfs havs nosbc is flawless. Battery life shot through the roof with this kernel, above everything else I every tried, and its smooth as can be.

Swyped from my Evo
[EVO 4G Android Development] buck1623:
you gettin this life?
[EVO 4G Android Development] mildlydisturbed:
Running 4.3.2-bfs-havs-sbc and it appears to have corrected the weird screen issues I would sometimes have when it started up.

Seems to be quite responsive so far. I am digging it...

I forgot - the charge time is incredible - it just gets on up there... don't even have to leave it on overnight any more...
[EVO 4G Android Development] gpz1100:
What sort of batt life were you getting before? Similar usage, standard battery?
[EVO 4G Android Development] EricSS619:
So does nobody else has any problems with their camera and this kernel? I tried reverting to stock and then reflashing and my camera just wont work when I flash this kernel. Anyone have any ideas of what I can do to fix this?
[EVO 4G Android Development] cheebahawk:
Thats awesome! Thanks for being so accommodating, I know you dont have to do it but I love how you are willing to go the extra mile!

Is it because of time or will you also no longer be doing MORE or LESS CFS Havs builds (including SBC builds)?
[EVO 4G Android Development] ryanalan82:
8-12 hrs from heavy to moderate usage on king's bfs 11.standard battery. O/c'd to 1152 on conservative. Now I'll be getting at least 12 with heavy usage. If I could stay on my phone all day I would....... Oh wait, I pretty much do, lol.

I was wondering though netarchy, what do you do different for havs in 4.3.1 cfs havs nosbc? How aggressive is the havs?

Swyped from my Evo
[EVO 4G Android Development] EricSS619:
OK I was reading the update notes wrong, I was reading the beta notes and thinking that it was referring to the stable version.

Looks like Ill need to try the beta if I want a working camera.
[EVO 4G Android Development] Atticustrd:
What does pri do? I'm on 1.90 and trying 4.3.1 cfs havs, and my battery drain is very high and temp to. When I browse im hitting 100 degrees. Will it affect anything else if I go down to 1.77 pri?
[EVO 4G Android Development] bigupurself7:
It won't effect anything else, I downgraded right after I upgraded. I was having lots of problems. This should teach us not to just upgrade things when we don't know what they do and the newer is not always the best!
[EVO 4G Android Development] Agfadoc:
I've been trying out 4.3.1 and my phone has never been this smooth...

Haven't determined battery life just yet, but I almost don't care..

Great job Net.
[EVO 4G Android Development] deathsled:
I noticed the same thing and had to downgrade to 1.77 as well. I'm wondering now if that combination is actually the culprit for the "SBC battery failures". I'm not sure I was seeing the same kind of drainage problems though when using 4.2.2
[EVO 4G Android Development] Agfadoc:
I down graded to 1.77 pri also
[EVO 4G Android Development] Atticustrd:
So just flash 1.77 pri right? Whats the NV should I flash that one to? What is pri? Ive seen reports of people bricking their phones when flashing radios id hate to do this myself.
[EVO 4G Android Development] BuddaBelly:
I also downgraded to 1.77 but left NV at 1.90. Everything is running smooth. Had terrible battery life on PRI 1.90