Quantcast
Jump to content


Recommended Posts

Posted

2021-04-12-01-banner.jpg.png

The Remote Device Manager provides a mechanism to deploy a project remotely from Tizen Studio to a Tizen-enabled device, such as Galaxy Watch. Tizen-enabled devices can be connected or disconnected through the Remote Device Manager if they are on the same network. Once the connection is made, a device log is shown in the Log View. You can also use the interface of the Remote Device Manager for executing SDB shell commands.

Prerequisites: Tizen Studio 2.0 or higher

Launch a project with Remote Device Manager

Step 1: Disable Bluetooth

If the watch has not been upgraded and the Tizen version is below 5.0, Bluetooth should be disabled during this process. In upgraded watches, you don’t need to disable Bluetooth.

Path: Settings > Connections > Bluetooth

Figure 1

Figure 1: Disabling Bluetooth

Step 2: Enable debugging mode

Make sure debugging mode is enabled. You can enable debugging mode from the Settings menu, as shown below.

Path: Settings > About Watch > Debugging is turned on

Figure 2

Figure 2: Enabling debugging mode

Step 3: Set the Wi-Fi to Always on

This step is optional, but to avoid any unnecessary issues, it is better to set the Wi-Fi to Always on. Leaving the setting on Auto can sometimes create issues.

Path: Settings > Connections > Wi-Fi > Always on

Figure 3

Figure 3: Setting the Wi-Fi to Always on

Caution: Setting the Wi-Fi to Always on can drain the battery drastically. After debugging, it should be set back to Auto again for better battery life.

Step 4: Connect to the network

Connect the watch to the same network as your PC.

Choose either of the following ways to connect the devices to the same network:
• By creating a mobile hotspot
• By using Wi-Fi under the same router

Step 5: Restart the watch

After the previous steps have been completed, restart the device. If you do not, the connection setup shows an error.

Figure 4

Figure 4: Rebooting the watch

Step 6: Establish the connection from the Remote Device Manager

  1. In Tizen Studio, go to Launch Remote Device Manager.

    Figure 5

    Figure 5: Launching the Remote Device Manager

  2. Scan for new devices. The window shows a list of available devices and their IP addresses. You can also add a device manually from the Remote Device Manager window.

    Figure 6

    Figure 6: Searching for available devices for connection

  3. To connect to the device, click on the Connect toggle next to the watch IP address and port information. The watch receives an RSA authentication request through a pop-up during this connection setup and it is mandatory to accept the RSA authentication to complete the process.

Figure 6

Figure 7: Connecting to the watch from the Remote Device Manager

You are now all set to deploy your app from Tizen Studio to the wearable device.

Step 7: Permit to install user applications

As a security feature, the device or emulator you have connected to does not contain the necessary certificates for installing user applications, and you must install them before being able to run your application on it. To do so, select “Permit to install applications” from the context menu of the device in the Device Manager.

If the “The permit to install application is not required for this device” appears, this step is unnecessary.

Figure 8

Figure 8: Setting the permit to install applications in the Device Manager

Step 8: Launch your project

Now, deploy your project on your connected watch, as shown in the image below.

Path: Right-Click on the project > Run As > 1 Tizen Native Application

Figure 9

Figure 9: Deploying the project from Tizen Studio to a connected watch

Some helpful tips for connecting your device with the Remote Device Manager

  • Check the IP address of your watch from Connections > Wi-Fi -> Wi-Fi Networks > tap on the SSID (your Wi-Fi name) > IP address.

  • If your device is already shown in the Remote Device Manager's history, delete it and try to connect again.

  • Launch the Device Manager to see the Log View.

    Figure 10

    Figure 10: The Log View from Device Manager

  • Make sure the watch is not connected with any other devices, including a phone. Otherwise, the connection fails and you receive the following error message:

    Figure 11

    Figure 11: Error message during multiple connections

  • If you cannot find the watch after scanning for devices from the Remote Device Manager, make sure your device is on the same network. To check this, go to the command prompt on your PC and ping the IP address of the watch in the following manner:
    ping < Watch_IP >

    If the ping command fails to connect to the IP address of your watch, it is not on the same network, and the SDB / Remote Device Manager does not work. To fix this, you need to change the network settings of your router or PC. The issue can also be caused by firewall settings, although this is rare.

