yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] motorazrv3:
Nearly identical combination. I am still on ext4.

This combo makes the phone really fast.
[Samsung Galaxy Nexus] santi1993:
Its usable as a daily driver?

Sent with love [MENTION=887416]tap[/MENTION]a
[Samsung Galaxy Nexus] Loureiro:
Yes you can rely on this one ;)
[Samsung Galaxy Nexus] büscher:
on pre54_3 since 12 hours. Running fine and also Ingress is a lot smoother than on pre54_2 (but I'm not sure if its only the kernel because also Ingress got an update). The phone still gets warm but not hot like before. Also I didn't see the wifi drops for now, I'm not at home often these days so that has to be confirmed by someone else.

edit: oh yes, the wifi reconnect just happened

<4>[10311.477264] wl_bss_connect_done succeeded with xx:xx:xx:xx:xx
<3>[10321.531890] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
<6>[10321.543395] cfg80211: Calling CRDA for country: CA
<6>[10321.702941] vibrator: value=1, pwmval=127
<6>[10321.724670] vibrator: value=21, pwmval=127
<4>[10324.055816] omap_hsi omap_hsi.0: Missed previous CAWAKE rising edge...
<4>[10325.586761] wl_bss_connect_done succeeded with xx:xx:xx:xx:xx
<6>[10325.600921] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[10325.651794] wl_bss_connect_done succeeded with xx:xx:xx:xx:xx
<4>[10325.753479] Unknown PRIVATE command WLS_BATCHING GET - ignored
<4>[10325.754272] Unknown PRIVATE command WLS_BATCHING STOP - ignored

now changed region code to europe and disabled wifi optimization.
[Samsung Galaxy Nexus] sgspluss:
Can some one tell me if the governor hotplug build in this kernel? Want to try an other kernel as the stock cm one...

Gesendet von meinem Galaxy Nexus

Sorry for the stupid question, just took a look into the kernel sources and found:

So i answer it on myself ;)
[Samsung Galaxy Nexus] RW-1:
Hi all,

Shiny rom for toro.

Has been running great so far pre-54-2, however today I'm getting repeated "Unfortunately email has stopped"

Free ram is at about half, have rebooted, same.

TCP on westwood. Gov is ondemandplus, normally I go to interactive, perhaps that's it?

The only other thing I do in trickster is undervolt MPU by 50 on each.

Anyone have thoughts? Stock Shiny, no mods, been great up to now.

Thanks beforehand.
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION], Here's my take on the heating issue... I can say that there's definitely improvement over the r54_2 but the temperatures are cooler in r53 in the cpu/gpu intensive tasks. Maybe if u can find a sweet spot over performance-temperature in the final release :good:

P.S : Plus the FPS "consistency" is definitely better over the r54_2(higher temperature output relative to fps drop) and r53(It used to slow down the fps overtime on this release) for sure on r54_3, all these are based on the PSP Emulator on my device.

And a big thanks again !!
[Samsung Galaxy Nexus] boype:
Try clearing the app's cache and try again.

I'm pretty sure this is not kernel related
[Samsung Galaxy Nexus] christopherrrg:
Hate to say I didn't read but got slightly confused. I'm on r53 so would I need to revert back to PA stock kernel before I flashed the pre54?

I'm assuming because of being contaminated? Or is dirty flash okay?

Forgot to mention I'm on 4.4.4.
[Samsung Galaxy Nexus] RW-1:
Will do, not saying it was, just reporting what I'm experiencing, should have thought of that myself too, only thing that I've been changing lately is kernel versions, 'cause you're so prolific as of late :laugh:

Just to expand though, the app is functional, I have no issues opening/running/using it, it's a background close message, I have two emails and my exchange account programmed into it at the moment.
[Samsung Galaxy Nexus] 1ce8reaker:
Same here when I play a 3d game. Playing cause overheating. I'm with pre54_3.
[Samsung Galaxy Nexus] aliesz:
I could flash my ROM (stock 4.3) and my kernel returned to stock 3.0.72, and then flashed the anykernel2 version of latest pre-release fancy kernel, but there is boot-loop already. the latest test version seems not working properly maybe on stock ROM.
[Samsung Galaxy Nexus] motorazrv3:
[MENTION=4615478]boype[/MENTION]

