remote test lab use the remote test lab service to test your applications on a real device. get started get started featured devices don't have a samsung device to test your app? no problem! test your apps on the latest samsung galaxy devices in our remote test lab. qled 4k tv galaxy z fold5 galaxy watch6 galaxy tab s9 ultra galaxy s23 ultra how to get started test your apps over the web in three simple steps step 1. sign up - it’s free! not a member? sign up now. step 2. select your preferences to learn more about using remote test lab, refer to the developer documentation. step 3. start testing go to the remote test lab page, and click start testing. remote test lab introduction remote test lab is a service that enables developers to control devices remotely. in this video, you will learn how to use remote test lab. video thumbanil video thumbanil how to test your mobile apps through a web browser in this video, you will learn how to test your mobile apps through a web browser using the remote test lab web client. remote test lab for tv use the remote test lab service for tv to test and verify your tizen tv app on a real device. provide feedback do you have feedback? are we missing a device? are we not supporting your 5k monitor? send us feedback about how we can improve this service. send us feedback

in the previous post, we introduced remote test lab, a service that enables you to test your application on a real mobile phone or watch device by interacting with it over the internet in real time. since last year, we have added more features for you to expand your test coverage. in this article, we introduce two new features available on the remote test lab service. many apps play a variety of common media types, such as audio, video, and images. previously, remote test lab showed the screens of real devices, but without any audio, which was inconvenient for testing audio features. we have now added an audio streaming feature that allows you to listen to the audio played through the test device in addition to seeing the device screens. the other new feature is multi-touch gesture support. this allows multiple pointers (fingers) to touch the device screen at the same time, enabling you to test scrolling, zooming in and out, and rotation gestures, on apps such as in google maps. start audio streaming the remote test lab client supports the audio streaming feature on devices running android 10 and newer. if you launch the remote test lab client, you can see the contextual menu by clicking the right mouse button. to start streaming, click experimental > start audio stream in the contextual menu. for security and privacy reasons, audio stream capture has some limitations. to be able to capture audio, the client brings up the prompt displayed by createscreencaptureintent(), and you must approve it. if you do approve, you can listen to the sound of the test device, with the exception of certain streams such as audiomanager#stream_ring, audiomanager#stream_alarm, and audiomanager#stream_notification. after audio streaming is started, the contextual menu item changes to stop audio stream. to stop streaming, click the menu item. for more information on media capture, see mediaprojectionmanager in the android api reference. use multi-touch gestures the remote test lab client also supports multi-touch gestures. in smartphone apps, multi-touch gestures include scrolling, zooming in and out, and rotation. although you cannot directly touch the screen on the remote test lab device, you can use your keyboard and mouse to perform multi-touch gestures on it, such as while using google maps. to use multi-touch gestures in remote test lab: press and hold the shift key on your keyboard. click on the device screen. without releasing the shift key, click and drag on the device screen to perform the gesture you want. to complete the multi-touch gesture, release the shift key. the following video shows how google maps responds to multi-touch gestures: remote test lab article series get started with remote test lab for mobile app testing loop test with auto-repeat (coming soon) run and test applications with remote debug bridge in android studio (coming soon) web-based client preview (coming soon) go to remote test lab follow up this site has many resources for developers looking to build for and integrate with samsung devices and services. stay in touch with the latest news by creating a free account or by subscribing to our monthly newsletter. visit the marketing resources page for information on promoting and distributing your apps. finally, our developer forum is an excellent way to stay up-to-date on all things related to the galaxy ecosystem.

remote test lab for tv remote test lab is a solution that makes it easy for tv application developers to use any real tvs they want. if you have an internet-connected pc, you can configure a remote development environment using a real tv. we support various models based on product and year, and no further effort is required to get access to specific models. all you need is your pc. back to list

