yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Branj812:
Im such a dumbass, i flashed Netarchys Kernel 4.1.9.1 for dc instead of the one for fresh, no wonder why my phone froze and rebooted atleast 40 times today.So now it is running perfectly. Still have 90% battery after i reflashed it 5hrs ago. I have tried the other top kernels with fresh but they all seem to be buggy on my phone
[EVO 4G Android Development] ZEDEK:
Is SetCPU and/or Proiles needed with this kernel?

Peace All,

Ever since the new OTA update my battery has gone downhill---no matter what kernel I use. Coming from Kings#8, I was informed that SetCPU could be used (only main page) with NO profiles. I wanted to know if this is the same case w/ 4.1.9.1 BFS (my phone seems to like BFS) which according to Net has HAVS

any assistance would be greatly appreciated
[EVO 4G Android Development] DroidGnome:
Strange.. same problem with me.. previously getting approx 20-25hours... now down to 10-12. I've tried a Kings kernel but the device would reboot for no reason about 1 every other hour or so. Back to stock kernel and no issues.

Whenever I tried SetCPU on either kernel.. the entire device slowed to a crawl... thinking maybe I should reflash back to an earlier ROM till it's all solved.
[EVO 4G Android Development] kellte2:
I'm having similar issues with battery life after the latest update. Hopefully someone on here will figure something out. I had heard such great things about the battery life on the upcoming update before it officially dropped.
[EVO 4G Android Development] EVOme:
What update....moving it from beta to stable? What else was done? I'm using the old 4.1.9 on BS 1.8 and getting far worse battery than I was on BS 1.7 with it. ARGH!!!!!!!!!!!:mad:

I think I found my problem....I wasnt using the kernel that says "Fresh compatible"...Dammit!
[EVO 4G Android Development] b0ricua:
Hey folks,

Anyone running 4.1.9.1 CFS/BFS on the stock 3.29 ROM that was just released? Let me know if it was compatible/how it went.

Thanks.
[EVO 4G Android Development] 2.0t03speed:
so wait with bs1.8 you have to use the fresh compatible kernel?
[EVO 4G Android Development] sfld:
Im getting screen tearing when i scroll in landscape while browsing a website and im on 1.8... i wonder if this kernel would help
[EVO 4G Android Development] ZEDEK:
*SO.......*

So...is SetCPU profiles necessary w/ HAVS or no?

PEACE

-ZDK-
[EVO 4G Android Development] RTC88:
Yes, it would help. There is no tearing with this kernel like there is in bs kernel 6. Although, I feel the bs kernel is a touch smoother.
[EVO 4G Android Development] mrwilly:
i'm running 4.1.9.1 CFS on the 3.29 ROM with no issues at all. i didn't like the stock kernel with the 3.29 ROM.
[EVO 4G Android Development] b0ricua:
Hmmm for some reason I am getting random reboots with 4.1.9.1 CFS and SteelH's deodexed stock 3.29 ROM. I wiped cache and dalvik cache prior to flashing using amon ra 1.8. Any ideas?

Sent from my Evo 4G
[EVO 4G Android Development] bigupurself7:
SetCPU

Are you guys using SetCPU or just letting it run itself?
[EVO 4G Android Development] mrwilly:
I'm using the odexed version of 3.29 with Amon RA 1.80.

I actually flashed 4.1.9.1 CFS right after flashing the ROM, so it was fresh install of everything from the beginning.

I came from the deodexed 3.29 ROM with stock kernel and definitely noticed a difference using the 4.1.9.1 CFS kernel.

just by itself
[EVO 4G Android Development] netarchy:
And thanks to feedback, here is (yes already) a revision for the 3.6 line:

Revision 3.6.1

Bugfix for the nova panels, please test this without using evo switch first. The intention is to have an fps solution for the nova panel that does not require evo switch. The evo switch support is kept in merely as a fallback in case the main fix does not work at this time.

Thanks for all the feedback!
[EVO 4G Android Development] st0921:
Is there a difference between 3.5.1 and 3.6.1 for Epson screen?
[EVO 4G Android Development] M@XLOL:
~ 30FPS in fpsd stdev 1.95 no evo switch.

14 fps in nena though

edit: running bug. beast with frozen eclair jit
[EVO 4G Android Development] Kongax:
Main I change depending upon what I'm doing, usually I leave it at 998 max / 384 min. Main basically is the default profile if none of the other profiles match the conditions they are assigned to. For example if I'm over 75% battery, not charging, and screen is on, then it will use the Main profile/setting.
[EVO 4G Android Development] Rudementry:
This is very good. Didn't have to mess with evo switch at all. Whatever you did with 3.6.1 its working beautifully.

Also just got 14.3 in Nenamark, my prsonal record. Oh and does this work with froyo?
[EVO 4G Android Development] spiicytuna:
setcpu = performance oc'ed to 1152

I consistently get 56-57 < 5

edit: with gears I get as high as 54 but it isn't consistent
[EVO 4G Android Development] rjmjr69:
I use dotty and touch test. Both register the same both are free on the market.

I get 7.67 mflops???? thats set to 12 too

I can get it to 46fps stdev 0f 5.58 to 6.68 cpu at 1136

Oh snap using the above settings I just got 54 at 12.33??? lol

I can also confirm that the HDMI out does not work. Well the icon appears when you plug the cable in my tv registers there is a device attached the phone acts as if its displaying something but nothing appears on the tv

And as a note I'm using a novak
[EVO 4G Android Development] rjmjr69:
WOW new kernal no evo switch Avg 55 stdev 6.63

but only 3.5 mflops
[EVO 4G Android Development] rmriggin:
Loving this new kernel. Not using evoswitch and getting 50-52 fps. linpack scores are around 18 on average. I now have 3 points of contact showing up in touch test when I used to only get 2. I'm running fresh 0.5.3 with vanilla lock and adw launcher, also I am using the JIT patch. Stable, responsive and smooth! Oh yeah I have 002 hardware and Novatek screen.
[EVO 4G Android Development] catpunt:
Nice! Getting 53 fps at 12 stddev with 3.6.1 and no EvoSwitch. Getting as much as 52 fps with gears, not consistent. Only getting 3 touch points with dotty instead of 5 like before, but I don't care. Great work! Google IO HW 0002 Novatek btw. This is the best I've gotten and camera, wifi and video playback all work! No touch input lag either.
[EVO 4G Android Development] Kongax:
Same here, went from 5pt to 3pt going from 3.5 to 3.5.1, gonna try 3.6.1 and see what happens.
[EVO 4G Android Development] rjmjr69:
Also lost my wifi and 4g with 3.6.1 going back to 3.6

3.6 restores wifi and 4g
[EVO 4G Android Development] spiicytuna:
with epson or nova?
[EVO 4G Android Development] rjmjr69:
Sorry running nova and damage 3.2.3 HDMI also does not work. But camera does and no lag actually fast as hell. Only 4.2 flops
[EVO 4G Android Development] Kongax:
3.6.1 also has only 3pt instead of 5pt like 3.5 had... but 3.5 had a undervoltage bug? Gonna stick with 3.6.1 for now since i care more about battery than 5pt, but it would be nice to have it back :D
[EVO 4G Android Development] spiicytuna:
The reason for the 3pt touch is because netarchy wanted it to be stable and work for everyone. 5pt touch breaks some ppl
[EVO 4G Android Development] netarchy:
Undervolt bug was fixed in 3.5.1

What I would prefer to do is code in an automatic check in the kernel that will set 5point or 3point automatically depending on the sensor detected in the phone, to avoid having to make separate builds. For now I'm defaulting to 3point because it's stable and everyone should be able to benefit.
[EVO 4G Android Development] Krandor311:
Figured I'd give 3.6.1 a test on my Epson phone, performance definitely tales a big hit compared to previous versions.

Props on the "universal" kernel though, flashing back to a previous version for now.

Edit: also see it broke my WiFi.
[EVO 4G Android Development] netarchy:
This should be fixed with 3.6.2
[EVO 4G Android Development] persibro:
Just flashed the DC compatible version of 3.6.1 on my 002 EVO. I'm getting 52 FPS average with stdev of 8-10. The only problem I'm getting so far is that my wifi isn't working like some of the others.
[EVO 4G Android Development] Rocklee99:
Last time I used this , it made my phone lag

And does bfs use more battery?
[EVO 4G Android Development] BlueHarford:
which kernel is the kernel that cyanogen is adding to their builds?
[EVO 4G Android Development] jorgeszabo:
No SetCPU here. Running 4.1.9.1 with Fresh 3.3. Great results.
[EVO 4G Android Development] :
some of you should state which version of the 4.1.9.1 ... CFS OR BFS(HAVS)

im using BFS with fresh 3.3 but i think cfs ran better on my phone .. today is day 2 of using bfs ...
[EVO 4G Android Development] mrwilly:
CFS ran better for me compared to BFS
[EVO 4G Android Development] tracyjarchow:
CFS ran better for me too.
[EVO 4G Android Development] sling:
Upgraded to CFS 4.1.9.1 a couple hours ago with Fresh 3.3.

Everything is running smooth smooth to the point its scarring me lol
[EVO 4G Android Development] Branj812:
I am running Fresh 3.3 with netarchy 4.1.9.1 CFS and since i installed it yesterday afternoon i keep getting random reboots every couple hrs. So i wipped all cache,Davlik, and user accounts and reset the phone and flashed everything back but still get the random reboots.
[EVO 4G Android Development] sling:
stupid question but did you make sure you installed 4.1.9 Fresh compatible version
[EVO 4G Android Development] Branj812:
yeah i made sure i did. would it be worth it to try the bfs version or should that not make a difference
[EVO 4G Android Development] sling:
I would flash 4.1.8 cfs run it for a few min then re-flash to 4.1.9 cfs
[EVO 4G Android Development] Rocklee99:
So should I wipe cache and dalvik cache before I flash this 4.1.9.1 cfs?
[EVO 4G Android Development] Branj812:
allright, flashed 4.1.8. ill leave it on there for 30min or so and go to 4.1.9
[EVO 4G Android Development] Branj812:
are there any apps i should'nt be using with this kernel that could give it problems
[EVO 4G Android Development] sling:
Not that I'm aware of
[EVO 4G Android Development] sling:
Its not necessary.
[EVO 4G Android Development] krampus503:
Stability issues with 4.1.9.1

Since installing the new Kernel, my phone has been all sorts of unstable. It reboots multiple times per hour with the BFS kernel and hangs outright randomly with the CFS kernel. I'm using the Fresh version now, after having tried both versions of the kernel previously with DC. When it isn't rebooting, a lot of apps have segfaults resulting in unexpected (note, not 'force closes') terminations. If i'm watching via logcat, i see the stack traces from the programs dying. I'm suspecting that this may be related to the undervolting mojo in the new kernel, since 4.1.8 was perfectly stable. Is there a way to disable this feature in the new kernel or change the parameters to it so that it is less aggressive with the undervolting? I'm wondering if the CPU in my phone happens to be a little less tolerant of the lowered voltages. Oops, it just rebooted again. :)
[EVO 4G Android Development] eniamg02:
Hey net posted this over in calks rom thread.

Dont know what's causing this but after I flash nets kernel estrongs file explorer disappears and I'm unable to re-dl it from market...very strange.ive tested it after a fresh flash and was narrowed down to that.

I even uninstalled before flashing the kernel (re dl after flashing) and still disappears after reboot.
[EVO 4G Android Development] kaediil:
Strange behavior with Fresh 3.3 and this 4.1.9.1 kernel.

