yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] R32_Rocky:
So do we still use SetCPU to OC? Just don't make any profiles? Cause it is starting to get a bit confusing for me. How else can you OC the kernel if not using SetCPU or the other OC widget? And then how would it ramp down when idle, or the screen is off? Ziggy's kernel in the early stages had a script that would allow his kernel to OC, then ramp down per usage, but it never seemed to work for me, and he stopped including them anyway now. So how else can the kernel be controlled?
[EVO 4G Android Development] netarchy:
The preview is very much alpha state (read: buggy/not ready for prime time)

Everything from HTC has to be ported/adapted over to work with the newer base, it's an imperfect process. It's more a teaser than anything else ;D

4.x is supported better on the evo for now.
[EVO 4G Android Development] barnacles10:
I'm not sure if .34 is entirely stable with the preview. .32 kernels showed very similiar benchmarks, so if you're flashing a custom kernel, I'd stick with a .32 base for now. You can certain see how .34 goes for you tho. Everyones different, and some things don't bother others.
[EVO 4G Android Development] netarchy:
No, there was a typo in the source when I compiled the interactive-default builds that made them min at 384 instead of 245.

It is fixed in the smartass-default builds (and you can still change to interactive via setcpu if you want to test it out, though smartass is looking really promising).
[EVO 4G Android Development] d0cx:
I see... so, having v4.1.9.1 installed, flashing v4.2 will keep the current tweaks from v4.1.9.1, correct?
[EVO 4G Android Development] netarchy:
You can still use setcpu, you just may find you don't need to use profiles (for instance, smartass already limits the speed when the screen is off and the phone is idle/sleeping).

If you want to overclock, you still need to use something like setcpu to raise the max, just like always.
[EVO 4G Android Development] netarchy:
Link is in the first post O.o
[EVO 4G Android Development] ms79723:
Idk how to check which panel i have, im looking into how to do that right now.

But i've tried all universal kernels on the MIUI build and the CM6.1 nightlies, on Sense roms they work great

And it's screen tearing, doesn't tear while playing a game, just tears on loading icons, icons in the status, keyboard suggestion bars etc...
[EVO 4G Android Development] netarchy:
Yes, universal builds keep whatever ramdisk you were already using, any tweaks based out of them should stay intact.
[EVO 4G Android Development] barnacles10:
:cool: I know.. that links not working.

I get stuck at 66% until it tells me dl failed.
[EVO 4G Android Development] netarchy:
adb shell "dmesg | grep -i mddi"

or add the power widget to one of your screens and toggle brightness a few times, if the brightness change is instant, you have an epson, if it has a fading effect in transition to the new brightness level, it's a nova.
[EVO 4G Android Development] netarchy:
Oh dear, I'll have to see if the host is having any issues, meanwhile... here you go.
[EVO 4G Android Development] barnacles10:
Thanks, appreciate it!
[EVO 4G Android Development] ms79723:
I have a nova
[EVO 4G Android Development] PlankLongBeard:
Thanks Net.. Appreciate the answer!

Sent From The Moon... :-)
[EVO 4G Android Development] ms79723:
Oh, forgot to mention that the preview 5.0 didn't cause screen tearing on any AOSP rom that i've used. But for one of the nightlies it did take away usb connect.
[EVO 4G Android Development] mjohnson4580:
thank you everybody for the responses and links
[EVO 4G Android Development] d0cx:
Very well. I already installed SmartAss More Aggressive and it seems to work just fine.
[EVO 4G Android Development] netarchy:
For those interested, there are now BFS versions of the smartass 4.2 beta builds available
[EVO 4G Android Development] achllles:
netarchy-toastmod-4.2-cfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)

Seems like It's working well with Myn's 2. 2

Thanks again.

If anyone have time to kill, what's difference between havs, nohavs, cfs, and bfs?
[EVO 4G Android Development] pastert33:
I'm running the RC CM and downloaded both bfs smarts** kernels. Both of them are showing I would call graphical tearing. It's hard to explain but as the battery is charging, the screen will tear over the battery symbal. Really wanna try this kernel out more!
[EVO 4G Android Development] beerad29:
Burnt Droid 1.3 with 4.2 CFS more aggressive smartass status

