yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Compusmurf:
Ok, If you're using Fresh 3.3 or 3.3.0.1, it has a newer kernel from HTC than 4.1.9.1 for which the source code isn't available yet.

If you're using any earlier Fresh 3.x version, you can use 4.1.9.1 because it's the same base kernel.

Sorry I didn't make myself clear.

However, folks are using 4.1.9.1 on 3.3 successfully, but then you're not getting any other bug fixes that HTC added in. Some folks that have tried have issues too. Me, I'm waiting until Netarchy gets the source for the updated kernel, adds in his goodies that way I have the correct matching kernel to the correct OS version.
[EVO 4G Android Development] netarchy:
Erm, the only "bug fix" they'd be missing with the different kernel is whatever changes HTC made with the battery stuff. Further, even without HTC's mystery changes, the kernel base is still 2.6.32, PLUS the kernel exists outside of the rom revision, there is no "matching" of kernel versions to the "correct" OS version. It doesn't work like that.

The kernel is a separate entity from the rest of the rom.
[EVO 4G Android Development] EVOme:
Hey Netarchy...welcome me back...I had to leave the Kings kernels and come back to you. Your 4.1.9 gives me the best batt life.

He just started using some Ext 4 code or some ****...what's that all about?
[EVO 4G Android Development] xlGmanlx:
dude, you should he great full that he might take you back. haha seriously though, looking forward to your. 34 kernel can do
[EVO 4G Android Development] robpet2:
quick question....

performance wise what are the differences between the cfs and bfs version of the latest kernel on fresh 3.3 ????

positives vs negatives ????
[EVO 4G Android Development] sling:
Ive never used bfs but can tell you that cfs version rocks.

Battery life is amazing , fps unlocked smooth performance 5 star for me
[EVO 4G Android Development] robpet2:
test the universal right now... might do the fresh compatible cfs in a few
[EVO 4G Android Development] netarchy:
A preview of netarchy-toastmod-5.0 has been posted for those of you that like to play on the bleeding edge. ;D
[EVO 4G Android Development] fastamx79:
schwing!! :D
[EVO 4G Android Development] PeoplesHelper:
Downloading.......:D
[EVO 4G Android Development] xhazyx:
Thanks man!... been waiting for this for a while, finally i dont have to lose anymore sleep at night. lol:cool:
[EVO 4G Android Development] Androidious:
All ya need is the boot.img from the stock Rom and u can flash it in adb by typing 'adb flash_image boot /sdcard/boot.img' or where ever the path is to the boot img. Just an alternative to having a flashable zip.
[EVO 4G Android Development] :
what did you do to "fix" the issue
[EVO 4G Android Development] wrich73:
quick question about streaming audio...

I'm running Fresh 3.3 and just updated my kernel to 4.1.9.1---is there a difference in the streaming quality between the 3.3 stock and 4.1.9.1? Which code is "better"?
[EVO 4G Android Development] xfusejc:
Nothing. Im still running the phone uncharged since I posted, now around 30%. I'm assuming the phone told me it was charged fully while the kernel needed more time.

The battery life beyond the 20% drop has been outstanding. Going almost on a day and a half and still not even at 20%.
[EVO 4G Android Development] kf2m:
Noted on 5.0.

Running SteelH RevG, and after loading up 5.0 (full wipe) I've noticed the screen getting distorted on the very top, and bottom of the screen. Went back to 4.1.9.1 and everything is fine.
[EVO 4G Android Development] psychopsilocin:
The 5.0 kernal works great on cm6 but with one exception. After a call ends, my phone goes blank and a battery pull is required.
[EVO 4G Android Development] sling:
Same here on screen distortion I returned back to 4.1.9 as well
[EVO 4G Android Development] bjevers:
Feedback on v5 preview.

Running EViO v1.31 with hardware 002 and Novatec panel; phone boots fine but touchscreen does not respond. Had to flash back to previous kernel.
[EVO 4G Android Development] fastamx79:
Netarchy did mention that there are graphical issues with this on sense roms according to the first post of this thread where you downloaded the kernel

But I had to go back to the last version due to massive amounts of random reboots (also using Steel's RevG deodex ROM)

edit--

But when my phone wasn't rebooting it was running very nicely! (graphic glitches aside)
[EVO 4G Android Development] d0cx:
seems to be working quite well on SteelROM RevG. using 4.1.9.1 CFS.
[EVO 4G Android Development] bigant262:
You can use these kernels with CM now?
[EVO 4G Android Development] netarchy:
The universal probably works with CM.
[EVO 4G Android Development] Swede2008:
Hardware 003 w/ Epson and VirusROM v3: Flashed v5.0 over stock kernel from OTA 3.29. Some random graphical errors throughout screen, but esp at top (the battery icon was always having glitches through it), but nice performance. 54 avg fps with stdev at 2.82 :D Overclocking worked fine for the short period I used it. Switching back to 4.1.9.1 CFS Fresh Compatable b/c of the graphical errors. Good work though netarchy! ;)

Edit: To give some perspective: The fps2d results above were with stock cpu speed (998). Overclocked to 1228 on 4.1.9.1 I get 54 avg fps with stdev at 5.54 (which I've read a lower stdev is more important than a higher fps avg).
[EVO 4G Android Development] NetEndeavors:
Tried the new preview 5 and "tastes good" with a shot of Texas Pete!

Gotta go back, cause it appears that every time my screen goes "to sleep", my phone restarts...

Lookin' forward to Beta 5.x
[EVO 4G Android Development] ameetmedi:
Setcpu States?

HI, I just flashed the Universal 4.1.9.1 kernel and it seems to be running great with Myn's new ROM. I did however notice that on my Info tab in SetCPU, it says Time in State :Null.. Shouldn't I be seeing the time spent in different states as i see in other kernels? I can clearly see that Setcpu is adjusting the states but seems i am not recording any of that historical information with this kernel. I just flashed from Kings CFS9 and CFS10 and i was seeing all that information.

Thanks

AM
[EVO 4G Android Development] justinisyoung:
i know that HTC sense roms handle touch inputs much differently than AOSP roms, like cyanogenmod, but do the universal kernels support both? or one? or did htc finally implement the aosp input range?
[EVO 4G Android Development] netarchy:
Universal supports both.
[EVO 4G Android Development] netarchy:
That'd be because the stats are disabled in the kernel config. I can always re-enable them in future builds if people really want to see em.
[EVO 4G Android Development] bigj225:
Yes if you wouldnt mind please do.... I always use that to see if my phone is actually sleeping, by looking at the total number counts it spends in 245 mhz
[EVO 4G Android Development] sturmen:
I tried 5.0 today and it seems to cause reboots/shutdowns when my phone is sleeping, so I'm switching back to stock. Seems promising, though; I'm looking forward to future versions.
[EVO 4G Android Development] xlGmanlx:
bump, how did this thread get so far back?
[EVO 4G Android Development] EVOme:
What's going on....any updates?
[EVO 4G Android Development] igotsthemagicinme:
the first oc kernel that WORKS for me. i guess i should have picked the one where the developer actually owns an evo lol.

making fresh silky smooth. thanks :)
[EVO 4G Android Development] HondaCop:
Quick question, if I want to install this kernel on Myn's ROM, do I need to flash the universal or can I simply flash the regular toast kernel? I ask because toast mentions this:

"The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel."

I already have zipalign on boot and the dalvik tweak setup correctly and was wondering if I flash the universal kernel, if then they will be disabled and not work.
[EVO 4G Android Development] netarchy:
I should probably clarify the universal build a bit. It uses the Anykernel method of installing a kernel. Basically it takes the ramdisk being used by whatever kernel is currently on your phone and combines it with the new kernel image to make a completely compatible boot image for your phone with the new kernel. This means that any custom inits (such as the stuff necessary for the dalvik tweak and zipalign check to work) that are in your current boot image are retained when the universal is flashed.

In other words, if you already have the dalvik tweak/zip align check scripts set up, you won't lose them, but if you were to flash the universal on a phone that was running a pure stock kernel, it won't *add* them in.
[EVO 4G Android Development] HondaCop:
Clear enough, my friend. Thanks! BTW, I guess I should use the Universal build instead of the regular build if flashing on Myn's ROM?
[EVO 4G Android Development] snandlal:
Uncle jimbaland??
[EVO 4G Android Development] crstfr:
loving the new HAVS.. i'm running the 4.1.9 with havs universal over fresh 3.3... using riptides clear froyov8 theme, and overclocked to 1226....

like i read in a previous post, I'm getting quick battery drain till about 80.. then creeps... so the first 20 % is a faster drain then the last 80..wild... ..i wiped battery stats before i flashed all the new roms and kernals....im now about to do the full charge, clear stats, let drain, recharge.....

but im really love fresh and toast!...

