yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Persnlmgr:
[EDIT: Okay, 4th time screen wouldn't come back and I had to pull battery. I'm going back to Ziggy471 12/17 CFS for now, but will keep checking back. This is a GREAT concept, but I rely on my phone so gotta go stable... And for Dev, I'm running Myn R4 on HW0003, if that helps... ]

So, I was researching this kernel yesterday and it piqued my interest.

I don't think I've used a Netarchy kernel since R2 for some reason, but a lot of y'all really swear by 'em, so what the heck. It seems like a great concept as far as battery life goes, so I flashed 131.

However, I'm already having a few quirks.

Under Software Information/Kernel Version it reads:

2.6.32.25-netarchy-toastmod-4.2.1-cfs-bfq-havs-more-smartass

There's no indication that it's a custom blend, and I'm wondering if I should turn SetCPU off as it says "smartass" right in the name. (The only thing I use SetCPU for is to set scaling to Smartass on boot, with no profiles).

On Ziggy and HTC kernels my battery (when plugged in) shows fully charged at 4204mAh. On this one, 4188. Not much difference, but enough for a phone call (or 30 seconds of Angry Birds).

Also, I'm used to a longer boot when I first flash a kernel, but then it goes back to the normal semi-quick boot thereafter. Not this one. It seems to take noticeably longer every time.

This thread cites people's screens not sleeping as a past known issue, but says nothing about the opposite. Twice (in 3 hours) I have not been able to bring my screen back from sleep, (happens to me personally all the time...), and had to do a battery pull.

For the last 45 minutes my battery widget has shown 100% and 4188mAh, but it's also still "bubbling", and the Notification Bar battery still shows as Charging. This is a bit vexing...

Anyone else trying this kernel got any feedback or opinions?

Inquiring mind wants to know...:confused:
[EVO 4G Android Development] beerad29:
Update with 129

MS - man you finally nailed this for my phone. My Evo has a Nova panel V003 hardware and I have the Seidio 3500 mah battery.

I loaded 129 last night before bed. Charged overnight woke up and the charging characteristics showed a perfect trickle charge. I am now running Net's BurntDroid 1.4 ROM. SetCPU is set for one profile - screen off @245.

My battery has been up for over four hours. The battery stayed at 100% for almost an hour and is now showing 96% with email, texts, some web usage. This is absolutely the best my phone has performed since I have bought it last July. What I find really interesting is that I have used mostly Net's kernels either 4.2.1 less aggressive SA or no HAVS. This is the first time my phone has performed well with the more aggressive SA. I changed from smartass to conservative governor on SetCPU reading Net's newest 4.2.2 update.

With no OC, my Linpack scores are 34.6-35.5 and Quad consistently 1415-1430. I do hope that you get credit when other kernel builders start using your charging profile.

Excellent work!:)
[EVO 4G Android Development] bmark34:
I also am experiencing my phone being constantly awake with this kernel. I was overclocked, and I set back to 998 with no profiles on setcpu. My battery drain is slightly less then what it was on ziggys 12/17...it did stay at 100 for 5 mins. I'm at 85 after 30 mins of xda browsing with wifi on. My phone had become laggy and I'm going to load netarchy's less aggressive (my normal kernel)

Update: my phone has now gone into a tailspin and phone continued to freeze up and all apps were crashing, I booted into recovery and cleared data, cache, and dalvik and reinstalled Myn v4...my phone now sticks at the white HTC Evo screen. I restored a nandroid backup and that works (but its from 3 months ago). Any one have any suggestions to resolve my issue to get Myn back up and running?

- from my battery sucking vampire Evo
[EVO 4G Android Development] casper97ta:
Im running myns rls4 on HW 0004, has this been proven to work on that combo yet?
[EVO 4G Android Development] sag7392:
@ms79723

I've been following your thread. I have to say the idea is good, so good that I switched to your/Net's tweaked kernel. I even installed the battery monitor widget to see if it is working...which so far it is. I did notice my battery temps jump to 100 degrees, but settled back down to the low 80's. Other than that, everything is working fine and I plan on keeping a battery/usage log as well.

Great job!

