Unsure how to run adb commands, also cannot generate a connected_devices.txt

[bounceconnection]

I would like to use this framework to send simple adb commands to multiple devices but it seems that I am unable to. I do not have a connected_devices.txt as asked by the config.ini file and I'm wondering how to generate it as I am unable to.

Also any help in getting a simple adb devices command or even better adb shell am start -a android.intent.action.VIEW -d http://www.google.com to send this command to multiple devices connected to STF, startup a browser, and go to a webpage would be great!

Thanks

[rseek]

Hi, @tomioueda, connected_devices.txt is generated automatically when you use connector.py.
It is a list of devices connected while stf-connect instance is running.

To specify devices to connect you need to modify spec.json file before running connector.py.

After you modify spec.json and run connector.py, you will be able to list connected devices with adb devices. (You need adb client installed on your client machine)

After you connect multiple devices, you can send command to all of them using simple bash script, for example like described here: http://stackoverflow.com/questions/17882474/running-adb-commands-on-all-connected-devices

If your have any problems with connecting devices, please, feel free to ask

[bounceconnection]

To specify devices to connect you need to modify spec.json file before running connector.py.

Are there instructions as to how to go about filling this out? I would like to simply connect all devices that are connected to the STF server.

[rseek]

To connect all devices, your spec.json should be like this:

[
    {
        "group_name": "alfa",
        "amount": "<number of devices on your STF>"
    }
]

Or you can set amount to 9999, but in that case connector.py will connect all devices on your STF and then periodically will ask STF, if there are new devices and connect them if so.

There are some examples in README.md, but it seems we need more simple README.md and some detailed docs

[rseek]

@tomioueda Did it help?

[prashanthd]

When I run connector.py it showing like DEBUG Device LGD8559407806f is available but when I check with command "adb devices", it showing no devices are connected. How to know when I run connector.py whether devices are bind or not to my client(system)?

[rseek]

@prashanthd It seems, you should edit your spec.json file.
spec.json contains specifications of wanted devices.
If you want to connect all devices on your STF, your spec.json should be like this:

[
    {
        "group_name": "alfa",
        "amount": "999"
    }
]

[prashanthd]

@rseek

I got below logs