Interesting post from osmosis here. Please take a look:

http://xdaforums.com/showthread.php?p=54617417

Unified v2 f2fs/ext4 support allows you to mix-and-match your partition formats however you want!
[Samsung Galaxy Nexus] Ashtrix:
Thats a damn cool feature :good: though, As per my exp the f2fs gains a boost over ext4 in many fields !
[Samsung Galaxy Nexus] Nuginuk:
guys, stoopid question..

which fancy version supports PGM/TC?, kinda busted my power button
[Samsung Galaxy Nexus] motorazrv3:
All since boype added pgm / tc module support. I don't know when it began but I remember something from r45 on. I choose cm11 module and this works all the time.
[Samsung Galaxy Nexus] bookerok:
In pre54_3 poweramp has must freezing=( never cannot see this bug on another kernel
[Samsung Galaxy Nexus] poo706:
What are you choosing the cm11 module from? I have the paid TouchControl app and the only choices I get are Franco Nightly #395, Ponury stock modified, and Dirty_V Dirty/Smitty 5.3.14.

[poo]
[Samsung Galaxy Nexus] motorazrv3:
I have got paid touch control 1.8.5.

There are some kernel modules offered. I choose the first module. Its called cm11.

Wait a moment. I will deleted my data and take a screen than I can show you the offered modules.

Here is the picture!
[Samsung Galaxy Nexus] poo706:
NOOICE! I was using the latest, 2.2.1. Luckily I still had an old TB backup of 1.8.5 and the cm11 module worked. I endured the bootloops of dirtyv for a long time because of TC and finally said screw it and switched to fancy. I had no idea that I could have my TC back!

[poo]
[Samsung Galaxy Nexus] motorazrv3:
I never noticed that there was a updated version from touch control to 2.2.1.

1.8.5 worked all the time for me. The cm11 module from 1.8.5 doesn't only work for fancy kernel. For example it works on most kernels that are cm11 based. I am using latest dirty unicorns rom at the moment and the cm11 module works with "stock" du kernel.
[Samsung Galaxy Nexus] drakohla:
Unfortunately I have the same issue.

Upgraded from CM11 M8 to M9 a few days ago, then flashed your 54_3

When I start Poweramp to listen to music and starting a workout with my favorite Sportstracking App called "Endomondo"., the music is stuttering/freezing as soon as the display shuts off.

This combo worked for years ;)

To check if it's kernel related I've flashed the DirtyV kernel but it got even worse ;)

So I thought it must be a CM11 M9 issue, and dirty flashed M9 again to get the CM11 default kernel, and guess what the problem is gone!
[Samsung Galaxy Nexus] piterdemon:
On newest touch control app "ponury stock modified" work with this kernel
[Samsung Galaxy Nexus] -=W1S3=-:
If you choose "ponury stock modified" you're just flashing THAT kernel. Check in "About Phone"!
[Samsung Galaxy Nexus] aliesz:
Yes that is right. The ponury stock is a modified kernel of htc I think.
[Samsung Galaxy Nexus] nonoperez:
Sure? Here it shows fancy kernel, I don't think the app flashes a new kernel, just modified it to work with TC.
[Samsung Galaxy Nexus] freshgiammi:
The old TouchControl was PGM (Ponury Gesture Mod)

Ponury is the name of the stock kernel with modules modifications. That options selects the module you have to download if you flash the stock kernel from TouchControl.
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION] sorry to bring this up again,

I was not 100% correct regarding my old post about the heatup, i had tested it again on PSP emu and found that the heat up, performance & consistency on OndemandPlus is more better over Interactive overtime. r54_3 might not need much rework AFAIK :good: !

Hope this helps,Thanks :) !
[Samsung Galaxy Nexus] boype:
So... Did former Fancy Kernel versions work fine with Poweramp / Endomondo?

To get this fixed, my guess is this: increase the max. screen off CPU frequency to 729 MHz and you'll be fine. I also remember there's some option in Poweramp in the advanced settings that could be checked if you experience music stutters... Cannot remember the name of the option, though. That would be my second guess.

P.S.: I use Endomondo myself, but I'm running without music ;)

I'm pretty sure that the app does not flash a new kernel.

Of course, PSP emu and games in general torture the CPU a lot and produce a lot of heat (especially in summertime). But if it's allright now, I'm happy with that.

Still, the heat thing got me thinking and I had some ideas how to handle that. We'll see if I can come up with something new and interesting :)

What I'm still missing is some more reports about Android 4.3 / 4.2 with the recent anykernel version of pre54_3. There's been one report that stock 4.3 does not boot. Anyone else? That includes both successes and failures.
[Samsung Galaxy Nexus] mkclove:
Just had a SOD on pre54_3 while charging through USB to computer. led was just flashing. Did not have access to adb at work. Had to pull battery. Holding power and volume buttons did not work.
[Samsung Galaxy Nexus] drakohla:
Unfortunately I don't know when this began, because I went with CM11 default kernel for quite a while now.

Need to check your two suggestions.

There is a setting inside Poweramp called "Use wakelocks (If sounds stops with screen off)" did you mean this one?

I need some "heavy metal motivation" during my workouts ..haha :laugh:
[Samsung Galaxy Nexus] infectedorganism:
I am on 4.2.2 and I can't give a detailed report yet as I just flashed r54_3, but it does boot.

As with any AnyKernel2 kernel I have tried, I am unable to access my internal storage. In order for me to regain access, I had to remove fstab* from the zip.

For my particular case, I am okay with ext4 as I have no plans on modifiying my ROM to support f2fs. For others on 4.2.2 who wish to do so, this may be a problem.

Request: because you are supporting 4.2, may I suggest reimplementing fstrim from r36. I know as of 4.3 fstrim isn't necessary, but for those of us on 4.2, it is needed.

If readding support will cause conflict, I suggest leaving it out as LagFix should suffice. If you do reconsider adding it again, I suggest having it disabled by default by including suspend_trim, but not initializing it in fancyinit. Perhaps even a section in the OP that will give instructions on how to enable it for those of us on 4.2.

Again, if it will cause conflict with versions 4.3+, disregard this request as those should take priority.

With all of that said, I hope to give a more detailed report in the near future in regards to kernel performance on 4.2.

Thanks in advance.
[Samsung Galaxy Nexus] namtombout:
It boots on 4.3 pac rom and works fine.
[Samsung Galaxy Nexus] osm0sis:
I've updated suspend_trim pretty nicely (I think) over on Dirty, if [MENTION=4615478]boype[/MENTION] wants to see about reincorporating it here. :good:

We decided it was useful even on 4.3+ since crack flashers tend to never make the 24h uptime requirement of the built in trim. ;)

https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV-f2fs/ramdisk-DirtyV/sbin/suspend_trim

https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV-f2fs/ramdisk-DirtyV/sbin/dvbootscript.sh#L135

One of the main things I did was add an "off switch" and have it off by default. :)

Also, Unified v2 is pretty badass, so I recommend updating to it as well. :D
[Samsung Galaxy Nexus] SoftWord:
Osm0sis what is this parameter?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
I don't follow you.. suspend_trim is described quite well a couple posts above mine, if that's what you mean. :)
[Samsung Galaxy Nexus] Rushead:
Holding buttons only works during the boot sequence.
[Samsung Galaxy Nexus] siealex:
Fancy pre54-3 anykernel does not boot on 4.3 PA 3.99.
[Samsung Galaxy Nexus] Orilin:
Pre54-3 works perfectly on Paranoid 4.5 beta1. Pretty smooth and no issue so far in one day usage. Seems to have a good battery stats too.

Sent from my ParanoidNexus
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4078274]infectedorganism[/MENTION] [MENTION=4615478]boype[/MENTION] Didn't we figure out the usb otg part of the fstab was what kept it from working on older versions?

Could just leave it out in the AnyKernel2 (people would just have to use Stickmount), or you could even hack it into fscheck with Unified as a detectable thing that gets hotswapped into the fstab before mount_all. :)
[Samsung Galaxy Nexus] elPicione:
Hi guys, nooby question here.

