yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] gleggie:
In my opinion, fastcharge should be removed. I don't use it nor do I ever plan on using it since i almost always charge my phone overnight. Increasing battery drain and heat is also not good for the longevity of the battery. Thanks for all your hard work iHate!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Ohhh forgot to mention that I'm rebranding this baby. Stock+ is going back to it's roots. I'll be starting over with a fresh fork of bone stock aosp. The only changes that will be made to stock+ will be official Linux upstreams and anything that comes straight from Chad. Deluxe will be renamed to Hiro Kernel and that will continue to have all the deluxe options people expect
[HTC Rezound] winston856:
Thanks for all your work :good:

Oh, and I vote fast charge be removed. I don't use it.
[HTC Rezound] hoovnick:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

I use it but don't necessarily have to have it. If you wanna trash it to save space or whatever go for it.
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Vote to keep it and here's why. I use GPS and maps ALLOT and sometimes stream audio at the same time. If I did not have fast charge then the phone would drain even while plugged in. I vote to keep it as one can just not enable it if so desired. The fast charge is one of the things that makes this ROM stand out and desirable in my opinion. Evey one else has fast charge for the most part, but yours does it faster.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Charging Problem was not related to, fast charge. So it stays
[HTC Rezound] RebelShadow:
THANK YOU THANK YOU THANK YOU. :good:
[HTC Rezound] hoovnick:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Cool
[HTC Rezound] QBall45:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Today's test build sent my rez into a tailspin. Was forces to wipe & restore nandriod. No worries though. Keep up the great work!
[HTC Rezound] brenuga:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Yeah, I'm interested to run newer versions of lulz and row, but the latest test in the op kept causing reboots that would get stuck at HTC white screen. It seemed to happen when I overclocked. Was undervolted at -50.

No complaints, just feedback.
[HTC Rezound] maximus20895:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

I don't understand. I thought fast charge only works when plugged in to the computer.
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

USB car charger as well, as long as it is at least 1A out. Mine has 2A output.
[HTC Rezound] mjones73:
Some car chargers aren't configured right either, I have a Belkin 2.1 amp that will only charge at 500mA because it doesn't have the data pins shorted out.

Don't get me started on the POS car dock either, mine has a mind of it's own, sometimes it charges right, sometimes it doesn't so having fast charge in a kernel is a plus.
[HTC Rezound] shrike1978:
Chargers that are made to work with iPhone/iPad have this issue, because Apple devices, at least as of the 3GS I had, wouldn't charge unless the charger was set up as USB, even if it was a high output AC charger.
[HTC Rezound] mjones73:
Yeah I think that's the problem with this one.

It's this one - http://www.belkin.com/us/p/P-F8Z689
[HTC Rezound] brenuga:
On the stock boot that comes with infection 2.2, my max cpu clock speed keeps getting reset to 1566 mhz for both cores. Not sure why because I have kernel turner set up to restore values at boot with an init.d script.

Does deluxe kernel support init.d scripting or is this something I can add on manually?
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Init.d is not kernel specific. It's ram disk specific. Also use on boot completed instead. Init.d from android tuner never worked right for our device, plus the alternative is a little safer to use.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

This is something I've been battling back and fourth with for some time. I didn't release a test kernel last night because I'm performing a massive code clean-up. To be honest I've learned a good bit since I started this, but I'm afraid my current repo has become too dirty. I'm constantly cleaning, and I'm thinking I might start over from scratch.

On a side note I've seen so many issues reported lately, that I decided to run a stock kernel and ROM for a while. Signal issues, heat issues, random slowdowns, system settings not sticking, random reboots,crackling sounds during calls. This all happened on stock cm10.1 with unmodified kernel it comes with. Yesterday my phone got stuck on 1x and when I checked mobile network setting my phone suddenly rebooted, then I got 4g back. Just saying, that some issues being talked about are not kernel related.

Edit: almost forgot to mention, the stock aosp kernel has no video tearing. Well not zero but it is like 99% gone. After some soul searching I discovered that lowering vfs cache pressure(which ALL custom kernels do) causes the tearing. My VM tweaks attempted to make up for the lowered vfs by changing swap and dirty ratio values. Doesn't work well though, so Basically as it is right now you get two choices lag free or near-perfect HD playback.
[HTC Rezound] Purpeltendire:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

The issues with settings not sticking is a ROM related issue, and it came to light with the release of Infected 2.2. There is a plethora of people who are having troubles with everything from keyboards not enabled to toggle data/wifi not sticking. For the record I flashed back to Infected 2.1 and Deluxe+/Hiro and my settings stay perfectly fine.

Sent from my Infected Rezound.
[HTC Rezound] gleggie:
Yea, unfortunately there are a lot of issues with Infection 2.2 currently, but its all good bc Neo is releasing 2.3 sometime this week.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Rebuilding from scratch was actually really painless, a little time consuming though. I'll have a test build for Hiro kernel in a bit. In my tests so far everything is working well :thumbup:

