Skip to main content

Tizen

The tvlabs connect command uses the Tizen SDK to connect with Samsung devices on the TV Labs platform as if they were in front of you.

Prerequisites​

Ensure that Tizen Studio 6.0 is installed and sdb and tizen are in your PATH. You can download Tizen Studio from the Tizen Developer website. Additional installation instructions can be found in the Tizen Studio documentation.

Connecting​

After the Tizen Studio and the SDK is installed, start a Tizen session on TV Labs and run tvlabs connect.

SDB Connected

Once tvlabs connect has successfully created a vendor connection, run sdb devices to check that the device is connected properly. The Tizen device should appear in the list of devices as <tv-ip>:26101.

SDB Devices

Port Mapping​

The port mapping when tvlabs connect is running and connected to a Tizen session is as follows:

  • Local port 26101 to Tizen device port 26101 (Samsung Debug Bridge interface)
  • Local port 9222 to dynamic inspector port when Web Inspector is started
  • Local port 8001 to Tizen device port 8001 (Remote Control protocol)
  • Local port 8002 to Tizen device port 8002 (Remote Control protocol w/ SSL)
  • Local port 26099 to server port 26099 (sdb server)
note

You may run a local sdb server on the same machine where tvlabs connect is running, however only requests to localhost will be forwarded to the TV Labs device sdb server.

Creating a Certificate​

To run your application on the TV Labs device, please ensure that you have a certificate to sign your application with. If you already have a certificate, you can skip ahead to Installing.

Prerequisites​

Before creating a certificate, it is important to ensure that the following Tizen Studio packages are installed the package manager.

From Main SDK:​

  • 8.0 Tizen

From Extension SDK:​

  • TV Extensions-8.0
  • Samsung Certificate Extension

Instructions​

If you have not created a certificate, follow the instructions in the Tizen Studio documentation for creating a certificate.

Info

When creating a certificate, if you are connected to the device via tvlabs connect, the DUID (device ID) should be automatically retrieved. If it is not automatically retrieved, you can retrieve the DUID by running sdb shell 0 getduidgadget.

The certificate can now be used to sign your Tizen application when packaging:

tizen build -- /path/to/application
tizen package --type wgt --sign <Name of Certificate> -- /path/to/application/build_output

Installing​

Once your application has been built and packaged using your certificate, you will be able to install and run your Tizen app on the device by running tizen install -n application.wgt. The installation command will output your application ID. You can then use tizen run -p <application id> to start the application.

Web Inspector​

The Chrome web inspector is available to use on Tizen with web applications. Before beginning, ensure that Chrome is installed.

To start the inspector, the tvlabs connect command must know the ID of your application you are targeting. Provide it with --application-id or -a.

tvlabs connect -a AvsPHsIO4r.HelloTVLabs

After the vendor connection is made and your application is installed, press "d" to launch the inspector.

Tizen Connect Debugger

Once the inspector is active, navigate to chrome://inspect within the Chrome browser. The device will appear on this page.

SDB Debugger Devices

If nothing appears in the inspector list, please check the tvlabs connect UI for errors. If there are no errors, ensure that your development application is open and running.

SDB Inspector Window

info

The Tizen inspector runs on port 9222 by default, but can be configured by setting the -i argument.

tvlabs connect -i 5678 -a AvsPHsIO4r.HelloTVLabs

Troubleshooting​

If application installation fails, please ensure that the device storage is not full.

If the device becomes disconnected during the session, check that the device is still powered on. Once the device is powered on, press the "r" key in the tvlabs connect UI to reconnect.

If the device becomes disconnected during the session while the device is powered on and pressing the "r" key in the tvlabs connect UI to reconnect does not work, try ending and restarting the session.

If sdb devices does not list any devices after a successful connection with tvlabs connect, and the above steps do not work, please ensure that development mode is enabled and the Host PC IP is set to 10.42.1.1. After ensuring that the device is powered on in development mode with the correct Host PC IP, try pressing the "r" key in the tvlabs connect UI to reconnect again.

Tizen Development Mode

If tvlabs connect still cannot make a connection after trying these steps, please contact TV Labs for support.