I'm on CM11 (stock kernel) and i really want to try this fancy kernel with f2fs.

How do you convert the partitions from ext4 to f2fs? Is it possible on a standard CM11?
[Samsung Galaxy Nexus] johansenmo:
Use this: http://xdaforums.com/showthread.php?t=2794702
[Samsung Galaxy Nexus] poo706:
I think he's asking how to convert a device to f2fs, not a ROM.

[poo]
[Samsung Galaxy Nexus] aliesz:
That is so strange that nobody have problem with anykernel2 on 4.2+ ROMs kernel except than me!
[Samsung Galaxy Nexus] johansenmo:
You are right :)

download patched twrp with f2fs support and convert your partitions.

Search xda/Google. You will find what you are looking for.
[Samsung Galaxy Nexus] jazle:
[MENTION=4615478]boype[/MENTION], I use pre54-3 since its first day and never find any problem with it, any plan when it would be released?
[Samsung Galaxy Nexus] nouman8:
Pre 54-3 anykernel is stuck in bootloop on my GN running stock 4.3..plz get it fixed also add cifs support if possible...:)
[Samsung Galaxy Nexus] SoftWord:
Change with new 4.4 Rom....:)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] aliesz:
Unfortunately None of 4.4.x custom ROMs with none of kernels for gnex is as stable and fast as 4.3 stock ROM with fancy r43 kernel.
[Samsung Galaxy Nexus] Madsunable:
Give Paranoid Android a chance! It is near stock and blazzing fast. You can use the latest beta.
[Samsung Galaxy Nexus] thecoolkid:
Bull shhhhhhh... ;)

I'm on cm11 with Fancy pre54_3 and my phone is flying, stock 4.3 is nowhere that fast...

Hey [MENTION=4615478]boype[/MENTION], does fancy include purple tint fix? If not, could you add it in the next release? ;)
[Samsung Galaxy Nexus] motorazrv3:
Fancy includes purple tint fix.
[Samsung Galaxy Nexus] aliesz:
Go f...ck away with your laggy CM!! It was my favorite ROM but all custom ROMs are full of sh...t.
[Samsung Galaxy Nexus] thecoolkid:
Which is again my point, even cm11 can be flying with new Fancy, just try before you complain. If you don't like it try something else... it's that simple.
[Samsung Galaxy Nexus] friedCELLS:
I was on fancy kernel R45 since it came out. One of the best kernels ever. Hearing the good reviews, I tried pre54-3. Holy crap! You outdid yourself. Best kernel ever! My phone is faster than ever. Thanks [MENTION=4615478]boype[/MENTION] . And I also went back and forth between 4.3 and 4.4 Roms for a while. 4.3 was nice and fast. Never was a big fan of CM. But with CM11 and this kernel, my phone has never been so fast (& stable). I've settled on this combo for a while now.
[Samsung Galaxy Nexus] boype:
I suppose I found and fixed the issue with the music stutters.

I'll try to push r54 tomorrow.
[Samsung Galaxy Nexus] poo706:
It was that STUTTERS=TRUE flag, I told you not to put that in.

[poo]
[Samsung Galaxy Nexus] mangusZen:
I was away and Im late to the party. Installed 54pre3

Terrific!

[MENTION=4615478]boype[/MENTION] outclass himself, astonishing work!

P.s. extended battery [emoji12]
[Samsung Galaxy Nexus] boype:
r54

Hi,

as announced yesterday:

r53 >> r54

drivers/cpufreq: round max. scaling frequency to the closest valid frequency (avoids CPU using only 1036 MHz as max frequency instead of 1228, even though 1228 are set as max)

several Linux 3.4 patch backports concerning irq, SLUB, sched/nohz, cgroup, vmscan, omap2, arm/mm (cache) (I browsed through the 3.4 updates since the 3.0 EOS and chose commits that seemed backport-worthy)

replace 192 MHz CPU step with 224 MHz for failsafe reasons (seriously, trust me when I say that you don't have to worry about increased power consumption)

slightly undervolt VAUX3 (display) from 3.1 to 2.9 Volts

ext4/f2fs detection script improvements that allow any possible combination of ext4/f2fs partitions for system/data/cache (thanks to osm0sis)

f2fs: few small mount-option improvements

decrease sched_wakeup_granularity a little (may help with responsiveness with longer up times)

Have fun with this one :)

P.S.:

The music stutter issue and some random crashes in idle mode from pre54_2 and pre54_3 should be fixed in r54

There is no fix yet for Stock Android 4.3 not booting with the anykernel2 version

There is no fix included yet for inaccessible user data on some 4.2/4.3 ROMs with the anykernel2 version. You still have to delete the fstabs manually.
[Samsung Galaxy Nexus] boki2911:
LS rom r 54

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] siealex:
R54 also does not boot on PA 3.99.
[Samsung Galaxy Nexus] sergialess:
r54 working like a charm in CarbonRom. Congrats Boype.
[Samsung Galaxy Nexus] boype:
Is that good?

Okay, that's what I figured since I didn't change anything to make it work. I'm on it at the moment. It's an SELinux issue.

[edit] I have an idea how to handle this ;) Strangely enough, I feel like I already implemented a fix for that in some fancy kernel version back in the days. But I cannot find it. Need to redo from scratch then
[Samsung Galaxy Nexus] Charmacas:
r54 works like a charm! Thank you very much boype!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] namtombout:
on CM 10.1.3 (4.2.2)

anykernel version of r54 boots but there is no access to internal storage (known issue i guess)

using osmosis android image kitchen and combining franco r384 ramdisk with r54 split img i got internal storage access back. I'll try the same thing but with fancy r36 ramdisk and r54 split img soon

Edit: r36 ramdisk with r54 split img boots and grants access to internal storage. as always Thanks boype and osmosis

p.s. if you really want to make an undeserving user happy can you look into adding the hotplugx governor in a future release? Im not sure when it became stable but it is. Been running it religiously on burstlam's lean kernel for 2-3 weeks.
[Samsung Galaxy Nexus] infectedorganism:
Known issue. Delete the fstab.* files from the zip prior to flashing and you should retain access to your internal storage.
[Samsung Galaxy Nexus] siealex:
Isn't this the same problem as mine?
[Samsung Galaxy Nexus] infectedorganism:
I can't say, but hopefully someone can give you some insight into your problem. According the changelog, boype says to delete the fstab files for 4.3 also, so give that a try. Hopefully that solves your issue.
[Samsung Galaxy Nexus] boype:
No

Your issue is next on my list ;)
[Samsung Galaxy Nexus] boype:
To both of you: Please try the following test version on top of a clean kernel (for that end, dirtyflash ROM is good practice before installing an anykernel2 kernel):

https://dl.dropboxusercontent.com/u/2652503/fancy_kernel-tuna-4.2%2B-r54-test-anykernel2.zip

Does that fix your problems?
[Samsung Galaxy Nexus] GilGameshn1:
Thanks for great kernel ... So far so good with LS 8/7 ... THANKS [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION],

The r54 is insane and beastly performance upgrade over previous releases in both snappiness of the ROM & Intensive tasks also. In the previous releases PSP emulator (gaming) it was like 39-52 of 60 FPS and later it would drop to ~42-45 of Avg FPS and this r54 is maintaining a 47-60 of 60 FPS & an avg of ~50+ FPS , which is an ultimate boost plus the temperatures are also quite cooler !!

Kudos man :cowboy: !!

Thanks :D !!
[Samsung Galaxy Nexus] SoftWord:
[MENTION=4615478]boype[/MENTION] any chance to build compatibility to Synapse?
[Samsung Galaxy Nexus] Natakranta:
Is that on SlimKat?

I'm planning to flash 7.2.1 on my wife's Maguro tonight and r54 afterwards. As it's wife's phone it needs to be stable. She uses it as a phone. No heavy tasks melting CPU.

No problems noticed with this combination? If she get a SOD she will go ballistic and my life will be miserable until some flowers and chocolate happens :D
[Samsung Galaxy Nexus] Ashtrix:
ha, yea man it's on 7.0 ;), i didn't knew that 7.2 was out gotta flash it :good:
[Samsung Galaxy Nexus] Natakranta:
Cool! Share your experience afterwards :)

