Our camera blobs trigger some checks for broken behavior (destroyed
mutex usage, invalid pthread usage) present in newer API levels.
Change-Id: I8705437e0a5c6d80b86748bff559ce1e8a7bf716
* Our camera requires 0x02000000U. Per headers from exynos5420,
this appears to be USAGE_PRIVATE_NONSECURE.
Change-Id: Ie5a8a46fef1c0f28ebd2cd3b3d29cc19763bc2a3
enable narrow search range for video encoding
Change-Id: Ica0de8c893fdabf1b4393abe72291814bb708f74
(cherry picked from commit 819706119048a5818560ff7dbd1cc5feb0229da0)
* Google has been tightening up mutexes by disallowing calling
pthread_mutex_destroy on an already destroyed mutex in P
* This normally isn't an issue, but Qualcomm, in their infinite
wisdom, decided to destroy a mutex in a loop in isp_module_stop_session
when they were freeing some related memory allocations
* This results in a SIGABRT in mm-qcamera-daemon from a
__fortify_fatal call in HandleUsingDestroyedMutex in libc
* To work around this, the CBNZ instruction (aka, the break condition)
in the loop was moved before the call to phtread_mutex_destroy so
that the during the 2nd (and final) iteration of the loop, it exits
*before* rather than *after* the calls to pthread_mutex_destroy
* ASM instructions:
- Before: https://gist.github.com/javelinanddart/9afdc8577134bf8ecd48b15213d66491
- After: https://gist.github.com/javelinanddart/789ba3bde8494ff4ba0b7967c93daa14
Change-Id: I36dfab9f3afb8c9e010da8c6b02c2d9eff856c07
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
The files in arm/arm64 are symlinks and pinning symlinks is not
supported. Pin the target vdex file intead.
Bug: 73990433
Test: manual
Change-Id: I313e1f53487c0a21b615f65dc64c21a1ecb4b7d5
Samsung 8976 targets are armv8 devices. Setting TARGET_2ND_ARCH_VARIANT
to armv8-a, instead of armv7-a-neon, can silence the related warning
during build.
Bug: 68012286
Change-Id: I18ae3aa985fd6bff11f043a155f3685d9f6644b8
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 8996 targets
Change-Id: Ib5caf362bc939911b357db186a274957d3fbf186
(cherry picked from commit 1f2b2f3a780bb7a6ed489bf86e18e77382f37514)
* We aren't building power.$(TARGET_BOARD_PLATFORM)
therefore there's no reason to sync this repository.
Change-Id: Icc2cff368c05ed3bf68e4c718dbcbcdab42244da
The wifi packet logging option has high overhead and several
security issues related to it. Also, packet logging has issues
when the device goes into low power mode and can cause connectivity
problems when the screen turns off. It is best to disable it.
Change-Id: Iac7bdb000c0e22ba9930365b6d8477b4c12a3248
The qcacld Qpower firmware feature may cause tcp resets while
the device is in sleep mode which indirectly causes random
wifi disconnects. Use the legacy powersave option instead.
Change-Id: Ic7f2e5f777fea083cb99ed9f2da7b6261fd953f0
* Apparently hwbinder causes issues with adaptive
brightness. Going back to passthrough seems to fix
this issue.
Change-Id: I47d60d2d7fb52b5001df8a0d385acddebaa0ec84
* This is required to properly apply the changes to the boot
and recovery images, as well as generating the right
recovery-from-boot patch file to allow auto updating of recovery
Change-Id: Ifaaead6d68aae115e8fb4b01ee50d09861e5df1c
* Mounting /system partition is handled in kernel now,
however removing the entry from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
LuK1337
Danny Baumann
Michael Bestas
dianlujitao
Ethan Chen
Kevin F. Haggerty
Bruno Martins
syphyr
Paul Keith
Jerry Zhang
Mathieu Chartier
Isaac Chen
Hung-ying Tyan
Roshan Pius
Jeff Vander Stoep
Etan Cohen
Lukas0610
Giuseppe Barillari
Sean McCreary