Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
The reason these files are moved to /vendor/etc/init/hw and
not /vendor/etc/init is because 'init' scans the /vendor/etc/init folder
for vendor service .rc fragments to import. That would either result
in duplicate imports or out-of-order imports of these hardware
specific .rc files and that *may* have unintended consequences.
In order to preserve the current import order for MTP, we move all
hardware specific .rc files to /vendor/etc/init/hw which is not
autoscanned by init BUT leave the init.${ro.hardware}.rc (i.e.
init.qcom.rc in this case) in root for 'init' to find.
Signed-off-by: Joshua Primero <jprimero155@gmail.com>
Recent changes to adbd have enabled nonblocking_ffs by default.
These have seeminly uncovered some bad memory corruption in the
kernel ffs gadget driver on every kernel I've tried so far.
Unfortunately I've not been able to diagnose what is going wrong,
so for now, lets disable the nonblocking_ffs.
We still need to root cause the issue as its a problem even with
the mainline kernel on HiKey, so its likely a generic kernel issue.
Change-Id: I81ac10edf5ddf9040852a4cb1f0f07c4ca16ef67
Newer AOSP deprecates LOCAL_MODULE_TAGS := eng debug.
We now remove that and instead add the package to
PRODUCT_PACKAGES_ENG or PRODUCT_PACKAGES_DEBUG as applicable.
To ensure that we don't miss out on any package during this switch,
we add these explicitly, even though it might have been already
added under PRODUCT_PACKAGES at some other location.
Change-Id: Id1f94f34e100d616d91292efe514c201f7d24642
* The permissions were not set to 222 instead of 220,
thus introducing regular logs from libcutils:
"cutils-trace: Error opening trace file: Permission denied (13)"
* Refers to frameworks/native/cmds/atrace/atrace.rc
Change-Id: I236ea25d2f2068f9f86a43492807f5f05e92da96
This file is used by hciattach when turning on bluetooth,
and without correct permissions, MAC address will be wrong.
Change-Id: Ie700a4be1a6b83932a9cffac45cd63f179f3edda
Change permissions of AMR-NB device node and change owner
and group of AMR-WB node to fix failure in opening of these
nodes from OMX component.
CRs-Fixed: 2072938
Change-Id: I5508529726ce0a3b763ac1364960def32887c6a2
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
* 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
