Absolutely. It's device-independent and ROM-independent. It works at the Linux level, not Android.
lambgx02 can i host the apk in my dropbox account as mirror? i want to create the mirrors to the most important mods, roms and kernels.
It seems to work and the phone is responding very fast. But if I open the app again the button shows me off. Also I've cheked auto start at boot and rebooted, the button still shows off. Is it like that by design or something's wrong.
Sent from my SGH-I927
I got troubles. Using Terminal Emulator I got an error message when I type the 3rd line ("cp /mnt/sdcard/rngd /system/xbin"), it says: "sh: cp: not found"
busybox cp /mnt/sdcard/rngd /system/xbin
My device gets hot..like..super hot...can I unistall the apk to remove this effect?
Wasn't it easier to just link /dev/random to /dev/urandom?
Or MAKEDEV /dev/random with the same major/minor as /dev/urandom?
I know it's more destructive, but you wouldn't need to keep waking up the phone, thus it would consume less power.
My device gets hot..like..super hot...can I unistall the apk to remove this effect?
My tmobile g2 runs very very smooth man. Thanks. However, many of my apps are not working. Root explorer and Tomtom application simply hang. Also for Cache Cleaner NG, it just hangs at cleaning cache screen. I never had a problem before.
Just a heads up.
Hmm.. odd. Can you try turning the service off and launching those apps again? Then, service back on, re-launch, etc.
I disabled the service and rebooted. After reboot, I launched cache cleaner ng, root explorer, and superuser app and none of them would open.
I am cleaning the dalvik cache and cache. I am not worried at all if I have to format my phone. I just want to dig deeper to why it would affect the apps.
I will keep you up to date.
su
seeder
su
cd /sdcard/install
sh install.sh
su
cd /sdcard
sh uninstall.sh
watch -n 1 cat /proc/sys/kernel/random/entropy_avail
pgrep rngd
su
seeder
su
cd /sdcard/install
sh install.sh
su
cd /sdcard
sh uninstall.sh
busybox sysctl -e -w kernel.random.read_wakeup_threshold=128;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=256;
while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1;done
busybox sysctl -w kernel.random.read_wakeup_threshold=2048
echo 1366 > /proc/sys/kernel/random/read_wakeup_threshold
busybox sysctl -w kernel.random.read_wakeup_threshold=1366
busybox sysctl -e -w kernel.random.read_wakeup_threshold=1024;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=2048;
Ok, I have a question for the OP:
I would like to know your through process that led up to the development of this patch. Was this just instinct or did you have a hint? Did you use a profiler of some sort? I'm just incredibly curious how on earth you arrived at the 'problem' before developing your 'solution'!