Net - great work. I am using your ROM with the 4.2 CFS more agressive smartass. When I changed over to this kernal, my initial battery drain was insane - 10% in about 15 minutes. I rebooted and things seemed to settle down and the phone is stable. It is very smooth and fast without overclocking. SetCPU is on with no profiles set. I am going to give this some more time to see what happens to the battery.

What change would you expect using a BFS kernel? My EVO seemed to like your 4.2 smartass no havs but I wanted a little more oomph from the kernel. Again well done!
[EVO 4G Android Development] meth84:
Hey I'm running myns warm 2.2 and was wondering what kernel would be good for this Rom nova display... 1258 oc stable

myns warm 2. 2
[EVO 4G Android Development] netarchy:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.

No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation

CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler

BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
[EVO 4G Android Development] juancaperez2000:
feeling like in the college lol, thanks for the explanation, also i just feeling like smartass governor is providing a really good battery life probably even better than conservative, im running CFS MORE AGRESIVE HAVS WITH OMJ 3.8

thanks, for your hard work
[EVO 4G Android Development] achllles:
Thank you buddy.
[EVO 4G Android Development] gotshores:
new 4.2 beta-screen tearing

My phone has done fine with the new 4.2 cfs and bfs. My wifes phone doesn't, she gets screen tearing on both betas, so i'm having to run 4.1.9.1 on hers for now. She also just got her digitizer replaced. Maybe the new one is different from mine. Not sure if this would have anything to do with it or not.
[EVO 4G Android Development] xHausx:
4.2 CFS low-voltage is working great for me so far. I have it running with a modified stock 3.30 ROM and SetCPU on interactive and browsing the web feels much much smoother. fps2d had a much larger stdev and linpack, nenamark got slightly lower scores but it's nothing noticeable.

Thanks for the update.
[EVO 4G Android Development] elas123:
Can't use this kernel on cm
[EVO 4G Android Development] -viperboy-:
I didn't see anything in the OP, so could we get a little more info on what smartass is all about? Thanks!
[EVO 4G Android Development] Darian89:
Which 1 has best battery life, cfs or bfs...Im running fresh 3.4.0.1 btw
[EVO 4G Android Development] halorin:
Pity. They are listed as universal. I use the 5.0 preview 3 without any screen tearing on 6.1RC1.
[EVO 4G Android Development] Rene2.5RS:
Net,

First off let me say that I absolutely love your CFS NON-HVAS kernels. I am getting the best battery life to date using them (go figure) in conjunction with setcpu. I am currently on 4.2 non hvas and have been testing the smartass governor and just watching the setcpu home screen it would appear that conservative still keeps the cpu at a lower frequency more often than smartass. I have screen video showing the differences between the 2
[EVO 4G Android Development] meatgel:
I have a daughter who is a PITA to get information from, always peace-meal. I did with Net's posts what I do with her ... string them together for all of the information.

Here's what Net says about smartass and more:

"Smartass is based on the ideas of the interactive governor, but is implemented differently.

The end result *should* be a pretty snappy phone while (theoretically) not breaking the bank in terms of power drain.

It also should spare you from needing to use setcpu profiles ;D

You can still use setcpu, you just may find you don't need to use profiles (for instance, smartass already limits the speed when the screen is off and the phone is idle/sleeping).

If you want to overclock, you still need to use something like setcpu to raise the max, just like always.

Yes, universal builds keep whatever ramdisk you were already using, any tweaks based out of them should stay intact.

Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.

No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation

CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler

BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler "
[EVO 4G Android Development] Rene2.5RS:
CFS should have better battery life and BFS should have better performance. But to really find out you should just test both. My phone hates BFS, always seems to very laggy with transitions and general phone use. While using a CFS kernel things are smoother more often than not
[EVO 4G Android Development] st0921:
This is my "hunch" on observing my phone after running 4.2-cfs-aggressive for 1 day. It seems like when the phone is idle the battery drain is extremely low, almost none. However, when the phone is active (using apps), the battery drain is noticeable. Although overall it's very snappy and quadrant score of 4.2-cfs at smartass governor is comparable to 4.1.9-cfs or ziggy's kernel at performance governor, both around 1600s. FYI, I use setcpu for overclocking purpose only at 1.19Ghz max and 384MHz min.
[EVO 4G Android Development] Clay333:
The 4.2 (cfs, smartass) beta plays REAL nice with my phone. Battery life is amazing. There is almost no lose in battery percentage when the phone is sleeping, it is incredibly smooth, and scores higher in benchmarks than 4.1.9.1. I have seen no bugs with this kernel either. Keep up the good work netarchy, I can't wait for a more stable release of v5 to see what it can do.
[EVO 4G Android Development] d0cx:
Hmm... I had to revert back to v4.1.9.1 from my last night's nandroid backup. It started to crash acore process nonstop. Rebooted and still the same thing so I reverted.
[EVO 4G Android Development] gotshores:
good stuff

