yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] scottspa74:
I've been playing with netarchy kernels since august. Lately since the 3.29 update (htc) I've been using the stock kernel cuz it gets amazing battery life. I would like to check out the new aggressive uv kernels. I know some phones don't handle undervolting as well as others. My question is

; if my phone won't really function due to aggressive undervolting, will I still be able to get into recovery to flash a different kernel back on it. ?

I have no idea how to access recovery thru a computer as I've seen some talk about, so I would have to be able to access it thru my Evo (amonRA).

If anyone can speak to this, thank you.
[EVO 4G Android Development] xhazyx:
^^^^^^

You Will be able to boot into recovery from the Evo.... just download the stock and netarchys kernel to flash back in case it doesn't work...

Or make a nandroid backup

you should be fine. ;)
[EVO 4G Android Development] ms79723:
You'll still be able to access recovery mode, the worst this kernel can do if it doesnt work is just keep you on the white EVO screen. But you'll still be able to access recovery, just gotta pull the battery.

And you can get into recovery on your computer by using adb. just go to androidsdk/tools in command prompt and type in "adb shell" *press enter* "reboot recovery" *press enter again*
[EVO 4G Android Development] scottspa74:
Wow that was fast! Thank you both. Yeah, I already have at least like 12 other kernels on my card I can use as ling as I can get into recovery. They're there cuz I've tried most kernels , just not the new agg uv kernels.

I still have never setup, or looked into how to use adb or android sdk, but thank you. You guys rock, thanks.
[EVO 4G Android Development] sag7392:
I'm still testing SA and all I can say is DAMN! Even with use, my battery is barely moving.
[EVO 4G Android Development] THunDA:
I hear ya..

What a combo, I just got a 3500 mah battery and paired with 421 SA MORE kernel im at 75% at 8:30pm and I took it off charge @ 9am... somewhat light usage but still much better then I was getting.

Thanks Net!
[EVO 4G Android Development] ms79723:
Yeah, smart ass is most definitely up there with the conservative settings, I love it. But right now I'm using different conservative settings, more aggressive settings, so I'm just testing it out.

Tomorrow I'm thinking about testing out the battery guzzling Desire HD rom with both smart ass and conservative. Haha these are the things I do when I don't have to work weekends.
[EVO 4G Android Development] elas123:
how do you guys get this great battery. i mean damn. i mean i can watch my battery drain just looking at it . tried them all and they drop 1 or 2 percent every couple minutes.

edit. in system panel my cpu never sits still its always jumping around
[EVO 4G Android Development] Biofall:
Just flashed the newest cfs more aggressive
[EVO 4G Android Development] ms79723:
Well Im not charging to 100% if you charge to 100% you'll notice the battery drop like crazy..

Here's how I do it. At first I do charge it up to 100% over night.

1. As soon as I wake up, i reboot straight into recovery while the phone is still on the charger then I wipe the stats and reboot.

2. Then I let my phone sit on the homescreen with the screen on for 5 mins and let the battery drain like crazy, then I reboot into recovery and wipe stats again after 5 mins.

3. When I reboot again, if the battery percentage is higher than it was before the second wipe, then I repeat #2.

After that I just let the phone do its thing.
[EVO 4G Android Development] xHausx:
try using OS monitor, it should show you what keeps using your CPU
[EVO 4G Android Development] elas123:
should my cpu activity in system panel be contantly jumping. not maxing out but im not even doing anythign and it jumping in the 500 back to 300's then to 400's
[EVO 4G Android Development] ms79723:
Well Netarchy said that that happens because your cpu is at work trying to update those stats in real time. So it makes sense that it would be jumping around. I notice the same thing with setCPU.
[EVO 4G Android Development] elas123:
ok i understand that but in cm6 or muiu this doesnt happen. i can sit there in system panel and the cpu activity hardly moves and stays very low 99% of the time. soon as i flash to a sense rom this is what happens and my battery is ****. not that it is any better in cm6 though
[EVO 4G Android Development] flooberz:
same here...

while the phone is sleeping though... it's freakin awesome.
[EVO 4G Android Development] ms79723:
Well they use different kernels...and on top of that, Sense has more crap on it, well, it depends on which Sense rom you're using.

