Earlier, this used to be set from rmt_storage service with
sys_admin capability. But now, that capability is dropped
off and hence, set it here in init scripts.
Change-Id: Ie8a3895c2b63da35d78fb9e571d74b735c969520
The legacy time_daemon binary relied on the old Android alarm dri-
ver for setting RTC at bootup. Once /dev/alarm support was removed
we found that time cannot be restored properly, unless a data con-
nection was available for NTP sync.
However, the blob already has a fallback mechanism that relies on
settimeofday(), except that it could never work properly. While
time_daemon is started under UID/GID of root, it immediately drops
to system/net_raw, which is required for subsequent socket commu-
ications (e.g., QMI, modem, etc).
The issue was that any UID transition from root triggers the remo-
val of all thread capabilities, including CAP_SYS_TIME, required
for settimeofday() or other RTC adjustments. Thus, time_daemon was
edited to skip the internal set[gu]id() calls altoghether, in order
to use the new capabilities mechanism introduced with Oreo init.
Change-Id: I8a0e220b724234c26b99a09b7f54af7996129d67
Signed-off-by: D. Andrei Măceș <andrei@unlegacy-android.org>
Signed-off-by: RenanQueiroz <queirozrrq@gmail.com>
Audio calibration delta files folder created at
/data/misc/audio/acdbdata/delta.
Path changed to provide access to media server.
Added /data/audio/acdbdata/delta path also
for backward compatibility
Change-Id: I53031d1aecd3f12a15d76db417d7a8eafd80cf8b
Fatal logging feature is not applicable for LA.BR.1.2.9, disable
this feature from ini.
Change-Id: I4188900c1823a5efe466687cd7362ab369c1b4d6
CRs-Fixed: 2044606
* The creation of /data/misc/wifi and /data/misc/dhcp was moved long ago
to the core init.rc script. Moreover, /data/misc/wifi is deprecated
since wpa_supplicant now relies on /data/vendor/wifi.
Change-Id: Ic0a33af44ffe163d3dd06cebdc1e192dc9bcb11f
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
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
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 8974 targets
Change-Id: Iaa2a8a42e4e3fd941c5be0f8fa691245cdb429e9
* In the previous commit, I failed to note that TWRP
also needs the AIO property set, so append local path
to TARGET_RECOVERY_DEVICE_DIRS to make both Lineage
Recovery and TWRP happy.
Change-Id: Ie1d8dfa252dad02787544a73e9d4ee1d44d30dbf
* TARGET_USES_OVERLAY and USE_OPENGL_RENDERER are largely deprecated
* Don't set triple buffering, it introduces latency
* Don't use custom VSYNC offsets
Change-Id: If2892c83726c3558a96b28a8404f49982ebb9ba0
[haggertk: Only triple offset aspect of this change is relevant to
this device family]
* Several items merged globally caused duplicate definition of paths
that were previously labeled here.
This reverts commit 27afbf1dc6.
This reverts commit 7fb5a8c6cb.
This partially reverts commit bb196ad94b.
This partially reverts commit c39a735ab5.
Change-Id: I901e5aa78058e1a465f110cde31fb7d76eaf3d51
* This fixes the following error on camera-in-mediaserver devices:
E CameraService_proxy: Calling UID: 1013 doesn't match expected camera service UID!
Change-Id: I185e34e8983b286436bfc0fe36cfdf260ef78170