FYI- I'm running Calkulin's EViO 2 ROM v1.7 (3.70.651.1) and SetCPU OC'd at 1075/245 (conservative) with a screen off profile (245/245). Also coming from Net's 4.1.9.1 universal aggressive, using the same SetCPU settings.
[EVO 4G Android Development] BAttitude7689:
just pulled it off the charger, after charging it past 100% so good so far put can anyone help me look at my screen shots & make sure that its doing what its supposed to be doing correctly, thanks
[EVO 4G Android Development] xlGmanlx:
looks good but doesn't look like it was done charging. you were at about 20mah when the OP says eventually it will go down to 0, but that is my two cents
[EVO 4G Android Development] roadster92:
Can't OC with OC widget

Anyone got problem overclocking the cpu with Kernel 131?

I can't overclock my CPU above 998. I have no problem overclock the CPU beyond 998 with the original Net 4.2.1

Thanks
[EVO 4G Android Development] xlGmanlx:
open setcpu - menu - autodetect - reboot

make sure you don't check set on boot until you know what works on your phone yet
[EVO 4G Android Development] roadster92:
I am using OC widget which work fine with the original net 4.2.1.

I did re-detected my frequency, saved (not auto start on boot)

but when I set it to the OC frequency above 998, It won't work.

And yes , I did reboot and doing it a few times too.
[EVO 4G Android Development] timdawgdentist:
on 129 since last night. Will flash 131 later. 129 is pretty impressive so far. Just the phone says its awake the same as uptime. I dunno if that info even means anything.

Great Job so far, my battery is very happy so far.

tim
[EVO 4G Android Development] luckylui:
Means ur phone is NOT sleeping...
[EVO 4G Android Development] Agfadoc:
The whole point of this situation was that the community, went on a witch hunt without any investigative information or facts.

The fact is that it only effected the Savage Kernels on AOSP. Period. Those are the facts that we are aware of. But everyone instead freaked out like lemmings and wanted to BAN MS! Force him out of the community, and blame him for their boo boo they got in the morning..

Silly rhetoric, and inflamitory innuendo was the corse of the day when every armchair "specialist" felt the need to spew their opinions based on ZERO facts.

But what could I expect, people can't even read the post above theirs, so of course I simply can't expect those silly facts to get in the way of a perfectly scripted public lynching.
[EVO 4G Android Development] BlueHarford:
We got our mod directly from his git, and MS is a direct contributer to ours. Our mod was exactly the same as everyone else's. Since I am one of the 2 developers of that kernel I can say for fact we did not change the mod. Why not ask the Devs before you make accusations of their kernels>
[EVO 4G Android Development] akiradavis:
To MS

Dude, I hate when people do not respect the hard work developers here at XDA do everyday. I just wanted to say dispite all the controvesy *bad spelling* surrounding this, your work is greatly appreciated.
[EVO 4G Android Development] mattykinsx:
I again ask this:

Who taught you that name calling strengthens your position?

The proof is in their posting.

Anyone can google something and post on it.

But it's very easy to tell in subsequent posts if that person is full of **** or if they actually have background in what they're saying.

Again, name calling doesn't strengthen your position.

Also, when did this happen?

This is all about the fact that even XDA has acknowledged that there is a potential for issues.

I love how you make claims of "spreading lies" simply because you don't agree with it.

It "drives me crazy" that it cannot be understood why this is different.

In all of the threads there is a warning.

When you root you get a warning about how you could brick your phone.

CM has a warring about the same.

Netarchy's kernels the same

etc etc etc.

The difference here is we have the suggestion, and people that have clear background knowledge in this, that these kernels may actually cause damage.

Instead of ms putting a warning up he actually endorses the idea that it won't cause damage.

That is why this is "being singled out"

So now it's come to the point where you will point fingers at other devs to defend ms?

That is completely inappropriate.

Your "evidence" seems to be completely wrong as evidence of jsseidel1's post.

IF ms would have put up the warning and not posted an endorsement of the idea that this kernel won't cause damage then the issue never would have come to what it has.

That is not an unacceptable request.

Side note: my "coloring and bolding" has nothing to do with personal recognition. As far as I'm concerned you can cover up the username posting this. And I don't care about "thanks" either.

The bolding and coloring is because after all this discussion you still have people asking "What happened" and other posts showing complete ignorance of the situation.