on april 30th, the remote test lab service was upgraded to version 2.0. with its new features and superior usability, the all-new remote test lab service makes remote testing a sheer pleasure. the remote test lab is a free service from samsung developers. with it, you can access a remote physical device through a network, install an application and test it remotely. for more information, click the url below. about remote test lab: https://developer.samsung.com/remote-test-lab the following shows you how to take advantage of the new features in the all-new remote test lab. 1. support for keyboard input while using the remote test lab, you may need to enter text into your remote device. so far, the virtual keyboard on remote devices has been used for this. the remote test lab now supports keyboard input, so whatever you type through your keyboard, while the rtl client is activated, will be sent to the remote device through the rtl client. 2. enable to change screen quality mode at low network speeds, you may want to streamline your experience to ensure it remains responsive and tests perform as expected. changing the screen quality mode image normal high the new remote test lab provides two quality modes for your testing convenience. when used with low network speeds, "normal" mode provides a more responsive experience. when connected to a faster network, choose "high" mode to increase the accuracy of the test. 3. support to change screen orientation mode by default, all devices support portrait and landscape modes. as long as your application supports both modes, you can easily test it through the new remote test lab. this feature is supported in android 4.0 (ice cream sandwich) and higher. 4. application lifecycle management the new remote test lab lets you manage the entire life cycle of your application - installing, running, uninstalling and exiting – all in one place, so you don’t have to use the handset ui or look for individual icons on the remote device’s screen. this feature will reduce the testing time. 5. support to reboot device sometimes, it is necessary to reboot a remote device when you use remote test lab. the new remote test lab lets you easily reboot remote devices. normally, you the rtl client screen will update when the device is completely rebooted and ready for use. the new remote test lab provides not only the new features mentioned above, but also a more stable service through an overall rebuild of the system. use the remote test lab to ensure your application runs as expected on multiple devices and register it on samsung apps! link to the remote test lab page

this blog is the fourth in a series of posts about remote test lab (rtl). in previous blogs, we covered what is remote test lab, its new features, and auto repeat. in this blog, we show you how to connect rtl to android studio and how to deploy and debug your app on the remote device. in an upcoming blog, we are going to take a deep dive into some additional features of remote test lab. remote test lab allows you to run and debug your application on real devices remotely. in this blog, we will connect a remote test lab device with a local development machine’s adb (android debug bridge) using remote debug bridge. the remote debug bridge tool enables you to run and debug your app to check compatibility with the latest samsung mobile devices, which solves the problem of not having your own physical devices. connect your remote test lab device to android studio to get started, launch a remote test lab client, then go to remote test lab and reserve one of the available mobile devices. the operating system version, device location, and desired time can be selected on the remote test lab page. a jnlp file is downloaded to your computer when you click the start button. if you run this file, the remote test lab client is launched and a live image of the device is shown in the client. step 1. when the live image is shown, right-click on the device's screen and select ‘test > remote debug bridge.’ step 2. in the pop-up window, view the required command and port number to connect your android studio to the remote test lab device. step 3. open a command prompt window and run the adb command with the given port number. in this example, the command is: adb connect localhost:50964 note: you must accept the rsa key prompt by allowing usb debugging when you run the adb connect command for the first time on a remote test lab device. deploy and debug apps from android studio step 1. the device is now ready to deploy your app from android studio. build and run your app from android studio. in the following screenshot, an app is being deployed on a remote test lab device from android studio. step 2. the app is deployed and launched successfully on the remote test lab device step 3. debug your app from android studio just like on a real device. in conclusion, remote test lab offers a convenient and effective way to check the compatibility of your app and use debug facilities. finally, our developer forum is an excellent way to stay up-to-date on all things related to the samsung galaxy ecosystem. remote test lab article series get started with remote test lab for mobile app testing what's new in remote test lab testing your app with auto repeat using remote test lab with android studio web-based client preview (coming soon) go to remote test lab

remote test lab is a service that enables developers to control mobile and watch devices remotely. with the remote test lab service, you can test your application on a real device by interacting with the device over the network in real time. the remote test lab service is an easy and effective way to comprehensively test your application’s compatibility with the latest samsung mobile devices, while reducing your spending on test hardware. remote test lab highlights application installation you can install and test android and tizen applications on the appropriate devices. screen capture and recording you can capture or record the screen during testing, whenever you need it. audio streaming you can listen to the audio played through the testing device. repeat testing you can record a sequence of actions and replay the sequence multiple times. remote debug bridge you can access the remote device through development tools, such as android studio, as if the device were connected to your computer. test applications on a remote real device in your web browser, go to distribute > remote test lab on the samsung developer site. before using remote test lab, make sure you have the system requirements: samsung account standard web browser with javascript support java runtime environment (jre) 7 or later, including java web start internet environment with port 2600 outbound open you can select the operating system, remote device, and testing time you want on the remote test lab page. when you select start, a jnlp file is downloaded to your computer, and when you run the file, the remote test lab client is launched and the live image of the device screen appears on the client. you can use the remote test lab device as if it were the real device. for example, you can even zoom in and out on google maps using multi-touch. a variety of testing tools are available in the client context menu: screen menu: screen quality control, orientation, scale, capture and record, screen share manage menu: application manager, clipboard synchronization, language, file manager, wi-fi reset, device reboot test menu: install application, auto-repeat, log viewer, remote debug bridge experimental menu: audio streaming for more information on the tools in the context menu, see the user manual. you can install your application on the remote device by dragging and dropping the application package from your computer into the remote test lab client. through the client, you can watch how the application behaves on the device, including in views such as flex mode on galaxy fold devices. for more details about the remote test lab service and its policies, see the remote test lab support. next coming up blogs on remote test lab: what's new featues on remote test lab loop test with auto-repeat run and test applications with remote debug bridge in android studio web-based client preview go to remote test lab

this blog is the third in a series of posts about remote test lab. in previous blogs, we covered what is remote test lab and its new features. next, we are going to take a deep dive into some useful features of remote test lab. the remote test lab service lets you install and test your applications on real devices. in this blog, we are going to install an application and test it on remote test lab devices with auto repeat. auto repeat is a tool that lets you create a test scenario automatically, repeat the same test several times, and reuse the test later. information: the auto repeat feature is supported on a java-based client only. install your application to get started, launch a remote test lab client, then go to remote test lab and reserve one of the available mobile devices. you can install your application on the remote device by dragging and dropping the application package from your computer into the remote test lab client. through the client, you can watch how the application behaves on the device. you can also install applications by going to management > application manager or selecting test > install application in the device context menu. install your application in any of the ways described above. record and play events recording and playing back events is one of the ways to test your applications automatically. when you record events for repeated testing, we recommend that you start and finish recording at the same screen on the remote test lab client. the following figure shows the most commonly used buttons in the auto-repeat window. ① the add button lets you add more actions manually. ② the record button starts recording actions on your device screen. ③ the play button starts playing a test. ④ the stop button stops playing a test. to start recording a test scenario, proceed as follows: click test > auto repeat in the context menu on the remote test lab client. in the auto repeat window, click the record button. once the record button is clicked, all events on the rtl client are recorded. the recorded events are added to the event list in the auto repeat window. click the stop button when you want to stop recording. the number of events and how long the test took to run appear under the event list. to run the test repeatedly, enter a number into the test repeat field in the test option section. click the play button. monitor the progress of your test in the auto repeat window. you can check the completion progress as well as which step is currently running. click file > save. an xml file is saved to your computer. you can reuse the xml file to test your application on other devices with the same resolution. the following video shows each step of recording events and playing back the test procedure. create test sequences manually you can also create a test scenario by adding events manually. this method can be more complicated but it lets you insert a wide variety of events to your scenario. to add an event to your test scenario, proceed as follows: click the add button in the auto repeat window. select a desired event. the selected event is added to the event list section. fill in the related information in the event properties section. every event has its own properties. properties you do not need to fill in are marked with n/a in the event list section. if a mandatory property is missing, the test isn't performed. click the play button. the following video shows each step of adding events manually. you can create complete test scenarios by recording events or manually add more events to make the test scenarios more sophisticated. remote test lab article series get started with remote test lab for mobile app testing what's new in remote test lab run and test applications with remote debug bridge in android studio (coming soon) web-based client preview (coming soon) go to remote test lab

last year, we released the latest version of remote test lab that supports the new web-based client and provides a user experience comparable with a real device. today, we are happy to introduce a new feature, remote debug bridge, that allows application developers to test and debug applications easily by creating an android debug bridge (adb) connection to a real device on the remote test lab in android studio. what is remote debug bridge? remote debug bridge (rdb) allows developers to use an android device provided by the remote test lab service in android studio. if you connect rdb with the web-based remote test lab client, you can see our remote devices in the android device manager and can have the same experience as a physical device connected to your host pc. reserve android device on remote test lab to use a remote device, first go to remote test lab. remote test lab provides over 1500 different devices, ranging from mobile devices, including the latest foldable models, to the newest smart watches. to use an android device, click "galaxy mobile" on remote test lab and then select one of the devices. for more information on how to use remote test lab, refer back the previous post: test your apps in multiple regions with the new web-based remote test lab run remote debug bridge application to run rdb, adb is also required. if you have not installed adb already, you must install it first. to download the rdb application: launch the remote test lab web-based client and click "remote debug bridge" on the navigation menu. click "connect" on the menu pop-up. if the rdb application is not running on your host pc, the download pop-up is shown. if you have already downloaded the file, you don't have to download it again and can move directly to the connect remote device section. click the "download" link on the pop-up to download the application to your host pc as a zip file. install the rdb application. the installation procedure differs slightly depending on your operating system: windows double-click on the downloaded zip file to unzip it. click on "rdb.exe" to run the application. you can see a command window running "rdb." macos double-click on the downloaded zip file to unzip it. click on "rdb" to run the application. you can see a command window running "rdb." linux open a terminal and move to the download directory. unzip the file:$ unzip rdb.zip run "rdb" on the terminal:$ ./rdb note : do not close the window running the rdb application while you are using the device with android studio. connect remote device to connect a remote device to your host pc: click the "connect" button on the "remote debug bridge" menu pop-up. the text on the menu pop-up is changed to "disconnect" when the connection between the device and your host pc is established. if the web-based client shows an rsa dialog on the screen preview, click the "allow" button. note : when you connect to a device running android 4.2.2 or higher, the system shows a dialog asking whether to accept an rsa key that allows debugging through this computer. this security mechanism protects user devices because it ensures that usb debugging and other adb commands cannot be executed unless you are able to unlock the device and acknowledge the dialog. now you are ready to use the device provided by remote test lab. use device in android studio when the connection between the device and your host pc is established, android studio shows the device name on the running devices list box. the device is also shown on the "physical" tab on the device manager. once the device is connected, you can also run adb commands in the command window or terminal. if you have any feedback about how we can improve our service, send us a support request.

