This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
* AOSP removed this as a platform-wide rule since it is "...not
present on Pixel devices". As it turns out, our RIL gets grumpy
and won't latch a data connection if it cannot open the device.
* own/mode aligned to AOSP values from before the change
* E RILD : ElapsedRealTime() Cannot open file /dev/alarm
* ref: LineageOS/android_system_core@16cdffe
Change-Id: Ib369e4b76653a412d75a3c8c37ee283f8c8e9239
