yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Rippley05:
OK should I be using setcpu to play with any overclocking on 3.7.3c DC version?

And should I be getting more than 44 or so FPS in fps2d? This is the first time I flashed any kind of custom kernal other than the one that comes with the RoMs I use and any tips/info would be appreciated.

Also, if I start messing with setcpu would the battery drain/rewards be worth using it in anyones opinion.

**edit** Using a 003 Nova screen**
[EVO 4G Android Development] freeza:
anyone tried apps2sd with this one? since it's supposed to be compatible now?
[EVO 4G Android Development] Alto101:
Rooted with Unrevoked 3 and just flashed with the 3.7.3c kernal. What a difference in the overall feel of the phone! My FPS as measured by Fps2d are 51 with a standard deviation of 10.74 (2nd run 51 and 10.72). I have a novatek screen and hardware version 3. I am not currently overclocking.

Question for all, and sorry if this is not the proper place to ask this question. Which custom ROM's can I use with my current setup?

Thanks to all of the developers for this great fix!!!
[EVO 4G Android Development] chazglenn3:
If you installed the netarchy 3.7.3c kernel you are overclocking. It is part of the kernel. You just are using the default overclocking protocols instead of tweaking them yourself with SetCPU or Overclock Widget.
[EVO 4G Android Development] acrh2:
Actually, I just installed the oc kernel, and it's not overclocking.

My cpu speeds are set by the kernel at 245-998MHz. The oc part are extra optional speeds 128-1150, but aren't enabled by default.
[EVO 4G Android Development] fatboypup:
thank you

this is the first time ive flashed a custom kernel painless and it works great :)
[EVO 4G Android Development] EVO-lution of Man:
Check your build. That doesn't sound right at all. You should be overclocking by default.
[EVO 4G Android Development] netarchy:
That is really strange. There's gotta be something in fresh that is triggering this in a small percentage of people, and I'll wager the culprit is a custom ramdisk. I can't say for sure at the moment since I don't make fresh, and I'm not familiar with its inner workings/tweaks.

I'm guessing you're heartset on using fresh, but I'd be curious to know if you run into the same behavior on a different rom.
[EVO 4G Android Development] acrh2:
Well, I checked. I'm pretty sure I also have setcpu disabled with autostarts, but i suppose i'll check again.

EDIT: I guess setcpu wasn't disabled. So you were right.

EDIT2: After reading post below, Netarchy must be right :)
[EVO 4G Android Development] netarchy:
Nah he's actually right, defaults are 245-998 with the option to set 128-1152 in the range in the oc-enabled 3.7.3c.
[EVO 4G Android Development] guyver2077:
I flashed this kernel over stock dc 3.2.3

I noticed in fps2d i broke the 30 fps barrier.. but I also have the same prob in setcpu. Cant set past 998 mhz

edit- Ok when into device selection and had it auto detect... and now i can set the max up to 1152000
[EVO 4G Android Development] EVO-lution of Man:
I should really pay better attention to what I'm doing to my device then. great work by the way.
[EVO 4G Android Development] guyver2077:
nicely done.. everything went smooth.

First time actually oc'ing the evo.. any apps that push the evo? What apps can i use to see any performance gain?
[EVO 4G Android Development] Fyahstarter:
Question? Does it matter which?? recovery I'm using? Using simpleroot, cm recovery, fresh 1.0.1 and this kernel I get nothing. Do I have to use amon-ra?
[EVO 4G Android Development] ticklemepinks:
look i'm having a slow night just to make sure if I download the one with overclocking I don't need setcpu... basically which is the best for battery life??? and if ya don't mind wut are the set cpu setting 245-998 right?
[EVO 4G Android Development] funcrusher:
Did you just start that with 3.7.3c? I thought you told me last night that it defaulted @ 245-1152. ;/
[EVO 4G Android Development] tuleshed:
any idea what would cause bootlooping after installing this kernel over fresh evo 1.01?
[EVO 4G Android Development] :
3.7.3c - still only get 30fps max......what the heck am I not doing?
[EVO 4G Android Development] kennyc1:
Similar experience with 3.7.3b earlier today. I swapped the battery and the phone won't boot. It was stuck on Evo 4G screen.

I had to do nand restore.
[EVO 4G Android Development] chazglenn3:
I used Amon-RA. I don't know that it is required, though.
[EVO 4G Android Development] chazglenn3:
Me too...:confused:
[EVO 4G Android Development] netarchy:
It should only apply with 3.7.3c, though in hindsight I could change it in future revisions if I'm gonna maintain a non-oc branch as well. The current non-oc builds are something of an experiment in seeing if it's worth it to maintain two lines vs one.

The intention is that you have the option to overclock if you want, rather than it being forced, due to the inherent risk of instability in overclocking. While the majority of phones can handle 1152, a few can't clock quite that high (yes I am aware that a few can also actually clock higher), and defaulting to it can result in poor performance on those phones until the clock is lowered.

Having the default as stock with the option to overclock through the use of setcpu or another similar prog, or even echoing values to the relevant device files seems like a good compromise. The system starts up at stable stock speeds, and you can overclock if you want.
[EVO 4G Android Development] fr4nk1yn:
I'm one of the one's who can't ): My stable is 1.07ghz.

Still a good improvement (: Thanks!

Is there any voltage tweaks included? Maybe a touch more voltage would get me stable higher.
[EVO 4G Android Development] gabemeyers:
im on fresh 1.0.1 and it still seems to be breaking ap2sd, well not braking just not using as my partition still seems to be there ohh 3.7.3c general oc'd

everything else is doing waht it should be though... 54fps 5.73setdev so on
[EVO 4G Android Development] nttdemented:
Spoken like a true overclocker!

Anyone use HDMI yet on the latest kernel? I'd try but I'm using Cyanogen's Nightly builds and I have no intent on flashing back to a 2.1 ROM any time soon.

I'm not feeling lucky enough to go gun-ho and install this Kernel over Cyanogen's, cross fingers and hope for the best. :p
[EVO 4G Android Development] netarchy:
That's good, as it wouldn't work ;D

The CM kernel includes our fixes from this one anyway ;D
[EVO 4G Android Development] appzattak:
I will try it on DC and see how it goes.....

same problem here...I've posted quite a bit about it a few pages back...
[EVO 4G Android Development] guyver2077:
Just wanted to update that hdmi worked great on latest oc kernel with dc 3.2.3

Great job
[EVO 4G Android Development] whoisatlas:
I just flashed this kernel along with Damage Control and it runs so much smoother. The response time seems much more snappier, and transitions are much smoother.

Thank you!
[EVO 4G Android Development] nttdemented:
*snaps fingers in the air like a black woman*

Oh no you didn't!!!
[EVO 4G Android Development] netarchy:
Right. For Fresh 1.01 users, I've packaged a build that should be totally compatible with Fresh. It's in the first post.

If you've been having issues using netarchy-toastmod on Fresh 1.01, give it a try.
[EVO 4G Android Development] blix1337:
I'm having stability problems. The phone reboots randomly. Im running DC 3.2.3 and 3.7.3C. I have these problems even when Im at default clock speed. I had the same problem w/ ffolkes kernel as well. Anyone know how to fix this instability? I have Nova 0003.
[EVO 4G Android Development] gangsterholla179:
I'm current having some issues..after two days of using the 3.7.3c, I regained the fps cap (30 avr and 5.13 stdev) and I'm only able to get 4 touch inputs instead of 5.. On top of that it, launcher pro is a bit unstable (it forces my widgets), and it resets from default. I'm currently running fresh 1.0.1 amonRA, aloysuis theme 2. Any ideas on how to fix that?
[EVO 4G Android Development] netarchy:
Does it happen with any other kernels?

Have you tried the no-overclocking kernel and seeing if it happens with that?

Random reboots could be a sign of a problem with the phone itself, or an issue with the rom, etc.

When you flashed Damage Control, did you do a full wipe first? If you did not, the random reboots could be caused by old data that didn't get overwritten when you flashed causing issues.
[EVO 4G Android Development] netarchy:
Try the newly posted Fresh compatible build on the first page and see if that helps.
[EVO 4G Android Development] gabemeyers:
with the new kernel for fresh 1.0.1 aps2sd is working 55fps with a setdev of 3.07

beer on the way! ohh and if the beer isnt enough, THANK YOU VERY MUCH!!!

edit.. Although I would like the donation to go towards the bunny take over, just to see it in action.
[EVO 4G Android Development] mylasthope:
If my phone is running just fine using the general population build of 3.7.3c, should I bother flashing the fresh 1.0.1 version? I'm using Fresh 1.0.1. Haha :)
[EVO 4G Android Development] freeza:
thanks for the report back! crossing fingers for it to work in near future updates.

and there it is! lol
[EVO 4G Android Development] ticklemepinks:
ok question can i get the 3.7.3c with oc and use setcpu to got to 245 when screen off or does it already know to do it, I'm really needing to save battery... thanks
[EVO 4G Android Development] freeza:
Beautiful work netarchy, just tried the kernel and apps2sd is working great. FPS are 52 and with build 002 and nova. perfect :)

