[Samsung Infuse 4G] Zen Arcade:
Note that there are actually two solutions in the OP now.

1 - the original tweak which installs and runs the rngd binary every time you boot.

2 - the zeppelinrox variation, which does not install any new software, but rather makes an adjustment to the read and write thresholds for filling the entropy pool via the standard method

The second, in my opinion, is the cleaner option as it does not involve running a third party app (source of which has not been posted, save for a patch file) which wakes up every second to jam bits into the entropy pool. I'm not sure option #1 offers a benefit over simply redirecting random to urandom (which some have suggested as an alternative).. it just pumps bits that will get discarded anyway and uses the same source (urandom).

The zeppelinrox option raises the floor on the minimum bits in the pool and should prevent locking due to read blocks on /dev/random. This solution just changes kernel parameters -it doesn't add files or muck with device redirection. It also preserves the higher-quality hardware randomness source that is standard in Android.

All this said, I have yet to see anything other than annecdotal evidence that the solution makes a difference. A source from the Android project indicated that there was a known bug in GB which was fixed later versions. I'm not ready to write it off as a placebo (as some have done without supplying evidence). I plan to test when I have some free time this weekend. Annecdotally :) it seems to me (on GB) that some apps are faster (i.e. maps), that I am seeing less lag events during routine activities like browsing the file system, and that battery life may be a trifle better (getting about 2% per hour now whereas it was 3% per hour prior to applying the zeppelinrox option). But this is just "snake oil" at present as I cannot present any real proof. BTW, I'm running the zepp option for "increase" at present.

As for the CWM flashables:

I've provided CWM flashables that have been tested to work on the Infuse4g for GB and are reported to work JB (I haven't tested the latter myself so I can't confirm). They use a generic mount command (main issue with the original CWM is that it assumes yaffs2 file system - this should work on any Infuse JB MTD roms, but defininitely not on GB, which is why I supplied the alternative). The generic mount command is not guaranteed to work on all phones - it is dependent on the existence of a /sbin/mount binary that will accept just two arguments to establish a mount specific to older Samsung phones like ours:

run_program("/sbin/mount", "/dev/block/stl9", "/system");

vs original command

mount("yaffs2", "MTD", "system", "/system");

Note that the former has a dependency on a specific device and a specific mount binary. The latter has a dependency on a specific file system and the availability of a fstab record which xrefs to the actual system device file.

This is the long way of saying that it's likely that none of the CWM zips out there, mine included, are going to work on all phones.

Best bet is to try on your phone and then check for the existence of the files. If they aren't there, you or a dev on your phone platform is going to have to modify the package.

How to check to see if the zip file worked (look for these files):

Option one:

/system/xbin/rngd

/system/etc/init.d/91RNGD

Option two:

/system/etc/init.d/09*Entropy* (* being used as a wildcard here)

How to check that either solution is actually operating as intended:

1 - open up a terminal emulator window on phone or use adb shell from PC

2 - run the following command:

while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1;done

3 - watch the number change as you do things on your phone (easier when connected via adb)... should be between 2000 and 4000 if the tweak is active, otherwise likely to never be greater than 500.