DVD to MP3 Ripper 2.2.1 serial key or number
DVD to MP3 Ripper 2.2.1 serial key or number
VLC media player
 | |||||||||||||
 | |||||||||||||
| Developer(s) | VideoLAN | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Initial release | February 1, 2001; 19 years ago (2001-02-01)[1] | ||||||||||||
| Stable release(s)[±] | |||||||||||||
| |||||||||||||
| Repository |  | ||||||||||||
| Written in | Core: C GUI: C++ (with Qt), Objective-C (with Cocoa), Swift, Java Bundled Extensions: Lua[11] | ||||||||||||
| Operating system | Windows, Windows Phone, macOS, Linux, Android, Chrome OS, iOS, iPadOS, Apple TV, Tizen, OS/2,[12]Xbox One | ||||||||||||
| Platform | IA-32, x86-64, ARM, ARM64, MIPS, PowerPC | ||||||||||||
| Available in | 48 languages[13] | ||||||||||||
| Type | Media player | ||||||||||||
| License | GPL-2.0 with some libraries under LGPL-2.1[14][15] | ||||||||||||
| Website | videolan.org/vlc | ||||||||||||
VLC media player (previously the VideoLAN Client and commonly known as simply VLC) is a free and open-source, portable, cross-platformmedia player software and streaming mediaserver developed by the VideoLAN project. VLC is available for desktop operating systems and mobile platforms, such as Android, iOS, iPadOS, Tizen, Windows 10 Mobile and Windows Phone. VLC is also available on digital distribution platforms such as Apple's App Store, Google Play and Microsoft Store.
VLC supports many audio and video compression methods and file formats, including DVD-Video, video CD and streaming protocols. It is able to stream media over computer networks and to transcode multimedia files.[17]
The default distribution of VLC includes many free decoding and encoding libraries, avoiding the need for finding/calibrating proprietary plugins. The libavcodec library from the FFmpeg project provides many of VLC's codecs, but the player mainly[18] uses its own muxers and demuxers. It also has its own protocol implementations. It also gained distinction as the first player to support playback of encrypted DVDs on Linux and macOS by using the libdvdcss DVD decryption library, however this library is legally controversial and is not included in many software repositories of Linux distributions as a result.[19][20]
History[edit]
The VideoLan software originated as an academic project in 1996. VLC used to stand for "VideoLAN Client" when VLC was a client of the VideoLAN project. Since VLC is no longer merely a client, that initialism no longer applies.[21][22] It was intended to consist of a client and server to stream videos from satellite dishes across a campus network. Originally developed by students at the École Centrale Paris, it is now developed by contributors worldwide and is coordinated by VideoLAN, a non-profit organization. Rewritten from scratch in 1998, it was released under GNU General Public License on February 1, 2001, with authorization from the headmaster of the École Centrale Paris. The functionality of the server program, VideoLan Server (VLS), has mostly been subsumed into VLC and has been deprecated.[23] The project name has been changed to VLC media player because there is no longer a client/server infrastructure. The cone icon used in VLC is a reference to the traffic cones collected by École Centrale's Networking Students' Association.[24] The cone icon design was changed from a hand drawn low resolution icon[25] to a higher resolution CGI-rendered version in 2006, illustrated by Richard Øiestad.[26]
In 2007 the VLC project decided, for license compatibility reasons, not to upgrade to just released GPLv3.[27] After 13 years of development, version 1.0.0 of VLC media player was released on July 7, 2009.[28] Work began on VLC for Android in 2010 and it has been available for Android devices on the Google Play store since 2011.[29][30] In September 2010, a company named "Applidium" developed a VLC port for iOS under GPLv2 with the endorsement of the VLC project, which was accepted by Apple for their App Store.[31][32] In January 2011, after VLC developer Rémi Denis-Courmont's complaint to Apple about the licensing conflict between the VLC's GPLv2 and the App store's policies,[33] the VLC had been withdrawn from the Apple App Store by Apple.[34] Subsequently, in October 2011 the VLC authors began to relicense the engine parts of VLC from the GPLv2 to the LGPLv2 to achieve better license compatibility, for instance with the Apple App Store.[35][36][37][38] In July 2013 the VLC application could be resubmitted to the iOS App Store under the Mozilla Public License.[39] Version 2.0.0 of VLC media player was released on February 18, 2012.[15][40] The version for the Windows Store was released on March 13, 2014. Support for Windows RT, Windows Phone and Xbox One were added later.[41] As of 2016[update] VLC is the third in the sourceforge.net overall download count,[42] and there have been more than 3 billion downloads.[43]
Version 3.0 was in development for Windows, Linux and macOS since June 2016[44] and released in February 2018.[45] It contains many new features including Chromecast output support (except subtitles[46]), hardware-accelerated decoding, 4K and 8K playback, 10-bit and HDR playback, 360° video and 3D audio, audio passthrough for HD audio codecs, Blu-ray Java menu support, and local network drive browsing.
In December 2017 the European Parliament approved a budget that funds a bug bounty program for VLC to improve the EU's IT infrastructure.[47]
Release history[edit]
| Version[48] | Codename | Release date |
|---|---|---|
| 1.0.0 | Goldeneye | 2009-07-06 |
| 1.0.1 | 2009-07-26 | |
| 1.0.2 | 2009-09-19 | |
| 1.0.3 | Goldeneye | 2009-10-30 |
| 1.0.4 | 2009-12-10 | |
| 1.0.5 | Goldeneye | 2010-01-28 |
| 1.0.6 | 2010-04-21 | |
| 1.1.0[49][50] | The Luggage | 2010-06-21 |
| 1.1.1[51] | 2010-07-20 | |
| 1.1.2 | 2010-07-21 | |
| 1.1.3 | 2010-08-18 | |
| 1.1.4 | 2010-08-27 | |
| 1.1.5 | 2010-11-13 | |
| 1.1.6 | 2011-01-23 | |
| 1.1.7 | 2011-01-30 | |
| 1.1.8 | 2011-03-23 | |
| 1.1.9 | 2011-04-12 | |
| 1.1.10 | 2011-06-07 | |
| 1.1.11 | 2011-07-14 | |
| 1.1.12 | 2011-10-06 | |
| 1.1.13 | 2011-12-20 | |
| 2.0.0 | Twoflower | 2012-02-17 |
| 2.0.1 | 2012-03-16 | |
| 2.0.2 | 2012-06-27 | |
| 2.0.3 | 2012-07-18 | |
| 2.0.4 | 2012-10-15 | |
| 2.0.5 | 2012-12-11 | |
| 2.0.6 | 2013-04-07 | |
| 2.0.7 | 2013-05-26 | |
| 2.0.8 | 2013-07-25 | |
| 2.0.9 | 2013-10-23 | |
| 2.0.10 | 2014-02-21 | |
| 2.1.0 | Rincewind | 2013-07-23 |
| 2.1.1 | 2013-11-11 | |
| 2.1.2 | 2013-12-09 | |
| 2.1.3 | 2014-01-29 | |
| 2.1.4 | 2014-02-21 | |
| 2.1.5 | 2014-06-06 | |
| 2.1.6 | 2015-02-26 | |
| 2.2.0 | Weatherwax | 2015-02-27 |
| 2.2.1 | Terry Pratchett | 2015-04-13 |
| 2.2.2 | Weatherwax | 2016-01-20 |
| 2.2.3 | 2016-04-26 | |
| 2.2.4 | 2016-06-01 | |
| 2.2.5 | 2017-02-03 | |
| 2.2.6 | Umbrella | 2017-05-24 |
| 2.2.7 | 2017-11-16 | |
| 2.2.8 | Weatherwax | 2017-11-21 |
| 3.0.0 | Vetinari | 2018-02-08 |
| 3.0.1 | 2018-02-26 | |
| 3.0.2 | 2018-04-19 | |
| 3.0.3 | 2018-05-28 | |
| 3.0.4 | 2018-08-09 | |
| 3.0.5 | 2018-10-19 | |
| 3.0.6 | 2019-01-10 | |
| 3.0.7 | 2019-05-24 | |
| 3.0.8[52] | 2019-08-14 |
Design principles[edit]
Modular design[edit]
VLC, like most multimedia frameworks, has a very modular design which makes it easier to include modules/plugins for new file formats, codecs, interfaces, or streaming methods. VLC 1.0.0 has more than 380 modules.[53] The VLC core creates its own graph of modules dynamically, depending on the situation: input protocol, input file format, input codec, video card capabilities and other parameters. In VLC, almost everything is a module, like interfaces, video and audio outputs, controls, scalers, codecs, and audio/video filters.
Interfaces[edit]
The default GUI is based on Be API on BeOS, Cocoa for macOS, and Qt 4 for Linux and Windows, but all give a similar standard interface. The old default GUI was based on wxWidgets on Linux and Windows.[54] VLC supports highly customizable skins through the skins2 interface,[55] and also supports Winamp 2 and XMMS skins.[56] Skins are not supported in the macOS version.[57] VLC has ncurses,[58] remote control,[59] and telnet[60]console interfaces. There is also an HTTP[61] interface, as well as interfaces for mouse gestures and keyboard hotkeys.[62]
Features[edit]
Because VLC is a packet-based media player it plays almost all video content. Even some damaged, incomplete, or unfinished files can be played, such as those still downloading via a peer-to-peer (P2P) network. It also plays m2t MPEG transport streams (.TS) files while they are still being digitized from an HDV camera via a FireWire cable, making it possible to monitor the video as it is being played. The player can also use libcdio to access .iso files so that users can play files on a disk image, even if the user's operating system cannot work directly with .iso images.
VLC supports all audio and video formats supported by libavcodec and libavformat. This means that VLC can play back H.264 or MPEG-4 Part 2 video as well as support FLV or MXF file formats "out of the box" using FFmpeg's libraries. Alternatively, VLC has modules for codecs that are not based on FFmpeg's libraries. VLC is one of the free software DVD players that ignore DVD region coding on RPC-1 firmware drives, making it a region-free player. However, it does not do the same on RPC-2 firmware drives, as in these cases the region coding is enforced by the drive itself, however, it can still brute-force the CSS encryption to play a foreign-region DVD on an RPC-2 drive. VLC media player has some filters that can distort, rotate, split, deinterlace, and mirror videos as well as create display walls or add a logo overlay. It can also output video as ASCII art.
VLC media player can play high-definition recordings of D-VHS tapes duplicated to a computer using CapDVHS.exe. This offers another way to archive all D-VHS tapes with the DRM copy freely tag. Using a FireWire connection from cable boxes to computers, VLC can stream live, unencrypted content to a monitor or HDTV. VLC media player can display the playing video as the desktop wallpaper, like Windows DreamScene, by using DirectX, only available on Windows operating systems. VLC media player can record the desktop and save the stream as a file, allowing the user to create screencasts.[63][64][65] On Microsoft Windows, VLC also supports the Direct Media Object (DMO) framework and can thus make use of some third-party DLLs (Dynamic-link library). On most platforms, VLC can tune into and view DVB-C, DVB-T, and DVB-S channels. On macOS the separate EyeTV plugin is required, on Windows it requires the card's BDA Drivers.
VLC can be installed or run directly from a USB flash drive or other external drive. VLC can be extended through scripting; it uses the Lua scripting language.[66][67] VLC can play videos in the AVCHD format, a highly compressed format used in recent HD camcorders. VLC can generate a number of music visualization displays. The program is able to convert media files into various supported formats.[68]
Operating system compatibility[edit]
VLC media player is cross-platform, with versions for Windows, Android, Chrome OS, BeOS, Windows Phone, iOS, iPadOS, macOS, tvOS, OS/2, Linux, and Syllable.[12] However, forward and backward compatibility between versions of VLC media player and different versions of OSs are not maintained over more than a couple or so generations.[69]64-bit builds are available for 64-bit Windows.[70]
Windows 8 and 10 support[edit]
The VLC port for Windows 8 and Windows 10 is backed by a crowdfunding campaign on Kickstarter to add support for a new GUI based on Microsoft's Metro design language, that will run on the Windows Runtime. All the existing features including video filters, subtitle support, and an equalizer are present in Windows 8.[71] A beta version of VLC for Windows 8 was released to the Microsoft Store on March 13, 2014.[72] A universal app was created for Windows 8, 8.1, 10, Windows Phone 8, 8.1 and Windows 10 Mobile.
Android support[edit]
In May 2012, the VLC team stated that a version of VLC for Android was being developed.[73] The stable release version 1.0 was made available on Google Play on December 8, 2014.[74]
Use of VLC with other programs[edit]
Bindings[edit]
Several APIs can connect to VLC and use its functionality:
Browser plugins[edit]
On Windows, Linux, macOS, and some other Unix-like platforms, VLC provides an NPAPI plugin, which enables users to view QuickTime, Windows Media, MP3, and Ogg files embedded in websites without using additional software. It supports many web browsers including Firefox, Mozilla Application Suite, and other Netscape plug-in based browsers; Safari, Chrome, and other WebKit based browsers; and Opera. Google used this plugin to build the Google Video Player web browser plugin before switching to use Adobe Flash.[84]
Starting with version 0.8.2, VLC also provides an ActiveX plugin, which lets people view QuickTime (MOV), Windows Media, MP3, and Ogg files embedded in websites when using Internet Explorer.
Applications that use libVLC[edit]
VLC can handle some incomplete files and in some cases can be used to preview files being downloaded. Several programs make use of this, including eMule and KCeasy. The free/open-source Internet television application Miro also uses VLC code. HandBrake, an open-source video encoder, used to load libdvdcss from VLC Media Player.[85] A program named Livestreamer may utilize VLC as its main video stream player and will not work without one. Easy Subtitles Synchronizer, a freeware subtitle editing program for Windows, uses VLC to preview the video with the edited subtitles.
Format support[edit]
Input formats[edit]
VLC can read many formats, depending on the operating system it is running on, including:[86]
- Container formats: 3GP,[a]ASF, AVI, DVR-MS, FLV, Matroska (MKV), MIDI,[b]QuickTime File Format, MP4, Ogg, OGM, WAV, MPEG-2 (ES, PS, TS, PVA, MP3), AIFF, Raw audio, Raw DV, MXF, VOB, RM, Blu-ray, DVD-Video, VCD, SVCD, CD Audio, DVB, HEIF, AVIF
- Audio coding formats: AAC, AC3, ALAC, AMR,[a]DTS, DV Audio, XM, FLAC, It, MACE, MOD, Monkey's Audio, MP3, Opus,[87]PLS, QCP, QDM2/QDMC, RealAudio,[c]Speex, Screamtracker 3/S3M, TTA, Vorbis, WavPack,[d]WMA (WMA 1/2, WMA 3 partially).[88]
- Capture devices: Video4Linux (on Linux), DirectShow (on Windows), Desktop (screencast), Digital TV (DVB-C, DVB-S, DVB-T, DVB-S2, DVB-T2, ATSC, Clear QAM)
- Network protocols: FTP, HTTP, MMS, RSS/Atom, RTMP, RTP (unicast or multicast), RTSP, UDP, Sat-IP, Smooth Streaming
- Network streaming formats: Apple HLS, Flash RTMP, MPEG-DASH, MPEG Transport Stream, RTP/RTSP ISMA/3GPP PSS, Windows Media MMS
- Subtitles: Advanced SubStation Alpha, Closed Captions, DVB, DVD-Video, MPEG-4 Timed Text, MPL2,[e]OGM, SubStation Alpha, SubRip, SVCD, Teletext,[e]Text file, VobSub, WebVTT, TTML
- Video coding formats: Cinepak, Dirac, DV, H.263, H.264/MPEG-4 AVC, H.265/MPEG HEVC,[89]AV1, HuffYUV, Indeo 3,[f]MJPEG, MPEG-1, MPEG-2, MPEG-4 Part 2, RealVideo 3&4,[g]Sorenson, Theora, VC-1,[h]VP5,[h]VP6,[h]VP8, VP9,[89]DNxHD, ProRes and some WMV.
- Digital Camcorder formats: MOD and TOD via USB.
Output formats[edit]
VLC can transcode or stream audio and video into several formats depending on the operating system, including:
- Container formats: ASF, AVI, FLAC, FLV,[e]Fraps,[e]Matroska, MP4, MPJPEG, MPEG-2 (ES, MP3), Ogg, PS, PVA, QuickTime File Format, TS, WAV, WebM
- Audio coding formats: AAC, AC-3, DV Audio, FLAC, MP3,[i]Speex, Vorbis
- Streaming protocols: HTTP, MMS, RTSP, RTP, UDP
- Video coding formats: Dirac, DV, H.263, H.264/MPEG-4 AVC, H.265/MPEG-H HEVC, MJPEG, MPEG-1, MPEG-2, MPEG-4 Part 2, Theora, VP5,[h]VP6, VP8,[h]VP9[89]
Legality[edit]
The VLC media player software installers for the macOS platform and the Windows platform include the libdvdcss DVD decryption library, even though this library may be legally restricted in certain jurisdictions.[90][91]
United States[edit]
The VLC media player software is able to read audio and video data from DVDs that incorporate Content Scramble System (CSS) encryption, even though the VLC media player software lacks a CSS decryption license.[92] The unauthorized decryption of CSS-encrypted DVD content or unauthorized distribution of CSS decryption tools may violate the US Digital Millennium Copyright Act.[92] Decryption of CSS-encrypted DVD content has been temporarily authorized for certain purposes (such as documentary filmmaking that uses short portions of DVD content for criticism or commentary) under the Digital Millennium Copyright Act anticircumvention exemptions that were issued by the US Copyright Office in 2010.[93] However these exemptions do not change the DMCA's ban on the distribution of CSS decryption tools; including those distributed with VLC.[94]
See also[edit]
Notes[edit]
- ^ abUntil VLC 1.1.0, to use AMR as audio codec, VLC and FFmpeg had to be compiled with AMR support. This is because the AMR license is not compatible with the VLC license.
- ^This feature needs sound fonts and might not work on every OS.
- ^RealAudio playback is provided through the FFmpeg library which only supports the Cook (RealAudio G2 / RealAudio 8) decoder at the moment.
- ^As of 2010[update], only supported in mono and stereo, so no multichannel support.
- ^ abcdThis is present in 0.9.0 and newer version.
- ^Indeo 4 and 5 codecs are not supported
- ^from 0.9.9 and over
- ^ abcdeThis is from the 0.8.6 version.
- ^VLC must be compiled with mp3lame support
References[edit]
- ^"15 years of VLC and VideoLAN". Jean-Baptiste Kempf. Retrieved April 15, 2017.
- ^"VLC 3.0.11 Vetinari - VideoLAN". www.videolan.org. Retrieved June 16, 2020.
- ^http://www.videolan.org/news.html
- ^"VLC for Android - Apps on Google Play". play.google.com. Retrieved June 16, 2020.
- ^"Index of /videolan/vlc-android/". get.videolan.org. Retrieved June 16, 2020.
- ^"VLC - Chrome Web Store". chrome.google.com. VideoLAN. December 23, 2015. Retrieved October 4, 2017.
- ^"VLC for Mobile". apps.apple.com. Retrieved June 16, 2020.
- ^"Official Download of VLC media player for Windows Store - VideoLAN". www.videolan.org. VideoLAN. July 20, 2018. Retrieved August 7, 2018.
- ^"Get VLC - Microsoft Store". www.microsoft.com. VideoLAN. July 20, 2018. Retrieved August 7, 2018.
- ^"Official Download of VLC media player for Windows Phone - VideoLAN". www.videolan.org. VideoLAN. July 20, 2018. Retrieved August 7, 2018.
- ^https://addons.videolan.org/p/1154045/
- ^ ab"Official Downloads of VLC media player". Videolan.org. Retrieved January 2, 2012.
- ^"VideoLAN internationalization". VideoLAN. Retrieved April 15, 2017.
- ^"VLC engine relicensed to LGPL". VideoLAN. December 21, 2011. Retrieved April 15, 2017.
- ^ ab"VLC reaches 2.1.2". VideoLAN. December 10, 2013. Retrieved April 15, 2017.
- ^"VLC media player, Index of /testing/". Retrieved February 9, 2018.
- ^"VLC Features". VideoLAN. Retrieved April 15, 2017.
- ^"Contrib Status - VideoLAN Wiki". wiki.videolan.org. Retrieved July 15, 2017.
- ^"libdvdcss - VideoLAN". www.videolan.org. Retrieved February 8, 2020.
- ^Hoffman, Chris. "Why Watching DVDs on Linux is Illegal in the USA". How-To Geek. Retrieved February 8, 2020.
- ^Kempf, Jean-Baptiste (November 23, 2006). "VLC Name". Yet another blog for JBKempf. Retrieved April 15, 2017.
- ^VideoLAN Team. "Intellectual Properties". VideoLAN Wiki. Retrieved April 15, 2017.
- ^"The cross-platform streaming solution". VideoLAN
Android 11 Compatibility Definition
1. Introduction
This document enumerates the requirements that must be met in order for devices to be compatible with Android 11.
The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in RFC2119.
As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 11. A “device implementation” or “implementation" is the hardware/software solution so developed.
To be considered compatible with Android 11, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference.
Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations.
For this reason, the Android Open Source Project is both the reference and preferred implementation of Android. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the “upstream” source code available from the Android Open Source Project. While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document.
Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK’s documentation. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition.
1.1 Document Structure
1.1.1. Requirements by Device Type
Section 2 contains all of the requirements that apply to a specific device type. Each subsection of Section 2 is dedicated to a specific device type.
All the other requirements, that universally apply to any Android device implementations, are listed in the sections after Section 2. These requirements are referenced as "Core Requirements" in this document.
1.1.2. Requirement ID
Requirement ID is assigned for MUST requirements.
- The ID is assigned for MUST requirements only.
- STRONGLY RECOMMENDED requirements are marked as [SR] but ID is not assigned.
- The ID consists of : Device Type ID - Condition ID - Requirement ID (e.g. C-0-1).
Each ID is defined as below:
- Device Type ID (see more in 2. Device Types)
- C: Core (Requirements that are applied to any Android device implementations)
- H: Android Handheld device
- T: Android Television device
- A: Android Automotive implementation
- W: Android Watch implementation
- Tab: Android Tablet implementation
- Condition ID
- When the requirement is unconditional, this ID is set as 0.
- When the requirement is conditional, 1 is assigned for the 1st condition and the number increments by 1 within the same section and the same device type.
- Requirement ID
- This ID starts from 1 and increments by 1 within the same section and the same condition.
1.1.3. Requirement ID in Section 2
The Requirement ID in Section 2 starts with the corresponding section ID that is followed by the Requirement ID described above.
- The ID in Section 2 consists of : Section ID / Device Type ID - Condition ID - Requirement ID (e.g. 7.4.3/A-0-1).
2. Device Types
While the Android Open Source Project provides a software stack that can be used for a variety of device types and form factors, there are a few device types that have a relatively better established application distribution ecosystem.
This section describes those device types, and additional requirements and recommendations applicable for each device type.
All Android device implementations that do not fit into any of the described device types MUST still meet all requirements in the other sections of this Compatibility Definition.
2.1 Device Configurations
For the major differences in hardware configuration by device type, see the device-specific requirements that follow in this section.
2.2. Handheld Requirements
An Android Handheld device refers to an Android device implementation that is typically used by holding it in the hand, such as an mp3 player, phone, or tablet.
Android device implementations are classified as a Handheld if they meet all the following criteria:
- Have a power source that provides mobility, such as a battery.
- Have a physical diagonal screen size in the range of 3.3 inches (or 2.5 inches for devices which launched on an API level earlier than Android 11) to 8 inches.
The additional requirements in the rest of this section are specific to Android Handheld device implementations.
2.2.1. Hardware
Handheld device implementations:
- [7.1.1.1/H-0-1] MUST have at least one Android-compatible display that meets all requirements described on this document.
- [7.1.1.3/H-SR] Are STRONGLY RECOMMENDED to provide users an affordance to change the display size (screen density).
If Handheld device implementations support software screen rotation, they:
- [7.1.1.1/H-1-1]* MUST make the logical screen that is made available for third party applications be at least 2 inches on the short edge(s) and 2.7 inches on the long edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.
If Handheld device implementations do not support software screen rotation, they:
- [7.1.1.1/H-2-1]* MUST make the logical screen that is made available for third party applications be at least 2.7 inches on the short edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.
If Handheld device implementations claim support for high dynamic range displays through , they:
- [7.1.4.5/H-1-1] MUST advertise support for the , , , , and extensions.
Handheld device implementations:
- [7.1.4.6/H-0-1] MUST report whether the device supports the GPU profiling capability via a system property .
If Handheld device implementations declare support via a system property , they:
Handheld device implementations:
- [7.1.5/H-0-1] MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.
- [7.2.1/H-0-1] MUST include support for third-party Input Method Editor (IME) applications.
- [7.2.3/H-0-3] MUST provide the Home function on all the Android-compatible displays that provide the home screen.
- [7.2.3/H-0-4] MUST provide the Back function on all the Android-compatible displays and the Recents function on at least one of the Android-compatible displays.
- [7.2.3/H-0-2] MUST send both the normal and long press event of the Back function () to the foreground application. These events MUST NOT be consumed by the system and CAN be triggered by outside of the Android device (e.g. external hardware keyboard connected to the Android device).
- [7.2.4/H-0-1] MUST support touchscreen input.
- [7.2.4/H-SR] Are STRONGLY RECOMMENDED to launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the on long-press of or if the foreground activity does not handle those long-press events.
- [7.3.1/H-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.
If Handheld device implementations include a 3-axis accelerometer, they:
- [7.3.1/H-1-1] MUST be able to report events up to a frequency of at least 100 Hz.
If Handheld device implementations include a GPS/GNSS receiver and report the capability to applications through the feature flag, they:
- [7.3.3/H-2-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
- [7.3.3/H-2-2] MUST report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.
If Handheld device implementations include a 3-axis gyroscope, they:
- [7.3.4/H-3-1] MUST be able to report events up to a frequency of at least 100 Hz.
- [7.3.4/H-3-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.
Handheld device implementations that can make a voice call and indicate any value other than in :
- [7.3.8/H] SHOULD include a proximity sensor.
Handheld device implementations:
- [7.3.11/H-SR] Are RECOMMENDED to support pose sensor with 6 degrees of freedom.
- [7.4.3/H] SHOULD include support for Bluetooth and Bluetooth LE.
If Handheld device implementations include a metered connection, they:
- [7.4.7/H-1-1] MUST provide the data saver mode.
If Handheld device implementations include a logical camera device that lists capabilities using , they:
- [7.5.4/H-1-1] MUST have normal field of view (FOV) by default and it MUST be between 50 and 90 degrees.
Handheld device implementations:
- [7.6.1/H-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
- [7.6.1/H-0-2] MUST return “true” for when there is less than 1GB of memory available to the kernel and userspace.
If Handheld device implementations declare support of only a 32-bit ABI:
[7.6.1/H-1-1] The memory available to the kernel and userspace MUST be at least 416MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).
[7.6.1/H-2-1] The memory available to the kernel and userspace MUST be at least 592MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).
[7.6.1/H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).
[7.6.1/H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).
If Handheld device implementations declare support of 32-bit and 64-bit ABIs:
[7.6.1/H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).
[7.6.1/H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).
[7.6.1/H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).
[7.6.1/H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).
Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations.
If Handheld device implementations include less than or equal to 1GB of memory available to the kernel and userspace, they:
- [7.6.1/H-9-1] MUST declare the feature flag .
- [7.6.1/H-9-2] MUST have at least 1.1 GB of non-volatile storage for application private data (a.k.a. "/data" partition).
If Handheld device implementations include more than 1GB of memory available to the kernel and userspace, they:
- [7.6.1/H-10-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
- SHOULD declare the feature flag .
Handheld device implementations:
- [7.6.2/H-0-1] MUST NOT provide an application shared storage smaller than 1 GiB.
- [7.7.1/H] SHOULD include a USB port supporting peripheral mode.
If handheld device implementations include a USB port supporting peripheral mode, they:
- [7.7.1/H-1-1] MUST implement the Android Open Accessory (AOA) API.
If Handheld device implementations include a USB port supporting host mode, they:
- [7.7.2/H-1-1] MUST implement the USB audio class as documented in the Android SDK documentation.
Handheld device implementations:
- [7.8.1/H-0-1] MUST include a microphone.
- [7.8.2/H-0-1] MUST have an audio output and declare .
If Handheld device implementations are capable of meeting all the performance requirements for supporting VR mode and include support for it, they:
- [7.9.1/H-1-1] MUST declare the feature flag.
- [7.9.1/H-1-2] MUST include an application implementing that can be enabled by VR applications via .
If Handheld device implementations include one or more USB-C port(s) in host mode and implement (USB audio class), in addition to requirements in section 7.7.2, they:
- [7.8.2.2/H-1-1] MUST provide the following software mapping of HID codes:
| Function | Mappings | Context | Behavior |
|---|---|---|---|
| A | HID usage page: 0x0C HID usage: 0x0CD Kernel key: Android key: | Media playback | Input: Short press Output: Play or pause |
| Input: Long press Output: Launch voice command Sends: if the device is locked or its screen is off. Sends otherwise | |||
| Incoming call | Input: Short press Output: Accept call | ||
| Input: Long press Output: Reject call | |||
| Ongoing call | Input: Short press Output: End call | ||
| Input: Long press Output: Mute or unmute microphone | |||
| B | HID usage page: 0x0C HID usage: 0x0E9 Kernel key: Android key: | Media playback, Ongoing call | Input: Short or long press Output: Increases the system or headset volume |
| C | HID usage page: 0x0C HID usage: 0x0EA Kernel key: Android key: | Media playback, Ongoing call | Input: Short or long press Output: Decreases the system or headset volume |
| D | HID usage page: 0x0C HID usage: 0x0CF Kernel key: Android key: | All. Can be triggered in any instance. | Input: Short or long press Output: Launch voice command |
- [7.8.2.2/H-1-2] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after the USB audio interfaces and endpoints have been properly enumerated in order to identify the type of terminal connected.
When the USB audio terminal types 0x0302 is detected, they:
- [7.8.2.2/H-2-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 0.
When the USB audio terminal types 0x0402 is detected, they:
- [7.8.2.2/H-3-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 1.
When API AudioManager.getDevices() is called while the USB peripheral is connected they:
[7.8.2.2/H-4-1] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0302.
[7.8.2.2/H-4-2] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0402.
[7.8.2.2/H-4-3] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSource() if the USB audio terminal type field is 0x0402.
[7.8.2.2/H-4-4] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x603.
[7.8.2.2/H-4-5] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x604.
[7.8.2.2/H-4-6] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x400.
[7.8.2.2/H-4-7] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x400.
[7.8.2.2/H-SR] Are STRONGLY RECOMMENDED upon connection of a USB-C audio peripheral, to perform enumeration of USB descriptors, identify terminal types and broadcast Intent ACTION_HEADSET_PLUG in less than 1000 milliseconds.
If Handheld device implementations include at least one haptic actuator, they:
- [7.10/H-SR]* Are STRONGLY RECOMMENDED NOT to use an eccentric rotating mass (ERM) haptic actuator(vibrator).
- [7.10/H]* SHOULD position the placement of the actuator near the location where the device is typically held or touched by hands.
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in android.view.HapticFeedbackConstants namely (CLOCK_TICK, CONTEXT_CLICK, KEYBOARD_PRESS, KEYBOARD_RELEASE, KEYBOARD_TAP, LONG_PRESS, TEXT_HANDLE_MOVE, VIRTUAL_KEY, VIRTUAL_KEY_RELEASE, CONFIRM, REJECT, GESTURE_START and GESTURE_END).
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in android.os.VibrationEffect namely (EFFECT_TICK, EFFECT_CLICK, EFFECT_HEAVY_CLICK and EFFECT_DOUBLE_CLICK) and all public constants for rich haptics in android.os.VibrationEffect.Composition namely (PRIMITIVE_CLICK and PRIMITIVE_TICK).
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to use these linked haptic constants mappings.
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to follow quality assessment for createOneShot() and createWaveform() API's.
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to verify the capabilities for amplitude scalability by running android.os.Vibrator.hasAmplitudeControl().
Linear resonant actuator (LRA) is a single mass spring system which has a dominant resonant frequency where the mass translates in the direction of desired motion.
If Handheld device implementations include at least one linear resonant actuator, they:
- [7.10/H]* SHOULD move the haptic actuator in the X-axis of portrait orientation.
If Handheld device implementations have a haptic actuator which is X-axis Linear resonant actuator (LRA), they:
- [7.10/H-SR]* Are STRONGLY RECOMMENDED to have the resonant frequency of the X-axis LRA be under 200 Hz.
If handheld device implementations follow haptic constants mapping, they:
2.2.2. Multimedia
Handheld device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:
- [5.1/H-0-1] AMR-NB
- [5.1/H-0-2] AMR-WB
- [5.1/H-0-3] MPEG-4 AAC Profile (AAC LC)
- [5.1/H-0-4] MPEG-4 HE AAC Profile (AAC+)
- [5.1/H-0-5] AAC ELD (enhanced low delay AAC)
Handheld device implementations MUST support the following video encoding formats and make them available to third-party applications:
- [5.2/H-0-1] H.264 AVC
- [5.2/H-0-2] VP8
Handheld device implementations MUST support the following video decoding formats and make them available to third-party applications:
- [5.3/H-0-1] H.264 AVC
- [5.3/H-0-2] H.265 HEVC
- [5.3/H-0-3] MPEG-4 SP
- [5.3/H-0-4] VP8
- [5.3/H-0-5] VP9
2.2.3. Software
Handheld device implementations:
- [3.2.3.1/H-0-1] MUST have an application that handles the , , , and intents as described in the SDK documents, and provide the user affordance to access the document provider data by using API.
- [3.2.3.1/H-0-2]* MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
- [3.2.3.1/H-SR] Are STRONGLY RECOMMENDED to preload an email application which can handle ACTION_SENDTO or ACTION_SEND or ACTION_SEND_MULTIPLE intents to send an email.
- [3.4.1/H-0-1] MUST provide a complete implementation of the API.
- [3.4.2/H-0-1] MUST include a standalone Browser application for general user web browsing.
- [3.8.1/H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that supports in-app pinning of shortcuts, widgets and widgetFeatures.
- [3.8.1/H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API.
- [3.8.1/H-SR] Are STRONGLY RECOMMENDED to include a default launcher app that shows badges for the app icons.
- [3.8.2/H-SR] Are STRONGLY RECOMMENDED to support third-party app widgets.
- [3.8.3/H-0-1] MUST allow third-party apps to notify users of notable events through the and API classes.
- [3.8.3/H-0-2] MUST support rich notifications.
- [3.8.3/H-0-3] MUST support heads-up notifications.
- [3.8.3/H-0-4] MUST include a notification shade, providing the user the ability to directly control (e.g. reply, snooze, dismiss, block) the notifications through user affordance such as action buttons or the control panel as implemented in the AOSP.
- [3.8.3/H-0-5] MUST display the choices provided through in the notification shade.
- [3.8.3/H-SR] Are STRONGLY RECOMMENDED to display the first choice provided through in the notification shade without additional user interaction.
- [3.8.3/H-SR] Are STRONGLY RECOMMENDED to display all the choices provided through in the notification shade when the user expands all notifications in the notification shade.
- [3.8.3.1/H-SR] Are STRONGLY RECOMMENDED to display actions for which is set as in-line with the replies displayed by .
- [3.8.4/H-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action.
If Handheld device implementations support Assist action, they:
- [3.8.4/H-SR] Are STRONGLY RECOMMENDED to use long press on key as the designated interaction to launch the assist app as described in section 7.2.3. MUST launch the user-selected assist app, in other words the app that implements , or an activity handling the intent.
If Handheld device implementations support and group them into a separate section from alerting and silent non-conversation notifications, they:
- [3.8.4/H-1-1]* MUST display conversation notifications ahead of non conversation notifications with the exception of ongoing foreground service notifications and importance:high notifications.
If Android Handheld device implementations support a lock screen, they:
- [3.8.10/H-1-1] MUST display the Lock screen Notifications including the Media Notification Template.
If Handheld device implementations support a secure lock screen, they:
- [3.9/H-1-1] MUST implement the full range of device administration policies defined in the Android SDK documentation.
- [3.9/H-1-2] MUST declare the support of managed profiles via the feature flag, except when the device is configured so that it would report itself as a low RAM device or so that it allocates internal (non-removable) storage as shared storage.
If Handheld device implementations include support for and APIs and allow third-party applications to publish , then they:
- [3.8.16/H-1-1] MUST declare the feature flag and set it to .
- [3.8.16/H-1-2] MUST provide a user affordance with the ability to add, edit, select, and operate the user’s favorite device controls from the controls registered by the third-party applications through the and the APIs.
- [3.8.16/H-1-3] MUST provide access to this user affordance within three interactions from a default Launcher.
- [3.8.16/H-1-4] MUST accurately render in this user affordance the name and icon of each third-party app that provides controls via the API as well as any specified fields provided by the APIs.
Conversely, If Handheld device implementations do not implement such controls, they:
Handheld device implementations:
- [3.10/H-0-1] MUST support third-party accessibility services.
- [3.10/H-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.
- [3.11/H-0-1] MUST support installation of third-party TTS engines.
- [3.11/H-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
- [3.13/H-SR] Are STRONGLY RECOMMENDED to include a Quick Settings UI component.
If Android handheld device implementations declare or support, they:
- [3.16/H-1-1] MUST support the companion device pairing feature.
If the navigation function is provided as an on-screen, gesture-based action:
- [7.2.3/H] The gesture recognition zone for the Home function SHOULD be no higher than 32 dp in height from the bottom of the screen.
If Handheld device implementations provide a navigation function as a gesture from anywhere on the left and right edges of the screen:
- [7.2.3/H-0-1] The navigation function's gesture area MUST be less than 40 dp in width on each side. The gesture area SHOULD be 24 dp in width by default.
2.2.4. Performance and Power
- [8.1/H-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
- [8.1/H-0-2] User interface latency. Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 secs.
- [8.1/H-0-3] Task switching. When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.
Handheld device implementations:
- [8.2/H-0-1] MUST ensure a sequential write performance of at least 5 MB/s.
- [8.2/H-0-2] MUST ensure a random write performance of at least 0.5 MB/s.
- [8.2/H-0-3] MUST ensure a sequential read performance of at least 15 MB/s.
- [8.2/H-0-4] MUST ensure a random read performance of at least 3.5 MB/s.
If Handheld device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:
- [8.3/H-1-1] MUST provide user affordance to enable and disable the battery saver feature.
- [8.3/H-1-2] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.
Handheld device implementations:
- [8.4/H-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
- [8.4/H-0-2] MUST report all power consumption values in milliampere hours (mAh).
- [8.4/H-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
- [8.4/H-0-4] MUST make this power usage available via the shell command to the app developer.
- [8.4/H] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
If Handheld device implementations include a screen or video output, they:
2.2.5. Security Model
Handheld device implementations:
- [9.1/H-0-1] MUST allow third-party apps to access the usage statistics via the permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the intent.
Handheld device implementations (* Not applicable for Tablet):
- [9.11/H-0-2]* MUST back up the keystore implementation with an isolated execution environment.
- [9.11/H-0-3]* MUST have implementations of RSA, AES, ECDSA, and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
- [9.11/H-0-4]* MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
- [9.11/H-0-5]* MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the feature which requires a keystore backed by an isolated execution environment.
When Handheld device implementations support a secure lock screen, they:
- [9.11/H-1-1] MUST allow the user to choose the shortest sleep timeout, that is a transition time from the unlocked to the locked state, as 15 seconds or less.
- [9.11/H-1-2] MUST provide user affordance to hide notifications and disable all forms of authentication except for the primary authentication described in 9.11.1 Secure Lock Screen. The AOSP meets the requirement as lockdown mode.
2.2.6. Developer Tools and Options Compatibility
Handheld device implementations (* Not applicable for Tablet):
- [6.1/H-0-1]* MUST support the shell command .
Handheld device implementations (* Not applicable for Tablet):
- Perfetto
- [6.1/H-0-2]* MUST expose a binary to the shell user which cmdline complies with the perfetto documentation.
- [6.1/H-0-3]* The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
- [6.1/H-0-4]* The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
- [6.1/H-0-5]* MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
- [6.1/H-0-6]* The perfetto traced daemon MUST be enabled by default (system property ).
2.3. Television Requirements
An Android Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user interface”).
Android device implementations are classified as a Television if they meet all the following criteria:
- Have provided a mechanism to remotely control the rendered user interface on the display that might sit ten feet away from the user.
- Have an embedded screen display with the diagonal length larger than 24 inches OR include a video output port, such as VGA, HDMI, DisplayPort, or a wireless port for display.
The additional requirements in the rest of this section are specific to Android Television device implementations.
2.3.1. Hardware
Television device implementations:
- [7.2.2/T-0-1] MUST support D-pad.
- [7.2.3/T-0-1] MUST provide the Home and Back functions.
- [7.2.3/T-0-2] MUST send both the normal and long press event of the Back function () to the foreground application.
- [7.2.6.1/T-0-1] MUST include support for game controllers and declare the feature flag.
- [7.2.7/T] SHOULD provide a remote control from which users can access non-touch navigation and core navigation keys inputs.
If Television device implementations include a 3-axis gyroscope, they:
- [7.3.4/T-1-1] MUST be able to report events up to a frequency of at least 100 Hz.
- [7.3.4/T-1-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.
Television device implementations:
- [7.4.3/T-0-1] MUST support Bluetooth and Bluetooth LE.
- [7.6.1/T-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
If Television device implementations include a USB port that supports host mode, they:
- [7.5.3/T-1-1] MUST include support for an external camera that connects through this USB port but is not necessarily always connected.
If TV device implementations are 32-bit:
[7.6.1/T-1-1] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used:
- 400dpi or higher on small/normal screens
- xhdpi or higher on large screens
- tvdpi or higher on extra large screens
If TV device implementations are 64-bit:
[7.6.1/T-2-1] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used:
- 400dpi or higher on small/normal screens
- xhdpi or higher on large screens
- tvdpi or higher on extra large screens
Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations.
Television device implementations:
- [7.8.1/T] SHOULD include a microphone.
- [7.8.2/T-0-1] MUST have an audio output and declare .
2.3.2. Multimedia
Television device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:
- [5.1/T-0-1] MPEG-4 AAC Profile (AAC LC)
- [5.1/T-0-2] MPEG-4 HE AAC Profile (AAC+)
- [5.1/T-0-3] AAC ELD (enhanced low delay AAC)
Television device implementations MUST support the following video encoding formats and make them available to third-party applications:
- [5.2/T-0-1] H.264
- [5.2/T-0-2] VP8
Television device implementations:
- [5.2.2/T-SR] Are STRONGLY RECOMMENDED to support H.264 encoding of 720p and 1080p resolution videos at 30 frames per second.
Television device implementations MUST support the following video decoding formats and make them available to third-party applications:
Television device implementations MUST support MPEG-2 decoding, as detailed in Section 5.3.1, at standard video frame rates and resolutions up to and including:
- [5.3.1/T-1-1] HD 1080p at 59.94 frames per second with Main Profile High Level.
- [5.3.1/T-1-2] HD 1080i at 59.94 frames per second with Main Profile High Level. They MUST deinterlace interlaced MPEG-2 video to its progressive equivalent (e.g. from 1080i at 59.94 frames per second to 1080p at 29.97 frames per second) and make it available to third-party applications.
Television device implementations MUST support H.264 decoding, as detailed in Section 5.3.4, at standard video frame rates and resolutions up to and including:
- [5.3.4/T-1-1] HD 1080p at 60 frames per second with Baseline Profile
- [5.3.4/T-1-2] HD 1080p at 60 frames per second with Main Profile
- [5.3.4/T-1-3] HD 1080p at 60 frames per second with High Profile Level 4.2
Television device implementations with H.265 hardware decoders MUST support H.265 decoding, as detailed in Section 5.3.5, at standard video frame rates and resolutions up to and including:
- [5.3.5/T-1-1] HD 1080p at 60 frames per second with Main Profile Level 4.1
If Television device implementations with H.265 hardware decoders support H.265 decoding and the UHD decoding profile, they:
- [5.3.5/T-2-1] MUST support UHD 3480p at 60 frames per second with Main10 Level 5 Main Tier profile
Television device implementations MUST support VP8 decoding, as detailed in Section 5.3.6, at standard video frame rates and resolutions up to and including:
- [5.3.6/T-1-1] HD 1080p at 60 frames per second decoding profile
Television device implementations with VP9 hardware decoders MUST support VP9 decoding, as detailed in Section 5.3.7, at standard video frame rates and resolutions up to and including:
- [5.3.7/T-1-1] HD 1080p at 60 frames per second with profile 0 (8 bit color depth)
If Television device implementations with VP9 hardware decoders support VP9 decoding and the UHD decoding profile, they:
- [5.3.7/T-2-1] MUST support UHD 3480p at 60 frames per second with profile 0 (8 bit color depth).
- [5.3.7/T-2-1] Are STRONGLY RECOMMENDED to support UHD 3480p at 60 frames per second with profile 2 (10 bit color depth).
Television device implementations:
- [5.5/T-0-1] MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output (where no audio decoding is done on the device).
If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:
- [5.8/T-0-1] MUST set the HDMI output mode to select the maximum resolution that can be supported with either a 50Hz or 60Hz refresh rate.
- [5.8/T-SR] Are STRONGLY RECOMMENDED to provide a user configurable HDMI refresh rate selector.
- [5.8] SHOULD set the HDMI output mode refresh rate to either 50Hz or 60Hz, depending on the video refresh rate for the region the device is sold in.
If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:
- [5.8/T-1-1] MUST support HDCP 2.2.
If Television device implementations do not support UHD decoding, but instead support an external display connected via HDMI, they:
- [5.8/T-2-1] MUST support HDCP 1.4
2.3.3. Software
Television device implementations:
- [3/T-0-1] MUST declare the features and .
- [3.2.3.1/T-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
- [3.4.1/T-0-1] MUST provide a complete implementation of the API.
If Android Television device implementations support a lock screen,they:
- [3.8.10/T-1-1] MUST display the Lock screen Notifications including the Media Notification Template.
Television device implementations:
- [3.8.14/T-SR] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window.
- [3.10/T-0-1] MUST support third-party accessibility services.
- [3.10/T-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.
If Television device implementations report the feature , they:
- [3.11/T-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
- [3.11/T-1-1] MUST support installation of third-party TTS engines.
Television device implementations:
- [3.12/T-0-1] MUST support TV Input Framework.
2.3.4. Performance and Power
- [8.1/T-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
- [8.2/T-0-1] MUST ensure a sequential write performance of at least 5MB/s.
- [8.2/T-0-2] MUST ensure a random write performance of at least 0.5MB/s.
- [8.2/T-0-3] MUST ensure a sequential read performance of at least 15MB/s.
- [8.2/T-0-4] MUST ensure a random read performance of at least 3.5MB/s.
If Television device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:
- [8.3/T-1-1] MUST provide user affordance to enable and disable the battery saver feature.
If Television device implementations do not have a battery they:
If Television device implementations have a battery they:
- [8.3/T-1-3] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.
Television device implementations:
- [8.4/T-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
- [8.4/T-0-2] MUST report all power consumption values in milliampere hours (mAh).
- [8.4/T-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
- [8.4/T] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
- [8.4/T-0-4] MUST make this power usage available via the shell command to the app developer.
2.3.5. Security Model
Television device implementations:
- [9.11/T-0-1] MUST back up the keystore implementation with an isolated execution environment.
- [9.11/T-0-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
- [9.11/T-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
- [9.11/T-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the feature which requires a keystore backed by an isolated execution environment.
If Television device implementations support a secure lock screen, they:
- [9.11/T-1-1] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds or less.
2.3.6. Developer Tools and Options Compatibility
Television device implementations:
Homebrew Formulae
What’s New in the DVD to MP3 Ripper 2.2.1 serial key or number?
Screen Shot
System Requirements for DVD to MP3 Ripper 2.2.1 serial key or number
- First, download the DVD to MP3 Ripper 2.2.1 serial key or number
-
You can download its setup from given links:
DVD to MP3 Ripper 2.2.1 serial key or number & Software
DVD to MP3 Ripper 2.2.1 serial key or number& Crack
DVD to MP3 Ripper 2.2.1 serial key or number
About Author
