system-corennnn

Fork

Merge changes from topic 'enable_persist_kernel_log' into nyc-mr1-dev

* changes:
logcatd: trampoline persist.logd.logpersistd to logd.logpersistd
logcatd: add stop and clear actions
logcatd: Do not su for setprop
logcat: allow comma-separate list of buffers
logcat: clear when specifying file output
logcat: Adjust help to make it more meaningful

Fix permissions for /data/preloads

Default permission bits are 771. It causes permission denied errors when
MediaProvider tries to scan /data/preloads. We have to allow read for others.

Bug: 29940807
Change-Id: I45645cf1154501ccb64bef08b9ad7bf7709dfd8e

Merge branch 'android-ia' into marshmallow-x86

Fix adb protocol issue when missed a packet

When there is an issue, adb re-initializes the connection and if it
misses the first 24 bytes "CNXN" packet, it will read the 8 bytes "host::"
packet instead followed by the first 17 bytes of the "CNXN packet" leading
to a new connection error; it reinitializes then the connection but
reads again the "host::" packet sent by the host etc and infinitely.

The device is then show offline or not shown at all on the host.

Change-Id: I4720c9494c7bede79becd5e916de50ace2115021
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-19456
Signed-off-by: Jean-Christophe PINCE <jean-christophe.pince@intel.com>
Signed-off-by: Clement Calmels <clement.calmels@intel.com>
Reviewed-on: https://android.intel.com:443/468687

Create mixins configuration for app compatibility
enhancement feature

This feature is created for some cerner cases of
app compatibility issue. It's disabled by default.
To enable it, please add below lines to mixins.spec.
Currently, it aims to handle below issues:

1. All native libraries are put under assets directory.
Some apps put their libraries under the assets directory
in their APKs, instead of lib directory. It's not a
problem if the ABI of app libs is matched with platform
default ABI. But for apps with other ABIs, this feature
must be enabled to call native bridge for help.

Change-Id: I98ec4d47bee4596bfe0e9efd4cd0b6fe0c90fdf7
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-24196
Signed-off-by: jgu21 <jinghui.gu@intel.com>
Reviewed-on: https://android.intel.com:443/481103

fs_mgr: fix encryptable=footer support

If the userdata partition has the encryptable=footer fstab option,
fs_mgr must leave room for the crypt footer.

Upstream: https://android-review.googlesource.com/206992
Change-Id: Id07818c5d93aafc27577f72fb0a780f26db51b16
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-23540
Reviewed-on: https://android.intel.com:443/479471

healthd: only kick animation once for charger unplug case

After animation done for charger unplug case, healthd may still
receive some uevent before the shutdown action. This change will
make sure battery animation will not be kicked for multiple times

Change-Id: I1e419b10b195d6919b5d5a83c87c334306896c2c
Signed-off-by: yangx.d.liu <yangx.d.liu@intel.com>
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-21840
Reviewed-on: https://android.intel.com:443/477709

adb: fix klocwork isssue 'use of free memory possible'

Change-Id: I334076094c8bf9ab6c90bd170e141e190058ed72
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-18056
Signed-off-by: Du, Changbin <changbin.du@intel.com>
Reviewed-on: https://android.intel.com:443/463913

adb: sockets: fix race condition between input_thread and fdevent callback

The transport's input_thread clean up all of its sockets by
close_all_sockets function before it exit. All sockets's callback is
invoked by local_socket_event_func by fdevent thread(the main thread).

But there is no synchronization between these two thread. Missing
synchronization can cause crash or unexpected behaviour. So far has
observed two crash issue:
1. after close_all_sockets return, still has sockets pending. Then when
the pending sockets try to access the removed transport cause segment
fault.
2. calling the socket's close callback(local_socket_close) but a socket
has been destroied. This will access a freed memory.

Change-Id: I9787b9ca7949946e977e102812518799051b9c67
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-12574
Signed-off-by: Du, Changbin <changbin.du@intel.com>
Reviewed-on: https://android.intel.com:443/461670

adb: fix a spurious fatal condition

The fde may be removed just after rutern from select in fdevent_process
fucntion. This is not a fatal error but normal. So just igore the event
for this fde.

Change-Id: I08fca0c6e539755fbc15c82d46c6b3f3855a2f41
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-12574
Signed-off-by: Du, Changbin <changbin.du@intel.com>
Reviewed-on: https://android.intel.com:443/460314

adb: fdevent: add synchronization logic to avoid crash

The fdevent part didn't implemente any synchronization protection. This
could introduce race condition issues. Espacially when adb is used for
Android stress test, this will be a problem that can cause server side
crash.

Change-Id: I93c311ed62770afc3061ccb8b60a0abd09f7453d
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-12574
Signed-off-by: Du, Changbin <changbin.du@intel.com>
Reviewed-on: https://android.intel.com:443/460313

adb: fix 'adb wait-for-device' thread leak issue

After the "adb wait-for-device" command is killed, the thread created in
adb server doesn't exit and keep it there to monitor device. If keep
doing this(like a automation test tool), hundreds of threads will be
crated and make adb server crash with running out of resource.

Steps to reproduce the problem.
- run "adb -s xxxxx wait-for-device"
- use "pstree -p <pid-of-adb-server>" to check count of threads
- kill it by ctrl+C.
- use pstree check threads info.

Change-Id: I96599c7b43df1f5c92edd7065d562a1bb6bacb19
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-12574
Signed-off-by: Du, Changbin <changbin.du@intel.com>
Reviewed-on: https://android.intel.com:443/460212

adb host: add device state in "adb wait-for-*"

The current implementation of the host commands "adb wait-for-*" allows
to specify only the transport layer (local, usb or any).
This patch allows the specification of the expected device state
(bootloader, recovery, device or sideload), this is usefull for
scripting purposes.

Use case:
$ adb reboot sideload-auto-reboot
$ adb wait-for-usb-sideload && adb sideload package.zip

This is a port of: https://android-review.googlesource.com/#/c/184290

Change-Id: I56a64b2d0f089cf1eb77424956296d660132b629
Signed-off-by: Leo Sartre <leox.sartre@intel.com>
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-15622
Reviewed-on: https://android.intel.com:443/450503

core: Enable houdini to Support the apps which put all libs under assets dir.

1. Many apps in PRC market put all arm native libs under assets/ dir in
their APK, instead of lib/ dir.
Since Lollipop, PakcageManager needs clear ABI info during app
installation.
If the ABI is not supported, houdini has not chance to involve in.
For above kind of apps, houdini will not be loaded to help arm libs.
To support such kind of apps, we have to enable houdini even without
clear ABI info only for PRC market

2. Fix GTS case failure caused by above modification,
which enforce to set arm ABI for all pure java

NOTE: Must merged together with https://android.intel.com/449222

Change-Id: I6d8cd263e3463f8e938b30f27e5db414eb2c96e9
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-12442
Signed-off-by: jgu21 <jinghui.gu@intel.com>
Signed-off-by: Zhou,KaiX K <kaix.k.zhou@intel.com>
Reviewed-on: https://android.intel.com:443/449223

healthd: Add USB_TYPEC to power-supply type list

A new power-supply type is added in power-supply framework to
support USB_TYPEC. healthd needs to be updated to accomodate this type.

Change-Id: Ib69d82c3460433161e2955d50765caf18538bed1
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-6732
Signed-off-by: Pavan Kumar S <pavan.kumar.s@intel.com>
Reviewed-on: https://android.intel.com:443/374693
(cherry picked from commit 601a4014f44e581832cad2e8f49051c9a6b33e75)
Reviewed-on: https://android.intel.com:443/429348

Package Manager : optimization for ZipFileRO->NextEntry

In functions like findSurpportedAbi and CopyNativeLibraries, it using
ZipFileRO->NextEntry to get FileName of each file in package, and then find a
best ABI or do CRC checking for native libraries.

But in current implementation, NextEntry will read info from both CentralDirectoryRecord
and LocalFileHeader, to compare the filename, signature and so on to check the integrity.

But on platform that has bad "read" performance like Sofia 3GR, it cost too much
time reading infor from LocalFileHeader in each NextEntry, lead to so much time
scanning one package that contains dozens of binaries.

So add the NextEntryNoIntegrity API for such processing that just need a filename, like
use case mentioned above. But it might not trustable if package damaged or changed
unpredictable.

Together with patch in frameworks/base/

