yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] apophis9283:
I use a script that enables full linaro optimization, including use linaro compiler flags. Would love to use your kernel as stock kernel for my builds
[Samsung Galaxy Nexus] sajty:
Good to hear that.Interactive gives me better performance than ondemandplus (but i believe,thats normal behaviour,interactive is more aggressive).
[Samsung Galaxy Nexus] creeve4:
Would you mind sharing your script?
[Samsung Galaxy Nexus] apophis9283:
I do not mind. Android is about sharing :). Get with me on gtalk. Credit for said script goes to iamtheonetheycallneo a good friend of mine.

steaven.android@gmail.com
[Samsung Galaxy Nexus] Rufufu:
I'm testing r32-tst1, and it is working fine for now! Seems stable with my old gnex which was previously not confortable with 1.4GHz OC. I'm doing some benchmarks for checking stability, but I can't compare with previous results.

For info, with cm10.1 and all stock setting, except 1.4GHz CPU and temp limit at 60°C

Nenamark 2:

-384MHz GPU : 33.5fps

-512MHz GPU : 39fps

*note I have to kill nenamark2 after changing GPU from 384 tu 512 MHz, else I'm having 31 fps with 512.

Antutu with 384 MHz GPU : 4656.

It's bad but I think itis because of throttling with my low temp control. I will trying with 70°C

EDIT : Indeed, it was throttling, with 70°C for max CPU temerature, I'm having 7813 with antutu.

EDIT2 : and finally, quadrant score with 70°C max temp and still 1.4GHz CPU and 384MHz GPU : 3416. The phone was already hot at the begining, so maybe still have a throttling issue.
[Samsung Galaxy Nexus] creeve4:
Anyone else running AOKP? Can you please comment on your GPU performance with Nenamark2?
[Samsung Galaxy Nexus] boype:
I checked the AOKP repo, it's all right... Nothing you need to set. Must be sth else then...

Go ahead :)

Exactly ;) Interactive is "performance, performance, performance" and ondemandplus is "moderate performance with moderate power consumption"

Do you have the charger / USB connected? Or is it getting very hot in general? It's probably the RAM tweak..?!
[Samsung Galaxy Nexus] creeve4:
Could it be my GPU? I tried running franco.Kernel and I get the same FPS for those frequencies, so it is not your kernel.
[Samsung Galaxy Nexus] apophis9283:
Thank you kind sir! Once I figure out which commit is causing a FC in romcontrol I will work to use your kernel as stock for my builds!
[Samsung Galaxy Nexus] stevensoaj:
I'm not sure about him, but my device is having no heat issues. I'm at max 1420 CPU and 512 GPU and I'm scoring 9100+ in Antutu with Thermal Throttling set at 64°
[Samsung Galaxy Nexus] Rufufu:
No, the phone was not charging, and I don't think it is the RAM tweak.

I did all the benchs in a row, without let the phone going back to room temperature. In addition, for the firsts test, the max temp was lowered from 64°C (defult setting, right?) to 60°C.

My phone has been hotter with stock cm kernel, or previous fancy releases, and I think 1.4GHz OC doesn't help my phone getting cooler.
[Samsung Galaxy Nexus] RevengeFNF:
With the last CM 10.1, and CPU at 1.2Ghz and GPU at 384Mhz, i get 33.1 fps with NenaMark 2.

If i set de GPU to 307Mhz, i get 28 fps.
[Samsung Galaxy Nexus] andry23jsv:
Can someone help me?