Conclusion

The main purpose of this article is to help new developers to deploy Tizen projects to a real device using the Tizen Remote Device Manager. Hopefully, this tutorial is helpful for beginners and gives them a good experience with Tizen Studio.

If you have any other problems or queries regarding launching projects with the Remote Device Manager, feel free to reach out through the Samsung Developers Forum.

View the full blog at its source



  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Similar Topics

    • By Samsung Newsroom
      Samsung Electronics, the global leader in soundbars, today introduced its 2026 sound device lineup, marking a new chapter in how sound is experienced throughout the home. The expanded range — which will be showcased at CES 2026 in Las Vegas, Nevada from Jan. 6-9 — delivers richer immersion, clean expression and more unified multi-device performance through next-generation soundbars and Wi-Fi speakers.
      “For more than a decade, Samsung has shaped the evolution of home audio through advanced acoustics, intelligent features and thoughtful design,” said Hun Lee, Executive Vice President of the Visual Display Business at Samsung Electronics. “We’re continuing that legacy with next-generation sound devices designed to deliver a rich, expressive performance for any space and moment.”

      Redefining Cinematic Sound With Samsung’s Q-Series Soundbars
      Samsung’s 2026 Q-Series soundbars reinterpret cinematic sound for contemporary homes, offering richer immersion across a range of room sizes and listening preferences.
      Samsung’s latest flagship Soundbar (HW-Q990H model) delivers its most immersive soundbar experience yet, debuting Sound Elevation, a technology that lifts dialogue toward the center of the screen for more natural sounding audio. It also introduces Auto Volume, which maintains consistent volume across channels and content for a smoother, more balanced listening experience.
      The 11.1.4-channel system combines a 7.0.2 main bar, 4.0.2 rear speakers and dual 8-inch driver built-in compact active subwoofer, refined for a powerful and space-efficient bass. Up-firing channels and next-generation AI tuning further broaden the sound field, bringing a sense of scale typically associated with professional home theater setups.
      New to the 2026 lineup is Samsung’s All-in-One Soundbar (HW-QS90H model), which blends performance with aesthetic versatility. Its Convertible Fit design supports both wall-mount and tabletop placements, while a built-in gyro sensor automatically adapts channel distribution based on orientation.
      A 7.1.2-channel system with 13 drivers — including nine wide-range speakers — and a built-in Quad Bass Woofer system deliver deep bass without the need for a separate subwoofer.

      Music Studio Series: Iconic Dor Design, Expressive Sound
      Samsung is introducing two new Wi-Fi speakers, the “Music Studio 5” and “Music Studio 7,” to build a stronger integrated ecosystem. These new models enable a wider range of sound system combinations than before, maximizing the audiovisual experience. Additionally, they offer richer sound experiences while also enhancing aesthetic harmony with users’ spaces, allowing users to enjoy an improved audio environment. Each model shares a timeless dot concept by renowned designer Erwan Bouroullec, inspired by a universal symbol in music and art — and grounded in Samsung’s signature aesthetic.
      Music Studio 7 (LS70H model) is the most immersive model in the series, delivering 3.1.1-channel spatial audio through left, front, right and top-firing speakers for natural 3D immersion. Samsung’s Audio Lab Pattern Control Technology reduces signal overlap for cleaner directionality, while AI Dynamic Bass Control delivers deep bass with minimal distortion and Hi-Resolution Audio enables audio processing up to 24-bit/96kHz. Also, thanks to the super tweeter, the frequency range can extend up to 35kHz for enhanced musical detail. Available in black and white, it functions as a standalone immersive speaker or can be paired with additional units or Samsung TVs via Q-Symphony for wider stereo or a full surround-sound setup. 
      Music Studio 5 (LS50H model) is designed for homes where aesthetic harmony is as important as sound, offering a smaller, gallery-inspired form that complements and elevates interior spaces. Tuned by Samsung Audio Lab, it uses a 4” woofer and dual tweeters with a built-in waveguide for clear, balanced sound, while AI Dynamic Bass Control deepens low frequencies without distortion. Wi-Fi casting, streaming services, voice control and Bluetooth via Samsung Seamless Codec provide smart, seamless connectivity.

      A More Intelligent, Connected and Immersive Sound Experience
      For 11 consecutive years, Samsung has been the global leader in soundbars, driven by a commitment to engineering excellence led by the Samsung Audio Lab in California. This foundation shapes every part of Samsung’s 2026 lineup, bringing together advanced acoustics, purposeful design and intelligent connectivity.
      In 2026, Samsung’s Q-Symphony becomes even more adaptive, enabling Samsung TVs, soundbars and Wi-Fi speakers to operate as a unified sound ecosystem. Users can now pair up to five sound devices with a Samsung TV while Q-Symphony analyzes room layout and device placement to optimize channel distribution. The result is clearer dialogue and more detailed surround sound as you are in the middle of the scene.
      Additionally, with Wi-Fi connectivity and the SmartThings app, users can control sound settings, manage group playback, and access music streaming and voice assistant features through a single, intuitive interface. SmartThings also provides instant music controls, making it easy to start listening and adjust playback from any connected mobile device.
      Samsung’s audio lineup also includes the all-new Sound Tower (ST50F and ST40F models) launched in late 2025, offering powerful outdoor and social listening experiences that complement the Music Studio and Soundbar families. Together, these innovations reflect Samsung’s continued leadership at the frontier of home audio, uniting acoustics, design and intelligence to create a sound experience that feels effortless, expressive and deeply connected.
      View the full article
    • By Samsung Newsroom
      The Galaxy Watch ecosystem is designed for seamless connection from capturing screenshots that sync automatically to your phone, to sharing what's on your wrist in seconds. This works great for most users.
      However, if you’re a developer, tester, or creator who prefers working directly on a computer, there’s a more efficient, hands-on way to capture your Galaxy Watch’s display.
      Using Command Prompt (or Windows Terminal) and Android Debug Bridge (ADB), you can directly screen record or capture screenshots from your Galaxy Watch without needing a companion mobile device or any third-party apps. It’s fast, simple, and perfect for creating app demos, tutorials, or development documentation.
      Record your Galaxy Watch screen via ADB
      Follow these steps to record your Galaxy Watch screen directly from your computer:
      Open the Command Prompt and use the cd command to navigate to the platform-tools folder: cd %LocalAppData%/Android/Sdk/platform-tools
      Pair and connect your Galaxy Watch to your computer over Wi-Fi. NoteThe link directs you to steps on how to connect the Galaxy Watch to Android Studio, but you can follow the same steps and commands when using the Command Prompt. Enter the command below to start screen recording your watch: adb shell screenrecord /sdcard/record_demo.mp4
      This command tells your computer (via ADB) to start recording the screen of your connected Galaxy Watch. Let's break it down piece-by-piece:
      adb – connects your computer to the watch or Android device. shell – opens a command-line interface inside the device. screenrecord – starts recording the device's screen. When you run screenrecord, the device starts capturing the display and saves it as a video file (the default format is .mp4). /sdcard/record_demo.mp4 – sets the file path where the recording will be saved on the device and the file name. Stop the recording by pressing CTRL + C.
      Transfer the recorded video to your computer: adb pull /sdcard/record_demo.mp4 C:\Destination\Folder\In\Your_Computer
      The pull command copies the recording from your watch to your computer.
      (Optional) Delete the recording from your watch using the rm command. adb shell rm /sdcard/record_demo.mp4 You now have a recorded video of your Galaxy Watch screen saved directly on your PC, ready for editing or presentation.


      Capture screenshots directly from Galaxy Watch to PC
      If you only need static images, you can easily transfer screenshots from your Galaxy Watch without using a phone:
      Take a screenshot on your Galaxy Watch by pressing the Home and Back buttons simultaneously until you see the screenshot animation.
      Locate the screenshot file using ADB shell and copy its filename.
      adb shell cd sdcard/DCIM/screenshots ls
      NoteYou can also run the simplified version of this command:
      adb shell ls /sdcard/DCIM/screenshots/ The ls command lists the screenshots stored on your watch.
      Transfer the screenshot to your computer: adb pull /sdcard/DCIM/screenshots/[File_Name].png C:\Destination\Folder\In\Your_Computer
      The image is now available on your computer for quick viewing or editing.

      Things to keep in mind
      This method works best with Galaxy Watches running Wear OS powered by Samsung (Galaxy Watch4 and newer models), as these devices support ADB connections for development and debugging. While this approach is highly effective for capturing screen activity, it has some limitations:
      Audio Capture: The screenrecord command records video but does not capture system audio. If you need audio, additional steps or tools may be required. Recording Duration: The recording duration may be limited (typically up to 3 minutes). This restriction can vary depending on the device and ADB implementation. Compatibility: Older Tizen-based Galaxy Watches may not support ADB connections, making this method unsuitable for those devices. Using ADB through Command Prompt provides a direct and efficient way to interact with your Galaxy Watch. Whether you're developing apps, recording demos, or capturing visuals for documentation, these simple commands make it easy to manage your device directly from your computer.
      View the full blog at its source
    • By Samsung Newsroom
      Due to advancements in memory management and performance optimization, Android is transitioning its kernel page size from 4 KB to 16 KB. This change impacts how applications manage memory and requires developers to ensure compatibility, and was addressed in Adding 16 KB page size to Android and Support 16 KB page sizes.
      Google Play has also published a blog post (Prepare your apps for Google Play’s 16 KB page size compatibility requirement) asking developers to support 16 KB page sizes in their applications.
      Native Code
      Applications containing native code must be built to support 16 KB page sizes. Refer to the official Google document for detailed instructions.
      Testing Environment

      Google Android Emulator provides a testing environment for 16 KB pages.
      For real-world testing, Samsung's Remote Test Lab offers a similar environment on actual Samsung devices. See Get Started with Remote Test Lab for Mobile App Testing, a previous Remote Test Lab blog, to check if your application works in a 16 KB page environment. We recommend that you search using the keyword "remote test lab" in the Blog list and look through other posts related to the Remote Test Lab as well.
      Understanding 16 KB Page Size

      For a general understanding of what a page refers to in the context of an operating system (OS), see Page (Computer memory).
      You can think of it as a way of managing DRAM memory in units called pages. For example, if you divide a physical DRAM memory of 32 KB into 4 KB pages, you get 8 pages. If you divide it into 16 KB pages, you get 2 pages. This physical memory is mapped into the virtual address space of each process, and the unit of this mapping is a page. When a process accesses a specific address, it goes through a page table to access the page of the physical memory corresponding to the address. If the page size is increased from 4 KB to 16 KB, allocating and mapping a memory of 16 KB that would have used 4 operations can now be done in just one. This affects not only in-kernel memory management, but also the file system and block layer, ultimately leading to an improvement in performance.
      Kernel mmap & Application Change
      Understanding the mmap API
      In a Linux kernel, user space processes use the mmap API to map files or devices into their virtual address space. One of the arguments in mmap is the offset, which is required to be a multiple of the page size, as shown below.
      Failing to adhere to the requirement will fail the mmap operation. If the application logic assumes that mmap will succeed, this may cause the application to crash.
      Impact of the Page Size Change
      When the kernel page size changes from 4 KB to 16 KB, the mmap's offset value must now be a multiple of 16 KB, not 4 KB. In other words, on a 4 KB page kernel, offsets of 0, 4, 8, and 12 KB work correctly, but on a 16 KB page kernel, offsets of 4, 8, and 12 KB do not.
      You can configure these mmap operations while building an application, but it is also possible the developer did not use the mmap themselves, because in many cases the internal linker performs the mmap automatically. A linker refers to the application's Executable and Linkable Format (ELF) to perform the mmap. It's important to build the application with 16 KB pages to make sure the linker performs the mmap to the correct locations for the 16 KB page kernel.
      To reiterate, if your application includes native code (not just Java), ensure that you have built it to support 16 KB page sizes. For guidance, refer to this Google Document. We have also provided a shell script that you can use to verify that your application supports the 16 KB page size.
      View the full blog at its source
    • By Samsung Newsroom
      SmartThings continues to invest in the Developer Center with tools for partners such as Test Suite, Product Cloning, and Certification by Similarity to simplify product integration and certification for a single product or an entire portfolio. After obtaining Works with SmartThings (WWST) certification, Analytics helps our partners gain valuable insights about how users interact with their products.
      With the goal of making integration easy for partners, SmartThings added another tool in the integration process called the Device Profile Builder, allowing partners to specify a device’s capabilities and how it interacts within the SmartThings ecosystem.
      “We’ve heard from developers that they wanted an easier way to build their devices with SmartThings. A tool with an intuitive user-friendly interface that would work for any device,” says Nate Porras, Senior Product Manager at SmartThings. “We feel like we accomplished that with Device Profile Builder.”
      SmartThings currently offers Device Profile Builder for Cloud integrations and soon for Direct Connected and Mobile Connected integrations.

      Read on to learn about Device Profile Builder and how to get started.
      Device Profile Builder
      SmartThings Device Profile Builder is a web-based tool that assists developers with creating Device Profiles, which define a device and its features on the SmartThings platform through Capabilities. It contains the Components—which is a group of SmartThings Capabilities—and metadata (ID, name, ownership, and more) of a device, defining how a device on the SmartThings platform behaves. For example, with a light, the component contains four common Capabilities for lights including Switch, Switch Level, Color Control, and Color Temperature.
      Use Device Profile Builder to:
      Define how you want your products to look to users in the SmartThings app
      Set SmartThings Capabilities for each of your products
      Get Started
      How to use the SmartThings Device Profile Builder:
      Visit the Products section in the SmartThings Certification Console where you can add a new product or edit an existing one. Under Integration Details / Device Capabilities, click Create a profile here. Or here is the direct link to the Device Profile Builder. Click the button Add new Device Profile and enter a unique name. Add your Capabilities and Components. You can also use product category specific templates to make the process faster. Use the Dashboard View to set how you want your product's icon, action, and state to look in the SmartThings App. Click Create Profile. After creating, you will have options to View, Publish, Edit, Clone, Download File, Upload file, and Delete under the Actions menu. Publish your Device Profile and use it to finish creating your product. Then submit your product to obtain the Works with SmartThings (WWST) certification. You can re-use a device profile for similar products or create as many variations as you need for your portfolio of products.


      Use Device Profile Builder when Creating a Product
      Below is the Create Product section in the Certification Console.
      In this section, you can provide the product details displayed to users across the SmartThings ecosystem.  Some of these include your product name, product image, and product description to help users identify your product. Plus you can add purchase link URLs so users can buy your product.
      When creating a product in the Certification Console, you can use Device Profile Builder to add your device profiles. Under Integration Details / Device Capabilities, click Create a profile here or Edit an existing profile.
      After finishing adding a product in the Certification Console, you can test it using Test Suite, and then go on to submit it for Works with SmartThings Certification (WWST).



      Here are images from the Device Profile Builder. We’ll use the Capabilities for your devices as part of the Works with SmartThings certification.




      Templates
      Get started faster with Templates. Templates are prebuilt sets of required and suggested Capabilities for common product types that help you create your device profile effortlessly. Simply select a product type and apply it to your component.

      Download / Upload File
      For even more customization, you can use the Download / Upload File functions to modify the JSON file. If you have a more complex scenario you want to configure, this functionality gives visibility into all the fields. For example, this can be useful for certain devices that have specific preference thresholds or operating limits, which can be configured for normal or alarm states. There is also an ability for more granular control of what your device looks like in the SmartThings app.


      Want to integrate your products with SmartThings? Visit our Developer Center to get started and access Device Profile Builder.
      View the full blog at its source
    • Government UFO Files





×
×
  • Create New...