I only colored and bolded the most important parts so it stands out and people can understand what the actual issue here is.

Who said it wasn't? This has nothing, at all, to do with his contributing to the community. Read a little.
[EVO 4G Android Development] Agfadoc:
I didn't mean to single out one developer, because I like the savage kernel.. But I was only trying to point out that as testers and developers, we should be immune to the craziness of emotion and look simply at the interaction and why's of what is happening.

I am certain that given time and information it could be resolved on any kernel for that matter.
[EVO 4G Android Development] swaze:
Personal attack removed

Sent from the HTC EVO 4G
[EVO 4G Android Development] Ceger:
Can someone "in the know" (as we seem to all of a sudden have many of them) tell me why the same battery that is used across the TP2 and WinMo variants, Hero and other Android phones, etc. has no such battery percent issues as on the EVO?

Why does the same battery charge to full and work from 100% from pulling the phone off the charger with no immediate 10% drop, yet the EVO does this?

Why does the battery appear to trickle charge on every other phone but the EVO, and now it is unsafe to do so on the EVO.

Why is the same battery so much more volitile on the EVO as opposed to many other HTC phones that experience no such battery drain issues from 100%?!?

Please enlighten us.

Ceger
[EVO 4G Android Development] Agfadoc:
BRAVO!!

My Blackberry charges to and stays at 100%, My laptop charges to and stays at 100% my Ipod charges to and stays at 100%, my freaking Sandisk MP3 player does too..

Why haven't these all "Blown up"? How does this equate?
[EVO 4G Android Development] Ceger:
Seems to me that many kernels should be under scrutiny for making the battery not behave as it should. Overclocking causes more pull on battery, HAVs draws different levels formt he battery than engineered to, etc.. Why is this the only one under such scrutiny?

Want to make eveyone take a step back on SBC? Fine, but then takethe same exact mentality with every kernel. My major issue here is the singling out.

Ceger
[EVO 4G Android Development] numus:
Because they used a less precise ADC circuit.

Wow.. and what do those 3 things have in common? Nothing... And if you dont believe WinMO and other device's have had this same problem and "blown up" I have a dell axim x51v with a curved battery door that begs to differ.

There is a reason I barely read posts in XDA... If you are going to make a statement about what should be scrutinized, please actually research and understand the differences between things and then determine what is actually not within engineering specs.
[EVO 4G Android Development] Ceger:
Link?

Ceger
[EVO 4G Android Development] matt2053:
Lithium Ion batteries.
[EVO 4G Android Development] numus:
Ya and my friends ford fusion has a lithium ion battery.. still doesnt mean they all are correlated the same way or even read the same way. In android, the battery status and apperent voltage is determined within the linux kernel, something that isnt the same for any of the other devices you mentioned. I can program a evo kernel that will tell you you have 100% all the time.. it is actually very simple to do, would that make you feel all safe?

Oh ya.. for future reference.. my Asus UL80V(t) laptop will only charge the battery if it is less then 95% capacity.. if it is 100-95% capacity it will disconnect the charge circuit and utilize AC only and leave the battery at its current capacity. Asus did this as a battery longevity enhancement.
[EVO 4G Android Development] Product F(RED):
Because the batteries and chargers for the other phones are designed to use trickle charging to stay at or near 100%. That reduces the lifespan of the battery drastically. The HTC charger that comes with the Evo is smart; it has a chip that controls the flow of electricity. Hence ms said at one point that "if you use your phone while it's charging with SBC, you might notice negative mAh's", meaning the green light would be on but the phone would stop charging until you unplugged it and plugged it back in. The Evo's charger, by default, charges to 100%, then lets the battery drop to 90% (while the LED is still green and the phone says Full), then repeat until you unplug it.

Sidenote, why is it alright that people who say they are engineers and professionals have reasonable answers, while the ones with absolutely no experience or data to back up their claims that there are no potential damaging effects just keep saying it's not true? I mean, it's easy for you to say "go kill yourself" or "that's a lie" with nothing to back you up. On the other hand, people are presenting you with factual data and you just choose to be ignorant. You don't have to believe it if you don't want to, but don't go around calling us idiots for siding with the people who present us with facts.

And by all means, post the kernels. We never asked for them to be taken down. Go yell at ms for that. He's the one that yanked them down and pointed the blame at us. If he believes they're so safe, then why doesn't he just put them up with a warning? He even said a few pages back that no one asked him to pull them down. So do go around snapping at us. There are two sides to every argument.
[EVO 4G Android Development] Agfadoc:
Li-Poly batteries are the commonality...in the case of the Ipod and the Blackberry.. Li-ion in the case for the laptop. They all charge to 100 and stay there.

My point is they all have the potential to overheat without any intervention or alteration of the user...everything has potential. Recalls would not occur if they didn't.

Who do you blame for your Axiom battery overheating? Or others batteries dying early? Did you alter your specs from the manufacturer specified norm?

http://computer.howstuffworks.com/dell-battery-fire.htm

http://www.fixyourthinking.com/2005/06/apple-agrees-to-ipod-battery.html

Millions of results...
[EVO 4G Android Development] thenewguy821:
Sorry if this sounded accusatory, that was not my intent. The wording of my post should have been better. I didn't mean to imply that you guys DID change the code or settings. I should have said that with, so far, only one variant of the kernel causing issues, what is it in that kernel that is different. This is not to blame the developers of the savage kernel OR ms, It just seems something about the SBC mod doesn't agree with that kernel. Again, my apologies.

The proof is in their posting? You couldn't possibly be THAT naive. I can just as easily look up a bunch of links on Google, claim to be an engineer and list those links, saying, "As shown here..." That doesn't make me an engineer.

XDA did acknowledge the POTENTIAL for issues, not confirmed proof of issues. As for your comment of me not agreeing with someone so I said they were spreading lies, True, I don't agree with their post, and will STILL continue to say they are spreading lies because not 1 instance of a battery "Exploding" has been mentioned. There have been a handful of batteries that no longer take a charge, and only one battery that started to smoke. To call a little smoke an explosion IS a lie.

I didn't say they DID do anything wrong, and as seen in the first quote I replied to, I have already apologized to those developers. That comment wasn't to defend ms by blaming another developer, just pointing out that, so far, only one kernel has been to blame.
[EVO 4G Android Development] Agfadoc:
BS.. MS was asked to take them down from what I read...
[EVO 4G Android Development] GadgetMonger:
I read plenty actually. What you linked me to are posters who's Batt's crapped out. No exploding phones. We all know(well those of us who have done any research at all on the subject) that the SBC kernels may be hard on some batteries. How do we know? Because there ARE warnings. Off the top of my head I can think of at least 2 entire threads devoted to warning people about SBC. And in every case you linked there were symptoms leading up to the failure that the user simply didn't pick up on. So to me that means they were either inexperienced or under informed, meaning they probably did little or no research before flashing. Also, for every one of the cases you linked me to I can link you to ten or more where the posters shared how they are experiencing no problems whatsoever. You can go to any of the top rom threads here at XDA where the rom is reported as fully functional by most and find at least one who says that same rom crapped out his phone. Do we now pull the rom? Or do we all know by now that these are isolated events most likely due to the user or his/her particular device or setup? In the cases you linked I'd suspect cheap batts. As for your engineers and their theories, for me my hands on experience with the kernels themselves trump their theories. ;)
[EVO 4G Android Development] numus:
As someone who has personally been in situations like the above mentioned (developers vs forum admins)... and from the forum admin side, i can gurantee you havent read the majority of what happened.

Remember, it is always the forum admins who have everything to lose and actually have legal exposure. It is not a right to be able to post on a forum and that privilege can be taken away at any time for pretty much any reason.
[EVO 4G Android Development] SouthernEvo:
How about this for a fix , Correct the kernel so that 90% of the battery equals 100% on the battery being displayed . With the current charging set up of the stock kernel its gonna charge to 100 then drop down to 90 before charging again . Well consider 90% of the battery the 100% and go from there . I dont know $hit about programing a kernel but if I did I would do it . Both sides satisfied people can charge their phone normally with out compromising battery safety , and the battery displayed icon would reflect it correctly . Boom Apple signal bar fix ala battery icon . =)
[EVO 4G Android Development] Product F(RED):
Really?

Also, hold on while I dig up factual information on why SBC is potentially harmful to Li-on batteries:

