yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] marc.tulley:
Nice boot animation

Didnt install in CWM so pushed it manually from inside the kernal zip

Note however my GN crashes on 7% antutu benchamark everytime. (14.3)

700-1350mhz, no UV, AOKP 21
[Samsung Galaxy Nexus] ro_explorer:
I don't argue with that. Having better or worse results in 350 or 700 or whatever value should be a matter of "better or worse" not "working or not working". That was my point.

So I would prefer to draw my own conclusions rather than following what others are preferring.

Conclusion: setting min. freq. to 350 will disable gsm signal completely while screen is off.

As for idle drain, in my case, #14.3 is at the same level with #13.1, definitely better than #14.2.
[Samsung Galaxy Nexus] kfluk:
I use bigxie Apex 1.0.0 rom and franco kernel 14.2. It run fine without problem with the following UV setting. While after update to 14.3, GN is unstable and hang within few minute after apply voltage after boot.

MHz 350,700,920,1200,1350

Voltage 800,925,1050,1150,1175

There is no change in rom or other setting before and after update from 14.2.

Can you explain the different on the voltage setting on both kernel again?

I hope to keep low voltage with your kernel and need stablility. i.e. rollback to 14.2

I'm use on demand governor.
[Samsung Galaxy Nexus] aimetti:
Well I am on 700 - 1200 conservative and getting the signal drop
[Samsung Galaxy Nexus] Mondfahrer:
Ok, now I get some bad issues with my GN again. After 2-3 minutes in standby, it start rebooting itself:confused:

There must be something rly wrong :rolleyes:
[Samsung Galaxy Nexus] mDroidd:
On AOKP, the bootanim is inside /system/media/ rather than /data/local