http://xdaforums.com/showthread.php?t=2336585
[Samsung Galaxy Nexus] parthipanramesh:
Running r32-tst1 now for a few hours. No problems. Everything is really smooth. Love it! :)

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] Charmacas:
If anyone had also the feeling the r32 is slower than r31: Stay tuned! Problem is solved plus I think it's even better as r31 now. ;)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] standa75:
Antutu results for r32 test 1 are attached.I do not take care about bench marks, but I saw few bench posts, so I did tests too.results are great, I would like to thank developer for nice work:thumbup:

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] Rufufu:
Have you f-sync enabled?
[Samsung Galaxy Nexus] iferlive:
Guys I know benchmarks are not the absolute truth about the phone performance but what are your settings? What rom are you using? And could you share your UV values? My GNex haven't been a fast phone since I updated to 4.2.2 it feels and acts like my old xperia x10
[Samsung Galaxy Nexus] nitsua98:
Daaang man that's really low
[Samsung Galaxy Nexus] thegtfusion:
try a different rom, without halo
[Samsung Galaxy Nexus] BOY_:
OK so I've been playing with benchmarks all night. 1st time, really, but with all the chatter figured what the heck. Some areas of note, my scores were all over the place but my best scores were with the following setup:

CPU 122880

GPU 384

UV (by group): -5, -5, -75, -5

Interactive governor with crossbreeder tweeks.

Nenamark2: 33.3

Leads me to question why I got terrible scores at 142080 and 512 :confused:
[Samsung Galaxy Nexus] kinfolk248:
well i just got a sod and hot reboot with r32 on sourcery rom

384/1036800/537

ondemanplus
[Samsung Galaxy Nexus] jesssiii:
How do you know this?

Toro GNex
[Samsung Galaxy Nexus] iferlive:
I have tried but the result is the same
[Samsung Galaxy Nexus] motorazrv3:
What do you mean? Please explain and give us more infos.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] nitsua98:
Have you ever wiped your phone? Might wanna try that if you haven't :p
[Samsung Galaxy Nexus] jeff5347:
I noticed the same. On all the previous kernels I got real good scores of 7500 or better. W 32test 1 I got a score 3 times in the 4000s. Hmmmm used the same settings in each kernel. Cubic, 512, bfq, 192, 1420, 537, 192... Fast charge on, MPs 0, mpu volts -50.
[Samsung Galaxy Nexus] motorazrv3:
Before my nexus I used a Sony Ericsson neo v. At the moment I am on purity 5.6.1 and fancy r32 ext.

My nexus is definitely much faster than my old neo v.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] jeff5347:
Not saying mine isn't fast. I'm using apops AOKP ROM w fancy but my score dropped dramatically. I know not to go by them but on how it performs,...just wondering why it all of the sudden dropped
[Samsung Galaxy Nexus] agritux:
Sure boype.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Edgarngg:
Hey Good Night fellas. I want to try this kernel. I come from ak kernel. But when I flashed r32 it took like around 4 hours at boot animation. Is this normal? What's the average time for waiting for the first time flash. I mean I could wait what ever time it takes but I wanna make sure everything is right.
[Samsung Galaxy Nexus] Seraz007:
O_o lol max time wud be abt 1 min

20 seconds for me
[Samsung Galaxy Nexus] Khizar:
no thats not normal.. the max it should take is a min or 2.. btw did you flash rom/gapps before flashing this kernel? AK uses a custom ramdisk so when switching to this kernel its necessary to flash rom/gapps first

Edit- just tried flashing this kernel(coming from AK Cylon 801) and it booted within a min
[Samsung Galaxy Nexus] bmg1001:
Reflash your rom with your gapps and such, and then flash Fancy Kernel. AK uses it's own ramdisk which breaks the rom if another kernel is flashed.
[Samsung Galaxy Nexus] motorazrv3:
Results using purity 5.6.1 and fancy r32 ext. Max CPU frequency is set to 1 GHz.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] Edgarngg:
Do i need to factory reset? Thank you!

well maybe cuz I come from skl 256? Does 801 uses custom ramdisk too?

Why just for you? :(
[Samsung Galaxy Nexus] Charmacas:
I think you missed it agritux...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bmg1001:
No Factory Reset needed, just wipe system partition, install rom + gapps and your other mods, and then the kernel.
[Samsung Galaxy Nexus] Edgarngg:
Ok Man thank you very much! Appreciate it!
[Samsung Galaxy Nexus] standa75:
No,Fsync was disabled.

Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[Samsung Galaxy Nexus] Rufufu:
OK, that's why you have impressive results... When someone post a bench result with disabled fsyns, it would be fair to indicate us.
[Samsung Galaxy Nexus] boype:
Using r32 or r32 test 01? When this is only happening on the test version, it clearly is an indication that RAM timings are too aggressive and I need to relax them.

R32 or r32 test 01? If you are on test 01, please test again with r32 and report. Also, watch your temperatures...

Is your phone running hot?

that's exactly what the test version is for: to see if the aggressive RAM timings make a mess for some users.

It can take up to 20 minutes on first boot if you wiped cache and dalvik, but all boots after that are normal.
[Samsung Galaxy Nexus] Edgarngg:
Oh yes I did wipe cache and dvk. So the thing bout custom ramdisk is true too?

And... What should a do then? Wait for r33? Since somebody.commented they are working on some issues.
[Samsung Galaxy Nexus] quickstang:
Dude, just dirty flash the rom, gapps & kernel like mentioned. You're making this more difficult than it needs to be. No need to wait for anything. Your not having any kernel issues so just flash away. You can try r32 or r32 test 01.
[Samsung Galaxy Nexus] Edgarngg:
Jaja yeah yeah I think I was just trying to make some chat over here. Jaja :P I'm going to try this :P I actually like to make that much questions because I like to learn. Sorry man. Chill out :)
[Samsung Galaxy Nexus] Riekr:
[MENTION=4615478]boype[/MENTION] much probably ram timings and temp control need to be relaxed for overclock. UV may influence those settings too.

Here is all OK without oc and new ram timings, even on benchmarks.

Maybe a ram governor? :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] boype:
The RAM voltage / timings are unaffected by CPU / GPU overclock.

And RAM governor won't be working I suppose... Can't be changed 'on the fly'.
[Samsung Galaxy Nexus] boype:
r32 test 02

I put up r32 test 02. It has slightly relaxed RAM timings.

This goes especially to those reporting problems with test 01 (low benchmarks, etc): Please test the new version and report if your problems persist.

http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-r32-tst02-ext.zip

Also, if you have not read it yet: READ THIS FIRST before trying the test version.
[Samsung Galaxy Nexus] jackyaway:
Hi! With r32 and wifi setting to "only when connected", wifi is always on. I haven't this bug on r31
[Samsung Galaxy Nexus] Riekr:
i suppose that overclocking will change "front clock" wich is the clock speed while talking with the ram (whole north bridge/fsb on desktops, front clock is the one still not multiplied by ddrN technologies).

aggressive timings may be too much when this frequency rises (on the other hand less aggressive timings _may_ allow overclocking). ram timings are delays so the real speed is frequency (fsb) dependant.

but sad to know it can't be changed dynamically :(
[Samsung Galaxy Nexus] littlepaulie:
My device is flying with tst01 and newest purity rom :)

Not sure if it's worth checking tst02 in this case?

Wysłane z mojego Galaxy Nexus za pomocą Tapatalk 4
[Samsung Galaxy Nexus] mpokwsths:
[MENTION=4615478]boype[/MENTION]:

It isn't confirmed that ram timings affect these people.

1. Synthetic benchmarks don't always say the truth. Real feel does.

2. You told those guys to test the normal version of r32 and they didn't.

3. You have much positive feedback from test 1, why don't you move that way?

To summarize... it could be a ROM problem or some mod that caused these strange results.
[Samsung Galaxy Nexus] blacra:
Please whitelist MiHome launcher.

com.miui.mihome2
[Samsung Galaxy Nexus] d0ge01:
Ignore benchmark, this kernel rule them all

My gnex seems HTC One now with almost good battery ( not excellent but very good )

Min: 192000

Max: 1420000

Governor: Touchdemand

changed set to inter_low : 500mhz step, inter_high: 700mhz step
[Samsung Galaxy Nexus] Starsream88:
[MENTION=4615478]boype[/MENTION],

Why you didn't implement 1300mhz cpu oc step on this great kernel like franco and ak ? That will be awsome :thumbup:
[Samsung Galaxy Nexus] BOY_:
Boype I was on test01 with fsync disabled running apops latest AOKP. Downloading test02 and will retest.
[Samsung Galaxy Nexus] quickstang:
Same setup here except fsync is on. Testing 02 right now. No issues with 01 all day yesterday fyi.
[Samsung Galaxy Nexus] zoomy942:
I will wait to see people's results from test1 before I just to test 2. I use stock kernel settings and didn't have any trouble.
[Samsung Galaxy Nexus] BOY_:
OK, same setup on test02 and the results were lower than test01. Going to reflash R32 and retest.

122880, 384

142080, 512
[Samsung Galaxy Nexus] BOY_:
Well, looks like r32 is no better (worse actually). Consistent observations, best benchmarks are at 122880 and 384 on all 3 versions. Test02 has best oc score but still below teat01 at above settings.

So clue what's going on but there is some data for you to ponder. Going back to test01 for now.
[Samsung Galaxy Nexus] thisguy23:
Benchmarks are junk. Test 1 is amazing! I would be interested in more dramatic timings! This thing flies. Been a while since I can say that.
[Samsung Galaxy Nexus] jeff5347:
Boype, OK tested test 2. Leaving the kernel stock I scored a 5203. Then I changed to my previous setting listed back 3 pages and scored 6823. Also you asked about temp. Temp hasn't been an issue. Phone w test 2 for all intended purposes is flying. Whether the score is better worse or the same this kernel is awesome. Overnight last night with t1 the phone slept for 6 hrs with .7% per hour drain. So screw scores this kernel works better than any I have tried before Fancy.
[Samsung Galaxy Nexus] boype:
To clarify: I am not throwing the settings from test 01 out of the window. I just want to check out all possibilities to not make a premature release with timings that make things worse instead of better for some users. We're in the same boat, I want the best performance too. That's why I am collecting information with the test versions.

Will do!

I'd like to. But I don't want more CPU steps (at once) than there are now, which is why I need to come up with a mechanism that disables the 1300 MHz step when 1400 MHz is activated. I'll look what I can do.

After reading this, I'm very much interested if you achieve good results with 1.4 GHz CPU / 512 MHz GPU on other kernels... Just to know if there's sth wrong.

Ah and also this: You're experiencing drops in performance with 1.4 / 512 compared to 1.2 / 384. But what about 1.4 / 384 or 1.2 / 512? It would help to pinpoint the problem.
[Samsung Galaxy Nexus] BOY_:
Boype, last night I tried every permutation you can think of, including voltages. I'm walking into the office so I won't be able to test until later. Depending on what you build in the meantime, I'll try Franco or Tiny later for comparison.
[Samsung Galaxy Nexus] DoesntPostAThing:
Very good kernel, on 1.2/384 with otherwise stock settings and XenonHD. I don't bother with benchmarks. Test01 was also a lot better to me than r32, which was miles better than the last time I tried Fancy Kernel, about r28. I came from a bunch of kernels such as Tiny Kernel 4.1.0, Nova Kernel 1.1, Franco r382, AK v256, etc.
[Samsung Galaxy Nexus] boype:
So what was it that caused the drops in performance? CPU -> 1.4 or GPU -> 512? Or only both at once?

Also: thanks in advance for testing
[Samsung Galaxy Nexus] BOY_:
Sorry, should've clarified. I saw no gains at either value or combination of the two. In fact, my performance with the GPU at 512 was comparable to the GPU at 307 :confused:

