Status Update
No update yet.
Comments
mu...@gmail.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.
rm...@google.com
It's about time, no?
rp...@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.
tr...@gmail.com
Maybe let us set the limit instead (size/duration) ?
As for new API levels, can you please make it reach Android 13?
ry...@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.
us...@gmail.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.
al...@gmail.com
The three-minute limit is imposed by Android itself, but it's going to be lifted in Android 14.
vi...@gmail.com
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.
hr...@gmail.com
Electric Eel can mirror physical devices similarly to scrcpy, but uses adb shell screenrecord for video recording. Reimplementing video recording without adb shell screenrecord is definitely a possibility. We may consider it.
ra...@google.com
ra...@google.com
If it uses the adb command, doesn't it mean it's also limited to 3 minutes?
ScrCpy is very efficient. And it has very convenient keys too (right mouse button for back key is the most common that I use).
The only downsides of ScrCpy currently, which I wonder if you solve, are:
1. mouse pressing doesn't show as touch. There is no way to put touch indication made by the mouse.
2. Unicode support. I can't type in Hebrew, for example.
3. No UI at all. Everything is in commands. They are quite good, but it means I have to read a lot to find what is useful for me.
Please consider teaming up with them. See what can help them to make it work better for both the tool, the IDE and adb commands.
Maybe have Android 14 more suitable for mirroring and screen-recording than ever.
sp...@google.com
Studio currently solves #3 but not #1 and #2. #1 is quite doable, but #2 is very hard. Please try mirroring in Studio (it's in Experimental settings in Electric Eel) and give us your feedback.
ra...@google.com
1. How is it doable? Please tell them about it too. I requested it here:
I find it weird that even for adb commands of simulating touches, it's not shown, yet for "pointer location" it does get shown. To me it looks like a bug, so I reported about this here:
2. I thought that maybe I could create an accessibility app that just writes the Unicode, but it seems that there are very few things that accessibility could write for the user. Is it technically possible using accessibility? I couldn't find, so I requested here:
I also requested support of typing unicode via adb:
3. What options are there in the UI ? How do you even get to this on the IDE? Could it handle multiple devices ?
sp...@google.com
https://github.com/Genymobile/scrcpy/issues/44 is pretty informative. Showing touches is harder to do than I thought.- Accessibility APIs are not supposed to be used for anything except accessibility.
- Try it ;-)
ra...@google.com
1. Please talk with them
2. A chair is supposed to be used for sitting, yet people sometimes stand on it to replace the light bulb. You should check the Play Store, of how many useful features apps use that are for everyone, not just people with some disability. Making life easier is not something that is good only for people with disabilities.
Besides, such a feature (typing for the user) is useful for all users, including people that have some issues with touches. Imagine for example an API that can type for the user, as it listens to what he says or thinks, using proper sensors. This can be useful for everyone. If a person lacks the ability to properly touch the screen, this can be useful. If the screen's touch doesn't work, it can be useful. There are plenty of usages that you can think of.
I myself don't consider myself as disabled in any way. Does it mean I'm not allowed to use apps that use accessibility API? Not even of Google? Of course not. Everyone should be allowed to use this API, whether it's for people with some disability or not.
3. Where?
sp...@google.com
sp...@google.com
sp...@google.com
an...@google.com
Could be nice if it had similar features, and also have similar control as on ScrCpy.
You should really allow to turn off the display of the device while mirroring. I do it to save on battery and avoid smartphone display usage over time.
Check what happens on ScrCpy when using this:
scrcpy-noconsole.vbs -S --always-on-top --stay-awake
Here, requested:
ep...@gmail.com
I usually prefer it being an on-top floating window
Click on the Window icon, which is to the left of the gear one at the top of the Running Devices window.
You should really allow to turn off the display of the device while mirroring.
See
ep...@gmail.com
A stand-alone solution should be offered, which the IDE is used only as a convenience to open it, just like the emulator.
As for the display, that's good. It's not a bug though. Why everything here is marked as a bug...
:)
Description
Scenarios:
1) Copy some text from anywhere outside the Android Studio (like browser/android Apps/other Linux apps...), try to paste anywhere in Android Studio (Dialogue box/Editor/terminal...) : NOT WORKING.
2) Copy some text from Android Studio, try to paste in android studio : NOT WORKING.
But the copied text is present in Clipboard. Checked by pressing Ctrl+Shift+V in Android Studio to show clipboard history.
3) Copy some text from Android Studio, try to paste outside Android Studio (like browser/android Apps/other Linux apps...) : WORKING FINE.
Android Studio Version : 3.4.1.
Device : Google Pixelbook (i5 7th Gen, 8Gb, 128Gb)
OS : ChromeOS
NOTE:
1) Not sure if it is an Android Studio Bug. Before updating to Android Studio 3.4.1, copy & paste is working very well without any bug in the same device.
2) Copy & Paste is working in Other Linux Apps. (Like Visual Studio Code, Terminal : by using Ctrl+Shift+V )
TRIED TROUBLE SHOOTS:
1) Uninstalled Android Studio.
2) Performed a Powerwash in Pixelbook.
3) Installed Android Studio again.
Still no use.
Build: 3.4.1, AI-183.6156.11.34.5522156, 201905012035, AI-183.6156.11.34.5522156, JRE 1.8.0_152-release-1343-b16-5323222x64 JetBrains s.r.o, OS Linux(amd64) v4.19.44-04905-gdcd4527c595a, screens 2400x1600Android Gradle Plugin: 3.4.1Gradle: 5.1.1NDK: 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); Source: user_sentiment_feedback IMPORTANT: Please read