Age | Commit message (Collapse) | Author |
|
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.
https://android.googlesource.com/platform/frameworks/base/+/c78a463e875d91eae2cf256042fd99d130217c38
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
|
|
Wpa_supplicant's random pool is not necessary on Android. Randomness
is already provided by the entropymixer service which ensures
sufficient entropy is maintained across reboots. Commit b410eb1913
'Initialize /dev/urandom earlier in boot' seeds /dev/urandom with
that entropy before either wpa_supplicant or hostapd are run.
Bug: 34980020
Test: Use wifi and wifi tethering on 8996 targets
Change-Id: Ib5caf362bc939911b357db186a274957d3fbf186
(cherry picked from commit 1f2b2f3a780bb7a6ed489bf86e18e77382f37514)
|
|
Framework will now add interface to supplicant (via HIDL) when it
needs to control an interface, so don't specify them in the startup
params.
Bug: 69426063
Test: Device boots up and able to connect to wifi.
Change-Id: I817d28093f8b982e3806c212babd888c0f5eb7c0
|
|
Bug: 72394251
Test: Able to start supplicant from framework using
ISupplicant.getService()
Change-Id: I19b8434e7241b9028e7dc86316ec9d5512affcca
|
|
Treble compliance.
Bug: 70228425
Bug: 70393317
Test: complete wifi test in b/70393317
Test: Test wifi on Taimen and Sailfish
Test: verify sockets exist in /data/vendor/wifi/wpa/sockets
Change-Id: I0bfc3a351419f0a03498e79664949f353369bf1b
|
|
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
|
|
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
|
|
* Mounting /system and /vendor partitions is handled in kernel now,
however removing the entries from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
|
|
|
|
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
|
|
Change-Id: I211da5781d8c7a16199fd8a18e1b00cfc9e01944
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
|
|
* Clean up unused configs
Change-Id: I0aae320468796a67fc2110aef0b31c06da2314e3
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
|