PS: I'm using a heavily modified version of fresh 0.3 as well.
[EVO 4G Android Development] netarchy:
Yes you can, just set up a screen off profile.
[EVO 4G Android Development] njfoses:
Do I have to be on a 1. 47 rom to flash this as I'm running bugless beast . 3 right now? If I flash and a new version of the kernel is released do I have to do a full wipe every time or just flash over top?

nvm: I flashed the kernal and everything is working great so far as i have 5 point and fps2d averages 52fps. Thanks.
[EVO 4G Android Development] scriptx:
3.7.3c general (overclocked) worked fine w/my Fresh 1.0.1. I don't use apps2sd. I wonder if that's where the hiccup occurs? I flashed the 3.7.3c Fresh build for s&gs.. average fps over 3 runs was 52, avg stdev was about 5.90. Thanks for taking care of the community.. though it kind of sucks you're having to maintain kernel builds for individudal roms now.
[EVO 4G Android Development] funcrusher:
Oh, ok. Personally, I think having them run @ stock as default w/ the option to overclock makes most sense, but hey, what do I know. ;)

Once again, thank you for the reply and kernel.
[EVO 4G Android Development] funcrusher:
Btw, even though the two different versions (oc and non-oc) by default are running at the same frequency, they feel like night and day to me. the oc version, by itself, no setcpu or anything--seems so much snappier.

