Testing Watch Faces in Remote Test Lab through Watch Face Studio
custom watch faces are a popular way for users to customize their smartwatches. watch face studio (wfs) is a universal gui tool that allows you to design watch faces for wear os devices. it supports various samsung galaxy watch features, such as styles, tags, sensors, and complications. although you can preview your watch face design and many of its features on the emulator included in wfs, some visuals and behavior can be different on a physical device. to ensure your watch face functions correctly on all the latest galaxy watches, remote test lab (rtl) enables you to test your applications on actual samsung galaxy devices without having physical access to them. advantages of testing your watch face in rtl include convenience and cost savings from having access to a range of galaxy watches without having to own them yourself, and the ability to test features that are not supported by the wfs emulator, such as watch face complications and launching applications from them. this article uses a sample watch face with some simple complications to demonstrate how you can make use of rtl to test a watch face created in wfs. the basic steps are to reserve and connect to an rtl device, link it to your computer through remote debug bridge (rdb), and then deploy the watch face to the device from within wfs. figure 1: sample watch face in wfs reserve a galaxy watch on remote test lab because rtl is a virtual credit-based time-limited service, to take full advantage of your credits and allotted time, make sure your project is ready to test before connecting to rtl. to reserve and connect to a remote device on rtl: sign in to the samsung developers website. in the “support” menu, select “remote test lab.” to view the device list, click “get started.” the device list shows all the available devices on rtl. to list the smartwatches only, select “galaxy watch” from the side menu. figure 2: available watches on rtl select the device you want to test the watch face on. select the physical location of the device you want to use and define the duration you want to reserve it for. figure 3: rtl device location and duration selection notereserving rtl devices consumes virtual credits. the cost depends on the duration of your reservation. the number of credits available on your samsung account is shown at the top right of the screen. to earn 10 credits once per day, click the “my credits” text. when you are ready, click “start.” the device launches in a new window. connect the computer to the remote device use the remote debug bridge (rdb) tool to connect the rtl remote device to your computer: from the sidebar of the rtl device window, select “remote debug bridge” and click “connect.” click “download” to download the rdb tool and “ok” to close the dialog. figure 4: rdb download in rtl extract the content of the downloaded file to a folder. run the “rdb.exe” application. a terminal window opens and listens for the rdb connection from the rtl server. figure 5: launching rdb return to the rtl window, select “remote debug bridge,” and click “connect” again. a connection is established between your computer and the rtl device. figure 6: adb connected to remote device through rdb the remote device is now connected to your computer. it responds to android debug bridge (adb) commands, such as “adb devices,” in the same way as if you had connected to a physical device in your possession. for more information on connecting your computer to devices on rtl, see connect to devices on remote test lab using rdb in android studio. noteto ensure adb commands work correctly, you must have adb already installed and added to your path environment variable. adb is included with your wfs installation. to add adb to the “path” environment variable on a windows computer: navigate to “start > control panel > system and security > system > advanced system settings > environment variables.” in the “user variables” section, select “path” and click “edit.” to add a new entry to the list, select “new.” enter the path to the “\tools\window” subfolder of your wfs installation folder, for example, “c:\program files\watchfacestudio\tools\window.” click “ok” and close the dialog. relaunch your terminal window. to add adb to the “path” environment variable on a macos computer: open a terminal window. enter the following command: “export path=$path:/applications/watchfacestudio.app/contents/tools/mac.” if your installation of wfs has a different location or application name, modify the command accordingly. relaunch your terminal window. deploy the watch face to deploy a watch face from wfs to the rtl device: in wfs, open the watch face project. click “run on device” at the top right of the screen. the “connected devices” window appears, listing the available devices. figure 7: remote device in “connected devices” list to deploy the watch face to the remote device, select the device from the list. deployment is complete when the “launch complete” dialog appears in wfs. your watch face is launched on the remote device. figure 8: watch face on the rtl device if the watch face does not launch on the remote device automatically, select it on the watch: to open the watch face menu, press and hold on the watch face home screen. swipe right until you reach the “add watch face” screen or a “+” button. tap the “+” button. to find the watch face that you deployed, scroll to the end of the watch face list. to select the watch face, tap the image of the watch face or the “download” button. figure 9: selecting the watch face test the watch face now you are ready to test the watch face on the rtl device. the following steps demonstrate testing watch face complications. to add a complication to the watch face: to open the watch face menu, press and hold on the watch face. select “customize.” the “styles” screen opens. scroll to the “complications” screen, which shows the available complication slots on the watch face. select a complication slot and confirm allowing the watch face to access watch data. figure 10: customizing complications select the complication you want to add to the watch face. in the following figure, the “chance of rain” and “battery” complications have been added. figure 11: custom complication on watch faces test the watch face in the same way as on a real device. for example, tapping a complication launches the appropriate application. when the battery widget is tapped, the battery application launches on the watch. the wfs emulator does not support this feature, showing only that the “‘complication slot’ is opened.” because the rtl device is a real device, you can observe the actual watch face behavior in real time. figure 12: custom complications on wfs emulator and on rtl device when testing is complete, disconnect rdb by selecting “disconnect” from the “remote debug bridge” menu and close the rtl window to end the rtl session. summary to comprehensively test your watch face, you can easily connect your computer to remote test lab devices and deploy the watch face to it through watch face studio. rtl allows you to test on a wide range of samsung galaxy watches without having physical access to them. because the rtl devices are real devices, you can also test watch face features that are not supported by the emulator. if you have questions or need help with the steps presented in this article, you can share your queries on the samsung developers forum. you can also contact us directly for more specialized support through the samsung developer support portal. additional resources to learn more about watch face studio, watch face complications, and remote test lab, check out the following links: watch face studio user guide design complications using watch face studio connect to devices on remote test lab using rdb in android studio troubleshooting common issues while using the remote test lab service