Open coinhu1995 opened 2 years ago
I have the same issue and only on pixel 3 (pixel 3a/3xl/4 works fine). temporarily workaround is factory reset device. but after a while the problem appears again.
I have the same issue on Pixel 4 Android S
There are 2 minicap implementations that stf can use: a binary and an apk. By default stf uses the binary which is the "legacy" one. Starting with Android 10, an apk has been experimented (because it is expected to be more stable API wise and easier to maintain). If the default one doesn't work, stf fallback to de second one.
Could you try by setting minicap-apk as the default one to see if this could be related to a timeout coming from the fallback being a bit long ?
You can easily try it by setting a environment variable like this:
SCREEN_GRABBER=minicap-apk bin/stf local
(or whatever suits your environment)
see commit https://github.com/DeviceFarmer/stf/commit/bb1c20d1f7bc662fc155f84b0af3374f7c7aeabd for more details It's been done like this in order not to break minicap at the early stage but maybe we coud now reverse the order.
Note also that the apk version is a bit longer to start than the binary. On my side I never experienced this issue but depending on your feedback there is maybe a couple of things we could try.
Thank you for your answer. Will "apk" be open source?
@csdaa it is open source since day one 👉 https://github.com/DeviceFarmer/minicap/tree/master/experimental
change your minicap to support SDK 31
There are 2 minicap implementations that stf can use: a binary and an apk. By default stf uses the binary which is the "legacy" one. Starting with Android 10, an apk has been experimented (because it is expected to be more stable API wise and easier to maintain). If the default one doesn't work, stf fallback to de second one. Could you try by setting minicap-apk as the default one to see if this could be related to a timeout coming from the fallback being a bit long ? You can easily try it by setting a environment variable like this:
SCREEN_GRABBER=minicap-apk bin/stf local
(or whatever suits your environment)see commit bb1c20d for more details It's been done like this in order not to break minicap at the early stage but maybe we coud now reverse the order.
Note also that the apk version is a bit longer to start than the binary. On my side I never experienced this issue but depending on your feedback there is maybe a couple of things we could try.
I have added this environment to my setup (Docker Compose) but Problem persist, Removing data did not worked
Also in logs I can see that minicap apk is installed
@pcrepieux I did some checks and Samsung is working but Nokia (I think the android one) is not working (Tested on android 12) Also on Xiaomi there is support for touch and other controls (Tested on android 13 [do not forget to turn on security option])
Oh, Xiaomi on android 12 is also working
minicap not support SDK 32? Pixel 3a xl (android 12) hava the same issue
What is the issue or idea you have? Pixel 3 (android 12) did not show screen Does it only happen on a specific device? Please run
adb devices -l
and paste the corresponding row. device usb:35717120X product:blueline model:Pixel_3 device:blueline transport_id:6 Please provide the steps to reproduce the issue. Run stf and use device pixel 3 What is the expected behavior? Device screen is shown Do you see errors or warnings in thestf local
output? If so, please paste them or the full log here.Please run
stf doctor
and paste the output here.