I installed this after using the Fresh ROM for a week or so, I installed the 4.1.9.1 bfs kernel. Now I have two problems:

1) Overclock widget and SetCPU both detect only 500MHz as the maximum CPU speed. I can override it, but the default keeps coming up with the wrong speeds.

2) I can't get gmail to properly sync my primary gmail account. It seems to hang or just not sync at all. Going to try and clear cache, and dalvik-cache etc and re flash the kernel to see if that helps.

-frank
[EVO 4G Android Development] TorxT3D:
cant wait until an official compatible netarchy kernel for fresh 3.3 is out.
[EVO 4G Android Development] Branj812:
I decided to stay on 4.1.8.1, the one thing i notice on either 4.1.8 or 4.1.9 is if i have setcpu installed it would freeze up and do the reboots. I uninstalled setcpu and have not had a reboot in the last fews hrs. I havent tried flashing back to 4.1.9 and dont think i will since as of right now 4.1.8 seems to be working for me with no problems so far.
[EVO 4G Android Development] freeza:
?? I'm using 4.1.9.1 cfs on fresh 3.3 just fine.
[EVO 4G Android Development] kaediil:
Yeah, for some reason I am not 100%. Reflashing the kernel fixed the gmail synching problem. It did not fix the issue I m having with setCPU and overclocking widget not detecting the right frequencies. At least it seems stable.

-frank
[EVO 4G Android Development] flying_low:
ran a little test today to compare 4.1.9 vs. 4.0.2 on my Evo running Fresh 3.3.0.1 *(also using setCPU to overclock up to 1.15, "conservative" for 4.1.9 and "on demand" for 4.0.2)

4.1.9 shows slightly higher Quadrant numbers (screenshots below), and Linpack was same for both at 35-38. but 4.0.2 just feels smoother when scrolling menus, and 4.1.9 had some ongoing random crash issues.

and i've stopped worrying about battery life, it's been poor on every one of the dozens of rom/kernel combos i've tried. i figure if you're gonna drive a ferrari you're gonna make more trips to the gas pump.

just my $0.02
[EVO 4G Android Development] robpet2:
might have to check out this kernel to see how battery life is.. right now using kings #8 bfs
[EVO 4G Android Development] netarchy:
I've posted a universal build of 4.1.9.1 that uses the anykernel method of installation, and should theoretically work on -any- rom.
[EVO 4G Android Development] xhazyx:
Thanks man, I hope this works.... I was having problems with a couple of roms trying to use your kernel, which is weird cuz I hadn't before.

Anyway, is there any word on the .34 kernel u "mentioned " in ur teaser
[EVO 4G Android Development] netarchy:
Still working on the .34.