crstfr
[EVO 4G Android Development] mayfly82:
Sorry for being a noob but what are the advantages of using this? I used 4.1.9 on my old evo and it lacked a 8mp camera, before it was stolen. I got a new one with all the updates and am just curious as to why i should use this kernal.
[EVO 4G Android Development] pbarrett:
Hmm - Tried 4.1.9.1 over my stock rooted 3.29.651.5.

It came up and ran for about a minute, then rebooted. All subsequent boot attempts don't even get that far before they restart.

Using the latest Amon-ra, and wiped the caches twice as usual.

If you're interested in seeing a log, lemme know what you want me to capture.
[EVO 4G Android Development] R32_Rocky:
For Fresh 3.3.01, which might work best then? The Fresh specific kernel, or the universal one?
[EVO 4G Android Development] igotsthemagicinme:
this kernel kicks ass dude

king got pwned
[EVO 4G Android Development] fr4nk1yn:
Just cooked my new ROM and tried King, scored 100 point more on Quadrant at 1.19 than the stock kernel.

Gonna give 5.0x a go now! (:
[EVO 4G Android Development] :
Awesome kernel!!! Except for the random reboot at the wee hours of the morning for some reason. Usually im guessing around 4 a.m.
[EVO 4G Android Development] netarchy:
Two things:

1. adb logcat

2. adb shell cat /proc/kmsg

You can actually fire those up during the boot animation (technically you can probably fire it up after it's been on splash for a few seconds, but it's hit and miss since things are still initializing).
[EVO 4G Android Development] netarchy:
Which kernel?
[EVO 4G Android Development] :
The only ones i have tried so far and its happened to both is 4.1.9 universal and 4.1.9 DC.
[EVO 4G Android Development] wfrandy:
I am using the universal one now and it is working great.
[EVO 4G Android Development] frickinjerms:
Hey netarchy I've flashed over the 4.1.9.1-cfs fresh compatible running fresh evo 3.3.0.1 and everything was fine for like 6 hours them bam random reboots while the phone slept, not while I was messing with it though... I wiped my cache and davlik then flashed the zip... I also had setcpu overclocked at 1152 mhz and underclocked at 245 mhz conservative with no profiles enabled... I also use auto killer set to strict, but I don't see how that could cause a random reboot... Should I try the universal instead? Any recommendations would be great cuz I was really happy with your work and my awesome quadrant scores haha
[EVO 4G Android Development] :
Edit: rebooted on me twice today. Maybe its my phone. Trying a different kerenl now to see whats up. I was on DC version of 4.1.9.1
[EVO 4G Android Development] EVOme:
5.0 will not allow my phone to boot. hangs on Evo white screen.
[EVO 4G Android Development] netarchy:
5 is a preview that is pretty much guaranteed to have issues atm ;D

I'm hoping to have time to put out a newer preview build during the weekend
[EVO 4G Android Development] :
Just flashed 4.1.8.1 cfs this morning and first boot got stuck at whitebhtc evo screen for 8 min. til i pulled the battery andbrebooted the phone. All seems good now and trying to drain the battery to do a power cycle but......the battery wont die!! Excellent work!
[EVO 4G Android Development] wmdunn:
Looking forward to it ... 4.1.9.1-cfs has been great.
[EVO 4G Android Development] xhazyx:
This 5.0 preview is very promising, can't wait for the next one... this .34 kernel shows some great performance, I'm just waiting to see fully functioning versions roll out. It'll be like Xmas
[EVO 4G Android Development] T Mac:
Now that damage control roms are now back in production, does the current 4.1.9.1 kernel for damage control still work and since there is a new 3.6 beta rom, will it work on that?
[EVO 4G Android Development] xlGmanlx:
probably a tough question to answer since that new ROM is or isn't in beta status and has or hasn't been built out yet. But my two cents ( yeah, i know its worth nothing) is that Net is moving away and rightfully so to ROM specific kernel's at this point, so i would surmise that yes, it would work with it ;)
[EVO 4G Android Development] :
Ok well i guess maybe im doing something wrong. First off im running one of the most incredible roms... Virus RC3. I ran 4.1.9.1 both universal and dc and random reboots. Then rlashed 4.1.8 cfs and it got stuck at white htc evo screen. Did a battery pull to reboot it and all was fine til it froze after another reboot. These kernels are fricken sweet, only wish i can use them. I also ran warm twopointtwo and it never made it past the white acreen. Am i diing something wrong.
[EVO 4G Android Development] randymac88:
Hey Netarchy, quick question, totally out of curiousity. I always thought that we needed the source code in order to really dig in and stabilize these ROMs/kernels. Yet, I see all of these ROMs/Kernels out there based on the latest OTA this and 3.29 that, and I don't get it...that source hasn't been released, right?

What I'm trying to figure out is, are we better off waiting to flash versions of kernels/ROMs that are based on the latest version, once the source has been posted? Or is there any real difference between what developers have access to right now vs. what they have when the source is out there?

Just curious...thanks in advance and I've been a loyal and longtime fan of your work. Thank you!
[EVO 4G Android Development] dthomas03:
Funny...because I have the same issue. Flashed 4.1.8 CFS and it always gets stuck on the HTC EVO white screen. Have to do a battery pull to reset it and then everything is fine...

Ahhh SeNSeleSS ---- VIrUS RoM
[EVO 4G Android Development] netarchy:
The rom and the kernel are separate components.

Think of the rom as the main files of the OS (which it is), it's android, it's sense, it's the base system files for the OS.

The kernel is the part that handles all the input/output that goes through the OS, it's separate from the rest of the software and can be modified/changed separate from the rest of the rom release.

The rom is the car, the kernel is the engine. You can replace the engine, you can modify the engine, and the rest of the car isn't gonna ***** about it as long as everything hooks up and runs.

That said, the stock kernel in the official 3.29 ota is still a 2.6.32 base, it just has some modifications we don't know the nature of at the moment because the modified sources haven't been made available.

Also bear in mind that "3.29.x" is HTC's version scheme. They decide to refer to the release as a whole as 3.29.x. In reality it's really Android 2.2 (Froyo) + Sense UI + a 2.6.32 kernel.
[EVO 4G Android Development] robpet2:
been running 4.1.9.1-cfs fresh compatible and its been smooth like butter.. no reboots , no slowdowns.. good work...
[EVO 4G Android Development] netarchy:
I've posted a second build of the universally compatible 4.1.9.1 kernel that has less aggressive undervolting to address the people whose phones seem to be really picky about how far they can handle undervolting.

If you've been getting random reboots or bootlooping, give it a shot.
[EVO 4G Android Development] wvcachi:
Love the 5.0 preview - that's gonna be really smooth when it's final.
[EVO 4G Android Development] TorxT3D:
LOVE this explanation. cheers to netarchy!!
[EVO 4G Android Development] :
Just flashed and worked right away. Will see how my phone reacts to this and report back. :)
[EVO 4G Android Development] dezel29:
flashed the 5.0 and man was it fast...great scores across the board...no problems that i could find except i kept getting little screen tears all over the place...like little graphical errors...kinda hard to explain...that was the only thing i expierenced while running it...looking forward to test driving again when its ready...ty
[EVO 4G Android Development] edboston:
Is there a list somewhere of what clock frequencies use what voltage? I saw one in the past and used it for setting up my SetCPU profiles but not sure if the change points are still the same.
[EVO 4G Android Development] randymac88:
Thanks for the explanation, Net. So basically, it sounds like kernel-wise, since its really the same source, we just don't know what mods HTC has applied to it (and we'll be very interested in finding out how the approached the FPS unlock). I don't totally understand how people are claiming that their ROMs are based on the 3.29 OTA base though, but i'll take your word for it! Really appreciate the info.