2016-05-31 19:08:18,987 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:21,992 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:21,993 DEBUG Setting read timeout to None
2016-05-31 19:08:22,016 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:22,118 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:22,119 DEBUG Setting read timeout to None
2016-05-31 19:08:22,134 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:22,236 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:22,237 DEBUG Setting read timeout to None
2016-05-31 19:08:22,251 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:22,354 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:22,355 DEBUG Setting read timeout to None
2016-05-31 19:08:22,365 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:22,467 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:22,468 DEBUG Setting read timeout to None
2016-05-31 19:08:22,481 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:22,583 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:22,584 DEBUG Setting read timeout to None
2016-05-31 19:08:22,598 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:22,599 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:22,600 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:25,605 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:25,606 DEBUG Setting read timeout to None
2016-05-31 19:08:25,630 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:25,733 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:25,734 DEBUG Setting read timeout to None
2016-05-31 19:08:25,743 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:25,845 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:25,846 DEBUG Setting read timeout to None
2016-05-31 19:08:25,859 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:25,962 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:25,963 DEBUG Setting read timeout to None
2016-05-31 19:08:25,972 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:26,074 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:26,075 DEBUG Setting read timeout to None
2016-05-31 19:08:26,088 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:26,191 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:26,192 DEBUG Setting read timeout to None
2016-05-31 19:08:26,201 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:26,202 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:26,202 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
^X2016-05-31 19:08:29,208 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,208 DEBUG Setting read timeout to None
2016-05-31 19:08:29,231 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:29,333 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,334 DEBUG Setting read timeout to None
2016-05-31 19:08:29,349 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:29,451 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,452 DEBUG Setting read timeout to None
2016-05-31 19:08:29,463 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:29,565 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,566 DEBUG Setting read timeout to None
2016-05-31 19:08:29,576 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:29,678 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,679 DEBUG Setting read timeout to None
2016-05-31 19:08:29,690 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
^T2016-05-31 19:08:29,793 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:29,794 DEBUG Setting read timeout to None
2016-05-31 19:08:29,804 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:29,805 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:29,805 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:32,811 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:32,811 DEBUG Setting read timeout to None
2016-05-31 19:08:32,836 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:32,938 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:32,939 DEBUG Setting read timeout to None
2016-05-31 19:08:32,954 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:33,056 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:33,057 DEBUG Setting read timeout to None
2016-05-31 19:08:33,068 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:33,170 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:33,171 DEBUG Setting read timeout to None
2016-05-31 19:08:33,180 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:33,283 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:33,283 DEBUG Setting read timeout to None
2016-05-31 19:08:33,304 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:33,406 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:33,407 DEBUG Setting read timeout to None
2016-05-31 19:08:33,419 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:33,420 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:33,420 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:36,426 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:36,427 DEBUG Setting read timeout to None
2016-05-31 19:08:36,450 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:36,553 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:36,554 DEBUG Setting read timeout to None
2016-05-31 19:08:36,565 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:36,668 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:36,669 DEBUG Setting read timeout to None
2016-05-31 19:08:36,678 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:36,781 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:36,781 DEBUG Setting read timeout to None
2016-05-31 19:08:36,791 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:36,893 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:36,894 DEBUG Setting read timeout to None
2016-05-31 19:08:36,908 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:37,010 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:37,011 DEBUG Setting read timeout to None
2016-05-31 19:08:37,022 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:37,023 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:37,023 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:40,029 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,029 DEBUG Setting read timeout to None
2016-05-31 19:08:40,049 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:40,152 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,153 DEBUG Setting read timeout to None
2016-05-31 19:08:40,164 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:40,266 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,267 DEBUG Setting read timeout to None
2016-05-31 19:08:40,282 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:40,384 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,385 DEBUG Setting read timeout to None
2016-05-31 19:08:40,397 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:40,499 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,500 DEBUG Setting read timeout to None
2016-05-31 19:08:40,513 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:40,615 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:40,616 DEBUG Setting read timeout to None
2016-05-31 19:08:40,629 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:40,629 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:40,630 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:43,635 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:43,636 DEBUG Setting read timeout to None
2016-05-31 19:08:43,660 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:43,762 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:43,763 DEBUG Setting read timeout to None
2016-05-31 19:08:43,776 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:43,878 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:43,879 DEBUG Setting read timeout to None
2016-05-31 19:08:43,890 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:43,992 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:43,993 DEBUG Setting read timeout to None
2016-05-31 19:08:44,007 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:44,110 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:44,111 DEBUG Setting read timeout to None
2016-05-31 19:08:44,122 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:44,225 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:44,226 DEBUG Setting read timeout to None
2016-05-31 19:08:44,241 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:44,242 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:44,242 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
2016-05-31 19:08:47,248 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,249 DEBUG Setting read timeout to None
2016-05-31 19:08:47,271 DEBUG "GET /api/v1/devices HTTP/1.1" 200 6936
2016-05-31 19:08:47,374 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,375 DEBUG Setting read timeout to None
2016-05-31 19:08:47,390 DEBUG "GET /api/v1/devices/edf912d7 HTTP/1.1" 200 1435
2016-05-31 19:08:47,492 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,493 DEBUG Setting read timeout to None
2016-05-31 19:08:47,504 DEBUG "GET /api/v1/devices/ZY2223V4Q5 HTTP/1.1" 200 1319
2016-05-31 19:08:47,607 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,608 DEBUG Setting read timeout to None
2016-05-31 19:08:47,619 DEBUG "GET /api/v1/devices/G1AXB702A106MY7 HTTP/1.1" 200 1448
2016-05-31 19:08:47,721 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,722 DEBUG Setting read timeout to None
2016-05-31 19:08:47,733 DEBUG "GET /api/v1/devices/CC52BYC03680 HTTP/1.1" 200 1525
2016-05-31 19:08:47,835 INFO Starting new HTTP connection (1): 192.168.3.183
2016-05-31 19:08:47,836 DEBUG Setting read timeout to None
2016-05-31 19:08:47,849 DEBUG "GET /api/v1/devices/S51C1LV1L0354591 HTTP/1.1" 200 1306
2016-05-31 19:08:47,850 INFO Got avaliable devices for connect:
[]
2016-05-31 19:08:47,850 INFO Trying connect devices... Wanted Amount: 999. Actual Amount: 0
^C2016-05-31 19:08:49,080 INFO Stopping connect service...
2016-05-31 19:08:49,081 INFO Stopping <STFDevicesConnector(Thread-1, started 139653248751360)>...
2016-05-31 19:08:49,152 INFO Stopping <STFConnectedDevicesWatcher(Thread-2, started 139653240358656)>...
2016-05-31 19:08:49,200 INFO Stopping main thread...
2016-05-31 19:08:49,200 DEBUG Deleting devices from group

