# LiteAVSDK's Android player ships as a demo project plus a licensed SDK download > The LiteAVSDK Player_Android repository is not the player itself but the demo source and documentation for Tencent Cloud's Player SDK, with a superplayerkit component, short video and feed modules, and a licence check that must be set before playback will work. The SDK is distributed as a separate zip download in a basic and a premium edition. **LiteAVSDK/Player_Android** — Super player for android... - Repository: https://github.com/LiteAVSDK/Player_Android - Website: https://cloud.tencent.com/document/product/881 - Stars: 541 · Forks: 121 - Language: Java - License: not declared - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/liteavsdk-player-android ## What the repository contains and what it does not The project description is minimal, calling it a super player for Android, but the README is clear about the scope of the repository. It contains the demo source code for the Android player SDK, demonstrating how the interfaces are called and covering the most basic functionality. The top-level entries show that directly. There is a Demo directory, an SDK directory whose own README.md holds the Android Player SDK download address, a Player-API-Example-Android directory, and the two README files, one in Chinese and one in English. The Player SDK itself is not in the repository. It is fetched as a packaged download, which is the single most important structural fact about this project for anyone considering it. The primary language is Java, the default branch is master, the last push was on 2026-09-07, and the recorded release list shows version 11.4 published on 2024-01-10, version 9.5.2 on 2022-01-24 and version 9.5.1 on 2022-01-14. GitHub records no licence identifier for the repository, and the documented product licensing is a separate commercial arrangement. ## The demo module layout mirrors the product surfaces The Demo tree is organised around the different playback scenarios the product supports, which makes it a useful map of what the SDK can do. The player demo, LiteAVDemo, covers audio and video playback, background playback, variable speed playback, live and on-demand instant start, and switching between quality levels. Inside it sit the app entry module, the superplayerkit player component, the superplayerdemo component demo, the tuishortvideo short video component, the feedvideo feed video stream component, the shortvideo short video component, and vodcommon, a set of shared utilities for on-demand playback. Each of those modules has its own documentation link, and the short video and feed components are documented separately from the player itself. The naming convention of two directories for short video, tuishortvideo and shortvideo, is the kind of detail that suggests a component that predates the current structure and a newer one alongside it, so anyone reading the tree should check which one the current integration guide points at. ## The licence check that gates playback The demo experience instructions describe a step that is not optional. After downloading the new demo you must set a licence through TXLiveBase#setLicence before playback succeeds, otherwise playback fails with a black screen, and it only needs to be set once globally. A live licence, a short video licence and a video playback licence can all be used for this. If you do not yet have one, the README links to a page for applying quickly and free for a test licence, and notes that a formal version licence has to be purchased. There is a second piece of configuration that catches people out. Once you have the licence URL and licence key, you assign them to the licenceUrl and licenseKey fields in the demo source file at Demo/app/src/main/java/com/tencent/liteav/demo/TXCSDKService.java. And the package name of the demo has to be changed to the package name you entered when applying for the licence, after which you open the project in Android Studio and run it. That coupling between the licence and the package name is the practical constraint: you cannot test the demo under a package name of your own choosing without invalidating the licence. ## Two SDK editions and what the upgrade changed The SDK is offered in a basic version and a premium version, and the split is by feature rather than by size alone. The basic version is for teams that want the smallest possible size increase, and the premium version is for teams that need advanced capabilities such as external subtitles, multiple audio tracks and DRM playback. The README notes that the player SDK from mobile version 10.1 onwards, across Android, iOS and Flutter, is built on the same playback core as Tencent Video, with video playback capabilities broadly upgraded, and that from that version onwards authorisation checks were added for the video playback feature module. The important part of that change is who it affects. If your app already holds a live streaming licence or a short video licence, upgrading to 10.1 does not affect you and you can carry on using it, and you can check your current licence authorisations in the Tencent Cloud console. If you never held those licences and you need the live playback or on-demand playback features in version 10.1 or later, you have to purchase a licence. If you do not use those features, or you do not upgrade, the change does not apply to you. ## The player component that wraps the SDK Beyond the raw SDK, the project offers a player component called superplayerkit, which integrates quality monitoring, video encryption, very high quality playback, resolution switching and small window playback, and which is described as suitable for both on-demand and live playback scenarios. The reason to care is stated plainly: it wraps the full feature set and provides the upper layer user interface, so it helps you build a video application comparable to the popular ones in a short time. That framing also sets the boundary. The repository gives you the demo for the component, and the component is a set of prebuilt UI pieces rather than a design system you own. If your product needs a playback experience that does not look like the reference implementation, you will be fighting the component's presentation layer rather than extending it. The documentation links listed in the README cover the integration guide, the capability list, common mobile playback problems, the API reference, the version history and an official demo app, so the API surface itself is documented outside the repository. ## Where this is the wrong choice The licence is the first limit and it is not a technical one. Playback does not work until a licence is set, the licence is bound to a package name, and the repository records no licence for its own source, which means the demo code is available to read but its reuse status is not stated. If you are building something that must ship under a permissive licence, or you want to fork the player and maintain it yourself, this is the wrong dependency. The second limit is the platform. The documented integration paths are Tencent Cloud, and the repository is Android-specific, so an iOS or Flutter project would use the sibling SDKs rather than this one. The third is the age of the recorded release information. The newest listed release is 11.4 from January 2024 while the repository was pushed to in September 2026, so the tags tell you little about what is shipping now, and the actual version in use has to come from the download page or the console rather than from the git history. The fourth is scope: this is a player SDK for one vendor's video platform, and the described capabilities are tied to that platform's ecosystem of encryption, quality monitoring and licensing, so it does not generalise to a player you point at arbitrary streams. ## Conclusion Adopt the LiteAVSDK Player for Android if you are building an app for Tencent Cloud video playback and already have a Tencent Cloud account, since the player itself is only available as a licensed download and the repository gives you the demo, the integration guide and the sample modules. Skip it if you want a permissively licensed player with no licence server, because the licence check is mandatory and the repository records no licence for its own source. Before you start, apply for a licence, set it with TXLiveBase#setLicence, and change the demo package name to the one you entered in the application form. ## FAQ ### What is in the LiteAVSDK Player_Android repository? It contains the demo source code for the Android player SDK, showing how the interfaces are called and covering the most basic functionality, including a LiteAVDemo with the player component, a short video component, a feed video stream component and shared on-demand utilities. The SDK itself is not in the repository; its README points to a download. ### Why does the LiteAVSDK demo show a black screen during playback? Because a licence has not been set. The README says you must call TXLiveBase#setLicence after downloading the new demo, otherwise playback fails with a black screen, and the licence only needs to be set once globally. ### What is the difference between the basic and premium Player SDK editions? The basic version is for teams seeking the smallest size increase, while the premium version adds advanced features such as external subtitles, multiple audio tracks and DRM playback. Both are distributed as separate zip downloads for Android. ### Does upgrading to Player SDK version 10.1 require a new licence? Only in some cases. Apps that already hold a live streaming or short video licence can upgrade to 10.1 and keep working, and can check their current authorisations in the Tencent Cloud console. Apps that never held those licences and need live or on-demand playback on 10.1 or later must purchase a licence. ## Sources - [Issues](https://github.com/LiteAVSDK/Player_Android/issues) - [LiteAVSDK/Player_Android on GitHub](https://github.com/LiteAVSDK/Player_Android) - [Project website](https://cloud.tencent.com/document/product/881) - [README](https://github.com/LiteAVSDK/Player_Android/blob/master/README.md) - [Releases](https://github.com/LiteAVSDK/Player_Android/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/liteavsdk-player-android