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: I68a94f8f26b65ab383c37274e4f631227a3c7d5f
Signed-off-by: John Stultz <john.stultz@linaro.org>
This makes bionic and various art tools that compile/runs cpu-specific
code choose the kryo variant at runtime. It does not affect
build-time compilation.
Bug: 120773446
Test: bionic benchmarks with and without this change
Change-Id: I766f7bbd9f1fab35991c313da7bfad8563108ef8
Follow blueline which has not demonstrated any regressions
after switching to a generic arch variant.
Bug: 120773446
Test: make
Change-Id: If64385d968cb923177f74b03a94633f0dbf42fbb
Add zero clearing of allocated nmea buffer to ensure
the nmea string is null terminated.
Change-Id: I78e8b03bc7d0f9b69e1a51356da379a57a647cad
CRs-Fixed: 2041933
some msm8226 devices (like the grand 2 and the S5 Mini duos) supports full mdnie display capability, while other (like the s3 neo) not.
drop the livedisplay manifest entry to device specific tree so every device can enable the service that it suports
* Rationale: speed has a lot of dex code expansion, it uses more ram and space compared to quicken.
Using quicken for shared APKs on Go devices may save RAM.
Note that this is a trade-off: here we trade clean pages for dirty pages, extra cpu and battery.
That's because the quicken files will be jit-ed in all the processes that load of shared apk and the
code cache is not shared. Some notable apps that will be affected by this are gms and chrome.
As seen here : https://android.googlesource.com/platform/build/+/refs/tags/android-9.0.0_r48/target/product/go_defaults_common.mk#45
* 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
* Use speed profile services and wifi-service to reduce RAM and storage.
* Always preopt extracted APKs to prevent extracting out of the APK for gms modules
* Use a profile based boot image
Change-Id: I41bea46ded542b37910fef6a08e49a8ab70c7d2a
Signed-off-by: RenanQueiroz <queirozrrq@gmail.com>
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>
