yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Undef:
Stop getting hung up on -mAs

A number of us have phones that will hover a tiny bit in the negative. This is normal. If you have Battery Monitor installed, look at the "Usage (mA)" graphs.

You will see a gentle curve approaching zero.

See the curves in the bottom (usage) graph as the top (available) graph nears 100%? That's the point of trickle charging. It gently charges your battery all the way up rather than slamming it then shutting off altogether. SBC puts a "throttle" on your charger.

The stock charging logic only know two speeds: balls-to-the-wall-all-the-way-on, and off. SBC makes it charge intelligently and gently.

See, the stock charger shuts off at the first moment the voltage reaches "full" (4200). But as we've seen using SBC, the voltage reaches the 4200 range long before the battery is actually fully charged. The SBC (trickle charge) logic continues to charge at lower and lower rates until the battery is really full.

You'll know it's working when you unplug your phone and it does NOT seem to lose 7-10% of its charge in the first 20 minutes.

Please don't get hung up on whether you see a minus sign, or the number never actually hits zero. If the number is single-digit--whether positive or negative--you're getting the benefit of SBC. If you unplug your phone and the battery percentage falls linearly through its entire range (instead of dropping like a rock for the first few minutes, then stabilizing), you're getting the benefit of SBC.

Undef

P.S. Oh, and ignore the start/stop times on the graphs. I changed the refresh rate just before taking these screenshots. The graphs show a couple days of use.
[EVO 4G Android Development] mroneeyedboh:
Cool man thanks for the graph. here is mine.

Seems legit
[EVO 4G Android Development] jelive:
Hmmm, interesting...I wouldn't think this would be an issue as those running stock HTC#15 (stock w/3.70) which includes drivers, aren't having issues...but ? Batt mod should have no impact.

Jim
[EVO 4G Android Development] mwielgosz:
I've never personally tested #15 to see how it runs, but when I run netarchy 4.3, im getting the same kind of battery drain I had on #17. The issue may be completely unrelated, but I don't have anything else to blame as netarchy 4.2.2 runs excellent and not a whole lot changed between the two versions.

Evolved into a higher form of communication
[EVO 4G Android Development] netarchy:
CFS builds of 4.3 without the SBC mod are up for grabs.

Edit: Without the SBC mod, but *with* HTC's battery/charger changes from the latest ota
[EVO 4G Android Development] frifox:
and the verdict on which is better is... ?

anyways, just did a 30min idle test.. Battery Monitor Widget (stats logged every 60 seconds) says that the phone averages at around 97mA. if the battery is 1500mA then does that mean that the phone will last only 15 hours while idle??? a while back i remember getting 3 day battery life with little usage... something isn't right here :confused:

edit:

2010/12/31|15:33:10|- 40mA|100%|4122mV|30.9ºC
2010/12/31|15:34:10| -70mA|100%|4122mV|30.9ºC
2010/12/31|15:35:10| -98mA|100%|4122mV|30.9ºC
2010/12/31|15:36:10|-110mA|100%|4122mV|30.9ºC
2010/12/31|15:37:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:38:10| -96mA|100%|4122mV|30.9ºC
2010/12/31|15:39:11|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:40:10|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:41:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:42:11| -70mA|100%|4122mV|30.9ºC
2010/12/31|15:43:10|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:44:11|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:45:11| -62mA|100%|4122mV|30.9ºC
2010/12/31|15:46:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:47:10|-104mA|100%|4122mV|30.9ºC
2010/12/31|15:48:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:49:10| -72mA|100%|4122mV|30.9ºC
2010/12/31|15:50:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:51:10|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:52:10| -72mA|100%|4122mV|30.9ºC
2010/12/31|15:53:10|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:54:11|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:55:10|-108mA|100%|4122mV|30.9ºC
2010/12/31|15:56:10| -86mA|100%|4122mV|30.9ºC
2010/12/31|15:57:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|15:58:11|-104mA|100%|4122mV|30.9ºC
2010/12/31|15:59:11|-108mA|100%|4122mV|30.9ºC
2010/12/31|16:00:10|-106mA|100%|4122mV|30.9ºC
2010/12/31|16:01:11|-106mA|100%|4122mV|30.9ºC
2010/12/31|16:02:11|-106mA|100%|4122mV|30.9ºC
2010/12/31|16:03:11| -98mA|100%|4122mV|30.9ºC
2010/12/31|16:04:10|-106mA|100%|4122mV|30.9ºC
[EVO 4G Android Development] apfrost:
This kernel was horrible for me, but with the 4.3 everything works much much better apart from one issue. Sometimes when I reboot it gets stuck on the HTC screen.
[EVO 4G Android Development] gpz1100:
Netarchy, any thoughts on what's causing these reboot lockup issues? I know they don't happen always, but more often then not, and seem to be usb related (at least in my case).