the battery seems to be a bit better on the non-oc. (when they're both running 245-998)
[EVO 4G Android Development] Shinzul:
I'm on the kernel #128 - is there any reason I should upgrade for performance purposes, or have there not been any changes for performance since then?
[EVO 4G Android Development] shad0w77:
using the new kernel for fresh rom....

now, i am getting a lot of wakeups from idle in powertop... ne ideas? msm_i2c and smsm_dev seem to be higher than what they were. gonna flash back to the general population build to see if that does nething in the mean time

Wakeups-from-idle per second : 107.0 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
39.5% ( 32.7) <interrupt> : gp_timer
18.4% ( 15.2) <interrupt> : msm_i2c
12.3% ( 10.2) <interrupt> : smsm_dev
6.3% ( 5.2) <interrupt> : msm_hsusb
3.6% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
3.2% ( 2.7) er.ServerThread : futex_wait (hrtimer_wakeup)
2.4% ( 2.0) WebViewCoreThre : futex_wait (hrtimer_wakeup)
1.8% ( 1.5) <kernel core> : hrtimer_start (tick_sched_timer)

UPDATE: Must have been caused by some of the apps I opened. On a fresh boot of the new kernel for fresh, my wakeups are low....

Wakeups-from-idle per second : 64.2 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
37.2% ( 19.7) <interrupt> : gp_timer
20.6% ( 10.9) <interrupt> : smsm_dev
10.2% ( 5.4) <interrupt> : msm_hsusb
5.7% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
5.1% ( 2.7) er.ServerThread : futex_wait (hrtimer_wakeup)
4.0% ( 2.1) <kernel core> : hrtimer_start (tick_sched_timer)
2.3% ( 1.2) rild : __netdev_watchdog_up (dev_watchdog)
1.9% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
1.9% ( 1.0) dc.bloo_free : futex_wait (hrtimer_wakeup)
[EVO 4G Android Development] mikevillarroel:
Hey netarchy, with the new 3.7.3c the menu. Home. Back and search buttons wont light up, went back to 3.6.4 and they are working.
[EVO 4G Android Development] bpqow:
On fresh 1.0.1 HW 003 and 3.7.3c. Everything is working fine here. Thanks.
[EVO 4G Android Development] scriptx:
Is anyone experiencing increased battery drain with 3.7.3? My battery is draining faster since having flashed 3.7.1+. My best battery performance, per JuicePlotter, was with 3.6.4. setCPU set ondemand, and screen off set to 285mhz.

Top causes for wakeups:
32.4% (104.3) <interrupt> : msm_i2c
18.6% ( 59.7) <interrupt> : smsm_dev
16.5% ( 53.0) <interrupt> : vsync
15.6% ( 50.3) <interrupt> : gp_timer
3.1% ( 9.9) <interrupt> : msm_hsusb
2.5% ( 8.1) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)

I've also noticed that after having turned 4G on and then off, in logcat I continue to see:

I/Wimax ( 384): <DC> Try to establish a connection to DC server.
E/Wimax ( 384): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'
I/Wimax ( 384): <DC> Try to establish a connection to DC server.
E/Wimax ( 384): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'
repeat..

I'm currently flased with the latest 3.7.3c fresh-tailored kernel. I'm going to flash back to 3.6.4 to observe performance there too.
[EVO 4G Android Development] netarchy:
That isn't from the kernel, it's a known bug with the wimax and turning 4g on/off. You would get that even if you were running HTC's stock kernel.

The only way to get rid of it is to reboot after you turn off 4g on the phone.
[EVO 4G Android Development] scriptx:
Thanks. It was just an observation made when trying to isolate what IS draining the battery so quickly.
[EVO 4G Android Development] plmiller0905:
What app is everyone using to see what their fps is?
[EVO 4G Android Development] torankusu:
Hi all,

i've been running stock sprint build rooted with toast method with no issues since i got my evo on june 4th. my hardware is a 002 with nova panel. i decided to give this fps fix kernel a try, i installed 3.7.3c no-OC and guys what a difference this thing makes, it is not that i needed it i was fine running fully rooted sprint stock build but this thing add some new flavor to the user experience on this phone. besides that i'm getting a lot of errors "call data failure" that i never saw before applying this fix but i think it is the phone trying to connect to the data network, no biggie but will report back if the problem persist, it could just be an outage here in NYC.

Anyways is there any extra tweaking that i need to do to the phone or some tests that i should be running to verify that the FPS fix is working as it should. like i noticed some screen tearing while scrolling only.

My thanks goes to all those involved in this project, guys you rock.
[EVO 4G Android Development] xak944:
Was getting some occasional random reboots with Fresh 1.0.1 and kernel 3.6.2, not sure if it's related or not. Just upgraded to 3.7.3c-fresh-compatible, will report if it's fixed or not.

Thanks for the awesome kernel!

EDIT:

