* This config needs to be modified for legacy devices. As
there is no easy way to split it, import it into device
tree and bind mount it instead.
* Head at android-10.0.0_r2
(3ac371484399da6efbd0c835aa461d3326263ab1).
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.
Signed-off-by: John Stultz <john.stultz@linaro.org>
Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
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.
rmt_storage should not be automatically killed by Android during
shutdown since it is needed to actually process the peripheral
shutdown
Change-Id: I58a29fe86955f0abad944727bb4208dad89f495d
Upstream does not use these settings
Fixes: "Revert "lowmemorykiller: adapt to vmpressure""
"Revert "lowmemorykiller: Introduce sysfs node for ALMK
and PPR adj threshold"
Change-Id: Ifa2a8b2aaa0ab9c6326ded570ccaf91c2ad5b8e1
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
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)
* 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
* This removes /system entry from fstab, since this partition
is now early-mounted and the fstab entry is specified in device tree.
* At the same time, also include a fully populated fstab, in order to avoid
build breakage while generating recovery updater scripts.
Change-Id: I8e558458b984e97a45a920c3751a6b7c3f2ebc5c
This will let the wifi hal run as "wifi" user and not need root
permissions to access this path for firmware reloads.
Bug: 33435250
Test: Compiles.
Change-Id: I84a38cea5e0f729147c3191c3485a3738d7838ef
aviraxp
npjohnson
ripee
Tri Vo
John Stultz
ArianK16a
Subbaraman Narayanamurthy
youngguo18
bgcngm
Bruce Levy
syphyr
Demon Singur
LuK1337
Jerry Zhang
Roshan Pius
Jeff Vander Stoep
Michael Bestas
Paul Keith
Abhishek Arpure
Alin Jerpelea
Luca Stefani
Rashed Abdel-Tawab
Christopher Wiley