MI9 failed to show the screen after click the `use` about stf

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.79. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[chaooe]

dock file ase below

docker-compose.zip

[denis99999]

@chaooe ,

I understand there are 2 providers running on the main host, which communicate with 2 ADB servers running on 2 remote machines (i.e. 192.168.33.100, 192.168.33.115), isn't it ?

In any case, you have to provide the --screen-ws-url-pattern parameter for each provider unit (cf. example in DEPLOYMENT.md).

But in my mind, it can't work because in your nginx.conf file, this URL is forwarded to the corresponding remote machine where only an ADB server is running and not a provider one, so this URL should be rather forwarded to the main host where the 2 providers are running, but in this case you risk having a port conflict between the 2 providers.

So, I think the good architecture, as described in DEPLOYMENT.md, is to deploy each provider on a remote machine where an ADB server is running, like this it should work !

[chaooe]

Thanks ,i will have a try by using the DEPLOYMENT.md to check if it can works or not.

[pcrepieux]

This line in the logs you provided:
android-provider2_1 | 2020-09-09T01:28:34.073Z INF/device:plugins:screen:stream 13 [35fbffe7] minicap says: "Vector<> have different types (this=0x7fca0f0de0, rhs=0x7fca0f0f30)"
seems to indicate that this is the same issue as #124

[chaooe]

@pcrepieux thanks for comfirm this. waiting for this fixed.

[varundtsfi]

Hi @chaooe here is the fix for vector issue in Xiaomi devices.

DeviceFarmer/minicap#6

[varundtsfi]

Hi @chaooe here is the fix for vector issue in Xiaomi devices.

DeviceFarmer/minicap#6

https://github.com/varundtsfi/Xiaomi_Vector_issue/tree/main/LG