Using the new 4.2 CFS and I'm getting some good battery life so far. Used it the whole way home from work (talking) and only went down 1 percent.
[EVO 4G Android Development] gotshores:
Sorry, whole way home equals around an hour
[EVO 4G Android Development] ms79723:
i can back up those claims for barely losing any battery. I walked from my home to the park with everything on: 3g, 4g, wifi, gps and bluetooth. It was about a 45min walk and my battery stayed on 89%. This phone also charges up quicker too, my phone is slowly replacing my laptop now.
[EVO 4G Android Development] halocaridina:
Hi gotshores and ms79723,

Thanks for the reports. Out of curiosity, which version of 4.2 Beta are both of you using: more aggressive undervolting, less aggressive undervolting or no HAVS?

Thanks in advance.
[EVO 4G Android Development] halocaridina:
Hi netarchy,

Great work with the 4.2 Betas. Really like what I'm seeing from my phone battery-wise running 4.2 more aggressive and setting governor to smartass via SetCPU (keeping it at 998).

Just noticed that you are packaging 4.2 no-HAVS with Burnt Droid ROM. Any particular reason for this (would have thought 4.2 more aggressive would be the default)?

Thanks in advance.
[EVO 4G Android Development] PlankLongBeard:
This is good to know..

Thanks for the dedication, cause honestly ppl forget, the Rom is the goodies but the kernel is the vroom vroom out the deal! :)

Sent From The Moon... :)
[EVO 4G Android Development] netarchy:
I packed in a build that I considered most likely to be stable while still being a bit experimental ;D

BD users are always free to change to another kernel of course
[EVO 4G Android Development] ricsim78:
Hey Netarchy,

Well, I have always gone back and forth between your kernels and King's.

4.2 with HAVS and aggressive undervolting now only makes my phone fly, it has definitely been good for battery life. I would say it is a definite keeper.

Excellent, excellent work. Donation incoming!

Transaction ID 7FT427144N475530H

With my new custom ROM (before it was even finished) and with your new 4.2 CFS HAVS with aggressive undervolting, SetCPU on 1190 Mhz (Smartass Governor) my phone pulled this off on the first run. No repeat run, nothing done to influence scores, just installed Quadrant and benchmarked.
[EVO 4G Android Development] ms79723:
More aggressive CFS. And overclocked to 1.22ghz.
[EVO 4G Android Development] wmdunn:
Hey Net ... I have been a big fan of 4.1.9 universal (aggressive) and it's predecessor ... using them on your own rom and several iterations of Amikam's Mikfroyo. Battery life has always been stellar. I started experimenting with the 4.2 smartass releases (havs and non-havs, more undervolting), and they are quite nice. They are smooth, very quick, and battery life hasn't suffered, even though it should get even better with time. My question centers around some graphical glitches that occur when I return to the home screen from the settings menu. Really, I can live with it, but thought you might like to know. I'm not doing anything with setcpu, just stock on Mikfroyo 3.1.

edit ... these are the CFS Smartass builds

edit ... just loaded the less aggressive CFS Smartass, and the glitches have gone away
[EVO 4G Android Development] beerad29:
4.2 CFS more aggressive SA update

I can corroborate excellent battery performance when the phone is asleep with this kernel. Last night, I went to bed with my phone fully charged and was at 97% six hours later. I had uninstalled SetCPU so I could see how my phone would work with no extra OC, etc.

However, when I started to use the phone the battery drain became quite noticeable. I lost about 20% in 25 minutes of emails, phone, and web usage. I am going to try the less aggressive SA and see if this works better with my phone. I loaded both 4.2 BFS kernels yesterday but these don't play nice with my phone.
[EVO 4G Android Development] gotshores:
I'm using the more aggressive CFS with no overclock and I leave it on the smartass governor
[EVO 4G Android Development] Biofall:
Testing what's in my sig (aggressive UV) and I'm getting great sleep, but its battery life while in use remains to be seen. I will post tests later.