I'm actually working on it right now incidentally, slowly making progress. Just tracked down and fixed some annoying usb stuff, the todo list continues ;D
[EVO 4G Android Development] Dan_:
Since flashing 4.1.9.1 cfs, everytime I reboot my evo it sits on the white "HTC evo 4g" screen, NOT the "HTC queietly brilliant screen." I have to pull the battery, only after a battery pull, it boots fine. Tried reflashing the kernel and does the same thing =( On VaelPak 2.2, it did not do this with VaelPak 2.2 with HTC #11 kernel.
[EVO 4G Android Development] xhazyx:
No presure lol... but any idea when there's gonna be a beta? If u need some feedback I can help test before u put anything out. :D
[EVO 4G Android Development] netarchy:
When I'm ready to release a beta ;D

There's still a couple issues I'm wanting to get tracked down before I start making public builds.

That said, my sources are on my github, you're always welcome to make a build from them if you want to try something in the meantime, your mileage may vary ;D
[EVO 4G Android Development] netarchy:
How long do you let it sit on that splash screen before pulling the battery?

First boot on the kernel can take a while, especially if you're on a deodexed rom. You think it's frozen but if you were to 'adb shell cat /proc/kmsg' you might possibly see it's actually doing stuff. I've had first boots that stayed on that splash screen for a couple minutes because it was doing a lot of dexopt work in the background before getting to the splash screen portion of boot.
[EVO 4G Android Development] Dan_:
Pretty sure I let it sit for quite a while, maybe 10ish minutes. The thing is, after the battery pull, it boots pretty quickly into android. Attached image is about 10 minutes on the screen.

Otherwise the kernel is awesome! Battery life is sweet.

edit: nvm its doing it with other kernels too :/

edit2: did a nand restore to HTC 11 and it booted fine with no battery pulls. Flashed 4.1.9.1 bfs and it wouldnt reboot without battery pull. Flashed 4.1.9.1-cfs-havs-universal and it seams to be rebooting fine. Oh well it works, thanks netarchy.
[EVO 4G Android Development] sling:
24 hours no reboots so far with 4.1.9 cfs / Fresh 3.3 combo.

All is running smooth.
[EVO 4G Android Development] cdorrell12000:
I tried installing your kernel (cfs) with myn's rom and got stuck at the 4g screen. I used the latest stable build. Any ideas? When I reinstated kings kernel I was ok.
[EVO 4G Android Development] sw99:
Yesterday i updated to the latest Ota stock rom and then flashes 4.1.9.1 cfs. Everything looked ok except for one thing. It looks like the cache is still using app space (i remebered reading that this kernel moves cache to ram/data). I'm getting low memory alerts when i try to restore my apps. I also use the "memory status" widget that shows my internal app space bouncing up and down a i open and close apps. I tried the 4.1.8 kernel with no change.

Of course I wiped cache and dalvik before each attempt.

Restoring the pre-ota had everything working again as expected. Anyone else have this problem?
[EVO 4G Android Development] tyrnight:
Im running it fine on Myn.. but I also cleared my Cache and Dalvic-Cache
[EVO 4G Android Development] parousia15:
I had the same problem. I installed the beta universal kernel and everything is working fine now.
[EVO 4G Android Development] bwtl1000r:
Ran a 1590 quadrant @1.15ghz. Fastest kernel I have used, but I will need a little battery life from it. We'll see... I am impressed so far.
[EVO 4G Android Development] mjohnson4580:
What does the universal build do?
[EVO 4G Android Development] gotshores:
I'm running the universal CFS on myn's ROM and everything is looking good. haven't had any problems and scored a 1540 on quad OC'd to 1152. Battery has been good too. thanks NA!
[EVO 4G Android Development] netarchy:
What does it do?

Hopefully it installs on -every- rom to spare me needing to make a compatible build for every custom rom out there. ;D

Theoretically it might even work on CM, though I haven't tested that one.
[EVO 4G Android Development] EVOme:
Help me understand your message....I'm running BS 1.8 on Kingz #9....I flash your universal over that...standard wipe cache dalvik batt stat??
[EVO 4G Android Development] Rocklee99:
Was I supposed to wipe cache and dalvikbefore installing ur kernel?
[EVO 4G Android Development] krampus503:
4.1.9.1 Universal

I gave the "Univeral" a try on my phone (with Fresh). It behaved the same as the bfs versions of 4.1.9.1. Boots, but then randomly restarts. It actually seemed like that one was less stable than the 'Fresh Compatible' version. Back to 4.1.8, which is again rock solid (for some values of rock. :P).
[EVO 4G Android Development] kaediil:
I mentioned this previously, but I can't get set cpu or over clock widget to detect any frequencies above 520 on fresh with either cfs or bfs. Does anyone else see this? It worked fine at some point with omj and the beta of 4.1.9.1.

I think there was an update to overclocking widget so that may be the problem. Anyway, does anyone else see this behavior?

-frank
[EVO 4G Android Development] Biofall:
You should always do that, just to be sure.

If you are running a Fresh Rom, use the kernel specified for it. Universal is for things that don't already have a kernel specified for them.

Wipe your dalvik cache and cache, reflash, then see if works. It should.
[EVO 4G Android Development] EVOme:
Is Universal the same as the other 4.1.9 kernel except it works on all roms?
[EVO 4G Android Development] Biofall:
Pretty sure that's answered twice on this page.

So:

Look this way ^^^^^^^^^^^^^^^^^^^^^^^^ for answer

Edit: I see you are just confused. If you don't have a ROM that has it's own specified kernel, the universal is for you. The answer to your q is yes.
[EVO 4G Android Development] tatnai:
seems like netarchy is saying that the new universal build is designed to be able to be used on even the ROMs that he has already built specific kernels for, like fresh and DC. so, I think people with fresh SHOULD test the universal out and see how it rides, unless they don't like rocking the boat.
[EVO 4G Android Development] netarchy:
That is correct, the universal is made to be able to work on all roms.
[EVO 4G Android Development] xlGmanlx:
so your just getting away from ROM specific kernel's ;)
[EVO 4G Android Development] xfusejc:
I installed the latest kernel for the Fresh ROM a few hours ago, and I left my phone to charge since it had run down to less than 5%. I unplugged it after it reached the fully charged mark and started messing around. By messing around, I mean I went online to 1 website, turned on my home WiFi and typed a text message.

Looking at my battery stats right now, it has been 7minutes and 30 seconds since the phone was unplugged, and I am down to 82% in battery. Is this is a first time after charge thing or is it really screwed up?

ETA: allright, it stopped dropping at 82% and it has stayed there since I posted all of 3 minutes ago. I charge my phone with the USB attached to my computer (no wall charger.) Could that Full Battery have been a sort of false positive? It needed to stay plugged for a while longer even though it said it was full? It's completely stopped there at 82%, and now I'm doing more battery forceful things on the phone, and it's still there.

ETA2: Down to 80% now, since last edit, which was 10 minutes ago. I'm actually doing stuff now.

ETA3: It's been 2 hours, and I left it alone for a while. It's down to 72% right now. I'm going to sleep.
[EVO 4G Android Development] shif7i7down:
Not sure about cm but it works on miui.
[EVO 4G Android Development] EVOme:
Hey wiseguy....No it isn't!
[EVO 4G Android Development] :
you could use either the one made for the specified rom - OR the universal .

the universal build is the "new" build to start from now on so that Net doesnt have to make multiple kernels. instead he created a universal in hopes that he can just build from that one instead of making numerous kernels.
[EVO 4G Android Development] :
i would try a batt stat wipe - and then "top off the battery" trick .
[EVO 4G Android Development] xfusejc:
I did the battery stat wipe before I loaded the kernel.

What 'top off the battery' trick?
[EVO 4G Android Development] Rene2.5RS:
While the phone is powered up charge the battery till the light turns green.

Power off the phone unplug and plug back in the light will be orange at this point. When it turns green unplug and plug back in, wait until it turns green and repeat about 10 time total while the phone is off.

Something I usually do is charge until green, reboot into recovery wipe battery stats and then power off and perform the powered down plug in unplug routine 10 times and then boot up after that.
[EVO 4G Android Development] xfusejc:
Well, I've been up and using it for about 4 hours now and it only dropped like 10 percent, so I'm thinking the fast drop to 80% was what I said, a sort of false positive, where it told me it was full but it needed a bit longer to truly charge to the brim.

It's good so far.
[EVO 4G Android Development] TorxT3D:
i need more to vouch for the new universal cfs working on fresh 3.3 before i give in.
[EVO 4G Android Development] sling:
ya me to.

Fresh cfs version is running perfection for me, to yank it out of my device would be a crime.
[EVO 4G Android Development] Compusmurf:
If what you have is perfect, why jack with perfection?

Using this kernel is rolling back to older code PRE pre OTA update.

Do what others are doing and wait for Netarchy to get his hands on the source for the latest OTA and then work his magic. Why mix old code with new code and risk your perfection you have now?
[EVO 4G Android Development] sling:
huh

..........