But for the most part, Sense roms will use more resources I guess and are more likely to cause the CPU to ramp up for no reason...but im getting better battery life on this rom than on both MIUI and CM6.
[EVO 4G Android Development] elas123:
which rom?
[EVO 4G Android Development] xHausx:
Trying out the 4.2.1 CFS less HAVS and this thing is quick. I dont know about battery life yet but linpack has been around 38-40 MFlop, Nena ~23fps and quadrant is around 1450

I can still see the tearing ever so slight if I try to make it do it but it doesnt seem as bad as it was before.
[EVO 4G Android Development] ms79723:
Hm? I was saying that it depends on which sense rom you're using...like Myn or Ava, they all tweak the system differently. Im currently using the OTA rooted and its bleh-meh. On to DesireHD next.
[EVO 4G Android Development] Biofall:
Just wondering if any of yall are getting the "device" usage in system panel going all the way up to 100% lately like I have. I'll post some screenies later, but during usage lately this has gone up all the way and I start to experience a drain. It's lame.

Also, my "system" process is using around 10%.. about 4 minutes and my phone has only been awake between 10 and 20
[EVO 4G Android Development] elas123:
thats what i ment which rom u using now
[EVO 4G Android Development] achllles:
I don't think this tweak works with 4.2's.

CPU usage were way too high.

Just go with what OP suggests, or just go with no tweak with 4.2's. Make sure you uninstall the tweak before you flash new kerels.
[EVO 4G Android Development] ms79723:
what tweak? talking about the batter tweak with the non-havs version of 4.2?
[EVO 4G Android Development] achllles:
Yeah collin battery tweak. I've tried 4.2's and cpu usage were too high. Nohavs 4.19 was ok though.
[EVO 4G Android Development] ms79723:
Ah, well I dont see the point of that tweak if all it does is scale down the CPU and not the voltage. You can probably have a more aggressive down scaling of voltage with setCPU by using conservative and playing with the advanced settings.

A combination of conservative/smart ass governor and aggressive undervolting is insane, you should try it out.
[EVO 4G Android Development] achllles:
Thanks, but never used setcpu (do have apk, just never installed it), and will try it some time.

It looks like the kernel I'm trying now - ziggy's undervolt, according to the kernel description in settings atleast. If this thing doesn't work out for me, i'm just gonna go back to my first kernel on my sig, or bfs version of it.
[EVO 4G Android Development] Atticustrd:
4.2.1 has been great. Used my phone off wifi today made more calls then I usually do checked xda through out the day as well I'm currently at 30% left with 15hrs un plugged. Great kernel thanks. AvaV9 rom.
[EVO 4G Android Development] xlGmanlx:
try wiping cache and doing a reboot. if its pegged at 100% try looking at spare parts to see if an app is causing wake
[EVO 4G Android Development] tomh1979:
OK, my observations:

Runing Fresh 3.4.1 with setCpu at just 614 on and 245 off on conservative, no profiles.

with 4.2 screen off was ok, when using phone though battery drained really fast, however the cpu temp was what i was watching, and i'm shocked no one else has mentioned this that i noticed, with screen off or on and not being used the cpu temp was anywhere from 67 degree's to 77 degree's ( depending wether i'm inside or outside), which is why i partially think the battery lasted decent with 4.2, but when in use it seems the battery would get to anywhere above 78 degree's and just drain fast.

Now with netarchy-toastmod-4.2.1-bfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting) i've noticed that with the same setcpu setting of 614 on and 245 off, that the battery temp does not drop below 90.3 degree's period, but the battery is not draining at that temp while off, but i have not used it that much to notice how fast it drain if at all while in use.

Edit: ok using the phone doesn't seem to drain as quick, but what i have noticed is that using OS Monitor that the actual battery temp say's 83.3, while setcpu seems to be stuck at 90.3 degree's, wtf.

Edit #2: rebooted phone, temp now at 87.3 from 90.3 on setcpu, it appears at though it's locking in whatever temp it starts from on setcpu, why?

Edit #3: removed setcpu, but between battery widget and OSmonitor the temp stays at 87.6 degree's, just seems like this kernel just doesn't go low on a temp scale, sorta like something is running and keeping the temp up, not running any process then OSmonito, which varies between 7% and 14% cpu usage.
[EVO 4G Android Development] thenewguy821:
There are a couple things that aren't right here....

If you take the phone off the charger when it reaches 100%, you don't get rapid battery drain. If you leave the phone on the charger overnight, or any extended period of time, the phone stops charging at 100% and works off the battery till it drops back to 90%, at which time, the charging cycle kicks back in. The phone recognizes the actual battery voltage and works it's way down to displaying that voltage. This is often mistaken for rapid battery drain.

