Status Update
Comments
pa...@google.com <pa...@google.com>
sp...@google.com <sp...@google.com> #2
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.
ea...@gmail.com <ea...@gmail.com> #3
It's about time, no?
sp...@google.com <sp...@google.com> #4
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.
ea...@gmail.com <ea...@gmail.com> #5
Maybe let us set the limit instead (size/duration) ?
As for new API levels, can you please make it reach Android 13?
ea...@gmail.com <ea...@gmail.com> #6
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.
sp...@google.com <sp...@google.com> #7
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.
ea...@gmail.com <ea...@gmail.com> #8
The three-minute limit is imposed by Android itself, but it's going to be lifted in Android 14.
sp...@google.com <sp...@google.com>
de...@google.com <de...@google.com> #9
Isn't there any kind of workaround for this?
What if you use on PC what ScrCpy is using, to mirror into the PC what's on the device (probably the same protocol as mirroring using USB to the TV), and capture the video straight into the PC, instead of storing anything on the device?
It's even better, because you aren't relying on Android versions, and the only restriction is how good the USB cable is.
Please think about it.
You could even record audio this way, because they also have some audio solution.
If you don't know of this marvelous tool, please check it out:
You could have some integration with it via the IDE, too (example is to detect if it's running, and if so, use it to record instead of adb). Maybe talk to the team there.
Description
Start from Dolphin | 2021.3.1 Canary 4 I cant run emulator in tool window
when I run it android studio close and when repeat this I found it running but android studio also close after I try to connect to it
note: I can run it in a separate windows
thanks for your times
Build: AI-213.6777.52.2113.8305692, 202203160046,
AI-213.6777.52.2113.8305692, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Windows 11(amd64) v10.0 , screens 1360.0x768.0
AS: Dolphin | 2021.3.1 Canary 7; Kotlin plugin: 213-1.6.20-M1-release-for-android-studio-AS6777.52; Android Gradle Plugin: 7.3.0-alpha07; Gradle: 7.4.1; Gradle JDK: version 11.0.13; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read