Status Update
No update yet.
Comments
wd...@google.com
je...@google.com
I'm not sure why the 3 min limit was put in place. It looks like it arbitrarily put in for Emulator recording in ag/3265023 and later in ag/3455232 was enforced on non-emulator recording as well.
I'll investigate why it was added in the first place and then experiment with a no limit version.
je...@google.com
It's about time, no?
je...@google.com
Seems like there was an arbitrary decision at some point to limit the screenrecord command to 3 minutes.
ag/350897
I have reopened internal bug
Note that if my request is approved, it'll only take affect for new API levels.
ts...@gmail.com
Maybe let us set the limit instead (size/duration) ?
As for new API levels, can you please make it reach Android 13?
ts...@gmail.com
I suspect that removing the limitation will not be accepted. The screenrecord command writes to a file on the device. Having no limitation can result in the device being rendered unusable due to lack of space on the file system where the file is written. For example, if a user runs adb screenrecord /sdcard/foo.mp4 and forgets about it, the sdcard will eventually be full and many apps will start to fail.
je...@google.com
ke...@ebay.com
I meant without limitation on duration. About storage, as long as there is enough and the OS is ok with it, it should be fine and without limitation.
If I want to take a video of hours of what's on the display, and I have enough storage for it, I see no reason why I shouldn't be able to do it.
After all, people can take very long videos using their camera (especially in low-resolution), so why can't I take a long video of something as simple as what's on the display?
You could even optimize it so that every now and then, the adb command will copy what the device has created and add it to what's on the PC, instead of having one huge file on the device that will be pulled. Meaning take small files one after another, and merge them. Or, have it stream it directly, without files on the device.
Description
*
*
*
*
We attempted to use Gradle dependency resolution to force a newer version of Netty, however this broke execution of instrumented tests via the connectedAndroidTest task.
As possible, please provide an update that does not depend on the vulnerable Netty versions.
Build: AI-211.7628.21.2111.8092744, 202201190556,
AI-211.7628.21.2111.8092744, JRE 11.0.11+9-b60-7590822x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1024.0x1280.0, 1920.0x1080.0
AS: Bumblebee | 2021.1.1; Kotlin plugin: 211-1.5.30-release-408-AS7442.40; Android Gradle Plugin: 7.1.1; Gradle: 7.3.3; Gradle JDK: version 11.0.12; NDK: from local.properties: (not specified), latest from SDK: 22.1.7171670; LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (unable to invoke cmake)
IMPORTANT: Please read