Apparently, the Oreo HAL doesn't like it:
E/BrcmNfcNfa(946): nfc_ncif_update_window: Unexpected call
E/BrcmNfcNfa(946): nfc_ncif_cmd_timeout
E/BrcmNfcJni(946): nfaDeviceManagementCallback: NFA_DM_NFCC_TIMEOUT_EVT; abort
E/BrcmNfcJni(946): nfaDeviceManagementCallback: crash NFC service
Let's just disable it, which shouldn't hurt things, as hammerhead uses
the same chip, with NFA_DM_PRE_DISCOVERY_CFG disabled.
Change-Id: I1085d41379c3be85dcffd189d7023fc1e48c4a82
Wraps our old API 1.0 sensors into API 1.3:
- fixes sensor flags and maxDelays
- adds batching support
- adds flush support (experimental, enabled by default)
Tested by running Android 8.1 CtsSensorTestCases, passing all tests.
Change-Id: I5aa66fa75f67f1775821975e1eab801d0ef42598
Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
After removing the prebuilt kernel headers, we need to include
the kernel headers from source to fix the build.
Change-Id: I0e7074076db50032862ae4d8f001580405e9cd99
Based on dmesg:
init: /init.duma.rc: 267: Unable to decode GID for 'qcom_oncrpc': getpwnam failed: No such file or directory
init: /init.duma.rc: 384: Unable to decode GID for 'qcom_diag': getpwnam failed: No such file or directory
Unfortunately, our camera blobs are too old to implement camera HAL 3.2
properly. These hacks fix most camera functionality with HAL 3.2, but
they're not exactly clean...
Some pieces are based on the hammerhead HAL.
This isn't passing CTS, but it's not too far away.
Sadly, in the foreseeable future, I won't have time to clean it up...
Change-Id: Iff4f0f25fe767e498db6e56fc2f47a13c4a97364
Signed-off-by: Daniel Jarai <jaraidaniel@gmail.com>
remove both avc encoder and avc decoder for flo
6d8ba49415
media: drop QCOM avc.secure decoder
This codec is broken and it doesn't seem to be used anymore since google moved to software widvine implentation, so let's get rid of it.
We need an enlarged system partition to fit even minimal gapps.
Flash a stock sized partition and resize to the actual partition
size before restoring gapps.
Change-Id: Id6d0d89fab5249f8e6b7eae9c1dd365f0357afed
* 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
The kernel does not support aio with ffs.
Set the property so adb/mtp know to use the compatible
functions, and the same while in recovery.
Bug: 37916658
Test: Use adb / use adb in recovery
Change-Id: Id35a05fcb9952dcf7239bd15a61cc620537419bc
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
followmsi
Ruchi Kandoi
D. Andrei Măceș
Daniel Jarai
Zhao Wei Liew
Ethan Chen
Alex Naidis
Den Kondakov
Vladimir Oltean
LuK1337
Emmett Tsai
JP Abgrall
Caio Schnepper
Bruno Martins
Lucas Dupin
Artem Borisov
Adrian DC
Jerry Zhang
Roshan Pius