The best part about squashing bugs is feeling their exoskeletons crunch and the juices squeeze out. I've squashed bugs relating to the device reporting the wrong BT MAC address (should fix BT tethering) and the video camera flash. Working on fixing the torch app (cuz I like it). Yes, I've been drinking. Thank you to anyone who has donated recently, I can now consume a bit of alcohol and somewhat escape the 2 extremely stressful jobs that I work at 65+ hours a week.
That said, to answer some FAQ's I'll answer this one time:
System and data partitions have been SWAPPED. The I500 has 2 internal memory chips. The OneNAND (that Samsung ships for system and other storage) and the eMMC (that Samsung ships for data and cache storage). The OneNAND is a total of 512mb and contains system, along with the kernel and recovery images, bootloaders, etc. The eMMC is ~1.5gb and is used for data storage. In the newest builds, system is now stored on the eMMC, data is stored on the OneNAND, and cache has been moved to /dev/block/mmcblk0p3 which is a previously unused (by us, used by Samsung/Vzw for their stupid paid apps like tetris and other bull****) that is on the eMMC. This eliminates the "lag" experienced in earlier builds due to the fact that write speeds on the OneNAND are extremely faster than write speeds on the eMMC (Samsung should've never shipped those stupid, ****ty-ass chips to begin with).
This means that with the bootloaders, kernel, etc there is only 468mb left for data storage, along with a ****load of extra storage available for system. This is bad due to the fact we have less data storage space, and good due to the fact the device now performs much better and future versions of android will have plenty of system space available to them. Just the upgrade from ICS to JB alone requires nearly an additional 100mb of space for system. If you're running low on data storage, either move apps to the sdcard, or if you're crafty enough, move certain apps to /system/app. Things like updated Google apps (Market, Maps, etc) are perfectly fine working from /system/app, and can conserve lots of space. Attemping to do other trickery like place certain chunks of data onto the eMMC without impacting performance is both difficult to maintain and a pain the ass to come up with anyways. It is what it is, and it'll stay that way.
If you're a user of BT tether, shoot me a PM, perhaps I'll send you a test kernel to see if tethering works now if I have the time to do so.