We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A bug on the Android emulator results in 0 byte output files:
https://issuetracker.google.com/issues/36982354
This seems to apply to both the AOSP emulator and the emulator with Google APIs. AdbScreenRecord gets a 0 byte video file which won't play.
This should probably show an error message in place of the video when a non-supported device is detected.
It might be possible to implement a workaround by using the a screen recorder on the host OS itself (e.g. recordmydesktop) to get the video.
e.g.
xwininfo -name "device name" recordmydesktop --windowid ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A bug on the Android emulator results in 0 byte output files:
https://issuetracker.google.com/issues/36982354
This seems to apply to both the AOSP emulator and the emulator with Google APIs. AdbScreenRecord gets a 0 byte video file which won't play.
This should probably show an error message in place of the video when a non-supported device is detected.
It might be possible to implement a workaround by using the a screen recorder on the host OS itself (e.g. recordmydesktop) to get the video.
e.g.
The text was updated successfully, but these errors were encountered: