Sent from my VS985 4G using XDA Premium 4 mobile app
I have read that, however despite that information I do perceive a difference and no its not a placebo. I understand that the professionals cannot substantiate a change. All that I can suggest is that anyone that has a complaint regarding the G3 and laggy behavior...give this a shot. If it doesn't work, chuck it....if it does great!
Understanding why is works? Hmm yeah Id love to know.
The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random… well… less random
I tried the symlink method and could not detect any appreciable change in load averages under otherwise similar usage scenarios. I cannot find evidence of access to the /dev/random file. I cannot find similar wait paths in the kernel code that accesses the entropy pool that is shared by /dev/(random/random). That leaves other kernel locking or blocking mechanisms (spinlocks?) if there really is a responsiveness boost. I haven't seen conclusive evidence either way, I am just trying to understand what would possibly influence responsiveness should this hack prove founded in data.
I'm sorry why no one is mentioning this, but the 'fix' involves running a daemon that writes to /dev/random every second. This daemon should affect the CPU freq governor and make the CPU run at higher clocks than a device without the daemon. This alone would account for the performance increase users claim to be experiencing.
I've played with CPU frequency governors in the past. Perception of lag is affected greatly by this.
The claims about the depleted entropy pool leading to lower performance are not substantiated. I am thinking that there shouldn't be such a huge dependency on /dev/random in Android to cause an appreciable performance difference.