Edit: the updated row scheduler is straight from vanilla cm10.1. Its the most recent change to Chad's kernel.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][PMEM][LINARO]Stock/Deluxe+ oveclock kernel [3/5/13]

Test build in the OP. Birth of Hiro kernel. No boot loops or charging issues. Smooth so far.

This test build probably won't change before release unless you guys find something major during testing. I personally feel this is @ a good spot to start the new Hiro line
[HTC Rezound] QBall45:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

By chance did you fix the proximity sensor issues in this new Hiro test build?
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

Nope. My proximity worked on the 3/9 test but not this one. No big deal as I'm not sure I like that feature anyway.

---------- Post added at 07:05 AM ---------- Previous post was at 07:02 AM ----------

Has something changed in regards to voltages? I used to be able to under volt -75 but this test build will only let me go to -50 in kernel tuner.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

I don't want you going less then -50 so now you can't ;)

As to the proximity sensor I have the fix, just forgot to put it in during building. Good catch :thumbup:
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

@ihwo

Found my issue. Mentioning it to you so you don't go doing the same. Don't try to limit your max clockrate without defining "cal_max" to do the same.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

I might just use perflock boot lock to limit boot frequency and leave the rest uncapped.
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

No I'm not talking boot clock. I'm talking max selective freq.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO]Stock/Hiro oveclock kernel [3/5/13]

I know, but I don't plan on limiting Max frequency. 0x1C changed to 0x22, i had that issue a while ago
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV]Hiro Kernel [3/12/13]

OP updated. Hiro kernel RC1 for those that used the test build, proximity sensor is now fixed.

Before everyone asks, I capped under and over volt to +/- 50. I did this because if you go any lower you could experience random issues with anything from camera to sound quality even screen issues. To avoid me having to hunt down random problems that don't exist I've put the limit in. A kernel with no over clock like Snuzzos kernel can handle lower voltages. 1.8ghz @ -100 undervolt is not going to work for 8/10 phones anyway.
[HTC Rezound] winston856:
Thanks for clarifying about the UV cap, just installed this going to see how it works. :good:
[HTC Rezound] RebelShadow:
This is just my initial impression on the latest RC but it seems to be drilling through my battery. Power usage seems higher acording to battery monitor widget pro using the same settings as all the other kernels (Weatley). Also, the screen off profile doesn't seem to be working as with other kernels I can see power usage in BMWP flatline in sleep but this kernel keeps draining during screen off. I will give it a full day tomorrow to see if it settles but this is just my initial observation.
[HTC Rezound] abby_nitewolf:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Another masterpiece! Running it with Tron 2.0 and it's soooooo smooth. Settings I'm running are 1.83 OC Lionheart with noop I/o
[HTC Rezound] gleggie:
I noticed the same thing. Battery drain seems to be pretty high on Hiro Kernel, although i didn't get this much battery drain in the Hiro Beta
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Let it settle. When installing a new kernel you should boot it once, then let it settle till the initial lag seems to subside. Then reboot again. At this point you should be good to go, but another day of settling is probably in order before you start testing battery life. I've run the stock kernel for a little bit and i can tell you the battery drainage is better then stock at least.
[HTC Rezound] highdro:
I was waiting until my battery drained all the way before I flashed the new release and I got 19hrs 28mins with around an hour and a half screen on time with the max oc on lulzactive so I'd say the battery life is just fine. On the first test build anyway.
[HTC Rezound] dplane:
Running very smooth thus far. Too early to give a definite opinion on batt life but seems on par w before thus far.. And thats great! Lulzactive w row and - 25 on the voltage. Had some 3hr screen on days on stock battery on your single last beta before hiro. Hadnt seen that type of battery life since the ics days. :)
[HTC Rezound] ChrisFa5:
Nice update, having a three year old son this is what I thought about when I saw what you renamed your kernel.
[HTC Rezound] manchucka:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Careful, friend. That's a lithium ion battery you've got there. Doesn't take kindly to full discharges.
[HTC Rezound] king.james:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Great work, the kernel is working beautifully. A+
[HTC Rezound] chupajr:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Gah, me too! The fact that I thought of that before Heroes made me shed a tear.
[HTC Rezound] brenuga:
I flashed the new Hiro RC1 today and have had an issue. It may be because I haven't let it settle, or because my battery was below 50 percent, but overclocking both cores to 1836 mhz and undervolting -50 didn't work on my phone. Kept rebooting for minor actions like pulling down the notification bar or unlocking phone.