And it's 7.2.1 actually. There were problems with 7.2 automatic build.
[Samsung Galaxy Nexus] Ashtrix:
Sure :) !!

Edit : [MENTION=5180758]Natakranta[/MENTION] it's the same with 7.2.1 also, works fast !!
[Samsung Galaxy Nexus] morfances:
R54 with validus!Thanks Boype!!
[Samsung Galaxy Nexus] motorazrv3:
I am still facing audio stutters. I am using fancy kernel r54 and dirty unicorns 7.8 test build.

Tried testing with Apollo music app, maybe it is still a rom problem and not kernel related.

Anyone else still having audio stutters?

R54 is another step forwards. So far kernel is performing fantastic. THX again for this update.
[Samsung Galaxy Nexus] lollipop:
for me with R54 audio stutters is fixed,i'm using carbon rom
[Samsung Galaxy Nexus] sagara.sandaru:
Are you guys talking about audio stutters that happens when screen locks?
[Samsung Galaxy Nexus] motorazrv3:
Yeeeeeessssss
[Samsung Galaxy Nexus] sagara.sandaru:
I'm on FML with R54 and I'm also still having audio stutters.
[Samsung Galaxy Nexus] büscher:
I'm on unofficial Liquidsmooth 8/11 and Fancy r54.

Playing music with Poweramp gives me no such stutters (and I know them from the early days of DrtyV)
[Samsung Galaxy Nexus] boype:
That's not a kernel issue. It first appeared with android 4.4.
[Samsung Galaxy Nexus] DR3W5K1:
+1

I've heard reports of this from the users of multiple devices running KK.
[Samsung Galaxy Nexus] zoomy942:
Thanks for the link. So far 15 has been the absolute best.
[Samsung Galaxy Nexus] boype:
r17 up

Hey all,

r17 is up. It focuses on fixing the flicker problem.

Best regards
[Samsung Galaxy Nexus] zoomy942:
Is there anyway around the 10% screen brightness change you've made? I live is a really sunny place in the Idaho mountains and outside its really hard to see.

Just curious.
[Samsung Galaxy Nexus] Fabur87:
I have tried to download the newest version using fuss three times now and I am always getting a MD5 error.

Using R16 I had one phone freeze while browsing with Chrome and receiving a phone call. The weird thing was that the phone still vibrated and showed a glowing LED some time after it froze, but it didn't play any sound or recovered from the freeze.
[Samsung Galaxy Nexus] agritux:
fuss says md5 mismatch :p

---------- Post added at 12:03 AM ---------- Previous post was at 12:01 AM ----------

and your site is down. only mediafire works. :good:
[Samsung Galaxy Nexus] bolanrox:
the site worked when i downloaded it (around 2pm)
[Samsung Galaxy Nexus] phishn:
Unable to update from r16 ext to r17ext using fuss. Keep getting md5 mismatch.
[Samsung Galaxy Nexus] lesclark:
worked for me.
[Samsung Galaxy Nexus] n2rjt:
R17 Std has good md5 but ext doesn't?

I flashed ext via recovery and it seems okay.
[Samsung Galaxy Nexus] gwindlord:
boype, you seemed to forget to fix update txt - the correct MD5 sums are 1f8aef4995250391e4c3c8f1cf6b4dfe and 2c93d8d518422cc240cf879e607bf665, and update.txt says about 9b9ba3ea39fdd11c56dce497aa1f68d5 and e75d4a1e7b4c6b7e0c6ed3d674b3ef58 :)
[Samsung Galaxy Nexus] boype:
Funny. I'm positive I updated the md5s... Will fix in a bit

[EDIT] fixed.

Put this in init.d:

#!/system/bin/sh

echo "1770000000 1810000000 2000000000" > /sys/class/misc/colorcontrol/multiplier
[Samsung Galaxy Nexus] Fabur87:
I am still getting MD5 mismatches trying to update ext version via fuss. :/
[Samsung Galaxy Nexus] boype:
lol it seems i'm just too stupid :D

fixed. for real.
[Samsung Galaxy Nexus] Lancez:
this kernel is soooooo under rated, first time trying this kernel and i'm suprised how fluid and battery friendly this kernel is. :good: