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
* Limits security exposure from shims
* As a bonus, we no longer need noatsecure
to make LD_SHIM_LIBS persist through services
Change-Id: I877192422062f3e59c81a7130ad1a2b4be5d1647
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.
Change-Id: I14531da05e2a3a256f734f8de96e1f1969c753f9