if you are a watch face designer and want to distribute your watch face, it is highly recommended that you test your watch face on a real device before publishing it. while galaxy watch studio (gws) provides an emulator (the run window) on which to run your watch face, it is not the same as running it on an actual device. remote test lab (rtl) is a service that allows you to test your app on a real device, access the device remotely through the web, and it’s free! rtl is an amazing solution if you can’t buy a device or if you want to test your watch face on different watch models. this reduces your hardware costs for testing a watch face. design a watch face if you don’t have a watch face to test, here is how to create a simple design using gws. launch gws and create a new project. for simplicity, add a background, analog clock, and digital clock. the digital clock is used to add a time zone selector. the intention behind using the time zone selector is because we can’t test the tap action using the run window. so, a real device is needed to test the time zone selector. if you want to know how to make a time zone selector, you can read this blog. after completing the design, you have to build the project so that a .tpk file is created. go to project > build, set the target api version, enter the password for your author certificate, and click build (see image below). if you don’t change the location path of the workspace folder, then the .tpk file is saved in c:\users\user_name\gearwatchdesigner\workspace. get started with rtl there are a few system requirements to run rtl on your pc. read about remote test lab from here. the system requirements are: a samsung account standard web browser with javascript support java runtime environment 7 or later with java web start. internet environment where port 2600 is available. first, go to remote test lab and sign in using your samsung account. if you don’t have a samsung account, create one and then sign in. next, click get started. now, select watch from left sidebar. there are four types of devices and os versions that are available (on 26th june, 2020): device name model name os version galaxy watch sm-r800 tizen 4.0.0.2 gear sport sm-r600 tizen 3.0.0.2 gear s3 sm-r765a tizen 3.0.0.2 gear fit2 sm-r360 tizen 2.3.1.6 choose a device based on your requirements. in the following example, galaxy watch is selected for testing. select the os version for the galaxy watch. select any available device from the device list. in the device name, in, kr, or us indicates the country in which the device is located. it is better to choose the closest country to avoid latency issues. for example, if you are in korea, you should select kr. choose the amount of time to reserve the device from reserve time. higher reservation times require more credits (credits are free and you receive a limited number every day), so it would be wise if you don’t reserve unnecessary time. after selecting all options for your selected device, click start. the details of your selected device are shown. if a download window displays, click on start to download the jnlp file. run the jnlp file to download the rtl client. the download window displays when the rtl client is downloaded for the first time or an updated version is available. after launching the rtl client, click run. the time to launch a device on rtl may vary depending on your network environment. a warning box appears. read the warnings and click** i understand and wish to proceed.** next, choose the language of your selected device. test your watch face on rtl after starting the device, follow the steps below to install and run your watch face. right-click on the watch to launch the context menu. to learn about all features of the context menu, read rtl client features. click on test > install application from the look in dropdown menu, navigate to the directory that contains the .tpk file which you want to test. select the .tpk file and click open. a dialog box shows the progress of opening the selected file on the remote device. click install from the application manager. click ok after installing the watch face. click on the default watch face. rotate the bezel clockwise or counter-clockwise to select your installed watch face. when you find your installed watch face, click on it to launch it. now, click on the digital clock to change the time zone for testing the time zone selector tap action. search for and select your desired city to change the time zone exit from the remote device it is recommended to uninstall your application from the remote device after completing your test. tap on the watch face and click on the delete icon to uninstall the watch face. now, right-click on the watch and click exit to close the remote device. using rtl, you can test your watch face designs on different watch models and different tizen versions of your targeted users. you can do it anywhere, even if you are not at home or in the office. remote test lab allows you to test your watch faces on many devices even if you have a small budget.

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