Google devices - Missing resources/unknown minicap grabber: minicap-bin #785
Comments
|
@KingRat0011 , it means if |
|
Hi @denis99999 , |
|
@KingRat0011 , currently the default operation is to try |
|
Hi @denis99999 when I open the device, I get this Setting it like this It just goes into the endless loop All the other devices like Samsung on Android 14 is fine, it is just these Google devices that seems to have the problem |
|
This fixed the realme problem that I logged, setting the --screen-grabber minicap-bin |
|
@KingRat0011 For Pixel devices, you can see SurfaceControl Error. You can use updated minicap apk which handles this error. |
|
Hi @KishanDasani |
|
@KingRat0011 moreover, not able to understand what you're saying about 3.6.8 version, whose version it is? |
|
Hi @KishanDasani |
|
@KingRat0011 Folks from DeviceFarmer can further guide on this if I am going in wrong direction, but here are the things I know DeviceFarmer's minicap repo is updated with latest changes. as of now, you will have to build APK with changes of SurfaceControl error and you can use that independently, that's what I have done. |
|
Hi I uploaded the new minicaps to /usr/lib/node_modules/stf/node_modules/@devicefarmer/minicap-prebuilt/prebuilt/arm64-v8a/bin etc Am I supposed to get an apk from the minicap build? |
I guess your device is pretty nicely enrolled, not seeing any errors. if you are able to see folders for SDK 32, 33, 34 inside @node_modules/devicefarmer/minicap-prebuilt/prebuilt/{supported ABI}/{SDK}, then you will possibly not needing the APK file. you can open experimental folder in Android Studio and follow the process to get an apk, place it in node_modules/@devicefarmer/minicap-prebuilt/prebuilt/noarch/ folder. if you need more help, you can reach out to people from DeviceFarmer, they can guide you better. or we can get in touch personally. |
|
Seem like the latest code fixed the problem, the device displays and I can control it Thanks @koral-- !!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running the latest release with node v17.9.0
$ node -v
v17.9.0
$ which node
~/.nvm/versions/node/v17.9.0/bin/node
$ stf --version
3.6.8
$ stf doctor
2024-05-30T08:15:54.034Z INF/cli:doctor 27704 [] OS Arch: x64
2024-05-30T08:15:54.036Z INF/cli:doctor 27704 [] OS Platform: linux
2024-05-30T08:15:54.036Z INF/cli:doctor 27704 [] OS Platform: 3.10.0-1160.118.1.el7.x86_64
2024-05-30T08:15:54.036Z INF/cli:doctor 27704 [] Using Node 17.9.0
2024-05-30T08:15:54.047Z INF/cli:doctor 27704 [] Using ZeroMQ 4.2.2
2024-05-30T08:15:54.058Z INF/cli:doctor 27704 [] Using ADB 1.0.31
2024-05-30T08:15:54.059Z INF/cli:doctor 27704 [] Using ProtoBuf 3.14.0
2024-05-30T08:15:54.060Z INF/cli:doctor 27704 [] Using GraphicsMagick 1.3.38
2024-05-30T08:15:54.060Z INF/cli:doctor 27704 [*] Using RethinkDB 2.4.4
$
But on the google devices with Android 14, I get Missing resources/unknown minicap grabber: minicap-bin when opening the UI
Below is for a Google Pixel 8a - Android 14
This just carries on and on when trying to open the UI, I dont think this is the problem, as I have a Samsung on Android 14, the logs for the Samsung gives the same error but the UI open
Below is for a Google Pixel 7a - Android 14
Below is a Google Pixel Fold on Android 14
For comparison, below is a Samsung device - Android 14 on the the stf server
The text was updated successfully, but these errors were encountered: