DeviceFarmer / stf

Control and manage Android devices from your browser.
https://devicefarmer.github.io
Other
3.52k stars 497 forks source link

No display screen #753

Closed LiWeiMr closed 10 months ago

LiWeiMr commented 10 months ago

I built it through docker, and after testing various models, the screen could not be displayed. The following is the specific log and display situation。

2024-01-24T13:16:13.533Z INF/device:plugins:touch 145 [37964b7a] minitouch says: "Note: device /dev/input/mouse0 is not supported by libevdev" 2024-01-24T13:16:13.543Z INF/device:plugins:display 139 [217ec694] Reading display info 2024-01-24T13:16:13.599Z INF/device:plugins:phone 139 [217ec694] Fetching phone info 2024-01-24T13:16:13.633Z INF/device:plugins:touch 145 [37964b7a] minitouch says: "Note: device /dev/input/mice is not supported by libevdev" 2024-01-24T13:16:13.647Z INF/device:plugins:identity 139 [217ec694] Solving identity 2024-01-24T13:16:13.660Z INF/device:plugins:solo 139 [217ec694] Subscribing to permanent channel "KOuGQ1o0ntrhYRlVDSCIWHT3Eto=" 2024-01-24T13:16:13.665Z INF/device:plugins:screen:stream 139 [217ec694] ScreenGrabber option set to minicap-bin 2024-01-24T13:16:13.667Z INF/device:plugins:screen:stream 139 [217ec694] ScreenFrameRate option set to -1 2024-01-24T13:16:13.669Z INF/device:plugins:screen:stream 139 [217ec694] Starting WebSocket server on port 7400 2024-01-24T13:16:13.684Z INF/device:plugins:screen:stream 139 [217ec694] creating FrameProducer: minicap-bin 2024-01-24T13:16:13.733Z INF/device:plugins:touch 145 [37964b7a] minitouch says: "Type B touch device synaptics,s3320 (1079x1919 with 10 contacts) detected on /dev/input/event3 (score 22447)" 2024-01-24T13:16:13.966Z INF/device:resources:minitouch 139 [217ec694] Installing "/app/node_modules/@devicefarmer/minitouch-prebuilt/prebuilt/arm64-v8a/bin/minitouch" as "/data/local/tmp/minitouch" 2024-01-24T13:16:14.066Z WRN/device:plugins:data 139 [217ec694] Unable to find device data { serial: '217ec694', platform: 'Android', manufacturer: 'XIAOMI', operator: '中国联通,中国联通', model: 'MI 6X', version: '8.1.0', abi: 'arm64-v8a', sdk: '27', product: 'wayne', cpuPlatform: 'sdm660', openGLESVersion: '0.0', marketName: 'MI 6X', display: { id: 0, width: 1080, height: 2160, xdpi: 403.4110107421875, ydpi: 403.4110107421875, fps: 60.000003814697266, density: 3, rotation: 0, secure: true, size: 5.98633490755939, url: 'ws://192.168.1.101:7400' }, phone: [Object: null prototype] { network: 'LTE' } } 2024-01-24T13:16:14.080Z INF/device:plugins:touch 139 [217ec694] Touch origin is top left 2024-01-24T13:16:14.084Z INF/device:plugins:touch 139 [217ec694] Requesting touch consumer to start 2024-01-24T13:16:14.090Z INF/device:plugins:touch 139 [217ec694] Launching touch service 2024-01-24T13:16:14.106Z INF/device:plugins:touch 145 [37964b7a] minitouch says: "Connection established" 2024-01-24T13:16:14.110Z INF/device:plugins:touch 139 [217ec694] Connecting to minitouch service 2024-01-24T13:16:14.113Z INF/device:plugins:touch 145 [37964b7a] Reading minitouch banner 2024-01-24T13:16:14.151Z INF/device:plugins:touch 139 [217ec694] minitouch says: "Note: device /dev/input/mice is not supported by libevdev" 2024-01-24T13:16:14.155Z INF/device:plugins:touch 139 [217ec694] minitouch says: "Note: device /dev/input/mouse0 is not supported by libevdev" 2024-01-24T13:16:14.160Z INF/device:plugins:touch 139 [217ec694] minitouch says: "Type B touch device NVTCapacitiveTouchScreen (1079x2159 with 10 contacts) detected on /dev/input/event2 (score 22535)" 2024-01-24T13:16:14.164Z INF/device:plugins:vnc 145 [37964b7a] Starting VNC server on port 7406 2024-01-24T13:16:14.178Z INF/device:plugins:browser 145 [37964b7a] Loading browser list 2024-01-24T13:16:14.221Z INF/device:plugins:browser 145 [37964b7a] Updating browser list 2024-01-24T13:16:14.224Z WRN/device:plugins:browser 145 [37964b7a] Unmapped browser "com.netease.cloudmusic" 2024-01-24T13:16:14.229Z WRN/device:plugins:browser 145 [37964b7a] Unmapped browser "com.sina.weibo" 2024-01-24T13:16:14.235Z WRN/device:plugins:browser 145 [37964b7a] Unmapped browser "com.youdao.dict" 2024-01-24T13:16:14.240Z WRN/device:plugins:browser 145 [37964b7a] Unmapped browser "com.jingdong.app.mall" 2024-01-24T13:16:14.249Z INF/device:plugins:touch 139 [217ec694] minitouch says: "Connection established"