So I've re-flashed and am going to just run stock settings with Hiro for a bit to see if stability is good, then try modifying stuff in KT. on the version of Deluxe that shipped with infection 2.3, I was able to run both cores at 1674 and -75 undervolting without any reboots what so ever, so I know my phone can OC.
[HTC Rezound] gleggie:
I had this same exact issue last night, got some instabilities when playing around with clock speeds while -50. I let the kernel sit more tonight. I just pulled battery and rebooted and then changed settings in Kernel Tuner, but i'm scared to experiment more, so im keeping at 1500 or lower for now. Don;t want to accidentally brick my phone lol. Maybe i'll reflash the kernel tonight and let it sit overnight
[HTC Rezound] layneja:
No problem here so far. Smooth as a baby's bottom.

Great job !!!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Let it settle. And as for undervolting, I only left it in because its a popular feature. Undervolt is worse for your CPU then over clocking is. I wouldn't suggest anyone run Undervolted AND overclocked. Especially while testing for stability. If you are battery focused just under clock. If you over clock try not to Undervolt. I've been looking into battery drainage while phone is asleep and here's the past four hours for me on default setting.

Used the phone for about an hour and then battery didn't drop at all in the three hours that followed
[HTC Rezound] greensky23:
Just a heads-up for anyone that may run into a similar issue: make sure to place the .zip on the root of your SD card. I mistakenly and stupidly placed it in ext_sd and tried to figure out a few times why it wasn't working. D'oh.

Thanks for the great kernel. Loving it on stock so far.
[HTC Rezound] mjones73:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

My battery life is doing well on the latest kernel, phone has been idle for 11+hours on the extended battery, sitting at 93 percent.
[HTC Rezound] gleggie:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Thanks, yea I figured I just had to let it settle overnight. Thanks for the info about OC and UV didn't know that before. After a night of letting the kernel sit, I let it go through a full run today.

Stock battery, about 1 hour screen on. Pretty decent battery life if I may say so myself. Gonna experiment with more screen on time tommorow

Btw, 1080/1512 MHz, Lulzactive both cores, -50 UV
[HTC Rezound] Snuzzo:
@iHWO

New Linaro toolchain got pushed yesterday if you want it. Already pre-patched for kernel building :)

https://github.com/VigorCM9/linaro/tree/13.02
[HTC Rezound] bacon612:
I still cant get my gps to work using this kernel. Ive flashed it and in GPS settings, i cant get the "GPS satellites" box to stay checked. I check it, leave the screen, come back and its unchecked. Ive tried wiping cache and davlik and even fixing permissions. Once I flash back to snuzzos 2.8, my gps comes back. Weird. Anyone else?

Edit : I am running infection 2.2
[HTC Rezound] Snuzzo:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

@bacon

I don't have a corrected base for v2.8 yet. If its working for you then cool. As soon as you get really bad lag or any other problems please revert to 2.7.
[HTC Rezound] ssb13:
The only GPS issue I have been having is sometimes it will not come on, although checked in location settings. A reboot fixes it. I am on the 3/10 build of CM10.1 from 'Stang. I am using Luz on both cores and SIO. it is not an all the time problem however.
[HTC Rezound] bacon612:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Snuz, I was actually talking about hiro withe the GPS issues. I tried it last night and it borked my GPS. Upon switching back to 2.8 (which I was using before I tried hiro), my GPS came back.

Edit: toggled GPS a few times and rebooted a few times. GPS now working. Really odd. Thanks guys. Let's see how these under volts and overclocks work out now.... :D
[HTC Rezound] RebelShadow:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Infection 2.2 has known issues with system settings not sticking. Try to reset permissions in recovery or wait until Friday for 2.3
[HTC Rezound] bik2101:
my gps has been working fine. also on infection 2.2

are you undervolted at all?
[HTC Rezound] bacon612:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

No undervolt. Didn't touch any voltages on either kernel. Using lulzactive and row

EDIT: Working now. See above.
[HTC Rezound] brenuga:
There are two things I think people need to be aware of with Hiro.

I found out the hard way that yes, you need to let the kernel settle at default values before attempting to overclock. I set both cores to 1836 at -50 undervolting and was very unstable.

Re-flashing over Neo's infection 2.3 beta, things were a lot more stable, was finding that I could run both cores at 1674 at -50 with no apparent issues.

But then I started fooling around changing the lulzactive-specific governor settings, and I think I got too carried away tweaking multiple settings toward battery life at once. That also led to random reboots which caused bootlooping.

I don't say these things as if there's some sort of defect with the kernel, bc there's not, but you definitely have to take a lot more care when overclocking and have access to a boot.img or nandroid backup to rescue you from bootlooping.

In about two days' time, I also have become an expert in the partial sdcard insertion trick to fix the problem you get where you are bootlooped but can't get into recovery/fastboot because the PH98IMG.zip is still on the sdcard. You basically slide the sdcard out where it is almost falling out, hold the battery at an angle so it is touching the contacts but you can still flick the sdcard back in with your finger.

