GitLab

Genrating 32bit and 64bit variant in local/tmp

Change-Id: Ia9a640eab5bfc428d00af4ae0ada6184d946108a

Bug: 22328419
Change-Id: I3521a246929c10dc1eb9c9dac75240197b5b0a40

Bug: 21989305
Bug: 22048934
Change-Id: I82c16c70a776e13b3365672b2820ee965525de9a
Signed-off-by: Thierry Strudel <tstrudel@google.com>

* commit 'c05f5e7a':
  mksquashfsimage.sh: Add forward slash for SRC_DIR

* commit '61cde7e4':
  mksquashfsimge.sh: Support creating a sparse image

Change-Id: Ibfa043e2a7400e659f0355bcd139352b02a058e9

* commit 'cc919ca1':
  mksquashfsimage.sh: Add forward slash for SRC_DIR

* commit 'eefe2f9e':
  mksquashfsimge.sh: Support creating a sparse image

* commit 'b4cf7b30':
  Add switches for compressor

There is a bug in mksquashfs that fails to interpret symlink dirs unless
they have a forward slash

Change-Id: I64df07d99858a792e1d7af5d11234fe8b75f91ae
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

There is a bug in mksquashfs that fails to interpret symlink dirs unless
they have a forward slash

Change-Id: I64df07d99858a792e1d7af5d11234fe8b75f91ae
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

Change-Id: Idc28996028e666f929c032e5380312b7b28faa91
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

Change-Id: Idc28996028e666f929c032e5380312b7b28faa91
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

* commit '720fd497':
  Introduce squashfs-utils that includes helper functions

* commit '802cb097':
  Introduce mksquashfsimage.sh

* commit '01e42b24':
  Introduce squashfs-utils that includes helper functions

Change-Id: I297321db3996d07e9eba3edc0b2837c8d221ab1a

For example: extracting filesystem size from superblock

Change-Id: I97c79d80ebb767a977c8ca27f7e0877b5ead8fdc
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

Change-Id: I2b916ef3ef60b40f506e1f1be59482f7b071cdb2
Signed-off-by: Mohamad Ayyash <mkayyash@google.com>

Change-Id: I182ee7f70c5a96bbcdb0fc9e35df67c45a937757

Bug: http://b/19483574

(cherry picked from commit ebb94682)

Change-Id: I2a00e1fb075131e7d7d1a45c196ab0ac414e39c0

For tools built for both host and device, only include if not host.

(cherry-picked from commit 6bc4a54f)

Change-Id: Ie102bd7575d2cf5eef3f95e6063c2970d143dac8

verify_boot_signature doesn't build on Mac currently.
Temporarily exclude it from Mac build.

Bug: 21669400
Change-Id: I7b978adafefb700d65f6fc10f69c949fce94c236

the activity name for chrome changed recently which broke
systemapps.sh for some devices/builds. This change removes
the dependance on the chrome activity name in  systemapps.sh

Change-Id: I7f194a5c60221650300b6ab0df526f5bdf4b7f79

Changes the wait time between apps. Example; "./systemapps.sh -W 1.2"

Change-Id: I3769aa93ebbcd129de2f3fa3df99720e1d83b2f9

- display frame latencies (90th/95th/99th) for recents and systemapps
- allow device type to be specified to capture
- workaround for am hang when starting chrome on volantis
- bullhead support for recentfling

New output of "recentfling.sh":

Fling recents...
Frames: 772 latency: 19/22/34 Janks: 131(16%)

New output of "systemapps.sh -T":

App      Start(ms) Iter(ms) Jank      Latency
gmail       1090    2168      69(72%) 65/75/88
hangouts    1757    2758      60(82%) 69/111/114
chrome         0     997      59(64%) 68/77/84
youtube     3533    4834     140(48%) 70/93/150
play        1868    3147      92(62%) 89/106/182
home           0    1125     210(15%) 62/84/129
TOTAL       8248   35052

Change-Id: If4fc94ab0188dae2afabfbf696be06b6ddf55ce1

In order to prevent this bug from happening, we must allow vold cryptfs
commands to complete while a long running mount is underway.

While waiting for vold to be changed to a binder interface, we will simply
create two listeners, one for cryptfs and one for everything else.

Bug: 19197175
Change-Id: Id87764ed68c169fc6b94ea4f4f7a51a7ec9c7564

(chery-picked from commit b01dc1c5)

Bug: 18151196

Change-Id: Icdb3d9afa1db125102d01cd06f45dbc99ca78021

(cherry-picked from commit 478a01d6)

As per discussion default permissions are the correct ones.
Note that since we use logon keys, they cannot be read outside
the kernel.

Note also that we limit who can read/write keys in selinux policy.

Bug: 18151196
Change-Id: I15dc0de92643ae1472b0cde79c464fb3e1a1d453