Question - any interest in working on a FPS-optimized kernel that disables HDMI, that could push closer to or hit 60fps? I never use the HDMI (and I would suspect many others don't as well) and knowing the difference between 49/50 fps and 53/54fps, getting to 60fps might provide a similar improvement in feel. I don't know what's possible though. I suppose as a general rule, you might want to build towards having everything working as opposed to just fully disabling or ignoring a phone's feature. Anyway just a thought, much appreciated for all your work on these Kernels.
[EVO 4G Android Development] netarchy:
5.0 Preview 2 has been posted for you gutsy bleeding edgers that don't mind playing with buggy stuff ;D

Now with 100% more not shutting down when the screen turns off! ;D

EDIT: ok it would appear I spoke a tad too soon there ;D that damned sleep bug is still lurking somewhere, and it's going to die a horrible horrible death when I get my hands on it!
[EVO 4G Android Development] wvcachi:
Seems like maybe the graphical glitches are slightly less in the 2nd preview. I'm gonna stick with rock-solid 4.1.9.1 while 5 is still in previews, but thanks for giving us an update to play with!
[EVO 4G Android Development] :
Installed easily and no more random reboots!! :)
[EVO 4G Android Development] sudhirkhanger:
Are the stock kernel posted in OP latest kernel from htc?
[EVO 4G Android Development] luckylui:
Hey Net,