Greets!
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=2088054]jhonnyx[/MENTION] did add the f2fs commits to franco kernel, pardon me if i misunderstood anything:laugh:
[Samsung Galaxy Nexus] jhonnyx:
Actually I'm with FK's fork with F2FS commit, everything's running good so far. Anyone needs some testing/output? I'd be glad to do so.
[Samsung Galaxy Nexus] osm0sis:
Can you make a pull request for it against the franciscofranco repo? And please mention in the comment for it whether there was any special voodoo required to get it to compile. :D :good:
[Samsung Galaxy Nexus] jhonnyx:
I'll try to merge my commits in a clean/proper way on a new repo tonight then generate the pull request ;)
[Samsung Galaxy Nexus] my573r10us:
i always get reboot after 5 minutes blank screen (only happen after reboot and not touch the phone till it black screen 5 minutes. how can i fix that? i really like this kernel.

r396 kk fixed kernel and happen with shiny 4.4.3 rom (on aokp too)

sorry bad english.
[Samsung Galaxy Nexus] lollipop:
What?!!! I'm on aokp and the kernel is working very well
[Samsung Galaxy Nexus] my573r10us:
really, i'm on aokp 02.25.14. and now on shinny 4.4.3.

try this:

reboot phone - just wait (dont touch anything on phone) - wait +- 5-10 minutes. and see is it happen to you too? or just me? bcause i try other kernel (dirtyv kernel), nothing happen like that.

something wrong with my phone? :(
[Samsung Galaxy Nexus] pianistaPL:
I remember i had the same problem.
[Samsung Galaxy Nexus] lollipop:
i'm on aokp 25/05/2014 ,nothing from what you say is happned to me, i can wait after reboot for hours ,all things is working perfectly
[Samsung Galaxy Nexus] DR3W5K1:
Turn off/on cab either off or on and it will go away.
[Samsung Galaxy Nexus] osm0sis:
It's actually from it being set disabled by tweaking apps when the screen's off if you don't unlock after boot. Setting it by init.d script fixed it for everyone I've ever seen, including myself. :good:

I set it off by default for the next version to fix it for good:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/ca64201f3d417c0e996b7f5d8f98efecaa134b87

:)

[MENTION=4328678]metalspring[/MENTION]'s build is tested and working great with my r396-fixed ramdisk, we're just waiting for him to have some free time to recompile it with SELinux default set to Permissive on the kernel build command line. That'll fix Wi-Fi Tethering on CM-tree based ROMs. :good:
[Samsung Galaxy Nexus] my573r10us:
me too, long time ago, but it happen again now :(

i dont know why it can be different :eek:

so it must be enabled or disabled? because i use trickster (set on boot) and i set CAB off, but same happen :(

edited : sorry i got it now. it must not be disable by tweaking app (like trickstermod), it must from init.d script. am i right? bcause now i use both trickstermod to set off cab (set on boot), and init.d script to disable cab together. and the issue still there.

btw, about wifi tethering, u mean right now we cant using it?

And, i will wait for [MENTION=4328678]metalspring[/MENTION]'s build to release.. it would be perfect hehehe...
[Samsung Galaxy Nexus] lollipop:
[MENTION=4544860]osm0sis[/MENTION] i'm now on omni rom should i use the default version or your fixed version
[Samsung Galaxy Nexus] osm0sis:
I'd say it's always safer to use fixed. :good: ;)
[Samsung Galaxy Nexus] lollipop:
I thaught that omni use different device tree that cyanogenmod ,so i thinked it's safe to use default version.can you explain please(sorry for my bad english
[Samsung Galaxy Nexus] osm0sis:
Correct. But it doesn't hurt to move forward to the new SELinux files, just when you move back. So if you want to use what'll be in r397 you can use my fixed version. On Omni you don't necessarily have to though, you're right. ;)
[Samsung Galaxy Nexus] lollipop:
thank you,will change to your r396 fixed version :cool:

waiting for the next version by franco , you and metalspring right?
[Samsung Galaxy Nexus] mangusZen:
Hi [MENTION=1143630]osmosis[/MENTION] or others, im so late to the party..what happened? Mpok released his sources? Do I understand well? Where I can find some info/news?
[Samsung Galaxy Nexus] antonio8297:
for the lovers of franco,there is a new version based on new commit of osmosis,with optimizazion by metalspring,and the same toolchain of dirtyV in the omnimetal.

i have the ext4 version,i can't try it,for who would try it send me a pm.

[MENTION=4544860]osm0sis[/MENTION] if you need who compile the kernel,if metalspring can't do this,i can do it.

when are you ready for compile it,pm me.

in 10-15 minutes the kernel is ready for upload.
[Samsung Galaxy Nexus] pianistaPL:
Could you make f2fs version?
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2180870]mpokwsths[/MENTION] released his source finally, yes. You can see the important ones for RAM speed have been cherry picked by me already on the f.K Github.

f2fs support will be coming. [MENTION=2088054]jhonnyx[/MENTION] already has it working for f.K and is making a pull request when he has time. I have a unified ramdisk created for DirtyV and can do the same for f.K but I'm waiting on a custom busybox build before I can release it. Happy to take volunteers to make that happen. Busybox needs to be v1.22.1 with the f2fs volume_id patch (in the official source since v1.22.0), needs to have blkid fstype display enabled in the build config and needs to be static but reasonable sized to keep it quick (Stericson keeps his around 1mb).

[MENTION=4328678]metalspring[/MENTION] is a busy guy, involved in a lot of projects (like myself), he'll post his builds when he finds the time to recompile with SELinux Permissive.
[Samsung Galaxy Nexus] antonio8297:
when i have a modded ramdisk i'll post it.

i would only help you,and the community,by offering my help
[Samsung Galaxy Nexus] osm0sis:
Any chance you could help with the busybox compile? :D That's what I desperately need to finish my work of a few days ago. Check my edit above. :good:
[Samsung Galaxy Nexus] antonio8297:
If you send me of what i have to do via pm,i'm very interested in helping you.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] metalspring:
Speaking of the mpokwsths commits, it may not be a good idea to include them at all. He got those commits from patches submitted to linaro for approval, and they were REJECTED because they weren't safe (can cause cache corruption) and were only good for benchmarks, not real world performance.
[Samsung Galaxy Nexus] osm0sis:
I saw that. They said there were definite improvements on synthetic benchmarks but didn't really state definitively that there weren't benefits in the real world. And they were a good idea, and the logic was sound, but the Linaro guys found a new errata that wasn't in the documentation which the commits would affect and so were potentially dangerous... :(

I'll inform Franco with a link to the Linaro Mailinglist and he can make the final decision. He took a look at just the commits so far and said "they look cool." :p
[Samsung Galaxy Nexus] bsmitty83:
I know that this will be long debated , but I'm removing them from dirtyV because I'd rather be safer than sorry , and even if there is no danger whatsoever , the commits really don't make a difference in normal use , so why take that chance .

I wish I knew more on this subject but that's just how I'm looking at it .

More than likely they won't ever cause issues , but if there isn't any benefit than its better to just ignore them .
[Samsung Galaxy Nexus] ashclepdia:
hot topic lately these "ram commits"by mpo(funny kinda in a way those who know what I'm getting to understand WHY lol)

and while I fully respect any devs decision to include or leave out this code, my ONLY hope is that it gets looked into FURTHER/deeper, as in any "safer" way to implement,.or get similar results while avoiding any"high chance"of error n

something which I'm certain our amazing developers have ALREADY started to look at or play with if possible.

sorry for jumping into the dev discussion in the subject, just wanted to put in A users viewpoint on this, one showing we EXTREMELY love what y'all do, whether you go balls in with hopes of no damage, or just TRY to keep things out that MAY seem good to users but in the end could hurt us MAYBE.

thanks ALL
[Samsung Galaxy Nexus] metalspring:
The main issue with those ram commits is they disable several arm erratas (https://github.com/metalspring/Tuna_JB_pre1/commit/0f0b9351378cbcc7393e10c48e410f30c298fd77). Arm erratas are enabled for different serious bugs for different arm cpus, and usually not bugs that just cause lag or freezes but may potentially brick your device, disabling them is usually a very bad idea.

Case in point smitty was testing disabling all of the erratas applied for the gnex, had one little freeze and reboot and ended up pretty much bricking his phone and needing a new board for it. While that might be an extreme case (and possibly extremely coincidental) , it just goes to show that those erratas can be very serious and should be left alone.
[Samsung Galaxy Nexus] pattyboi:):
do you think if we re-enable the erratas the ram speed increase would still work?
[Samsung Galaxy Nexus] metalspring:
no, they require those erratas to be disabled to work
[Samsung Galaxy Nexus] antonio8297:
http://www.mediafire.com/?ux21a52snrc6mj4

F2fs version tested and booting.

Metalspring toolchain from omnimetal and dirtyV optimizazion,and latest franco code.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] mangusZen:
Ok for the well explained technical part, thank you..but some gossip? How come mpok release commits now after all the drama involved?
[Samsung Galaxy Nexus] DR3W5K1:
To much bad karma.

Probably couldn't sleep at night and things kept going bad in life?
[Samsung Galaxy Nexus] sunscape:
Working great. Best antutu scores i've ever had if that means anything.
[Samsung Galaxy Nexus] morfances:
Sorry to be a noob question, but to put this kernel is also used to have a rom that supports f2fs?
[Samsung Galaxy Nexus] pianistaPL:
Yes, only f2fs

Wysłane z mojego AOSP on Maguro przy użyciu Tapatalka
[Samsung Galaxy Nexus] metalspring:
You mean why did he release his source after all this time? He probably wanted to be allowed to post new kernels for other devices, which the mods probably wouldn't allow if he never updated his tuna source... (Since its a violation of gpl to not have up to date source)
[Samsung Galaxy Nexus] lollipop:
What about ext version? Thanks
[Samsung Galaxy Nexus] antonio8297:
I've an ext version but need test.

If you would test send me a pm.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] jhonnyx:
EXT version should run out of the box if you flash zImage via fastboot from the zip file.

---------- Post added at 10:07 AM ---------- Previous post was at 10:04 AM ----------

[MENTION=4562296]antonio8297[/MENTION] has delivered on time ;) I had the commits and got it booting but my source is not clean enough, you can check on my git sorry!
[Samsung Galaxy Nexus] antonio8297:
with the four commit by arter97 and your configuration in defconfig,works so good.
[Samsung Galaxy Nexus] antonio8297:
ext4 version tested:

http://www.mediafire.com/download/efow8cgdlqu2i6x/franco.Kernel-tuna-nightly-r396-ext4optimized.zip
[Samsung Galaxy Nexus] lollipop:
i use omnirom:

-with default FK kernel i get 9870 in antutu benchmark

-with this optimized version i get 12043
[Samsung Galaxy Nexus] jhonnyx:
And, in real life, how does the phone run? do you notice improvements or it's a placebo?
[Samsung Galaxy Nexus] lollipop:
Yes,it's no placebo.the phone is very smooth and responsive .you can try it!!!!
[Samsung Galaxy Nexus] jhonnyx:
I meant Franco vs optimized Franco. For me it's the same, that's why I was asking :(

Neverthless I'll give it a shot
[Samsung Galaxy Nexus] morfances:
I can use this on any 4.4.3 rom?
[Samsung Galaxy Nexus] antonio8297:
yes,i tried it on aosb.
[Samsung Galaxy Nexus] lollipop:
nooo, optimized FK is smoother and more responsive than default FK (about +2500 points benchmark)(is there someone who confirme that:confused:)

i use omni-4.4.3-20140609-maguro-NIGHTLY ,so maybe a problem with your rom
[Samsung Galaxy Nexus] pkgnex:
There's something wrong with your install or settings with the "default" kernel. I get ~12,100 antutu on it, and every other modified / optimized version I've tried to date. My settings aren't extreme either, I OC to only the 1305 level.
[Samsung Galaxy Nexus] jhonnyx:
Neh, nothing's wrong with the roms I flash ;)

Probably it's my lack of testing. But I don't notice difference between when antutu scores 10000 upwards. Feels smoother, but If you use FK 395 and the latest one, you should notice no difference over smoothness. Maybe some benchmark over disk can change, but FK is smooth always.
[Samsung Galaxy Nexus] sunscape:
FK is definitely the best I've tried. I think he's got it just about perfect minus any upcoming tweaks coming down the pipe. Personally I'm hoping for more f2fs fixes. A bunch are part of the recent 3.15 kernel.
[Samsung Galaxy Nexus] osm0sis:
The test builds still have the ever-controversial mpok commits in so there should at least be some benchmark improvements. Shrug.
[Samsung Galaxy Nexus] my573r10us:
is it fixed the reboot on boot problem (because of adaptive brightness)? i mean the ext4 test version
[Samsung Galaxy Nexus] osm0sis:
It's the latest commits, so CAB should be disabled by default. My hope was that would fix the spontaneous first boot lockscreen reboot issue. So you tell me? ;) :fingers-crossed:
[Samsung Galaxy Nexus] giorgis91:
What version can i use with carbon rom 4.4.3?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] antonio8297:
Or mine version or the fixed by osmosis.

CAB commit included.

Reading some pages of the thread i saw that the kernel need changes on selinux stats? If you tell me what i have to do i can do it and compile another version.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Ah I thought you did that. Oh well, no biggie. It just needs SELinux set Permissive to fix Wi-Fi Tethering on CM-tree based ROMs. Right now it's Enforcing.

I'm not 100% on the how but I think it's part of the command line when you build the zImage. Thanks for all the help! :D
[Samsung Galaxy Nexus] bsmitty83:
Add this to CONFIG_CMDLINE "androidboot.selinix=permissive"

Hack The Tuna
[Samsung Galaxy Nexus] antonio8297:
tomorrow i'll try it.

thanks
[Samsung Galaxy Nexus] hdoraemonk:
F2fs version stuck at Google logo, test with PA 4.4 (4.4.3), ext4 version ok.
[Samsung Galaxy Nexus] giorgis91:
Differences?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] antonio8297:
If you have a filesystem in ext4 is normal that f2fs bootloop.

Mine have the latest update from franco.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Soy_Filipo:
Has someone tried this kernel on shiny 4.4.3?
[Samsung Galaxy Nexus] garuhhh:
I did try it for day, maybe. Then I went back to the unmodified Franco r396, as I felt lag when scrolling while using that optimized version.

Maybe my experience was different, as I dirty flashed the ROM, and no issues so far.
[Samsung Galaxy Nexus] Soy_Filipo:
For some reason the only kernel that worked so far for me on shiny 4.4.3 has been the original on shiny, am I doing something wrong? I dirty flashed from 4.4.2
[Samsung Galaxy Nexus] aliesz:
No that is right rule. if you only want to upgrade 4.4.2 to 4.4.3 shiny rom and just wipe cache and wipe dalvik.
[Samsung Galaxy Nexus] pkgnex:
You must be doing something wrong... I've tried multiple different kernels (Franco, Fancy, Dirty-V) on Shiny 4.4.3 and all worked fine.

A clean flash always helps - especially when updating to a new android version (e.g. 4.4.2 to 4.4.3 or 4.2.2 to 4.3.1). Smaller build-number-only changes usually dirty flash fine (e.g. KXX#XX to kXX#YY, with no android version bump).
[Samsung Galaxy Nexus] Culex316:
A lot of apps force close with the latest CM11 M7 and r396. Must be CM changing things in the ramdisk.
[Samsung Galaxy Nexus] osm0sis:
r396 or r396-fixed? http://v.ht/osmod
[Samsung Galaxy Nexus] Culex316:
the original r396 released by franco himself and downloadable on page 1 of this thread, not any of the offshoots that have been posted since then.

I will give this one a try then after CWM finishes restoring my last build. :/ Thanks :)
[Samsung Galaxy Nexus] osm0sis:
Mine aren't offshoots, they're bugfix releases of the same official zImage with the updated ramdisk that will be in the next official release. ;)

Anyway it's based on the newer CM ramdisk from a couple months back, so let me know how it goes. :)
[Samsung Galaxy Nexus] Culex316:
Hey this version with the newer Ramdisk works perfectly on CM11 M7 so far!

You are a genius dude!
[Samsung Galaxy Nexus] hp13:
R394 is my favorite for 4.3 ROM.
[Samsung Galaxy Nexus] MarCus M.D:
where is it?
[Samsung Galaxy Nexus] jhonnyx:
on 1st post ;)
[Samsung Galaxy Nexus] hp13:
best kernel for it. fancy is another good contender along with trinity.

i've used mpokang v9,10 but i had sod with v10 so went back to franco for now
[Samsung Galaxy Nexus] MarCus M.D:
Currently I have version 3.96, 4.3 Jelly Bean. I would switch to the version 3.94 as recommended, how can I do?

"Kernel Emergency Settings Reset" from Osmosis to uninstall? Wipes?
[Samsung Galaxy Nexus] osm0sis:
It's a kernel. Just flash.
[Samsung Galaxy Nexus] pirigu:
hello guys a question ... use the rom shiny 4.4.4 release ... which kernel do you recommend? Thanks in advance
[Samsung Galaxy Nexus] osm0sis:
Going to go out on a limb here and suggest franco.Kernel. ;)
[Samsung Galaxy Nexus] pirigu:
[MENTION=1143630]osmosis[/MENTION] hahaha sorry but I expressed myself badly ... That release of the Franco Kernel do you recommend? the latest or an older one??
[Samsung Galaxy Nexus] osm0sis:
Ah haha. Latest is greatest like I explained a page ago. Read back for the link. :good: :)
[Samsung Galaxy Nexus] pirigu:
[MENTION=1143630]osmosis[/MENTION] thank you very much friendly as always
[Samsung Galaxy Nexus] giorgis91:
Optimized version works well also on 4.4.4
[Samsung Galaxy Nexus] Soy_Filipo:
I'm sorry to repeat myself, but is there an optimized version for Shiny 4.4.4? Care to post a link for it? [MENTION=4544860]osm0sis[/MENTION] Is that the optimized version for 4.4.4?
[Samsung Galaxy Nexus] osm0sis:
Kernel source/ramdisk didn't change with 4.4.4 so they all work, my fixed version has the newer ramdisk to avoid issues on CM-tree based ROMs (and is good for all), but optimized isn't from me. Search the thread for it. :good:
[Samsung Galaxy Nexus] Soy_Filipo:
My phone worked flawlessly with this kernel when I was on 4.4.2, but I dont know what happened after 4.4.3, it lags and on 3G the battery drains a lot faster, I even did a clean flash and installed everything all over again, I don't know if xposed has something to do with it :/
[Samsung Galaxy Nexus] osm0sis:
I'd say 4.4.3 happened, the kernel didn't change. :p
[Samsung Galaxy Nexus] Soy_Filipo:
Yeah I was actually thinking of downgrading to 4.4.2, is 4.4.4 ok?
[Samsung Galaxy Nexus] osm0sis:
Things are decent enough for me on Carbon. :good:
[Samsung Galaxy Nexus] poltor:
I'd like a version compatible with f2fs of this kernel. [MENTION=4544860]osm0sis[/MENTION] you can do something?
[Samsung Galaxy Nexus] osm0sis:
Nope. That requires some heavy commits. [MENTION=3292224]franciscofranco[/MENTION] will have to make that call for the official builds. [MENTION=4328678]metalspring[/MENTION] attempted to build his fork with f2fs at one point and couldn't get it to, but I know [MENTION=2088054]jhonnyx[/MENTION] and [MENTION=4562296]antonio8297[/MENTION] managed it somehow. Search back for their test builds. :good: :cowboy:
[Samsung Galaxy Nexus] Soy_Filipo:
Pardon my ignorance, but whats F2FS and why is so important? What are the benefits of it?
[Samsung Galaxy Nexus] quickdraw86:
http://en.m.wikipedia.org/wiki/F2FS