Change-Id: I915b60c4b3cfa9c17929b207149a03b73a197147
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-5845
Signed-off-by: Shuo Gao <shuo.gao@intel.com>
Signed-off-by: Johnson Z Wu <johnson.z.wu@intel.com>
Signed-off-by: taozha2x <taox.z.zhang@intel.com>
Reviewed-on: https://android.intel.com:443/427235

property_service: log pid,uid and gid of setprop client

When auditing setprop denials, it is often unclear of who the process is
in a multi-process domain. To help identify the invoker, log the pid, uid,
and gid of the caller.

Before:
avc: denied { set } for property=wifi.xxx ...

After:
avc: denied { set } for property=wifi.xxx pid=30691 uid=123 gid=345 ...

Upstreamed: https://android-review.googlesource.com/174062
Tracked-On: https://jira01.devtools.intel.com/browse/OAM-4996
Change-Id: I5cdcb3d18fbd52e0987b5e1497b9f6620c6c742a
Signed-off-by: William Roberts <william.c.roberts@intel.com>
Reviewed-on: https://android.intel.com:443/423303

Allow native bridge to work without a code cache

In isolatedProcess, the app_code_cache_dir is not needed
for native bridge. This commit allows native bridge to work
without a code cache in isolatedProcess.

Tracked-On: https://jira01.devtools.intel.com/browse/OAM-1596
Change-Id: I8580268d5ec6ca8d44e4500c3fafe10408e1e0d3
Signed-off-by: jgu21 <jinghui.gu@intel.com>
Reviewed-on: https://android.intel.com:443/406649

merge in nyc-mr1-release history after reset to nyc-mr1-dev

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb am: cb4d905c96 -s ours am: e467cced5c am: 174579d6ef am: a3a674ea10 am: ff716c73ea -s ours
am: 77374d698d

Change-Id: I9cdd6842033e57837a6466e8669aaa75f22af53e

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 36dd144367 am: 9048b3bb8e am: 6cb199bf4a -s ours am: 851f840835 am: be484f3f7b am: 1e1eae1992 am: 71908ef2f8 -s ours
am: be2e5ea5a9

Change-Id: I9916a033d3fa29d340ef75e5a7c866415e4ce517

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb am: cb4d905c96 -s ours am: e467cced5c am: 174579d6ef am: a3a674ea10
am: ff716c73ea -s ours

Change-Id: I50b3147d6d31c1b8fec7ae4601f72ab9ce71327b

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 36dd144367 am: 9048b3bb8e am: 6cb199bf4a -s ours am: 851f840835 am: be484f3f7b am: 1e1eae1992
am: 71908ef2f8 -s ours

Change-Id: I0dda3544e9c6c44b61cd088e1423d42af35ad0e0

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb am: cb4d905c96 -s ours am: e467cced5c am: 174579d6ef
am: a3a674ea10

Change-Id: I95414ed03014463d684b64c06b74a2a8616faaa2

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 36dd144367 am: 9048b3bb8e am: 6cb199bf4a -s ours am: 851f840835 am: be484f3f7b
am: 1e1eae1992

Change-Id: I2bd7a6994c5d426402ee9d3e2adcc16f603b7c62

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb am: cb4d905c96 -s ours am: e467cced5c
am: 174579d6ef

Change-Id: Ie3efaa41bacc640286a3aa6cfe353b16c707f15f

Merge \\\\\"DO NOT MERGE: debuggerd: verify that traced threads belong to the right process.\\\\\" into mnc-dev am: 73922b82ee am: 8a9e4369f6 am: ba143fd959 am: b1471215a8 -s ours
am: e11ffee38c

Change-Id: Id1459e5c49d640dfbc826e32e1081480353d31f7

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb am: cb4d905c96 -s ours
am: e467cced5c

Change-Id: Id5534fddb6ca8c237fbcfd310a6843f03c12a3d3

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 36dd144367 am: 9048b3bb8e am: 6cb199bf4a -s ours am: 851f840835
am: be484f3f7b

Change-Id: I1c9a4f7cdec227e78910678f05e6232a60f05bb1

DO NOT MERGE: debuggerd: verify that traced threads belong to the right process. am: 0528829b73 -s ours am: b9b6ec3644 am: 5920345eeb
am: cb4d905c96 -s ours

Change-Id: Ia99e7055a24da12133e48e03b466fe09ebcb811f