With sdcard slid partially out and battery touching, press power and volume down to start phone. It will launch bootloader and give you a chance to start recovery. Press Power to launch recovery, then as it's booting, use your finger to push the sdcard back in and lay the battery down flat in its normal position. Then in recovery, you can go to Developer Options and remove the PH98IMG and then re-flash your boot.img. You need to confirm that your boot partition is booting before you re-flash kernel. Hope this helps someone.
[HTC Rezound] mjones73:
I believe it's recommended you don't undervolt if you're gonna overclock also...
[HTC Rezound] gleggie:
Haven't tried the SD Card trick, but what i do is I just use adb reboot recovery
[HTC Rezound] mjones73:
It works great if you're stuck and you don't have access to a PC.
[HTC Rezound] eriscentro:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

USB micro SD card readers are well worth the 90 cents I paid for mine :)
[HTC Rezound] manchucka:
Fastcharge and cpu 1 revert settings upon reboot

I find that fastcharge status (which I usually have off) reverts to on, and cpu 1 reverts to ondemand after each boot. Is this typical? CM 10.1 3/10 build. Latest HIRO.
[HTC Rezound] mjones73:
What app are you using to control the kernel?

---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------

Yes, still doesn't help if you have a PC handy when you mess up your phone. :D
[HTC Rezound] manchucka:
Latest version of Kernel Tuner from Play Store
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

That's weird because the default governor is interactive not on demand.
[HTC Rezound] xXezmacXx:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I'm new to kernels and this seems overwhelming. Is there a guide or tut explaining what each option does, what governors, are etc? A kernel 101... I have no idea what app to use to control the kernel and what settings to put it on. I hear that this kernel has improved the video tearing prob for some.
[HTC Rezound] replica9000:
http://xdaforums.com/showthread.php?t=1369817
[HTC Rezound] replica9000:
Actually instead of limiting each frequency to -50mv, you have actually limited each frequency to a minimum of 750mv :p
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

:cool:
[HTC Rezound] replica9000:
Didn't know if that was intended or not. I set my max to 810mhz, so voltage on anything above that doesn't matter. Next reboot those will return to normal.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I apologize for the lack of test builds, but I've taken a three day break. I resume tomorrow with some sweep to wake testing. if I can get snuzzo to share, maybe some TCP congestion stuff too.
[HTC Rezound] platinumrims:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

So should I update Neo's tron umbrella rom with this? Or not mess with it?
[HTC Rezound] gunzup3:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Great job on this kernel, I got over a day n still at 15% battery using intellidemand both cores, io set in noop, over clocked to 1674. Under volted just a tad. Thumbs up :thumbup:
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Test build in the OP
[HTC Rezound] ssb13:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I am down (loading) to try it.

First 5 minutes are great. Actually made update: made it through a video on the gallery which is nice.

Seems smoother, crisper, snappier.

Love your work.
[HTC Rezound] xXezmacXx:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Can someone give me some settings to use for CPU master?
[HTC Rezound] Snuzzo:
Tried it just breifly. It sucks.....

Jk man. Keep up the awesome work! :good:
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

http://xdaforums.com/showthread.php?t=1989824
[HTC Rezound] mjones73:
Can we disable S2W on the test build?
[HTC Rezound] manchucka:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Yes. Turn it off under "Misc" in Kernel Tuner.
[HTC Rezound] mjones73:
I stopped using it due to the fact you can't set certain governors correctly with it.

I would assume I can flag it off using an init.d script then, thanks. :)
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Big thanks to the people that answer questions! One less thing for me to worry about :thumbup:
[HTC Rezound] Snuzzo:
Android Tuner now has s2w support.

EDIT:

Now if only AT can support TCP congestion control selection.

@iHWO

Take a peak.

https://github.com/Snuzzo/funky_kernel/commit/5307fe2a8389b94dfc49986788cc5d8e7e0b4f97

All of the TCPCC drivers are in our source, just not enabled for build.
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I noticed that yesterday!
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Isn't KT open source? Maybe I'll add TCP control myself.
[HTC Rezound] drynyks:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Been using #1 since release. Working perfect so far. Thanks
[HTC Rezound] iHateWebOS:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Another test build out. Just check frequently I don't want to announce everyday.
[HTC Rezound] Tidewater:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

Damn man, you are a kernel making machine. Every one of these has been greatness. I know other people have been complaining about battery drain and various other issues but I have had none of that. Thank you sir.

Sent from my zombi-fied rezound thanks to Neo
[HTC Rezound] Dogbone737:
Re: [Kernel][AOSP][LINARO][OC/UV] HIRO Kernel [3/12/13]

I just switched to the test build released on the 18th and everything seems much smoother and snappier than your default kernel that was baked into infection 2.2 (I forget which one was default but I know it was yours) it almost feels like a fresh install of a Rom it's so smooth. Keep up the awesome kernel work!