Same for NenaMark2, 307 and 512 were comparable but 384 was smokin.
[Samsung Galaxy Nexus] Charmacas:
I think the question is also if there is any benefit in adding this step!?

We now have 1228 which runs really nice if you're not heavy gaming. But in addition to that we got 1420 so we can squeeze a bit more power out of our GNex with now the same stability. If there is really a benefit of the 1300 step why not remove 1228 and add 1300!?

But now I really don't understand this request. :)
[Samsung Galaxy Nexus] sajty:
For me,benchmarks of r32,r32-tst01 and r32-tst02 are pretty much the same - i dont see any noticeable difference.

EDIT: just reached the highest score ever in AnTuTu with Fancy,but only few points more than before.So still,no noticeable difference for me.

---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------

Because of possible data drops? :D
[Samsung Galaxy Nexus] zoomy942:
testing if test two has better battery life

---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------

To clarify, I felt test 1 drained a bit quicker than normal.
[Samsung Galaxy Nexus] Khizar:
ALL Of the AK kernels use a custom ramdisk.. and no need to do a factory reset just flash rom/gapps(this will revert your ramdisk back to stock) then flash kernel :good:

PS- after trying this kernel for you i went back to AK and now i am on ASKP and still dont have any issues.. so i 99% sure your issue was due to the custom ramdisk and flash rom/gapps then kernel will fix your issue :highfive:
[Samsung Galaxy Nexus] creeve4:
I don't see it in the OP, but I assume that Fancy uses its own Ramdisk? Is it possible to build without a Ramdisk, so the ROMs Ramdisk is used?
[Samsung Galaxy Nexus] mpokwsths:
Flash another ROM. Factory reset and flash a good fast, Linaro and bionic optimized preferably, ROM. Then flash Fancy kernel.
[Samsung Galaxy Nexus] DoesntPostAThing:
I'm not sure if Fancy uses it's own ramdisk, but in general I flash ROM + gapps everytime I switch kernels. Upgrading kernel versions it's ok to just flash the kernel, but when switching I do it because it's still faster than asking and waiting for an answer. Reflashing does no harm, either, so why not?
[Samsung Galaxy Nexus] mpokwsths:
I tried that. Extracted zImage from boot.img and used r22's ramdisk (because it messes up the colors and fixes my PURPLE TINT after some calibration, which ). It worked BUT I didn't have WiFi because boype since r2x-something compiled it as a module (so it is not part of the zImage).

[MENTION=4615478]boype[/MENTION], how can I use the zImage from your new kernels with the ramdisk from r22 (and have operational WiFi)? Some init.d script or something?
[Samsung Galaxy Nexus] BOY_:
I'm on a linaro optimized ROM.
[Samsung Galaxy Nexus] bolanrox:
Do you any ROM's to keep an eye on? The one i use is probably not getting any new versions, and I need to jump to something else once the next Android version drops.. or if i get really really bored in the mean time. :)
[Samsung Galaxy Nexus] boype:
New release 'r6' up

Hi all,

I updated the OP with r6. As you may have noticed, I changed the labeling from 'rel' to just 'r'. This release contains mainly updates and adds Android 4.2.2 compatibility. Anyway, here's the changelog:

updated gpu: pvr to DDK 1.8@2198402 to support Android 4.2.2

updated ARM CPU topology to latest version

updated kernel to Linux version 3.0.63

updated BFQ I/O scheduler to version 6

updated interactive governor to latest version

simplified ondemandplus code and made tunables easier to understand

enabled NTFS support for USB-OTG (upstream change from CM10.1)

a few more things and updates... check the sources if you're interested.

As a personal (and therefore subjective) experience, this version has become smoother in terms of UI interaction.

Best regards
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

i am test it now:D
[Samsung Galaxy Nexus] agritux:
boype! keep it going! :D

a beer from me for you :) :highfive:
[Samsung Galaxy Nexus] str8killinya:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Running great so far, thanks dev for the great work. Will try for a few days and report back with battery readings

DEVICE: Maguro

ROM: Bigxie Stock Rooted 4.2.2

KERNEL: Fancy v6
[Samsung Galaxy Nexus] boype:
I'm running CM10.1 nightlies on my device. But I don't update every day, I always check the changelog and see if it's worth flashing a new version.

Battery life: I think I may have a 'golden sample' device (or maybe it's just my particular usage with mostly web-browsing and messaging)... When I charge the battery full and empty it in ~24 hours, I get a screen-on time of roughly 4 1/2 - 5 hours. When I don't use the device that much (empty battery in 48+ hours, hence more battery drain due to standby), I get up to 4 hours screen-on time. I always have sync enabled, but when I sleep I switch to flight mode.

Now look at that - the beer is in my paypal account :D You're the first donator since I'm on XDA. Thanks buddy :>
[Samsung Galaxy Nexus] agritux:
it is my fault sorry.

i was always loved your cm7 kang while i am using p970

i always used your format script when i install any custom rom

i used your cm7 kernel with all cm7 based roms

and now i am using your kernel with gnex

it is a little gift i know.

but it may increase in the future :)

thnx
[Samsung Galaxy Nexus] AKA_noodle:
pls, explain me the meaning of Read Ahead Buffer Size
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

what about sio or bfqv6:p
[Samsung Galaxy Nexus] gwindlord:
It means how much will be read in 1 block (read operation) from disk. If it is bigger, bigger files are read faster, smaller ones a bit slower, and vice versa :)

Sio, that's always sio :) It is solid, reliable and I cannot remember any issues with it.
[Samsung Galaxy Nexus] Degrated Shadow:
excellent... there is just no lag... not on games or whole ui atleast as much as i have been through.. still gotta do some battery test. will report back

ps: most wanted only works on this excellent kernel.. loving it. thanks a lot.:good::good::good::good::good::good::good::D:D:D
[Samsung Galaxy Nexus] :
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Thumbs up for the OP!!! :D
[Samsung Galaxy Nexus] albsat:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Latest release looks very smooth.
[Samsung Galaxy Nexus] bolanrox:
So far so good with rel 6 here. Flashed around 5:30am and have had no issues.
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

use r6 with 4.2.1 aokp

only change cpu uv

40% battery i got 2h40min screen on time

thanks boype :D

great kernel !
[Samsung Galaxy Nexus] aHecticLife:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

What is your uv numbers?

Sent from Blah Blah using XDA's Blah Blah Premium App
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)
[Samsung Galaxy Nexus] aHecticLife:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Will try it now thanks :D

Sent from Blah Blah using XDA's Blah Blah Premium App
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

on learn kernel i can use

750mv-180mhz

775-230

800-350

875-700

975-920

1100mv-1200mhz

now i use fancy kernel

i found fancy kernel smooth than learn kernel use the same battery

my poor english:p
[Samsung Galaxy Nexus] boype:
Are there any music-listeners here who find the battery life remarkable too? I just listened to two hours of music with screen off and I only lost only 7 percent battery. If you'd extrapolate, that would be more than 28 hours of music with one battery charge :cyclops: Or is that normal for all kernels?
[Samsung Galaxy Nexus] bigknowz:
What's your trick?

I listen to music to/from work. I lose about 5 - 7% battery in 35 minute commute, and some of that is in airplane mode. I use Rocket Player, and it is Force Closing when I swipe away. Any thoughts, only happens on fancy, not other kernels.
[Samsung Galaxy Nexus] midnightdevil66:
Having an issue with GPS lock on r32 on toro. Will not lock on even after 10+ mins wait time. I flashed back r31 and it locked in in less than 5 seconds from the same location.
[Samsung Galaxy Nexus] paarthdesai:
carbon, rootbox, axiom..

sent from my sexy Nexy ;)