Thanks net
[EVO 4G Android Development] netarchy:
There does appear to be some room for tweaking frequency behavior during active use (go go gadget beta testing! :D). The idle/sleep power consumption is fantastic, so it's definitely progress ;D

Could you elaborate if possible on how the BFS builds were not "playing nice" with your phone?
[EVO 4G Android Development] ms79723:
hm, well i know for a fact that the 4.1.9.1 universal aggressive volting kernel was the bees knees when it came to great battery life while the screen was on. But for some reason, my phone never went to sleep with that kernel...so now i dont know if i should go back to that kernel or stick with this one...hmm..
[EVO 4G Android Development] Biofall:
I've been plagued with similar sleep issues. I have to reboot, then use system panel to kill all startup tasks or my phone WILL NOT sleep. Proven and tested close to twenty time, no exaggeration. Sucks because I have to do it on every reboot. I wonder what is causing it.
[EVO 4G Android Development] ms79723:
glad to know that im not the only one who was having that issue, whenever i brought it up nobody could relate. SetCPU couldn't even help, the battery would just tank when the screen was off >.<
[EVO 4G Android Development] halocaridina:
Hi gotshores and ms79723,

Thanks for the quick replies and info.

I'm seeing results similar to both of your reports as well as others such as beerad29. Namely, the 4.2 CFS w/ HAVS more aggressive kernel with smartass governor running sleeps like a rock and consumes almost no power while screen is off (with no SetCPU profiles and at 998). While the screen is on, the battery drain becomes noticeable relative to similar usage running the 4.1.9 universal (aggressive) kernel OC @ 1.19 w/ SetCPU.

As a reference for my first 24 hr period with 4.2 CFS w/ HAVS more aggressive kernel with smartass governor:

54% left with 15 hr 30 min since unplugged

Cell stand-by at 43%; time without a signal at 34% (lots of signal issues in the building I work in, which typically drains power real quick).

Given the above, I'm really liking this kernel in combination with Calkulin's EViO 1.3.1 ROM.

Guess its decision time between power save in sleep or power save in usage. Nice to have two great kernels to fawn over until Net's cooks up the next source.

Net, thanks also for your reply. I thought widest application might be your reasoning with the kernel choice for Burnt Droid. Again, I/we really appreciate all of your dedication to these kernels.
[EVO 4G Android Development] ms79723:
went back to 4.1.9 aggressive kernel and now this phone is sleeping like a baby. of course i have to use setCPU profiles but atleast its sleeping. Hopefully it still kicks ass with the screen on, gonnna test tomorrow.
[EVO 4G Android Development] beerad29:
Update to Net's last inquiry

Net - both BFS 4.2 havs kernels drained my battery like water through a sieve. I have never seen anything like it. I could have tried to recalculate my battery again but have been using Battery Snap and watched battery voltages/temps. I have a Nova display but the CFS kernels seem to work better on my phone. I was using your latest ROM but am trying Azrael 2.4 for the next 24 hours as a comparison. I know that everyone's EVO is different but this has been fascinating watching the radically different reactions to different setups.

If I wanted to use SetCPU without profiles, what settings would you suggest? I will keep everyone informed of what my phone's performance is like with the new setup.
[EVO 4G Android Development] nugzo:
Testing beta 4.2 BFS,Havs,Aggressive UV @ 1228mhz on MIUI 10.29 Rom. Looks and feels good so far!
[EVO 4G Android Development] jayv1717:
nice!! think you can run battery tests and report back??
[EVO 4G Android Development] netarchy:
Both? There are three builds for BFS, if you tried two of them with these results, which two did you try? (I'm guessing the HAVS builds, if that's the case, would you mind trying the BFS nohavs build and seeing if you have the same problem?)
[EVO 4G Android Development] godfirst:
So far u can say I'm liking 4.2 bfs more aggressive, I'm at 60% with 18+hrs of up time and 2+hrs of awake time with moderate use, not too heavy. I'm oc to 1152 with no profiles used, will post pics when I'm done.
[EVO 4G Android Development] sling:
I'm using 4.2 CFS HAVS aggressive undervolting finding Slacker & XiiaLive Radio cut out-music stops playing shortly after screen goes into sleep.

Anyone running build please test out provide feedback
[EVO 4G Android Development] ms79723:
That's probably because of the really low frequency the cpu goes to while the phone is sleeping. I assume that because both those apps seem like they would require a lot of power to run, don't think any device with a 128MHz processor could run those, and that's probably the frequency the cpu goes to while the screen is off.
[EVO 4G Android Development] sling:
I will give less aggressive undervolting version a go then.

Update

hmm maybe the more aggressive version was settling into Rom.

The reason I think this is because I started both apps music playing on both at same time with no cut out...I even sent emails while they were running no crash was had
[EVO 4G Android Development] achllles:
Hmn I tried 4.2 cfs havs more agressive undervolting and slacker worked fine. I run every day, and usually listen to slacker for about 15-20 minutes while I'm running. I also run sportypal at the same time though.

Oh sorry, didn't read the part that you are on fresh. I'm on myns 2.2
[EVO 4G Android Development] xHausx:
Scratch that post. I must have had an older copy of 2.2, I'm using the CFS low voltage build w/ smartass now and the performance is much better now. This is the quickest kernel I've seen so far.
[EVO 4G Android Development] EliWay:
Actually to everyone saying this is a CPU issue, it's not. It's a well known Android bug with the 3G connection.

The fix: Make sure WiFi is ON (Not associated or connected to a WiFi network, just on), and you will notice that it will keep playing.
[EVO 4G Android Development] sling:
4.2 CFS HAVS more aggressive undervolting will be a keeper on my device.

Battery life is outstanding & scores not bad :)
[EVO 4G Android Development] xlGmanlx:
they will probably get better if you turn off GPS. also, QUAD's scores are good for judging performance difference on your device but are can be duped, the KISS rule applies though, if it feels fast and you think its fast, then it is fast!! Fresh was the first ROM i loaded after i rooted and his have always been rock solid outings
[EVO 4G Android Development] sling:
opps posted wrong screen shot a couple post back
[EVO 4G Android Development] parousia15:
Running cfs w/havs and aggressive under volting. I've noticed improved animations overall. Can't comment on battery life since I flashed this the same time I started using an 1800mah battery. Did you tweak the gpu again? I now get 19.7fps on nenmark.
[EVO 4G Android Development] achllles:
The battery life on

netarchy-toastmod-4.2-cfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)

is outstanding. I only used it for a day before I flashed kernel, and I'm back to using it. I think I unplugged at 94% and it lasted about 15-6 hours before I went and flashed other kernel.

It's a keeper imo. Just give it a couple of days.
[EVO 4G Android Development] sling:
I use them everyday at work for long periods of time just about never have connection issue on 3G
[EVO 4G Android Development] freeza:
Running at 1228MHz now thanks to this kernel!

4.2/cfs/aggressive/havs/universal/smartass
[EVO 4G Android Development] dkelle4:
Tried running all three 4.2 CFS kernals (aggressive, less agressive, non-havs) and I had an incredible amount of screen tearing in all 3. I was using them on the MIUI ROM if that makes any difference.

PS. This was without the use of SetCPU
[EVO 4G Android Development] xlGmanlx:
thoughts on battery life while idle, in use?
[EVO 4G Android Development] ms79723:
The universal kernels don't play nice with aosp roms for some reason.
[EVO 4G Android Development] dkelle4:
Doesn't that defeat the purpose of them being universal? :p jk

I've used 4.1.9.1 Universal on both CM and MIUI without any screen tearing issues.
[EVO 4G Android Development] ms79723:
Well 4.1.9 caused tearing for me on both of those, but 5.0 was smooth. I guess it just depends on the phone.
[EVO 4G Android Development] freeza:
Still testing, but I would say this Kernel is a winner. I haven't noticed any abnormal drain, even running at 1228MHz.

Pretty much getting the same battery life as with 4.1.9.1. The increase in MHz may be attributed to the same battery life, in which case battery life would be better at lower frequencies!

Using it with SetCPU profiles for charging[ondemand] and screen off[max245/min128] since i'm not sure what the default idle/screen off functions are for smartass.