Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
* RenderScript is deprecated on newer platforms and
is being officially replaced.
* On April 19, 2021, Google announced that RenderScript
will be deprecated in Android 12, and recommended
porting existing code to Vulkan.
https://android-developers.googleblog.com/2021/04/android-gpu-compute-going-forward.html
Change-Id: I19460ef266a646b046f1e7d2f0b4eab7c48ae536
* BOARD_HAVE_BLUETOOTH is uneeded.
* BOARD_HAVE_BLUETOOTH_QCOM is only important if
you build libbt-vendor which we don't.
Change-Id: Ib0465b3c0d5138a70cee6a3c3d5f08dd7ce9aa57
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: I670c8acd094090135515688c5f057c2cc08a083f
This makes the system image more generic. The intent is so to
add another set of flags to allow the vendor partition to compile with
more specific flags once the build system can support that.
Bug: 120773446
Test: make
Change-Id: I3c31669bf7e19504b802ec1db9283467418ed4bb
* Stop handling vendor mounting from kernel, first stage init is gonna
do that, together with system (which is now /system)
* Use correct mount flags coming from kernel dts
* Move system and vendor mount points to /dev/block/by-name/, we don't
have bootdevice symlink to that point in init
* Copy fstab to recovery for first stage init
Change-Id: Iaa0ecc3f13c3cfd3fe357ca509549d0f68a29cf0
Android moved to a versioned approach in R and vendorcompat libs were
still possible to build, but not anymore with the Android U release.
Change-Id: Ibe06bf8d22ab0ce24ac5d5d9f3394b8593ee46cb
So that /dev/block/by-name/ symlinks are created.
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I270c1899e4487ed5e7657038c4ed07e407476953
This HAL makes use of the sysfs attribute /sys/class/qcom-battery/restricted_charging
to control whether fast charging is allowed or not.
When fast charging is disabled (i.e. 1 is written to the sysfs
attribute), current is restricted to 1 A (the value at
/sys/class/qcom-battery/restricted_current, in uA).
This has been tested on the Nokia 6.1 (PL2); however, it should work
on other Nokia SDM660 devices as well since they share the same
kernel source.
Adapted from the work at android_hardware_samsung:
https://github.com/LineageOS/android_hardware_samsung/tree/lineage-20/hidl/fastcharge
FastCharge interface definition:
https://github.com/LineageOS/android_hardware_lineage_interfaces/tree/lineage-20.0/fastcharge/1.0
Change-Id: I78ce842ef6263c19088f29a40abfa1ef6534cc99
* So many people are doing _something_ that causes these to not
be labeled how we intend them too, no matter the restorecons,
no matter whatever-else we do, they find a way.
* I am tired of dealing with it and we allow neverallows anyway for
said restorecons, so merry chrismas DRG users.
* Also, validly allow hal_fingerprint_default to read default_prop.
Change-Id: I174f9c583eeba4bb249aa89c1802573ae95b48fc
