Devices stuck in preparing, cycling service start #730
Comments
therock24
changed the title
Let me knom if it fixes your issue? |
|
I seem to have the same problem as reported in #692 |
|
@denis99999 it seems to be only the Google devices, for example I have a Samsung Galaxy on Android 14 that works fine The 3 devices that does not work are Google devices, the amazing thing about them is that lsusb reports them as Samsung devices!, I did play with the udev rules, but it still says Samsung Please let me know if you need more information |
|
@KingRat0011 ; on my side Google devices work fine in Android 14, try to upgrade your ADB binary to a recent version, it seems to be very old as well as your OS, what is it ? Also, to ensure your Google device is well supported by the latest STF version, make a test with the official docker image of STF! |
|
@denis99999 I've tried in the past to follow the docker deployment https://github.com/DeviceFarmer/stf/blob/master/doc/DEPLOYMENT.md, but failed, are there any step by step deployment guides that you are aware off for Ubuntu maybe?. I'm not understanding the deployment, for example the statement "You have two static IPs available for the main communication bridges (or "triproxies"), or are able to figure out an alternate method. In this example we'll use devside.stf.example.org and appside.stf.example.org as easy to remember addresses." where are these 2 IPs, on the main STF server? on the Rethink DB server and lots of other questions.... |
|
@KingRat0011 , you have just to download the docker image and launch it properly in local mode (i.e stf local ..), you can do the same with ADB and rethinkdb, managing them through a docker-compose file, there are a lot of examples on the net. |
|
Hi @denis99999 The adb docker container, was it build for RPI's? I can build the normal adb on the RPI, would I be able to use that? |
|
@KingRat0011 , if you are using a Raspberry Pi I recommend you to install the |
|
Thanks @denis99999 , I'll try the stf, rethinkdb docker on the main server and use the adb build from the RPi, hope this will work.. |
|
@KingRat0011 , you have also to run STF on the Pi, at least a device provider service! |
|
Yep that will be the challenge as I cannot use the standard docker images on the RPi |
What is the issue or idea you have?
I have 4 devices plugged in and working fine, stf was able to prepare them.
1 of these devices are always in preparing state and stf log shows cyclic retries indefinetely.
Does it only happen on a specific device? Please run
adb devices -land paste the corresponding row.H5517MCA0N7412W device usb:1-7.3 product:full_tb8765ap1_bsp_1g model:T1 device:tb8765ap1_bsp_1g transport_id:6
Please provide the steps to reproduce the issue.
I am just starting stf with this command
stf local --no-cleanup --public-ip 10.x.x.x
What is the expected behavior?
The devices should become ready.
Do you see errors or warnings in the
stf localoutput? If so, please paste them or the full log here.(1) cyclic service restart device
Please run
stf doctorand paste the output here.The text was updated successfully, but these errors were encountered: