[T-Mobile Samsung Galaxy S II SGH-T989] bmg002:
I'm having no unexpected issues with this ROM/Kernel pair. The normal vibration issue that seems to pop back up all the time for me (not for others, so thinking one of my config files is busted... ie my problem, not a rom/kernel issue), but is coming up MUCH less than previous versions of this ROM.

Only one little thing I found weird: if I turn on the battery bar, set it to center-mirrored with charging animation on, it fills up from center to the right side of the screen, the left side doesn't grow or really do anything so it looks weird. More of a cosmetic issue (and could be an issue with the per-app DPI stuff from xposed and not a ROM issue... I'm tempted to attribute it to that more than anything).

I miss the "default DPI' option available in PA-based ROMs, but this ROM is much more stable and I can live with out a default per-app DPI stuff. Just a quick config change to 1 program that I need to set up once and I'm good to go.

Thanks for the awesome ROM. It has become my DD since PACMan got too buggy for me (too many boot loops). May attempt PACMan again at a later date, but for now, this is my DD.

On a side note, I was checking my mount points and saw that a lot of them that I don't think should be changing after flashing have a lot of free space that could probably be tweaked (I don't want to tweak them as I don't want a brick and the Devs on this forum are much smarter than me in this area). But mounts like /firmware shouldn't really change much after initial flash, right? If so, I am using 21.4 MB out of 199.8 MB so I am really wasting 178.4 MB there. /system/etc/firmware/misc_mdm is using 23.7MB out of 199.8MB, and I am noticing that the 5 tempfs ones (/dev, /storage, /mnt/secure, /mnt/asec, /mnt/obb and /mnt/fuse) are all using nearly 0 bytes (/dev is using 48.0 KB) out of 393.9MB. Since these are tmpfs files, I THINK they are probably just sitting in RAM (right?) and thus shrinking them will muck the phone up bad and get a soft-brick, but the other 2 should be safe to shrink so we could grow a different partition (/data for example or make a new one for a swap file), right? It isn't much space, but having an extra 300 MB of RAM (swap file... not quite the same as RAM, but close) or for data would be awesome for our phones, eh?

And one last thing: looking through the init.d scripts, the new 50selinuxrelabel script looks like it should really be part of an install script not a "run at each boot" script, shouldn't it? Once restorecon is run on each of those folders one time, it should never need to be re-run unless something goes wrong and you should probably reflash at that point. Also, the 02_cache script looks to be broken (the CACHE_DIR line should be:

CACHE_DIR=(`busybox find /data/data -type d -iname cache -print`);

Putting the *'s around cache (as it is now) results in it looking for <something>cache<something>; when the folder name is cache it doesn't match *cache* as it would in windows (linux is more fussy that way). So it finds nothing... but at the same time, do we really want to clear out /data/data/*/cache at every boot? that seems like a slow and potentially dangerous solution... and 00_setpermissions looks like something that should only need to be run at install time not at every boot.

Just my 2 cents.