Quick question for u, does diff bases affect diff kernels?? Reason why I ask is because on avas rom and myns the base is the 3.29 but no release keys also stock kernel.. Now when I try to flash kings or ur kernel it freezes at the white first boot, ive triied amon ra I use clockwork but neither worked. Another thing is their anothr base that is 3.29 but w release keys and that base is found in calks rom and that base lets me flash kings and ur kernels... Is that weird??
[EVO 4G Android Development] skydeaner:
still gettin some graphical glitches on the preview 2 alpha. It seems more stable than the first though. My excitement can hardly be contained.
[EVO 4G Android Development] wmdunn:
Same here, but moving in the right direction ...
[EVO 4G Android Development] netarchy:
5.0 preview3 posted

The sleep bug has been beaten severely with a baseball bat.

;D
[EVO 4G Android Development] SteelH:
Looking forward to a stable 5. Currently using your 4.1.9.1 950 less undervolt. I have one of those damn pesky phones!
[EVO 4G Android Development] frickinjerms:
I flashed the less aggressive undervolting version of the 4.1.9.1 cfs universal and everything has worked like a charm :) battery eh but that's to be expected and my phone required a battery pull when I tried to overclock to 1.267ghz haha but it is doing just fine at 1.152ghz and no more random reboot whill its sleeping :)
[EVO 4G Android Development] eniamg02:
Hey net I've been using the stable 4.1.9.1 cfs for quite a while everything running smooth.is there any difference,advantage/disadvantage in using universal cfs?or are they pretty much the same? Thanks
[EVO 4G Android Development] freeza:
Okay, so i'm currently on fresh compat 4.1.9.1cfs, If i were to choose to use the aggressive undervolting kernel, could any of the tweaks that were removed be added via build.prop or any other method of manual editing? If not, are those tweaks really noticable as performance enhancers enough to stay with the fresh compatible 4.1.9.1cfs?

What does dalvik tweak do?
[EVO 4G Android Development] netarchy:
if you were to move from the fresh compat build to the universal you wouldn't lose the tweaks because the universal would be re-using the existing ramdisk from the previous boot image and just replacing the kernel.

As for re-adding them later it would require a ramdisk edit as the tweaks are made to be run during init.

The dalvik tweak basically makes dalvik-cache use the /cache partition instead of the /data partition. This results in having around 80 megs more space on /data for apps (not that most people are necessarily even close to maxing out their data partitions but still).

On an unrooted phone, /cache is normally used for things like storage for downloading OTA updates. Since rooted users don't accept OTA's (unless they like losing root ;D) it goes largely unused (wasting about 160megs of usable space).

Performance wise you probably won't see any difference with the dalvik tweak, it's really a storage space thing.

The zipalign script basically has zipalign check all the apps on the phone during startup to make sure they're all zipaligned (and if they aren't, it zipaligns them). Zipaligned apps tend to load faster.

The script basically saves you the trouble of running zipalign manually if you're so inclined. It's not essential, but it can have a bit of a boost *if* the app in question was previously not zipaligned. Most, if not all custom roms are already zipaligned from the get go, and it's only apps that are added later that may possibly be in need of a zipalign pass for optimization.
[EVO 4G Android Development] JZR:
I loaded up 5.0p3, and it was very fast and seemed stable. Only minor graphical glitches. I let my battery run out, and when I went to restart the phone it got stuck on the white 4G screen. I pulled the battery and tried again, with the same result. I tried restoring a NAND backup, but it wouldn't restore (first time I've had that happen). I ended up wiping cache and dalvik, and was able to get it to boot.
[EVO 4G Android Development] mrwilly:
4.1.9.1 CFS Non Universal has been running smooth and great for me on 3.29 odex ROM. Battery life on this kernel has been excellent too. With moderate usage, texting, and calls here and there, I can go 2 days on a single charge, all with the phone checking a IMAP email account every 30 minutes, checking weather every hour, a Exchange Active Sync account, and 2 Gmail accounts.
[EVO 4G Android Development] Branj812:
Does your 4.1.8.1 fresh build use the davlik tweaks
[EVO 4G Android Development] mjohnson4580:
Net could you make a universal for 4.1.8 please. I would much appreciate if not no big deal. Cause my phone does not like havs at all. And i would like to try out the universal installer.
[EVO 4G Android Development] freeza:
Fantastic :)

Just moved over to the universal kernel.