Differences

This shows you the differences between two versions of the page.

--- playground:playground [2021/07/19 18:09]
wai
+++ playground:playground [2021/07/21 09:01] (current)
jason
@@ Line 1: / Line 1: @@
 ====== Android DVB Tuner Framework ======
+===== Important =====
+This information in this page relates to the first release of the DTVkit TunerHAL implementation. This is an alpha release and has primarily been tested using the Android emulator. The Android emulator has certain restrictions in that only H264 video is currently supported and audio is not supported for broadcast media formats. The release has been made available for members that want to experiment with the code at an early stage. The release makes use of a modified version of the Android 'TunerHAL' code that enables transport stream data to be read from a file. With this the DTVkit release can be run in the Android Emulator, it is then possible to 'tune' to the file source, receive SI/EPG information, decode video (H264), and change channel. The code base is currently being tested on reference hardware and will be updated in due course.
+=====Background=====
+Android 11 introduces a new hardware abstraction layer for tuner, demux and descrambler the TunerHAL. This enables the front-end hardware components to be accessed using standard Android APIs in a platform independent manner. Android 11 also introduces new 'passthrough' AV decoding which enables AV decoding to be performed by the secure video hardware of the platform under the control of the standard Android Media Framework APIs. By making use of both the TunerHAL and Android Media Framework APIs it is possible to create an Android integration of DVBcore that is platform independent. It will run on any Android platform that support the new TunerHAL APIs and is not specific to any one silicon platform. This makes it simpler to use the same instance of DVBcore across a range of Android devices.
 =====Overview=====
 The DTVKit Android Tuner HAL solution integrates DVBCore with Android using the Android TV Input Framework (TIF) and the Android Tuner Framework. By using the TIF and the Tuner Framework, manufacturers can provide a TV input source that new and existing apps, such as Live Channels, can use through a standard Android API.
 =====DTVKit Android Architecture=====
-{{:dtvkittunerhalarchnocas_1_.png?600|}}
+{{:playground:dtvkittunerhalarchnocas_1_.png?700|}}
 =====Input Source=====
@@ Line 77: / Line 86: @@
 =====Building DTVKit Android 11 TunerHAL=====
-The repository can be cloned from [[https://github.com/DTVKit/Android_11_TunerHAL|Github]]. This release of the tuner HAL implementation is for the emulator.
+The repository can be cloned from [[https://github.com/DTVKit/Android_11_TunerHAL|Github]]. This release of the Tuner HAL implementation is for the emulator.
 ====Build and installation====
 . Clone repo and copy ''default'' folder contents into ''$ANDROID_BUILD_TOP/hardware/interfaces/tv/tuner/1.0/default''
@@ Line 93: / Line 102: @@
 </code>
+====Run====
+This Tuner HAL implementation looks for TS files under ''/vendor'', every file must have a valid frequency as name. For example ''470000000.ts'' (frequency in Hz) for DVB-T.
 =====SELinux Configuration Android 11=====
 Android uses Security-Enhanced Linux (SELinux) to enforce mandatory access control (MAC) over all processes. SELinux operates in two modes:

DTVKit Wiki

User Tools

Site Tools

Differences

Page Tools