IF you charge overnight, when you unplug the phone, wait a minute or so, then reconnect the charger. This will kick the phone back into charging mode to top off the battery. When the light turns green at 100%, unplug the phone. This will ensure you actually have a full charge.

When you do a battery wipe, the phone needs to be at 100%. If you charge overnight, and the phone has started working off the battery, the wipe will give a false 100%. (If the battery was actually at 92% when you wipe, the phone will now see that as fully charged). If you are going to wipe your battery stats, Charge the phone to 100% as explained above. When the battery reaches 100%, while still plugged in, reboot to recovery and wipe battery stats. Reboot the phone, then disconnect the charger. Use the phone normally, letting it discharge completely till it powers itself off when fully drained. Now the battery is calibrated.

Because of the way Lithium Poly batteries work, the phone as a safety feature does not "trickle charge". This has confused a lot of people into thinking the phone wasn't charging right, or they had a bad battery. LiPo's need to be charged CV/CA (Constant voltage/Constant Amperage). If the phone didn't cut off the charge at 100%, the life of the battery could be shortened or worse, the battery could completely fail. If lucky, when the battery fails, it could just lose voltage and the ability to take a charge. I have seen LiPo batteries ignite if not charged properly.
[EVO 4G Android Development] MJStephens:
Flashed cfs-more-smartass last night and my battery drained over night. Up time and awake time are almost the same. CPU is not stuck at 100% usage either. What's really weird is that it charges on a usb charger but did not charge on my ac charger over night. Hmmm. I'll flash a few more of the new net kernels but I may go back to 4.9.1 for a while.
[EVO 4G Android Development] thenewguy821:
What Rom are you using, and are you using the Colins battery tweak?

Sounds like you have a renegade app, or something isn't agreeing with your phone. I have been running the 4.2.1 CFS More aggressive SA w/HAVS since 1pm yesterday, and other than being hooked up to the computer for 5 minutes yesterday to load Myn's Rls3 to the SD card, I have not hooked to a charger. Battery is currently at 56% (With Moderate usage, not a lot, but not a paperweight).

There is also a possibility, that your phone isn't handling the more aggressive scaling. Try the Less aggressive kernel and see if that makes a difference.
[EVO 4G Android Development] ms79723:
I've done that so many times, and its a hassle..Also by doing that, i found that every time i install a new rom or go into recovery to flash anything I would have to wipe the stats again because my battery wouldnt be reading the right percentage when i reboot again.

To me, it does not make sense to charge to 100% and wipe, mainly when 100% is more likely not to be 100% Bump charging while the phone is off is tedious, much easier for me to wipe stats at 95%, because 100% of the time I know that when my phone is at 95% it is actually at 95%. If you wipe at 100% your phone could actually be at 92% and sometimes I just dont have the time to be spending my mornings trying to bump charge.

So far what I've said works for me, plus not charging to 100% and just doing small charges up to 90&-95% helps me with my battery. I know it may not be the correct way for doing things, but it makes me feel better.
[EVO 4G Android Development] ms79723:
Make sure your actually on the smartass governor...if you've never used setCPU before, then you are on the governor, but if you've played around with setCPU's settings before flashing, then it might've just went with your old governor and not the new one.

That might explain the battery drain, not the up time and awake time. Wipe cache and dalvik cache and see if that fixes the problem.
[EVO 4G Android Development] randymac88:
Question sir. What is the logic behind making the charging cycle kick back in at 90%? 10% of your battery in flux like that seems awfully high. Why not 95%? 98%?
[EVO 4G Android Development] tomh1979:
why not just buy a external battery charger, they work better then anything out there, or any method out there, best if you have a spare battery, it'll charge to 100%, and actually hold the charge, i've gone anywhere from 2-5 hours with no drain from 100%, sure very little usage, but still being used, if i loose anything in that time period it may be about 1-2%.
[EVO 4G Android Development] Biofall:
Yeah see that's the thing. System panel/spare parts don't show anything. Lol that's the whole problem. I can easily see nothing obvious is the culprit.
[EVO 4G Android Development] thenewguy821:
The 10% drop is basically a "safe" area. It gives the LiPo battery time to stabilize and cool down. 10% may be too big of a cushion, but I have seen LiPo batteries combust. I would much rather have a larger safety cushion, than a combusting battery. True, LiPo combustion doesn't always happen, but when it does, it gets ugly fast.
[EVO 4G Android Development] elas123:
I feel your pain.I had rhw same problem with any rom or kernel.I tried everything and nothing works and I do have external cjargerand spare batteries
[EVO 4G Android Development] hackulous:
Can't find the download link help would be appreciated would like to get my hands on this
[EVO 4G Android Development] ms79723:
It's on the main page. And I like your username btw...ah, the memories :)
[EVO 4G Android Development] fixxxer2008:
any way i can get my camera to work? ive tried to clear defaults but it won't let me. im running the steelh rom.
[EVO 4G Android Development] achllles:
I've read something about new cameras (new hardware version 0004 I think, but not 100% sure) not working properly after flashing some where. It's not the kernel or the rom. Try to post this in general and see what people says.
[EVO 4G Android Development] flooberz:
I find that anytime i try to wipe my battery stats, i end up getting this 100% awake time....causing MAjor battery drain

To get rid of it... do a factory rest, and restore a nand backup... i'm thinking a cache&dalvik wipe should get rid of it too...
[EVO 4G Android Development] xlGmanlx:
If your only on your phone tapa won't show the links as clickable because they are quoted. Try navigating using the browser.

Try settings - applications - Camera - clear defaults or another rom

Make sure your either fully charged or let it charge after you wipe. It takes some time for the stats to settle in, are you getting severe battery drain?
[EVO 4G Android Development] flooberz:
Is it supposed to do a 100% awake thing after you wipe battery? because i've done it many times where i charged all the way to 100%... bumped charged it... stuff like that.. and it just doesn't sleep..

how long is it supposed to last? I try to make it sleep and it stays awake 100% for maybe 10-15 mins.. and i get ansty and just do a factory rest.
[EVO 4G Android Development] xlGmanlx:
The times are slightly skewed since you just reset to zero. If it doesn't go down, either try a reboot or wipe your caches
[EVO 4G Android Development] flooberz:
So it is supposed to do the 100% awake thing?
[EVO 4G Android Development] xlGmanlx:
If your using it yes haha
[EVO 4G Android Development] rjmjr69:
You tell him

Wow what a dink this is a work in progress and some stuff will just inevitably need to be tweaked or worked on if you dont like it dont use it

Anyhow I'm just waiting on boot to check the newest version and wifi

Wifi still does not work but 4g does. Even with the suggested quick fix I can't get it to work. 4g seems to kick off after a few seconds though. Back to 3.6 lol

Appreciate the hard work I'll keep testing if you keep posting lol
[EVO 4G Android Development] nuetron:
Wifi still unable to start on 3.6.2a. Wiped Dalvik cache and cache then flashed. 4g connected fine.
[EVO 4G Android Development] toneman1984:
Thankyou! If you could include browsing the interwebs and homescreen navigation that would be excellent.
[EVO 4G Android Development] mrkmrk:
Hmm. I seem to be getting intermittent locked back at 30. And while trying to type that, another problem: the keyboard doesn't recognize long presses.

Baked Snack 9.6 on an 002 Novatek, for what it's worth.
[EVO 4G Android Development] nuetron:
Pushing bcm4329.ko then insmod in adb shell.

Turning on/off Wireless Tether 2.0.5.

This process will let wifi start and connect.
[EVO 4G Android Development] netarchy:
here's an idea, remount the system read/write, adb shell, cd /system/lib/modules , rm *

then reflash the kernel.

I'm curious at the statement earlier regarding wifi-tether making the wifi work after that insmod trick... Makes me wonder if wifi-tether could be the culprit making the wifi not work and not an issue with the update itself (by all rights there's nothing I can discern that should make it *not* work, the module obviously works since we can manually load it with insmod).

If my previous idea doesn't work, try uninstalling wifi-tether and reflashing the update.
[EVO 4G Android Development] netarchy:
Could you do an "adb shell cat /sys/android_touch/vendor" and tell me what you get?
[EVO 4G Android Development] rjmjr69:
I have it installed as part of the rom but do not use it. But why would it work in one version of your kernal and not the other? just curious
[EVO 4G Android Development] netarchy:
That's a very good question, there's no reason the update itself shouldn't be installing the newer driver (and in fact it is since we can insmod manually), so it seems like *something* in the system is blocking actually turning the thing on afterwards.
[EVO 4G Android Development] nuetron:
Tried both methods, still would not start for me.
[EVO 4G Android Development] rjmjr69:
ok uninstalled wifi lets see what happens now