Running SBC for Netarchy's CFS More Aggressive 4.2.1 (aka 131) does not seem to suffer from this issue.
[EVO 4G Android Development] mroneeyedboh:
and my case too. I duno if it was here or in MS79327's thread but I was having the same thread.
[EVO 4G Android Development] netarchy:
Elaborate when you say usb related, they're happening when the usb is plugged in and you reboot the phone?
[EVO 4G Android Development] MCLFLN:
I haven't trouble shot it enough to tie it to your kernel - but I have experienced a few hangs when plugged into usb and rebooting. It is of course, random - so it could be fun to track down root cause on.
[EVO 4G Android Development] lostsoul77:
How do I know if I have the old camera or new one? I have Rev 0003
[EVO 4G Android Development] netarchy:
Well, one way is if you flash any kernel build under revision 4.3, and the camera works, it's the old one. ;D

That said, 4.3 supports all the currently used cameras in the various evo versions.
[EVO 4G Android Development] mjohnson4580:
Netarchy, Is there any performance difference between the 4.3 with sbc or the one with out?
[EVO 4G Android Development] MCLFLN:
Another observation: twice now I have been rebooting into recovery when this hang happened.

I am about to try your new kernels without SBC and attempt to recreate the issue.
[EVO 4G Android Development] fastamx79:
I'm having 0 issues with 4.3 cfs-havs-more-sbc with Burnt Droid 1.4

To those with issues.. if you have SetCPU.. clear data, uninstall it, reboot into recovery.. wipe cache and dalvik, reflash the kernel, then once your phone is fully booted reinstall SetCPU, do the auto scan and make adjustments. This has worked on my phone in the past (003 with old camera and 5pt nova screen - bought in June '10)

In 5 hrs time of no use my phone dropped 1%

FWIW I am running conservative with min at 128 and max at 1075 with screen off profile with 245 max and 128 min (I do that because I stream internet radio and if I do 128/128 the audio is very choppy)
[EVO 4G Android Development] gadean:
netarchy, just wanted to drop by to report that v4.3 cfs-havs-more-sbc (using myn's rom with an old camera) is working great on my phone! I'm getting excellent battery life with unmatched performance. (1450+ Quadrant scores!)

I'm using SetCPU conservative with 128min/1152max & 128min/245max on screen off. Battery Monitor Widget is showing 0mA - 2mA during its overnight charge-- just what I wanted to see. (thanks ms)

I was so impressed with the results that I installed it on my wife's and friend's phone - both are very happy. Thanks for all you do for us!

I'll be sending you a well deserved donation.
[EVO 4G Android Development] gpz1100:
Before I flash any new kernel, I always wipe the cache and dalvik cache. The hard lockup (requiring battery pull) occurs when rebooting (normal), or reboot to recovery. I believe on one shutdown, the subsequent reboot was a hard lockup at the splash screen (not the animation screen that follows, but initial splash). Having the device plugged into the usb port on the pc seems to be the only commonality. That is, I'l have the phone plugged in, transferring some apk's or other data. Mess around with it for a bit (5-10 min?) I haven't been able to track a pattern down. Then, do a reboot to recovery. It does the reboot vibrate, then just locks at the splash.

As stated in the post you replied to (http://xdaforums.com/showthread.php?p=10231043#post10231043), there have been zero such reboot issues with that kernel.

Setcpu is not installed, nor is any other cpu related program. Only have the battery widget installed.

If there's more info you need, please let me know. I'd like to try some of the newer kernels, but I can't move forward if this issue is present.
[EVO 4G Android Development] netarchy:
What might help is if you could get a log of the failed boot when it happens. Here's a way you might be able to do such a thing.

The next time you encounter that problem, when you get the phone booted back up, connect to usb, and try using adb to pull the last kernel log like such:

"adb shell cat /proc/last_kmsg"

If the phone booted enough for the kernel to start going through inits when it locked up, that file should exist, and will have information on the last attempted bootup; if the kernel encountered an error that caused that boot attempt to lock up, the clue may be in the log.

I highly advise *not* posting the output of that command in a forum post here, as it is likely to be somewhat long ;D

Tossing me a txt file with the log is perfect ofc.
[EVO 4G Android Development] chingy51o:
dont know if i read the op wrong and just wanna double check but these kernels work on any rom?
[EVO 4G Android Development] netarchy:
They should work on any sense rom.

They might work on aosp, your mileage may vary.
[EVO 4G Android Development] gpz1100:
Yup... I know better than to do something like that... there was no last_kmsg, but there was a kmsg. Is last_kmsg the previous log while kmsg is current. If that's the case, then we're sol as far as logs go..?

My scroll buffer ran out, so some of the earlier lines are missing. This is after a battery pull following a lockup during reboot to recovery.

FWIW, all kernels so far have been more/less havs with SBC. I'm going to try your 4.2.1 without sbc (netarchy-toastmod-4.2.1-cfs-bfq-havs-more-smartass-universal-signed), see if that makes a difference. Also, this last lock up occurred with the phone NOT plugged into usb. But rather several hours after being AC charged and idling.
[EVO 4G Android Development] ronniewilb1:
EVO Half Rooted ?

I have tried Every way I Can to Install BusyBox, to no Avail at all Thus Leaving My EVO Not Fully rooted. Have Supperroot Icon and It Ask Permission for some /Most Programs But the Ones that Dont Open , give Message that BusyBox is Not Installed, I have Uinstalled Busybox and Reinstalled it and When I Open it It Just REBOOTS Deviceand it goes on its Merry Way as if NOTHING Happened. I Attempted Recovery/Installing it through ZIP and NOYHING HELP !!???
[EVO 4G Android Development] chingy51o:
Anyone confirm these working on DInc? getting stuck at splash screen..
[EVO 4G Android Development] mroneeyedboh:
yeah man report back. because so far on these SBC kernels ( I tired both more and less HAVS ) I get hung up when booting into recovery via powering off in the rom.
[EVO 4G Android Development] dkdude36:
my battery is messed up. it is dying (0%) at 3500 mV. how can i calibrate it to die at 0 mV?

the surprising thing is it takes a long time for it to go from 4200 to 3500 mV, so that means it is a good kernel. thanks a bunch net.
[EVO 4G Android Development] gpz1100:
dkdude36 , you can't. The device requires a certain amount of voltage to operate properly. When the power source can no longer supply the min voltage needed, it shuts down.
[EVO 4G Android Development] mroneeyedboh:
Is your battery bad then?
[EVO 4G Android Development] dkdude36:
3500 mV is very, very far from the minimum. i just want normal battery at the least. does anybody know of a calibration method? the battery should be dieing close to 0, not 3000 away from 0.
[EVO 4G Android Development] netarchy:
kmsg is the current kernel message log, not much use. What I would need (and this is assuming that the phone boots far enough to even generate any kmsg entries) is the last_kmsg, immediately after booting up from a lockup (there is a chance that the lockup might happen before it's far enough into init to make any entries and there could never be a last_kmsg).

I would be interested to know if it happens on a nohavs sbc build as well. It's possible that the havs builds are undervolting a bit too aggressively for your phone (some phones are REALLY picky about tolerating undervolting), and that's the culprit.

If that's the case, nohavs or nohavs with no undervolting would get around that.
[EVO 4G Android Development] netarchy:
The method I always used was to deliberately drain the battery till the phone shut off, pull the battery for a minute, replace, power the phone back up, resume deliberately draining (doing things like streaming data, turning on the flashlight, running a gps app, etc all speed this up) till shutoff again, repeating until the phone doesn't power back up after a battery pull, then charging to full with the phone completely off.
[EVO 4G Android Development] mroneeyedboh:
yeah thats whatI was thinking on mine too. But it ran smooth with more aggressive havs and still locked up in less aggressive havs.. So Its like mhm. deal with occasional lock up when rebooting into recovery or have glorious battery life?
[EVO 4G Android Development] gpz1100:
Thanks all for the replies...

@netarchy, testing continues.. We'll see how it is tomorrow.

If this is indeed an issue of too much voltage scaling (to levels too low) during reboot, perhaps that can be addressed? The device itself is fairly stable during use, with no FC's, reboots, or other crashes. If the problem is low cpu speed/voltage during reboot, perhaps there's something in the kernel that can be tweaked to ensure that during power down/reboot, cpu/voltage are at higher levels, which would alleviate this issue.
[EVO 4G Android Development] dkdude36:
ok, i think i figured it out. charge to full, wipe stats, let battery die. keep turning phone on until it cant any more. then recharge to full and prosper.

btw, could too aggressive havs be to blame for random reboots when playing games web browsing etc?
[EVO 4G Android Development] netarchy:
It could be, yes. You could try the less aggressive havs build, or the nohavs static undervolted build and see if either of those are more stable.

Worst case scenario, you grab the build with no undervolting.

Remember, undervolting is not the only thing that improves battery life in the kernels. How the kernels idle, how the cpu governor behaves, among other things all factor in.

Obviously undervolting will benefit battery life more than not, just remember that there are some phones that will inevitably not tolerate undervolting to a significant degree.
[EVO 4G Android Development] dkdude36:
ok, now this is reeeealy wired. i got to 1%, and have flashlight, screen, and 4g on. i am using battery monitor. so my mVis 3470, and it wont go down. i am getting -400 consistantly, but battery stays at 3470 mV. that is just wired. i wonder how long it will take until it registers any change. and why
[EVO 4G Android Development] dkdude36:
ok, finally shut down.
[EVO 4G Android Development] MCLFLN:
netarchy,

Since switching to: netarchytoastmod-4.3-cfs-nohavs-noUV-nosbc-universal (No Undervolting) last night....

I have attempted to reboot 5 times with no hang on reboot. I will continue to occasionally try this.

Thanks,

Matt
[EVO 4G Android Development] ZEDEK:
Peace All,

(posted this also in ms's thread as well)

I am currently using 4.3 CFS- no havs-SV-SBC

Hardware version 0002

Is it me--or maybe my configuration on my device with SetCpu--but has anyone noticed that while the SBC hack works wonders on the trickle charge [defect] of HTC, and it takes awhile for it to actually leave 100%--but it appears to continue to drain (at least on mine) during periods of inactivity even with the profile set to SMARTASS 384/128. Other kernels i've used when the phone's screen is off there is very little or no drainage. Currently my configuration on SetCpu is

1152/ 384 CONSERVATIVE

384/128 SMARTASS

(in advance settings):

Sampling Rate: 50000

Up Threshold: 95

Down Threshold: 45

Ignore Nice Load: 0

Frequency Step: 15

Any help on this would be greatly appreciated

-ZDK-
[EVO 4G Android Development] gpz1100:
Have you tried the 4.3 with havs (aggressive or less aggr) WITHOUT SBC? Since switching to 4.2.1 more agg without sbc, my lockups have gone away. Earlier this morning, switched to 4.3 more aggr also w/out SBC, and so far so good with no lockup on the reboots.
[EVO 4G Android Development] Brandito:
couple questions, probably answered before, havs i am assuming is the undervolting? what is sbc?
[EVO 4G Android Development] squick:
Hey Net, little birdie told me that your 4.3 was only for people with the new camera. Is this true or can it be used for 0003 and 0002 hardware such as mine and my wifes? I was using the SBC kernels from the other thread, 4.1.9.1, to be exact, and would like to upgrade to at least 4.2 but you dont have it in your 2.2. So can I use 4.3 or will it mess things up?
[EVO 4G Android Development] netarchy:
That little birdie is mistaken.

4.3 includes support for the newer camera, but works for all evo models.
[EVO 4G Android Development] Jbcarrera:
I'm pretty sure its based on kernel 15 so that would mean all phones

Sent from my EVO at the edge of hell
[EVO 4G Android Development] Jbcarrera:
Super battery charging

Sent from my EVO at the edge of hell
[EVO 4G Android Development] squick:
Thank you very much. This has made me very excited cause that other kernel I was using was incredible and I want the newest and best. Thats why I've come to you, lol.
[EVO 4G Android Development] netarchy:
SBC is a mod aimed at Superior Battery Charging. It is developed by ms79723.

The official thread about SBC is here.

It started as a battery mod based on the kernel sources at my github page ;D

HAVS, to be more precise, is dynamic voltage scaling (typically used around here for dynamic undervolting).

With static undervolting, the cpu receives one specific amount of power depending on its speed. With HAVS, there are a range of voltage values that can be fed to the cpu at any given speed, depending on a number of factors, such as cpu load, battery temperature, etc.

This means that it's possible for HAVS to scale the voltage higher or lower than the static voltage setting for the same cpu speed as needed/possible.
[EVO 4G Android Development] mr.BeBoT:
for those having trouble with the reboot lockup, I'm 99% sure I've isolated it to the SBC mod. I posted about it in the ms SBC thread but it's probably since been buried.
[EVO 4G Android Development] brol1k:
Hey net why dont you make it in big bold plain letters in the first post that 4.3 only works with any and every evo including 004 and the other older kernels are only for 002 and 003 evos? seems like to many asking the same question
[EVO 4G Android Development] mr.BeBoT:
I thought it might be helpful to include more information and repost in the ms SBC thread, hopefully will help others:

"Just wanted to post this again as it seems like more people are reporting the issue.

I believe there's something in the SBC mod that is causing reboots to hangup (whether you do it from quickboot or shutdown and power in to recovery) After a battery pull it does clear up. I've been on Calk's evio roms and changed nothing but kernels this last 2 weeks and I have been able to replicate it with V7, 131,#15 and netarchys 4.3. I didn't have the issue with V4 (but also didn't get as good a result)

I'm currently trying #15 and it's the FIRST time i've seen -mAs in any SBC kernel. I've rebooted and will give it another charge cycle to see if it was a one time deal or not.

Overall the battery pull isn't too big a deal considering the advantages of SBC. But for us flashaholics it does get bothersome!"
[EVO 4G Android Development] ZEDEK:
Net or anyone...can u address this ^^? Is drainage with inactivity normal for SBC?

-ZDK-
[EVO 4G Android Development] gpz1100:
Ditto! My testing has shown similar results. So long as any of the kernels (4.x.x) don't have the SBC variant, I get no reboot lockups. Once a kernel with SBC is introduced, lockups start occurring inconsistently (though more often than not) on reboots.

Something in SBC is creating issues during reboots... Or perhaps some flag(s) is/are set on power down just before rebooting that generates this issue....
[EVO 4G Android Development] netarchy:
Done.

Though to be fair, it would be a bit silly to release a kernel build that only supported one hardware revision. ;D
[EVO 4G Android Development] sgt. slaughter:
and common sense if you know how changelogs work, the version includes everything form previous versions plus anything noted in the changelog for the current release. So by default it would include old and new camera drivers.
[EVO 4G Android Development] sgt. slaughter:
You see any reason that they would have taken a step back using the .17 base?

What differences between the bases are there? jw
[EVO 4G Android Development] matthewjulian:
I was referred to netarchy kernels as I am seeking a kernel with loop devices enabled, I am on the newest OTA with the newest radios and newest stock kernel, I was already considering OCing my Evo (but really I just want the option to when I want to), the main thing is that these have loop enabled. So...being on everything stock rooted which of the kernels here is recommended(or which will just work)?:D
[EVO 4G Android Development] squick:
Hey Net, me and the wife are having some problems and they've only started since using the new SBC kernels. I don't know if it's the kernel or not. When my wife started taking some pics for her ebay store and then checked them on the computer they were there. Then she took some more and went to check them and we can see them on the phone but they're not there when you open DCIM on the computer. Then the phone starts giving a mounted read only error. This happened a couple days ago when I had 4.1.9 from the SBC thread installed. The only way I could fix the read only problem was to format the card through the computer cause the phone wouldn't mount as a disk drive. After it just did it again with 4.3 from your page she tried my phone and the same thing happened. Now I have to reformat both cards.

I'm just wondering if you have any idea about this or know if it is related to the kernel.
[EVO 4G Android Development] jelive:
Doubt it's the kernel. Going to make suggestion based on same happening to me multiple times until I figured it out. You don't have to format card. If you have a card reader pull your SD card and put in card reader, then select drive properties, then tools, then scan-correct errors. I finally pinned down why I was getting the problem...having phone hooked up by USB in drive mode and unplugging it too quickly after I'd transferred a file, etc. or w/o changing back to charge only before pulling cable.

Jim
[EVO 4G Android Development] acrh2:
What exactly is the difference between the two builds, please?
[EVO 4G Android Development] netarchy:
The only difference between the two are the init sequences for the epson, the values in the second build are from the htc released source while the first comes from the makeshift kernel.

Sent from my Evo4g with tapatalk
[EVO 4G Android Development] netarchy:
Actually at the moment the epson gets higher fps, though when proper fixes are found for both there really should not be a difference in performance.

Sent from my Evo4g with tapatalk
[EVO 4G Android Development] netarchy:
Which is "better" is largely subjective, both will eventually be properly uncapped and fps isn't likely to be better on one vs the other

Sent from my Evo4g with tapatalk
[EVO 4G Android Development] Android Believer:
My biggest concern from the get go is the screen tearing. It's extremely annoying lol. Do you have any idea of a difinitive fix for this or anything of the sort?