- Tip & Tech
- Code Snippet
- Tizen Projects
- Tip & Tech
- Code Snippet
- Tizen Projects
Device Manager is a standalone tool that manages devices and allows you to access their internal file systems and logs. A device can be either a virtual device, such as an emulator, or a physical device connected with a USB cable or a wireless connection.
Device Manager provides a graphical user interface that is more convenient than Command Line Interface (CLI). You can use it to connect and disconnect devices to and from your computer, as well as to access devices' internal file systems and push or pull files between the device and your computer. Device Manager provides the device logs in a table format, and you can use filters to find the entries that interest you.
To use Device Manager with a specific device, you must connect the device over Smart Development Bridge (SDB). Physical devices can be connected with a USB cable, and emulators can be connected through Emulator Manager. When the device is connected over SDB, it is automatically displayed in Device Manager and its directory structure and logs are shown in the File Explorer and Log views, respectively.
There are two different ways to access Device Manager:
|Desktop > Applications > Device Manager:
|Start > All Programs > Tizen Studio > Tools > Device Manager:
|Finder > Applications > Tizen Studio > Device Manager:
If the program is executed normally, the Device Manager window appears.
Figure: Device Manager main screen
Device Manager shows both local devices connected to the system and any configured remote devices:
Figure: Connected devices in Device Manager
Connecting a device to a computer depends on the device type:
When you connect a local physical device with a USB cable, it automatically appears in Device Manager.
To connect a virtual device, click Emulator Manager , select the virtual device, and click Launch.
When the emulator finishes booting, the device appears in Device Manager.
To connect a remote device, follow these steps:
When the connection is established, the remote device appears in Device Manager.
You can install a Tizen application to a connected device with the TPK or WGT file:
The application is installed and launched on the selected device.
If your device has a distributor certificate that contains a DUID starting with 1.0#, you must give the device permission to install applications.
Assume that you have registered two devices, the Gear S2 and Gear S, in your distributor certificate. The Gear S2 DUID starts with 2.0# and the Gear S DUID starts with 1.0#. This means that the certificate format is issued internally based on the 1.0# device, and both Gear S2 and Gear S devices must get permission before installing an application.
To permit a device to install applications, follow these steps:
device-profile.xml file, issued in your profile directory, is pushed to the
/home/developer directory of the device.
Figure: Context menu for the File Explorer view
A distributor certificate containing only #2.0 devices does not have the
device-profile.xml file, and consequently does not require this process to push the file to the device.
You can browse the internal file structure of a connected device in the File Explorer view. Depending on your permissions, you can create and delete files on the device, and pull and push files between the device and your computer.
All files are granted read, write, and execute permissions and they cannot be arbitrarily changed.
You can perform a variety of actions through the File Explorer view:
Writepermission set for the
When a device is connected to Device Manager, a device log tab is automatically created in the Log view. The default tab name is the device ID, but it can be modified. You can create additional tabs for a device, and you can set different filters for each tab. Tabs for disconnected devices are shown as inactive, and are reactivated when the device is reconnected.
Figure: Log view
Each log tab contains a toolbar and a log table. The log table lists log messages in chronological order, and this order cannot be modified. Each log message contains the Time, Level (priority level of the log message), Pid (process ID), Tid (thread ID), Tag (identification of the log message source), and Message fields, and you can create filters for each field.
You can perform a variety of actions in the Log view:
You can create a new log tab in two ways:
To edit the log tab name, click Edit Tab . Enter a new name for the tab and click OK.
You can either delete a single tab, or delete all tabs related to a device:
You can filter log messages based on the table columns:
To clear all log messages from a tab, click Clear Logs .
To export logs to a file, click Export Logs , select the file storage location and file name for the exported log, and click OK.
You can access Device Manager Configuration window by clicking the Settings icon.
Figure: Device Manager Configuration
You can set the following settings for Device Manager:
To set the application installation path and data storage location, select the General tab, change the directory paths, and click OK.
This is the maximum wait time for push and pull operations in the File Explorer view. To set the timeout value, select the Device tab, change the value, and click OK.
This is the maximum amount of log entries to store in the log table. To set the buffer size, select the Log tab, change the value, and click OK.