nope same thing

hhmmm what huge thing did you change lol 3.6 works just fine
[EVO 4G Android Development] persibro:
Not working for me either :confused:

I tried:

- erasing everything in the modules folder then reflashing

- uninstalling wifi tether then reflashing

- uninstalling wifi tether then erasing everything in modules then reflashing

- even tried flashing the wifi/4g fix from ffolkes' thread for kernels based on toast's godmode :p

Alas, nothing worked. This is going to be my last input of the night, but I'm sure you'll figure it out! Thanks for the hard work!
[EVO 4G Android Development] netarchy:
That's just it, there was no huge change, it makes absolutely -no- sense.

And even more peculiar, all the problems seem to be specific to damage control.
[EVO 4G Android Development] dwntwnall4u:
Seems to be all working for me. Fresh 0.3, nova 0003
[EVO 4G Android Development] netarchy:
I'm gonna pull the damage control build from the first page for now until I can talk with the DC devs and see if the cause of these issues can be tracked down.

You can try your luck with the normal build, though your mileage may vary.

There is an official DC kernel for reverting from a custom kernel build in the DC thread for the time being.

One way or another this will be solved.
[EVO 4G Android Development] shymog:
I flashed this on the latest Baked Snack over ffolkes kernel. Is there anything special I should be doing? SetCPU can change the speed (via min speed) but I'm getting no scaling, even though I have it set the same as before... Any ideas?
[EVO 4G Android Development] netarchy:
Fire up setcpu, hit menu, device selection, and have it detect frequencies.

It may just a rescan since it's a new kernel. There are some changes to the frequency table in my kernel vs what is likely in ffolkes, as some bugs were corrected.
[EVO 4G Android Development] walkingcorpse:
I've flashed both kernels from tonight including the dc one with no problems. Im running dc 3.2.3. I just installed the zip via rom manager on clockwork recovery. Doubt it helps but figred id report back. Thanks for the hard work.
[EVO 4G Android Development] netarchy:
And the wifi works and everything?
[EVO 4G Android Development] shymog:
I did that and if I put min to 128, max 1,092, it just sits at the minimum... I've tried restarting without any luck :(
[EVO 4G Android Development] flooberz:
Well obviously...

But i'm not... i'm trying to get it to sleep...so i'm not using it.
[EVO 4G Android Development] fixxxer2008:
tried, no dice. ive already flashed 3 roms, no camera after using any custom kernel. must be a bug or something in the new OTA. looks like i have to use the stock kernel for now, i just wanted the audio tweaks anyways.
[EVO 4G Android Development] xlGmanlx:
Try a reboot otherwise I got nada.

Try loading a stock rooted rom and see if that helps. I just heard that 3.30. is due to new hardware in the evo, maybe yours isn't playing nice. Maybe try a 3.29 based rom

One is BFS and the other is CFS. There should be info online as to both but they are pretty technical
[EVO 4G Android Development] mstgkillr:
What is the difference between 4.2-cfs-bfq-havs-more-smartass-universal and4.2.1-cfs-bfq-havs-more-smartass-universal?
[EVO 4G Android Development] wmdunn:
Been asked and answered a couple of times in the last few pages. Netarchy tweaked the kernel just a bit, in order to allow for better battery during "active" usage.
[EVO 4G Android Development] Biofall:
Rebooting in general gives me 100% wake time unless I do these steps now.

1. Reboot phone.

2. Instantly upon reboot, as soon as you gain control, open up some type of monitor/taskkiller

3. "kill all" tasks on startup; about 5 times in quick succession should do the trick.

4. Turn off the screen and leave it for about five minutes.

5. Check the up time v. awake time and see if they are the same.

6. If they are, repeat steps 1-5. If they are different, you are good.

*Some apps or processes begin to run at startup and keep the phone awake. These apps are not detected by things like spare parts or system panel, unless sometimes represented in the "system" process, in which case its usage will be unusually high.

This shouldn't take more than three repeats, and if it does, you need to factory reset, and slowly add apps back to see what's causing the problem.
[EVO 4G Android Development] xlGmanlx:
man, that is extreme!! i have loaded warm 2.2 v3 and i have no such issues like that with stock ROM. i am sure you have looked for rogue apps so that is probably something specific to your ROM, on warm i had about 9 hours of up time with 2 hours of awake time