http://xdaforums.com/showthread.php?p=10530215#post10530215

http://xdaforums.com/showthread.php?p=10409142#post10409142

http://xdaforums.com/showthread.php?p=10462779#post10462779
[EVO 4G Android Development] NewZJ:
my plugged in record is 5 days with no ill effects/heating/reboots/explosions i didnt have my phone wrapped or in an intentional hot location
[EVO 4G Android Development] numus:
Actually.. this is how the majority of devices are coded :eek:
[EVO 4G Android Development] SouthernEvo:
My point is HTC should have addressed this issue in the first damn place . Its apparent from some of the electrical engineers on the forums say trickle charging is bad so changing the charging routine is not a fix . Then why not change the way the battery charge is displayed on the phones screen and be done with it . Why again has HTC not done anything to adjust this is beyond me . Do they not even pay attention to what some people complain about , especially since the 10% drop has been an on going complaint by most HTC Evo customers .........

(end rant)
[EVO 4G Android Development] numus:
Question... Does the stock rom display the battery percent or does it just show a battery icon with different amounts of color in it?
[EVO 4G Android Development] scooter185:
Not sure about the iPod since it doesn't have a removable battery, and I've never owned a blackberry, but with the laptop, with it plugged in it charges the battery but also uses the charger for it's power. So it will charge the battery to 100 and then just use the AC from the wall. The evo doesn't do this, it is always using the battery, so after it's done charging the charger shuts off and the phone uses the battery and the charger stays off until it drops to 90, when it starts charging again.
[EVO 4G Android Development] Product F(RED):
That's correct. Battery power is essentially cut off and AC power is used until you unplug the device.
[EVO 4G Android Development] mcampos7:
Well I've got already got all the kernels, and I'm going to continue running them. If my phone blows up, catches on fire, turns into an iphone whatever. HTC or Sprint will be replacing it. As they should for pushing out a phone that seems to have been designed by a F***** idiot. Spint/HTC can go F*** themselves. I'm pretty pissed right now, if you can't tell. MS if you continue to develop any more of there kernels, I'd like to have them, so please let me know.
[EVO 4G Android Development] mattykinsx:
You're mad at Sprint/HTC for basic physics???

[Also, Sprint just carries the phone, HTC designed it so I guess if you're going to be mad at anyone...HTC...]

And I sincerely hope that Sprint or HTC will NOT replace it.

Your choice to abuse the phone.

Insurance isn't for intentional abuse.
[EVO 4G Android Development] Agfadoc:
Thanks for the link, I wasn't too sure about MS decision, but I got the impression from the Savage Kernel thread and the Netarchy thread that the pressure has been pretty high.

The operative word there is "potential". I am not saying it couldn't happen.. I know that it "could". It also "could" "potentially" all on its own without any modification..

My whole issue is that this was happening to people on AOSP Savage Kernels with SBC, shouldn't we as a community strive to find out WHY only Savage and SBC was the issue and nobody else? Do we owe it to ourselves to find out WHY?

There is a reason, I guarantee it, that only certain people experienced it, and because most of us are highly technical in the first place, we should set out for controlled tests to find out exactly instead of freaking out and asking for MS to be banned, SBC is voodoo, we should delete all posts.. and the rest of the emotional diatribe.
[EVO 4G Android Development] mattykinsx:
Everything you've said here is generally agreed upon.

But with what you've said here, doesn't it warrant a warning in the OP?

That's all that's been suggested, that and further testing.
[EVO 4G Android Development] Product F(RED):
That's all we, the ones who are cautious, are saying. Slap a warning on them like every other responsible developer has (Myn, Cyanogen, etc) and then go do your research (@ms). I don't understand why people are telling us to "go kill ourselves".
[EVO 4G Android Development] mcampos7:
Physics? Really? It couldn't have been designed to charge a battery properly based on physics?

[Also, Sprint shouldn't sell a phone for $400 with so many flaws, or at least without as many downfalls as the Evo, so yes I'm going to be pissed at sprint too.]

And I sincerely hope that you know I don't give a damn about what insurance is intended for.

GFYS
[EVO 4G Android Development] Product F(RED):
Yes, physics. Well, physics and chemistry, but mostly physics since that's what electricity falls under.