Confirmed 5 touch points and 50+ FPS! (ATMEL_x0080_x0016 and Novatec).
[EVO 4G Android Development] scriptx:
fps2d or gears
[EVO 4G Android Development] BB15:
Flashed 3.7.3c running DC 3.2.3 and right out of the box I'm averaging 46fps and have 5 point touch input. I was already running SetCPU and kept my previous profiles. Battery life (so far) seems unchanged and everything else seems to be working fine.
[EVO 4G Android Development] netarchy:
You'll probably get a bit higher fps if you change your profile in dconfig to something less battery-saver-ish. Of course, this probably would come at the expensive of a bit more power use, but it's up to you ;D
[EVO 4G Android Development] netarchy:
If that's error 67 that would indeed be a Sprint-related error, prolly due to whatever issues are going on in your area.
[EVO 4G Android Development] BB15:
Yeah, just not sure if the tradeoff for a few more fps is worth it for me. Can't wait for DC Froyo with the new netarchy kernel! :cool:
[EVO 4G Android Development] torankusu:
yeah that is what i thought. is battery life normal using this kernel, like is this kernel known for using more battery that the stock ? just wondering. i'm on latest sprint rom fully rooted.
[EVO 4G Android Development] saipoob:
Any chance of having your fixes merged with the Fresh Toast BFS fixes? I really like the Fresh Toast BFS kernel but I have a Novatek and the panel code is way behind yours. I'll happily donate 20 bucks if you can merge the two code bases.
[EVO 4G Android Development] wuclan48:
I'm pretty sure all custom kernels have better battery usage than stock. I'm using almost no battery when the screeen is off. Charged it to 100% this morning, turned off the screen and three and 1/2 hours later was still at 100%.
[EVO 4G Android Development] torankusu:
WOW that sounds good. lol. i usually get 20 hours to a day: gmail push, work email every 1 hour, weather every 1 hour, news every 1 hour, screen brightness like 25%, even thou i dont know where to check screen brightness percentage. 2x2-5 minutes call within and hour from 9am to 5pm. so yeah i had good battery life with stock, let see with this.
[EVO 4G Android Development] netarchy:
Battery life also depends highly on how you use the phone, and how you manage power.

For instance, I usually have gps off, I run juicedefender to manage turning wifi and data on/off, setcpu with profiles set up to lower the max speed of the cpu as the battery hits certain drain points, I don't run 4g unless I need it for something, I keep bluetooth turned off unless I need it, and I use a static brightness setting (25% in my case) instead of the auto adjust.

With my average usage of the phone, I have up to ~24 hours on a full charge according to juiceplotter.

Obviously that's gonna fluctuate a bit depending on how hard I use the phone.
[EVO 4G Android Development] wuclan48:
Exactly. I don't keep anything on I don't need, and I have my power usage optomized as well. If I use it straight from full charge down ~10% with the screen on the whole time (surfing the web, downloading, using FB chat, etc. heavy usage, but on wifi, not 3g or 4g) I'll get about 6-7 hours of life. If it's a weekend and I barely touch it I'll get more than two days on a charge. Everything else is somewhere inbetween depending on usage.
[EVO 4G Android Development] fatboypup:
I accidently installed the

gen pop build on fresh 1.0.1 because I didn't see the one for fresh users haven't seen any problems yet should I leave well enough alone or switch?
[EVO 4G Android Development] wuclan48:
I used the most recent gen pop build until the fresh specific one was released. I did switch because on an earlier build (3.7.2 I think) I was getting random reboots and although it hadn't happened yet with this gen pop build I figured I'd be proactive.
[EVO 4G Android Development] xusxmarinesx:
Has anyone had the problem when pressing and holding down a letter to get a symbol or a number it doesn't let you it just automatically types the letter
[EVO 4G Android Development] funcrusher:
It's happened to me a few times before I had this kernel flashed and after.

I'm on back snack 9.7, although it has happened to me on 9.6 too.