it can dramatically improve the speed of SD card and eMMc writing, and improve performance, in theory, if TRIM is working.
[Samsung Galaxy Nexus] Myster:
i am having severe problems with the last version of franco kernel application and color profiles

every time i reboot rgb resets to zero and barely can see
[Samsung Galaxy Nexus] PCWright86:
Had same problem, if you have color profile set on boot it will happen every time. My only way was to "speedily go into Franco app and unclick " set on boot " for colors. After phone boots you can load and apply your color profile manually.

Beamed from a KitKat injected with Franco goodness
[Samsung Galaxy Nexus] PetritH:
Charging stops at 99% anyone having this issue?
[Samsung Galaxy Nexus] quickdraw86:
If you use the FKU app, go to kernel in the side menu, and check to make sure that "battery life extender" isn't set to 99. It's also possible that your power consumption during charging is such that you can't reach a full charge... Hope that helps.
[Samsung Galaxy Nexus] PetritH:
Thanks for your reply.. battery life extender is 100% ofc.. also I wasn't playing with the phone it was just charging wifi-off and airplane mode on... I don't mind though its all good :)
[Samsung Galaxy Nexus] aliesz:
Is there any new version in planning?!
[Samsung Galaxy Nexus] Mademos:
This is still good for kernels with Franco gamma right? I'm on mako, so I hope I only need to edit the values to the profile I prefer and I'm good to go I hope.

Sent from my Nexus 4
[Samsung Galaxy Nexus] osm0sis:
Tuna is the same interfaces as always. I really doubt Fransisco will try and backport gamma to us.
[Samsung Galaxy Nexus] aliesz:
Can I install the r396 kernel on 4.3JB android?
[Samsung Galaxy Nexus] skulldreamz:
Yes, answer is in the 2nd sentence in the op. Next time read a little ;)
[Samsung Galaxy Nexus] aliesz:
Thanks [emoji4] but when I flashed it on my gnex with stock 4.3 ROM it was stopped in google logo.
[Samsung Galaxy Nexus] amigo061:
Can I install the r396 kernel on CM11 Snapshot M8?
[Samsung Galaxy Nexus] osm0sis:
Use the 4.3 version.

Try and let us know. It's easy to flash back if it doesn't work.
[Samsung Galaxy Nexus] hp13:
For me your r395 optimized version got stuck at Google logo. Using 4.3 ROM.

But r395 and 396 worked fine on it.
[Samsung Galaxy Nexus] aliesz:
Yes I Had installed r396 4.4 version. I changed it and it works fine.
[Samsung Galaxy Nexus] osm0sis:
Not mine, they were metalspring's. But yeah, the optimized versions used the KitKat ramdisk as stated in the posts for them. ;)