The previous impl keeps the demux and frontend mapping in the
Tuner implementation even the instance has been closed.
Clean up the mapping and the local vectors in the Tuner impl
when Demux or Frontend is closed.
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150952766
Change-Id: I2038e902ba7ab323c6dacc886ac6984ee7c475aa
For the APIs that have both 1.0 and 1.1 versions, the VTS 1.1
only tests the 1.1 version of them.
For example for getId in IFilter 1.0 and getId_64bit in IFilter 1.1,
the 1.1 VTS only tests the getId_64bit.
Test: atest VtsHalTvTunerV1_1TargetTest
Bug: b/159058358
Change-Id: Ibef0ef40c3d1fbb9ff034bfcabeb44663a444d23
This CL enables the android.hardware.tv.tuner@1.1-service
with the default implementation of Tuner HAL 1.1
The 1.0 Tuner HAL interface implementation are identical to the 1.0
default implementation.
The 1.1 new API implementation are added with *_1_1 suffix.
Note that we cast all the uint32_t id in the 1.0 Hal implementation
into uint64_t even calling the old 1.0 APIs. This makes sure
the 1.1 default implementation internally only record 64-bit ids.
Test: atest VtsHalTvTunerV1_1TargetTest
Bug: b/159058358
Change-Id: Ic506376e520f03235010bc503e337c02d5735ec3
The first feature to support in this new Tuner HAL is the 64-bit id.
In the current CL, we support Demux and Filter ids in 64-bit format.
More component ids will be suppored in 64-bit in the following CLs.
Test: atest VtsHalTvTunerV1_1TargetTest
Bug: b/159058358
Change-Id: If05eb9f0cd76935064b2e51ff3ff1a3a477e3bd1
parameterized tests.
This test can be disabled on the phone target once there is
a cuttlefish tv target enabled to run the test continuously.
The test will be removed from the exception list afterwards.
Test: make VtsHalTvTunerV1_0TargetTest
Bug: 161805444
Change-Id: I7a2ad0e8a43c6262628354be316c530ab00ac520
Merged-In: I7a2ad0e8a43c6262628354be316c530ab00ac520
parameterized tests.
This test can be disabled on the phone target once there is
a cuttlefish tv target enabled to run the test continuously.
The test will be removed from the exception list afterwards.
Test: make VtsHalTvTunerV1_0TargetTest
Bug: 161805444
Change-Id: I7a2ad0e8a43c6262628354be316c530ab00ac520
The previous implementation did not check some of the
Descrambler API test results to stop the test.
And the test itself was also implemented in a wrong way.
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150987138
Change-Id: Ie26db0ec1b231062d0314631eebec319382da1bc
(cherry picked from commit 6d774c89a1)
The previous implementation did not check some of the
Descrambler API test results to stop the test.
And the test itself was also implemented in a wrong way.
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150987138
Change-Id: Ie26db0ec1b231062d0314631eebec319382da1bc
HIDL libs are not necessarily part of VNDK now. Because some are
used by VNDK libs, they are still VNDK. But rest are now just
vendor-available.
.hidl_for_test files are also removed because they are used to exclude
test-purpose hidl libs from VNDK libs.
Instead, .hidl_for_system_ext files are added to tests/lazy to
distinguish them from others which are installed /system.
Bug: 143933769
Test: update-makefiles.sh && m com.android.vndk.current
Merged-In: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
Change-Id: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
(cherry picked from commit b0907a6bb8)
HIDL libs are not necessarily part of VNDK now. Because some are
used by VNDK libs, they are still VNDK. But rest are now just
vendor-available.
.hidl_for_test files are also removed because they are used to exclude
test-purpose hidl libs from VNDK libs.
Instead, .hidl_for_system_ext files are added to tests/lazy to
distinguish them from others which are installed /system.
Bug: 143933769
Test: update-makefiles.sh && m com.android.vndk.current
Change-Id: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
This CL also provides a new VTS case to test ES input stream.
Please see the test.es https://drive.google.com/file/d/13ZDT9uhEO1LXDT2GcOhB91iIK6m_KEER/view?usp=sharing
ES Format(all the numbers are in decimal):
1. First line is a general meta data to describe the whole file
m:meta data size in bytes, l:ES frame line count X, V:video raw data size
int bytes, A:audio raw data size in bytes, pv:video pid, pa:audio pid
2. The following X lines(equals to the ES frame line count) are the size/pts information
of the video or audio ES frames. Starting with v means video, a means
audio. They are printed in the same order as how they presented in the
original ts.
v, Len:current ES frame size in bytes, PTS: current ES frame PTS
3. After the X lines of ES frame descriptions, there are the video ES raw
data connected with the audio ES raw data.
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 159027928
Change-Id: I56bd799fd6eda867df54d593235510a5e4758257
/data directory is a proper place for test pusher to adb push the ts
during run time. It saves image size comparing to bundle the ts during
compiling.
Files under the /data directory could only be passed around by fd
instead of directly opening. This CL also changes the way the DVR VTS
reads the ts.
Also for virtual frontend, to read the shell data file, we need the
DVR playback to input the data when testing frontend.
This CL also changes the way default implementation reads the data -
from the dvr playback fmq.
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 153366959
Change-Id: I72a98e4c4c0328206da106fb1c3459745c1644b7
Note that this test also includes MediaCasService openSession test
to pass the session id as the key token to the IDescrambler
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150987138
Change-Id: Iacd4ad5fcd957a6e3bb4a5730337ecaa3adc0aa2
This CL fixes the following issues:
1. Modified some unnecessary or not proper debug msg in the VTS/Default
impl
2. Some incorrect VTS testing order
3. Added a flush test on Dvr status
4. Used a ts from Android aosp cts for testing
5. Changed the configuration to run with the new ts on cf
6. Fixed some deadlock and logic issues in the VTS/Default
implementation
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150989084
Bug: 153366959
Bug: 153367094
Change-Id: If7eb8534caff4fc11ac4e166ef5391e8f543408d
Note that this refactoring extracts two header files for
VtsHalTvTunerV1_0FrontendTest and VtsHalTvTunerV1_0TargetTest.
Test: atest VtsHalTvTunerV1_0FrontendTest/VtsHalTvTunerV1_0TargetTest
Bug: 150953857
Change-Id: Ie5f0dc4a9180ecc779004cb451a45ae54a6ea47c
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
Note that we are not testing them right now
Test entry will be implemented or uncomment in next Tuner develop phase
Test: cuttlefish + vendor device
Bug: 135708935
Change-Id: Iea72bd54c85105f74133c67433bd51f8fd07f28d
(cherry picked from commit fc7cc15ebb)
Note that other interface tests are comment out in this CL
and will be refactored and uncomment in the CL chains.
Test: cuttlefish atest + vendor device test
Bug: 135708935
Change-Id: If831219fc588827c9367a506ba7fe7c96bea0286
(cherry picked from commit a5d00e6498)
These values are specific to phase modulation in ISDB-S.
It's not general use case.
bug: 148110220
Test: Manual
Change-Id: If847ca6c31681b1fe9dd94512c41b194dba41127
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: I075670b64eebbbbd6a6ae0e84ad51bf1c6f5ba36
* changes:
Tuner HAL Demux Filter VTS
Tuner HAL Filter APIs default implementation
Add filter function to Demux interface and Add program info to Descrambler
* changes:
Tuner HAL VTS for Demux and Descrambler Interface.
Tuner HAL default implementation for Demux and Descrambler Interface.
Add Demux and Descrambler interface to Tuner HAL Test: Manual bug: 135709729