I can't say whether or not it's exclusive to baked snack because I haven't tried anything else and was only on stock for a few hours.
[EVO 4G Android Development] appzattak:
Netarchy, the latest for fresh now works, thanks so much!
[EVO 4G Android Development] PhantomApollyon:
my battery life was about 15% better according to juiceplotter with 3.6.4 than it is with the most recent 3.7.3c - so yes I am

that being said, making it through a day and half of moderate usage is fine by me....but 2 days is better(which I WAS getting with your previous setup as well)
[EVO 4G Android Development] BB15:
Hmm, my battery life seems to have taken a giant dump today. This morning it "seemed" relatively unchanged from before flashing 3.7.3c, but now it's tanking. I'm currently at 61% and have been unplugged for about 7 hours. Not terrible, but this time yesterday (prior to the new kernel) I was at about 81%. Have used the phone very moderately today.
[EVO 4G Android Development] revengesrage:
this is so freaking awesome I've got a 5 point multi touch screen!!! about the battery drain don't know cause I'm using the dc no oc 3.7.3c
[EVO 4G Android Development] BB15:
I'm using the same.
[EVO 4G Android Development] scriptx:
Thank you for confirming. I am going to flash back to 3.6.4 and compare some stats/services to see if sticks out :)
[EVO 4G Android Development] N00dle:
So this might be a dumb question guys however, the undervolting is not manually adjustable? When using SetCPU and just setting the overclocking it automatically adjust the undervolt?

Am I getting this right.

I'm running 3.4.7c Fresh 1.0.1
[EVO 4G Android Development] EtherealRemnant:
I don't understand where the overclocking went wrong.

When I was running ffolkes' kernels on my phone, I could hit 1.2Ghz no problem and stably. The voltage on this kernel causes it to freeze and reboot if I clock it to 1152. How much of a voltage difference is there? I would really like to have my 1.2 back...
[EVO 4G Android Development] mawst95:
I had my first reboot at 1.15ghz today with the latest 3.7.3c kernel. Hadn't experienced this before with 3.6.4.
[EVO 4G Android Development] gangsterholla179:
I have tried out.. fixed the fps cap.. But still having the other issues
[EVO 4G Android Development] shuggashuggs:
RvU 1.4 and 3. 7. 3c wow! No problems... thanks!
[EVO 4G Android Development] netarchy:
I'm looking into this. Would you mind trying the overclocking enabled kernel (and just not setting overclocking frequencies in setcpu or oc widget if you're wanting to stay at stock speeds) and letting me know if the battery drain seems better?
[EVO 4G Android Development] liquidkernel:
I have 3.7.3c w/o overclocking for DC installed on DC 3.2.3. SetCPU installed, not used. Evo Switch installed, not being used.

Battery life is fantastic. 3 hours unplugged and 90% remaining with plenty of usage during that time.
[EVO 4G Android Development] netarchy:
Still having reboots even at stock speeds?

For the sake of experimenting, try using a stock kernel for a while and seeing if the reboot issue goes away (I know losing the fps fix and such for a while will be annoying but it can help in tracking down the source of the problem).

If they still happen with a stock kernel, that would eliminate the kernel from the equation and make it more likely that it's either an issue with the rom, or an issue with the phone.
[EVO 4G Android Development] netarchy:
Really now... I'll hit ffolkes up and see if he did tweaks of his own to the OC stuff in his kernel.
[EVO 4G Android Development] elhalish:
Fps resets back to stock after some time. Tried Evo Switch after but the frequency also changes back to stock. Also getting some tearing.
[EVO 4G Android Development] PhantomApollyon:
I have to clock mine down to 1113mhz max to avoid random reboots with the newest kernel as well, back on 3.6.4 I had no issues getting up to max. Not that its a huge issue, but just confirming.
[EVO 4G Android Development] PhantomApollyon:
I also get the occasional reboot at 1152mhz and have had to set it back to 1113 to avoid that issue. Back on ffolkes I WAS also able to stably hit 1.2Ghz.