-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tried new approach on Android 12 beta-1 #14
Comments
@varundtsfi, thanks for taking the time to give it a try ! |
@pcrepieux But I have once concern about it. Performance is bit slow as compare to original minicap. No. of frames are like less? Can we put logs to find out no of frames? |
@varundtsfi the first goal was to get something up and running. At the moment, it is likely that performances are not as good as before (thought it looks rather good as far as I tested). I'll see how to improve it in a second step. |
@ #27 |
WE can close this now. As so and apk both approach we have. https://github.com/varundtsfi/Android12Support_withso/tree/main/aosp/android-31/arm64-v8a |
What is the issue or idea you have?
Have you tried STF?
@pcrepieux I have tried new approach which you have provided Experimental ([#12)] on Google Pixel 3XL (#12) which is not working. I know it's in beta version but still I gave it a try and getting below stats
1:- adb shell CLASSPATH=/data/local/tmp/minicap-0.1-debug.apk app_process /system/bin io.devicefarmer.minicap.Main
PID: 6057
Listening on minicap
createDisplay
Killed (getting only Killed nothing else not much data to debug)
2:- node app.js
Listening on port 9002
Got a client
chunk(length=24)
banner { version: 1,
length: 24,
pid: 6057,
realWidth: 1440,
realHeight: 3040,
virtualWidth: 1440,
virtualHeight: 3040,
orientation: 0,
quirks: 2 }
Lost a client
Got a client
The text was updated successfully, but these errors were encountered: