语言

Menu
Sites
Language
Installing integrated Gear 2 apps on Samsung Remote Test Lab

Hi. I have made an integrated Gear 2 app, but I haven't got a Samsung Galaxy device and due to that I have to test it using Samsung Remote Test Lab, but when I install the apk (the apk is generated selecting my provider project and clicking on file -> export -> Export Android Application) to the Samsung Remote Test Lab Phone Emulator (I was using a Samsung Galaxy S4 emulator with Android 4.4.2), the app works fine on the Gear 2 (the Consumer part), but it doesn't connect to the phone (to the Provider part of the integrated app).

I saw a video from Samsung Developers where the man says that to test an integrated app using a real Samsung Galaxy device and the Gear 2 emulator, it's neccessary to install three apks from the following URL: http://img-developer.samsung.com/contents/cmm/Applications_for_Emulator.zip , but I don't have a real Samsung Galaxy device, so I don't have to install them.

So, how can I install an integrated Gear 2 app on the Samsung Remote Test Lab Emulator? Should I install those apks?

 

Thanks.

编辑者为: Fernando García Álvarez 开 16 7月, 2014
列表

响应

2 回复
AVSukhov

Hello,

May be this article help you:

https://developer.tizen.org/forums/general-support/how-connect-gear2-emulator-devices-or-emulators?langredirect=1

Michelle Somerville

When you use the Samsung Remote Test Lab (RTL) you are not using emulators, you are actually connecting to real devices through a web interface.

 

To run and test your applications on the RTL devices you do not need to follow any of the instructions detailed in that video. Those instructions are for connecting a real Samsung host device to the Wearable emulator running in your own development environment.

 

If you installed the Gear (consumer) app successfully on the RTL device from within your Android (provider) app, the devices are connected. There must be an issue with your SAP code if the Gear app is not communicating correctly with the host. You’ll need to add some debug code to track down the issue.