In Q, this looks like it's making the system wait for a
specific widevine service, which we don't have.
Removing this appears to make L3 start working again.
Change-Id: Ib410029519e1d3cb0f0f3a5aa553976b36bca8c3
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
* Switch to binderized HAL services as possible and update
HIDL manifest accordingly.
* Following considerations regarding those without any change:
- Sensors left out of the game because wouldn't work
otherwise.
Change-Id: Id50291488d655187aa013c51bdd6890dca010564
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
