yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] netarchy:
Do you overclock? If so you may want to try changing the default speeds in setcpu to stock, flashing the kernel, re-detecting the speeds in setcpu when it boots up, and then going back to your regular speed settings.
[EVO 4G Android Development] cosine83:
Overclocking even to 1.13 is causing lock ups and reboots from android mode. This wasn't happening in Hero_Over's kernel. I cleared cache and dalvik twice before flashing. Runs fine not overclocked. I also only have conservative, interactive and performance governors available in setcpu (4.1.3 kernel).

I'm also getting SD card error where it's being mounted as read-only.
[EVO 4G Android Development] tarheelsmj12001:
Still reboots everytime :-(. Im running baked snack.
[EVO 4G Android Development] netarchy:
Interactive? That's not even compiled into the kernel, your choices should be ondemand, performance, or conservative.

I'm guessing you had king's kernel flashed at some point, and setcpu is still seeing settings it had for it. Try wiping cache/dalvik-cache, and re-detecting frequencies in setcpu. *EDIT: are you using clockwork or amon as your recovery?
[EVO 4G Android Development] cosine83:
Pardon, I meant on demand. I was thinking about interactive because I'd just read your post mentioning it and lines of thought crossed.

I did the re-detect before I even applied OC and wiped cache/dalvik twice before flashing.
[EVO 4G Android Development] koricua74:
+1 On this as soon as I OC'd it rebooted
[EVO 4G Android Development] netarchy:
Hrmm, what speed did you try and overclock to?
[EVO 4G Android Development] bacdoliljo:
Can someone try this if you're using swype : swype vertically and follow the trace. It's fairly straight right? Now swype horizontally. It zig zags right? I'm not sure if it's related to the kernel or not but that's the only thing I changed since I noticed this problem. I've reverted back to 4.0.3and am still getting the same problem
[EVO 4G Android Development] cosine83:
I attempted 1.13 and 1.26. Both caused locks and reboots.
[EVO 4G Android Development] netarchy:
Ok, I've reproduced it, working on it.
[EVO 4G Android Development] koricua74:
1.19 (ondemand); but now after the reboot everything is running smoothly OC'd to 1.19 (ondemand) I even set up my profiles with no issues. Probably a isolated incident.
[EVO 4G Android Development] nugzo:
Fresh install of everything, wiped everything, 4.1.3 setcpu to 1228 which i'm stable on all other kernels(sept 4.1.2), somewhat stable on 1267 with some kernels, but as soon as i set to 1228 and hit performance, which automatically applies the 1228, i locked up instantly.
[EVO 4G Android Development] nugzo:
you may not have stressed it to 1119 yet. set setcpu to performance and see if your still good.

you know what would really help out, is a cpu voltage monitoring tool. something we could log or see onscreen. Everest for android would be awesome!
[EVO 4G Android Development] koricua74:
It's set to performance now since it's charging and one of my profiles is that when charging it scaling is performance.
[EVO 4G Android Development] cflynt:
Thanks for the update, hope you had fun at Quakecon. I flashed the latest Fresh, and put this on and still getting the error like others on Error 9 I believe. Still flashes most of the kernel but not sure if it does it all or not. I have flashed other kernels without issue, so not quite sure why these have been giving people fits. But just wanted to let ya know. Appreciate all your work.

Edit: I should note that when it does fail like that, I do lose ADB capability. But SD Card still works and such.
[EVO 4G Android Development] OneStepAhead:
no problems with swype for me on KK Kernel 6, Netarchy 4.0.3, or Netarchy 4.1.3, but I've now heard of people having problems using swype with those 3 kernels. horizontal and vertical are all good. try shapewriter for the time being, same exact thing as swype (maybe better).. personally once I found SwiftKey I quite using swype/shapewriter.
[EVO 4G Android Development] Bradart:
Yeah, if i overclock it at all instant lock up and reboot. Every single time. No matter what.
[EVO 4G Android Development] eniamg02:
I know not new but +1 since HAVS
[EVO 4G Android Development] bacdoliljo:
Thanks. I just wiped caches and flashed the latest kernel Again along with re installing swype. Everything seems to be working fine again.
[EVO 4G Android Development] appzattak:
same here, and I only am tryin to overclock to 115X , whatever you maxed the previous kernel at....
[EVO 4G Android Development] TorxT3D:
awesome work, but i'll wait for the dust to settle on the latest fresh rom before flashing the latest. seems like everyones having some issue.
[EVO 4G Android Development] kf2m:
4g refuses to start. :( Rebuilt from ground up.
[EVO 4G Android Development] Reaper333:
lol Im back again. I thought I had 4.1.2 running good. But, once I switched on wifi it crashed and went into eternal boot loop. No fun. So, I dropped back down to an 4.0.3 again. Works fine. Will me waiting for the next release. :)
[EVO 4G Android Development] smw6180:
Always make sure when testing OC kernels that you do NOT tell setCPU to apply on boot (I assume you're using setCPU, if not, disregard). If you get a 'bad' clock setting and then it applies on reboot you will indeed eternally bootloop.
[EVO 4G Android Development] d4sheriff:
4.1.3 is not working for me now..... I had it working just fine, but then applied the new Fresh upadate, and now I have constant boot loop..... restoreing back the original Fresh. Hopefully Netarchy will update the Kernal to run with the new Fresh Upadate!!!!!
[EVO 4G Android Development] drapeto:
Great advice. Thank you
[EVO 4G Android Development] drapeto:
Thanks for the advice!
[EVO 4G Android Development] fr0st420:
Running 4.0.2 again. The newer versions with havs seems laggy to me. Keep up the good work.
[EVO 4G Android Development] Reaper333:
Yeah I learned that the last time I flashed a kernel. So this time I deleted setcpu before I installed the kernel. Then after I had finished installing it I reinstalled setcpu and tested it that way. It worked fine overnight then this morning I turned on wifi and at that instant it crashed and from that point it would lock up every time it got back to the lock screen after boot. So, I nand back to an older version and its working great. So, who knows Im not sweating it. Ill just wait for the next release to try. No big deal.
[EVO 4G Android Development] bc0508:
Having some issues with 4.1.2 i am seeing alot of reboots. I am going back to 4.0.2 I am running netarchys rom also.

Anyone seeing reboots? 4.0.2 has been rock solid... I am running setcpu with profile but it is not set on boot.

Have I missed something that I should have done with the new kernel
[EVO 4G Android Development] ZELL22:
Getting reboots too on 4.1.2 upon overclocking. I did not wipe cache first, so I'm going to go back and try that and if I still get reboots I will revert back to 4.0.2 as well.
[EVO 4G Android Development] rutter9:
This kernel works great. I used your rom since I know it will work. Also, I can play psx4droid at 50-60 fps no hiccups. :D
[EVO 4G Android Development] lucidox:
Upgraded my DC ROM to 4.1.3 last night. I've been unplugged for roughly 8 hours now, with light use and am at around 95% battery. Incredible job Netarchy!
[EVO 4G Android Development] eniamg02:
Hows the monster spanking coming along? :D
[EVO 4G Android Development] dudleyfire:
It seems neither 4.1 or 2 are "fresh compatible".
[EVO 4G Android Development] drdrewdown:
its working fine as long i dont overclock. & this is referring to the new fresh incremental update i did 3.1.0.2
[EVO 4G Android Development] Young_e:
what about the new 4.1.3??? I just flashed fresh's update and wanted to try this kernel
[EVO 4G Android Development] drdrewdown:
4.1.3 was pulled!?!?
[EVO 4G Android Development] Young_e:
thanks for the info i just updated and getting ready to flash this kernel now, have you tried Kings kernel? and if so which one do you like better??
[EVO 4G Android Development] drdrewdown:
i have not tried it, its been tempting but netarchy is the man in my book. & 4.1.* has been impressive, seems to be quite a bit snappier
[EVO 4G Android Development] dudleyfire:
I'm getting boot loops even with a full wipe using 3.1.0.2
[EVO 4G Android Development] drdrewdown:
do you use setCPU?? do any overclocking at all?
[EVO 4G Android Development] dudleyfire:
Yes but I get the same results "even with a full wipe"
[EVO 4G Android Development] drdrewdown:
the only thing i know to suggest would be to put 4.03 on for to start with. then once its up & running with that kernel, do the 4.1.2 without any overclocking & see what happens
[EVO 4G Android Development] GruvyDude:
I have been flipping back and forth between netarchy and kingz the past few days and Im sticking with netarch's kernel releases. Im not sure whats up with kingz, but there seems to be some sort of video glitchiness. Performance is hampered on kingz kernel.
[EVO 4G Android Development] dudleyfire:
Haven't got to test it out since it was pulled.
[EVO 4G Android Development] Sprintdaddy:
I was on fresh .1 and Kernel 4.0.2. Flashed to Kernel 4.1.2 and mine was working fine, pretty snappy to me. I am using SETCPU to OC to only 1152000. It does seem like alot of ppl are unable to use 4.1.2 on Fresh's ROM, not sure why mine is. I just updated to fresh .2 and it's working good also.
[EVO 4G Android Development] lath19:
4.1.2 is working good for me. Fresh 3.1.0.2.

Linpack of 35

FPS of 50
[EVO 4G Android Development] akarol:
Yuck! That's no good. Go for kinglick's Kernel. You won't regret it.
[EVO 4G Android Development] makskylan:
I am running the 4.03 kernel, Dc 3.5 rom and Riptide theme. I haven't noticed any issues as of yet. I see where people post their Linpack settings they are getting. What are good numbers? The lower the number the better or is it the other way around?

I am getting 23.54 on the linpack test.
[EVO 4G Android Development] eniamg02:
Higher the better
[EVO 4G Android Development] prjkthack:
4.1.2 is working great for me so far. No issues. Even battery life has much improved. almost going on 9 hours and I'm only at 90% remaining.

mflops: 35

fps: 54

quadrant: 1366
[EVO 4G Android Development] leeoniya:
4.1.2 good here as well, on Fresh 3.1.0.2.

mflops: 33

fps: 54

quadrant: 1255

using setCPU, maybe explains my lower linpak & quadrant?
[EVO 4G Android Development] fazzmanic:
King kernel #1 /w bfs

mflops: 38

fps: 54

Using set cpu at 119XX
[EVO 4G Android Development] barnacles10:
Yuck? Lol. I'm pulling 54 avg fps with a std of 3 and 35 in linpack. If u use the old linpack the scores will be different. I was running the old and would avg 39 then I upgraded and avg about 35

These results are no better than what I saw over my 3 4 days on kings kernel. Plus I'm not overclocked so those scores r stock kernel.
[EVO 4G Android Development] EvoNotEvil:
flashed latest # 1 and now I have no htc music app? tit doesnt restore either.?? why?

Can someone post apk for me?
[EVO 4G Android Development] djskunkdiesel:
Nice!

Just put 4.1.3 on top of Fresh's latest and pulled this out of the hat.

Thanx man!
[EVO 4G Android Development] Rene2.5RS:
When you are posting Quadrant results like these you really should include what else you have done, what tweaks and what speed you are running.
[EVO 4G Android Development] lokko21:
Whatever he said... +1

Sent from my Awesome Fresh EVO.
[EVO 4G Android Development] lath19:
Meh, I'm happy with it. Fps of 53 seems reasonable as does a linpack of 35 considering I'm not overclocking the cpu.
[EVO 4G Android Development] nemesys504:
Is there to add powersave governor to your kernel?
[EVO 4G Android Development] Wisiwyg:
Same here. I'm happy. FPS 53, Linpack 34-35. No OC other than what's baked into the kernel. On for 9 hrs and still have about 80% battery with moderate email usage.

Netarchy 4.1.3, OMJ Froyo v3.0 Odexed

HW v02, Novatec, 16g Cls 6 SD
[EVO 4G Android Development] prjkthack:
I have to say, I've just hit 12 hours and only down to 60%. Moderate texting. The battery life is totally amazing to me. Haha.

4.1.2, using OMJ's 3.0 ROM.
[EVO 4G Android Development] J3wBaccA:
using DC3.5 and after the new 4.1.2 kernel, the phone has been crapping out as soon as it is pushed passed stock voltages :( Battery seems to be a lot worse too :((
[EVO 4G Android Development] SteelH:
Tried 4.1.3 on Froyo stock deodexed, same boot looping as 4.1.2, back to 4.0.3.a and I'm fine. No OC.
[EVO 4G Android Development] Rootwind:
4.1.2 seems to work good for me on DC 3.5 at stock speeds with the CPU down-clocked when the screen is off, but it's mostly been just using push e-mail (Touchdown). I'm at 87% after 10 hours.

No instability so far, but haven't really pushed it very hard yet.
[EVO 4G Android Development] netarchy:
New Revision: 4.1.4

Notes for Revision 4.1.4

- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)

- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so

- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)

- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
[EVO 4G Android Development] SteelH:
Grabbing 4.1.4 to test now. /me p[rays for no boot looping.
[EVO 4G Android Development] netarchy:
If you get one, you let me know, I've been puttin the smack down on bugs all day ;D
[EVO 4G Android Development] Danielfo:
Testing now
[EVO 4G Android Development] leeoniya:
Just flashed 4.1.4 on Fresh 3.1.0.2. no boot loops before...and still no boot loops :)

btw...not overclocking. what would posses someone to overclock this phone? the battery life is already blah.
[EVO 4G Android Development] thecodemonk:
Downloaded and applied 4.1.4. Any overclock reboots the device for me. On stock speeds (998) it appears to be staying stable though.

Fresh 3.1.0.2
[EVO 4G Android Development] SteelH:
Yeah, damn thing, making me crazy. I wiped cache/dalvik-cache. Reflash 4.1.4. Phone boots, go to do something on the phone, screen locks and reboots. No OC or anything else. I rebooted phone, let it sit for 3 minutes. Then i turned screen off via power button it rebooted. Not usable at all for me. It reboots itself randomly. Back to 4.0.3.a for now I guess.
[EVO 4G Android Development] jeffsanace:
Have been running 4.0.2 for a while now and I'm pretty happy. Have got scores of up to 42 on linpack and have hit 1500+ on quadrant, and steady 54 fps. I cant seem to update to the newer kernels, they'll flash with a line 5 error and I lose wifi and 4g. I keep reverting back to 4.0.2, but then again I'm pretty happy with it. Any insight as to why the newer versions are not working for me, I'm running your original stock rooted rom with Riptides V5 theme. Have no problems with the setup I have now, but still curious. Thanx in advance for any insight.
[EVO 4G Android Development] THEGAMEPLAY94:
4.1.4 reboots as soon as I try to over clock.
[EVO 4G Android Development] eniamg02:
im going to try this in a few cant wait. thanks netarchy
[EVO 4G Android Development] l33tlinuxh4x0r:
4.1.4 getting reboots on overclock to 1152 never happened before havs.

EDIT: on first boot it crashed but now it is fine so far knock on wood.
[EVO 4G Android Development] fazzmanic:
arghhhhhhhhhhhhhhhhhhhhhhhh i want some netarchy-kernel!
[EVO 4G Android Development] mlin:
Same thing here. Running DamageControl 3.5. I tired uninstalling and reinstalling SetCPU and disabling "Set at Boot" and it makes no difference. Thanks for your hard work Netarchy! Either way I am getting phenomenal battery life with 4.0.3a so I'm very happy.
[EVO 4G Android Development] netarchy:
This happens much longer I'm gonna end up pulling havs and sending it to hell.
[EVO 4G Android Development] l33tlinuxh4x0r:
No we don't want that.
[EVO 4G Android Development] HondaCop:
Don't give up, bro! There are plenty of us who don't have any problems with HAVS and your Kernels.
[EVO 4G Android Development] barnacles10:
Honda what kernel you rockin

N net I'm having no issues with havs. Keep em coming!
[EVO 4G Android Development] Apo11on:
Running Ava-FroyoV3RevA rom. Tried v4.1.4 - phone keeps booting in an endless loop. Did full factory reset again, wiped cache, dalvik cache, reflashed 4.1.4 again - same thing. Going back to 4.0.2 from nandroid backup
[EVO 4G Android Development] HondaCop:
Running Netarchy's 4.1.4 without a problem whatsoever! Using Fresh 3.1.0.2
[EVO 4G Android Development] eniamg02:
Are you setcpu oced?
[EVO 4G Android Development] Apo11on:
I've waited for a kernel, which would allow overclocking beyond 1152mhz for so long, and now that it's out - it doesnt work :confused:

I haven't even attempted the overclock - the phone never fully booted
[EVO 4G Android Development] fr4nk1yn:
Had crazy issues today after undoing 4.1.3 by flashing 4.0.3a over.

Real sluggish couldn't score over 900 on Quadrant even with the Kingwhaterver kernel.

Restored to a clean backup before any kernels and updated to 4.1.4 and scored my normal 1450, at 1.19ghz though. Then went for a 1.22ghz test when it rebooted. Phone reboots just sitting now ):

Restored to my clean backup again.
[EVO 4G Android Development] zone23:
Fresh 3.1.0.2

Revision 4.1.4 - Fresh3 Compatible

As soon as I touch the slider in SetCPU device locks up and reboots.
[EVO 4G Android Development] l33tlinuxh4x0r:
Knocking on wood did not work I have boot loops now. :(
[EVO 4G Android Development] barnacles10:
Saweet. Thank you sir!

I don't oc, so I guess these issues people are experiencing I might not have a chance to experience for myself.
[EVO 4G Android Development] chillware:
Resolved my lockups w/ 4.14!

I went from 4.03a to 4.1.2 today w/o issues. Then went to 4.1.4 just a bit ago and started getting crazy lockups as soon as phone booted or as soon as i tried to do any thing.. several reboots and same issue..

I think I resolved it tho..

I flashed back to 4.03a, opened setcpu and did a phone re-dedect. then I disabled profiles and set the speed back to stock 245/998.

then i again flashed straight back to 4.1.4, no lock up! I opened setcpu and did another re-detect and now I can oc to 1.22 w/o issue. get linpack score of about 38 mflops while at 1.22, any higher of speed and it locks, but i expect that.

Just fixed my setcpu profiles and re-enabled them.. all seems fine so far.

Oh yeah, I haven't done any cache wiping at all during this.. Hope this helps!

EViO 1.1 Rom + Netarchy 4.1.4

Edit: Just hit 1475 Quadrant, sweet! Averaging around 1350's +
[EVO 4G Android Development] Apo11on:
wrong. other and myself reported you dont even get a chance to overclock - phone starts boot looping right after you flash the kernel. You never even get a chance to open SetCPU.

And if you dont overclock - why are you even interested in these kernels?
[EVO 4G Android Development] zone23:
You can still underclock, better battery life and its faster then stock. Its not all about overclocking to everyone. Plus unlock 50+ fps.
[EVO 4G Android Development] Rippley05:
Better performance, bettery battery life... FPS unlock.

You think the only difference in this and stock is overclock?
[EVO 4G Android Development] Jetdr:
4.1.4 is working fine for me on the latest fresh. Setcpu in conservative mode O/Ced to 1113 low set to 245 all seems to be working fine for me.

I did notice if I go to ondemand setting with the same settings the CPU alternates back and forth repeatedly from high to low.

Just what I'm seeing. Ondemand everything seems to be great.
[EVO 4G Android Development] Richkid:
Same here; can't clock over 1152000... Random rebooting even while idling :(
[EVO 4G Android Development] zone23:
I can do 1190 tops
[EVO 4G Android Development] fastamx79:
Right there with ya... I can't go above 1113600 without reboots, FCs, and other strange crap :(

Oh well though.. my main goal was to get better battery life and I've done that without turning this off and that off ;)
[EVO 4G Android Development] l33tlinuxh4x0r:
me too but i get random lockups no matter how far i overclock.
[EVO 4G Android Development] netarchy:
New Revision: 4.1.5

Notes for Revision 4.1.5

- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion

- Clock frequency table remains opened up, with static undervolting in place

- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
[EVO 4G Android Development] NeoDark:
Thanks for the quick fix!
[EVO 4G Android Development] JackDaniels7:
i'm sorry but what is HAVS?
[EVO 4G Android Development] fastamx79:
Oh thank God!!! I have been rebooting over and over as soon as I try to bump it up over stock 1 notch and it is unstable. hopefully this revision fixes it!

Other than that excellent work on these kernels!! :D
[EVO 4G Android Development] l33tlinuxh4x0r:
variable undervolting
[EVO 4G Android Development] netarchy:
It's supposed to be dynamic undervolting, to undervolt a little more efficiently than static undervolting. It didn't want to play nice with overclocking though, so at the moment, it's been canned. I like the idea behind it through, so it's something I'm gonna keep working on as a side project.
[EVO 4G Android Development] cosine83:
Talk to Hero_Over. In his #2 kernel he's managed to balance HAVS, BFS, and minor overclocking (1.14 or so). I'm running it right now overclocked as high as it'll go and it's solid as a rock.
[EVO 4G Android Development] Rene2.5RS:
Now I have more work to do, I have been running bench marks on all the kernels lately and logging the data and when I think I am done there are 3 more to test :( be back in a while with some Linpack and Quadrant results
[EVO 4G Android Development] HondaCop:
Hi netarchy. I hope you don't discard development on HAVs bro. I HAVE 4.1.4 running flawlessly at 1.15 on Fresh 3.1.0.2.

Some people need to understand that undervolting and overclocking just don't play nice together. The more you overclock a cpu, the more voltage its going to need. Those of you that think you can overclock at will AND have the benefit of staying undervolted is simply not going to work.

Net, I think you should continue with developing HAVs because after all, it provides a great balance between battery savings and performance.

- Sent via my EVO from the back seat of your Mommy's car.
[EVO 4G Android Development] SteelH:
Too bad he doesn't have a non-OC kernel. I'd prefer the option to be normal clock or OC it myself via SetCPU instead of built in at 1.14. This is one of the main reason's I always stick with netarchy's kernels.

Just flashed 4.1.5, no touch screen. Froyo deodexed stock, no OC.
[EVO 4G Android Development] Rene2.5RS:
my screen is completely unresponsive with 4.1.5.........

HW 0002

Nova panel

Burnt Droid

I am going to a known working kernel right now and will set setcpu to original frq and try again
[EVO 4G Android Development] netarchy:
Wipe cache and dalvik-cache as well, there's no reason the touchscreen should be as responsive as a corpse ;D
[EVO 4G Android Development] mikevillarroel:
Does the 4.1.5 has what is needed to run wired tether?
[EVO 4G Android Development] netarchy:
Oh I haven't given up on it, I just don't want to keep releasing it in public builds when unexpected issues like this pop up. Next up on the list is merging in bfs anyway, but I'm keeping HAVS as a side project.
[EVO 4G Android Development] SteelH:
I wiped dalvik cache and cache prior to flashing 4.1.5. My touchscreen was a corpse also.