am skip reason: Change-Id I09be1dc79b69caadd2a5468c4e6ed9c1efd76ffd with SHA-1 82cf1f1bb2 is in history
Change-Id: I2be922e38b47da0d0ad130c083d4358d41521801
am skip reason: Change-Id Ib7ba41f4da12c60658e938fa14c53ba37c74bd1a with SHA-1 83a02a7aaf is in history
Change-Id: I13e2d8944a719005503e74cb2053715f7e0b3993
am skip reason: Change-Id Id1b8f6073c98db36c0ac86a881e7220ecfd0a71f with SHA-1 e2a91ed317 is in history
Change-Id: I1e2c793549a28165dc30a5c5fac64977dde133df
Dumping android.hardware.tests.extension.vibrator was ommited
because of difference of module name across branch.
Bug: 153501107
Bug: 152655547
Test: m
Change-Id: Ia272ffa77add9ef0b02ee0a23fc2389ac69fa9aa
AIDL interfaces which are vintf-stable have to be frozen in release.
But these interfaces have been never frozen, so freeze them.
- android.hardware.power
- android.hardware.identity
- android.hardware.keymaster
- android.hardware.vibrator
- android.hardware.light
- android.hardware.tests.extension.vibrator
Bug: 153500421
Bug: 153500550
Bug: 153511407
Bug: 153500549
Bug: 153501107
Bug: 153501202
Test: m
Change-Id: I643c25fc695f9d1e874dcceb327d465c49e9cab6
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: I93fba2721695a14e0eb4a2173066ce132228b895
Merged-In: I93fba2721695a14e0eb4a2173066ce132228b895
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: If47c5982894dc99a7f2d1767d64be60b491842c7
Merged-In: If47c5982894dc99a7f2d1767d64be60b491842c7
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: Id167905590c0a596b0ed470ef668c47810966836
Merged-In: Id167905590c0a596b0ed470ef668c47810966836
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: Idb1c34df81674321911e4a85f9e862b539a3f30c
Merged-In: Idb1c34df81674321911e4a85f9e862b539a3f30c
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: Ia633e3a143b35626c59b2447c38c1710ee270f0c
Merged-In: Ia633e3a143b35626c59b2447c38c1710ee270f0c
Modify the name of the Surround View interface to match the one in VTS
and the one in the default implementation.
Bug: 150412555
Test: m -j
Change-Id: I36c2a9187ae0973444ce441bda09c31d9b73809d
am skip reason: Change-Id I562b4dc50765e953800a814a8fd84a01c1b9352b with SHA-1 ba894f81db is in history
Change-Id: If2b6bd01e241c30f0b56fe2ed21f3323760a8096
Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
Please expect to see a refactoring on a more robust and cleaner version
of the new filter tests the child CL.
Test: atest VtsHalTvTunerV1_0TargetTest on cf and vendor device
Bug: 150953857
Change-Id: I34fbb193d0208d19496f360d900ae5078ece2cc5
am skip reason: Change-Id I4ad91c99956525120549321d227aaf6864877c76 with SHA-1 3d0285b182 is in history
Change-Id: I5f3d6cdcc79a761e50873ec902a70f76076ee223
Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
