WebApp for Coolita TV

Coolita is a flexible operating system based on Linux and Web to address the market
needs of large-screen OS solution include Smart TVs, Smart Projector, Smart dongle
etc. With Coolita, a device manufacturer can begin with configuration, modify it to
serve their own needs and quickly bring it to market.

Coolita integrated a Chrome Browser based on Chromium/Blink engine, which

supports latest W3C HTML5 specifications, supports Widevien/Playready DRM, thus
web apps for Coolita are basically very similar to standard web apps. If you have an
experience in building web apps, you can start developing web apps for Cooltia TV
easily, with your knowledge in standards-based web technologies, such as HTML,
CSS, and JavaScript.
1. Supported web API: Below is information about using standard web API in
developing a web app for Coolita:
a. HTML, CSS, and JavaScript are the core web technologies to build web
pages or web apps. HTML presents the structure of the pages or the application
using markup and CSS formats the contents written in HTML such as colors,
layouts, font, etc. JavaScript is a programming language for the web which has
been standardized in the ECMAScript. Using HTML5, CSS3, and JavaScript,
you can develop web apps for Coolita.
2. Browser engine:
a. We provide the browser engines and their versions used on Coolita. Web
App developer can check the compatible version of Chrome on Web APIs in
Browser compatibility of each API.
b. Browser engine version ：Currently, Chromium 79 is used on Coolita.
We plan to introuduce and adapt Chromium 103 next year.
c. Browser engine features：Browser based on Chromium/Blink engine and
specially adapted for TV/STB. It can provide full support for HTML5.
i. Based on Blink rendering engine and Google V8 JavaScript engine
can quickly and stably display pages, load pictures and quickly execute
JavaScript extensions.
ii. Use OpenGL technology to accelerate the graphics processing ability.
iii. Standards:
1. HTML5 (Canvas 2D, Web Storage, Web Workers, Web Socket,
Audio/Video Tags, SVG, etc.)
2. HTML4.01 (XHTML 1.1, XHTML Basic 1.1, CE-HTML, XML 1.1,
 RSS feed,etc.)
3. CSS3 (3D Transforms, CSS3 Animations & Transitions, CSS3
Media Queries and Selectors, CSS3 Opacity, CSS3 Outline, CSS3
Background), CSS1, CSS2.1
iv. Protocols : HTTP 1.0/1.1,HTTPS,SSL v3, TLS 1.0
v. Supported DRMs: Widevine L1, Playready SL3000
vi. Supported Streaming Protocols: HLS, MPEG-DASH，MSE(Media
Source Extensions) , EME(Encrypted Media Extensions)
3. Cookie and cache support of browser engine
a. The browser engine supports cookies and saves cache for enhanced
performance. The stored cache is used only while the web browser engine is
running and is not used anymore once an app has been terminated.
4. User Agent string：

a. A web app can get the string from navigator.userAgent. The same string is
included in the HTTP request User-Agent header. The userAgent string that
corresponds to the browser engine is as follows:
i. UserAgent：Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/88.99.234.5 Safari/537.36 Coolita OS
QJY/2.0
5. The difference between Web Apps on PC and TV.
a. User operation mode：

i. PC mode： In PC usage scenarios, web apps or websites are

opened through a PC browser and operated with a mouse;
ii. TV mode：In TV usage scenarios, web apps or websites are opened
through a browser and typically operated and selected through the
directional keys on the remote control;
iii. Examples：

1. PC mode: https://www.mxplayer.in/ link is for PC use, and

support mouse to operate. This link already worked in coolita browser,
but mouse operation mode is not friendly for TV users.
2. TV mode: support 5-key operate( OK/Enter, arrow keys: up,
down ,left , right), it will suit TV users. Below are some typical TV
mode web apps:
a. https://app.plex.tv/tv-v5-generic?platform=skyworth

b. https://tv.iq.com/

c. http://tv.deezer.com/smarttv/622973e257290b8d68de0ddb873fc
c30/foxxum/
 b. Hardware resource:
Unlike PC environments, embedded systems have limited hardware
resources, especially memory resources. It was recommended that the
memory usage of the web application layer be within 200MB. The less
memory occupied, the smoother the program runs.
i. UI resolution(pixel) : 1280x720.
6. HTML5 app links to integrate on Coolita
Same as the standard Web App, the actual content of the app resides on the
remote web server, you can update the content, including code for new features, at
any time without having to worry about pushing updates to devices.
When a user launches the local app on their device, the URL of the app is redirected
to the web app on the web server, and the resources are downloaded from the server
to the device.

Step by step guide on how the process of link sharing, integration, and future
analytics/updates looks like
• Content/App Provider provide us the H5 URL, test account(if need), add our IP
into whitelist(if need). In additional, We have VPN network to simulate the real
network enviroment.
• Coolita R&D team will adapt to the H5 app, include test and address the issue.
If issues need Content provider to fix, we will provide the issue list and cause
• Once issues are fixed, Coolita QA team will test and confirm.
• When App reach the release standard, Coolita Commercial team will contact
with App provider(if need), Coolita Operator team will put the App url link to Coolita
operator server, then home/Launcher of the TV will show the App for the end user to
select and use.
• In addition, Coolita OS also support to show the contents' poster of the App on
TV's home/launcher for the end user to browser and watch the movie. This feature
requires App provider provide the metadata through API.

7. HTML5 app links to integrate on Coolita

• For information about specification for the Chrome Browser, please refer to
"QJY Chrome TV Browser Introduction.pdf".
• The browser provided chromium standard key mapping for App developers. For
detail information, please refer to "QJY Browser KeyMap.pdf"
• To enable browser in debugger mode, please refer to "How to enable browser
debugger mode (chrome remote).doc"
• To get the values of a few parameters from the platform/os; like resolution,
scale, model, manufacturer, locale, region, network information, please refer to "
JavaScript usage of QJY SDK for deviceinfo.pdf"
• To exit the web application， please call window.close() to exit and back to
home/launcher.

8. The Chromium debugger (web inspector)

• The Chromium debugger (web inspector) is disabled by default on production
devices. If engineers need to enable web inspectors，it requires a special software
version or debug tool.

9. Platform Security (hardware-secure boot, TEE）

• The chip solution provider for this

platform is Amlogic. Secure OS is
developed by Amlogic. It is a secure
kernel that can be run in parallel with a
full featured rich operating system such
as Linux or Android on the same ARM
core.
• It uses ARM TrustZone technology
to protect trusted applications and any
secure peripherals from code running in
the rich OS.

• The implementation of Amlogic Secure OS has been reviewed by ARM.

• With Secure OS, trusted applications will be executed in the secure world while
rich OS is executed in the normal world. This means that even if the rich OS is rooted,
the hacker is still unable to access the secure world.
• Amlogic Secure OS is Global Platform compliant. Trusted Application developed
using Global Platform TEE API can be ported to Amlogic Secure OS platform easily.
• TEE Development Kit (TDK) is a development kit which can provide libraries
and demos for Trusted Application (TA) and Client Application (CA). Using TDK to
setup a Trusted Execution Environment (TEE), to develop Digital Rights
Management (DRM), Conditional Access System (CAS), Secure Payment or other
trusted applications.