what I am trying to do is
using this project I want to bind all the device from openstf to my system and run appium test cases.

but this project not at all binding the devices.

[prashanthd]

I am expecting like when I use this project, when run adb devices it should show devices which are connected to openstf

[prashanthd]

Hi,
Now I am getting like below when I execute adb devices command after running connector.py
ravikumar@ravikumar-pc:~$ adb devices;
List of devices attached
ip:7433 offline

some times getting nothing

[prashanthd]

While running connector.py do we need to run the command "adb connect " to connect to the device? I run that command then I am able to run the test cases.

[rseek]

Hey, sorry for late respone,

I am expecting like when I use this project, when run adb devices it should show devices which are connected to openstf

And it should work as expected, if it doesn't, it means you have some problems either with STF instance itself or with stf-utils configuration. Let's try to localize the problem and fix it.

Now I am getting like below when I execute adb devices command after running connector.py
ravikumar@ravikumar-pc:~$ adb devices;
List of devices attached
ip:7433 offline

That's kinda progress :)
So, please, tell me the present situation. As I understood:

1. You are able to connect device from STF via adb connect, so you can see it in adb devices and you can run tests cases on it
2. After you changed spec.json, you tried to use connector.py, but you can only see offline device in adb devices
   am I right?

While running connector.py do we need to run the command "adb connect " to connect to the device? I run that command then I am able to run the test cases.

By design you don't need to run adb connect, connector.py should do this for you.

[bounceconnection]

Hi Arseniy

Sorry for not replying. Since my post, I had actually left that project and moving on to other opportunities. I apologize for neglecting the post but I hope that this keeps going and your answers help future developers in the future!

Sent from my iPhone.

On Jun 15, 2016, at 11:34 PM, Arseniy Rozov notifications@github.com wrote:

Hey, sorry for late respone,

I am expecting like when I use this project, when run adb devices it should show devices which are connected to openstf

And it should work as expected, if it doesn't, it means you have some problems either with STF instance itself or with stf-utils configuration. Let's try to localize the problem and fix it.

Now I am getting like below when I execute adb devices command after running connector.py
ravikumar@ravikumar-pc:~$ adb devices;
List of devices attached
ip:7433 offline

That's kinda progress :)
So, please, tell me the present situation. As I understood:

1. You are able to connect device from STF via adb connect, so you can see it in adb devices and you can run tests cases on it
2. After you changed spec.json, you tried to use connector.py, but you can only see offline device in adb devices
   am I right?

While running connector.py do we need to run the command "adb connect " to connect to the device? I run that command then I am able to run the test cases.

By design you don't need to run adb connect, connector.py should do this for you.

―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.