微信图片_20240125084903 微信图片_20240125084907

yunki-cmd commented 10 months ago

Are the provider's port ranges connected to the rest of the components?

LiWeiMr commented 10 months ago

Are the provider's port ranges connected to the rest of the components?

Thank you for your reply, but I don't quite understand what you mean. Current android phones are on the same machine where docke is deployed and are not connected to other devices

denis99999 commented 10 months ago

@LiWeiMr , please fill the issue template correctly with expected information, please provide in detail your architecture, how STF is deployed (local or distributed mode) and associated files, launching commands, etc.. Please open developer tools in your browser to see what is the error? Did you build the STF docker image yourself ? If yes, try with the docker image provided by DeviceFarmer.

LiWeiMr commented 10 months ago

My current system is centos7 stf is docker pull devicefarmer/stf:latest docker pull rethinkdb:latest adb already exists locally, so I did not pull the corresponding docker, but I pushed a copy to stf docker to ensure that adb devices can be obtained in stf docker. The start commands are in sequence: docker run -d --name rethinkdb -v /srv/rethinkdb:/data --net host rethinkdb rethinkdb --bind all --cache-size 8192 --http-port 8090 docker run -d --name stf --net host devicefarmer/stf stf local --public-ip 192.168.1.101. Captured when I opened my browser's developer tools 0.3571155fdc1069373bba.chunk.js:83316 WebSocket connection to 'ws://192.168.1.101:7110/socket.io/?uip=%3A%3A1&EIO=3&transport=websocket' failed WebSocket is closed before the connection is established.

denis99999 commented 10 months ago

@LiWeiMr , did you checked the 7110 socket port is reacheable from your browser client? Try to take a network trace (tcpdump or wireshark tools) to see exactly the issue?

LiWeiMr commented 10 months ago

@LiWeiMr , did you checked the 7110 socket port is reacheable from your browser client? Try to take a network trace (tcpdump or wireshark tools) to see exactly the issue? Hello, I have checked that port 7110 is indeed inaccessible. What is the cause of this problem? How should I deal with it?

denis99999 commented 10 months ago

@LiWeiMr this means that this port is not open either on the server side because of an internal firewall, or on the path between client and server because of an external firewall, so you need to investigate in this direction, also note in your case that not only port 7110 must be open but also the provider ports: 7400-7700 (default)

LiWeiMr commented 10 months ago

@LiWeiMr this means that this port is not open either on the server side because of an internal firewall, or on the path between client and server because of an external firewall, so you need to investigate in this direction, also note in your case that not only port 7110 must be open but also the provider ports: 7400-7700 (default)

Thank you very much! I solved my problem by opening the corresponding port through the firewall