scrcpy v3.0

Changes since v2.7:

• Add virtual display feature (#5370, #5506, #1887, #4528, #5137)
• Launch Android app on start (#5370)
• Add OpenGL filters (#5455)
• Add --capture-orientation to replace --lock-video-orientation (which was broken on Android 14) (#4011, #4426, #5455)
• Fix --crop on Android 14 (#4162, #5387, #5455)
• Handle virtual display rotation (#5428, #5455)
• Add --angle to apply a custom rotation (#4135, #4345, #4658, #5455)
• Add --screen-off-timeout (#5447)
• Adapt "turn screen off" for Android 15 (#3927, #5418)
• Add shortcut Ctrl+Shift+click-and-move for horizontal tilt (#5317)
• Add shortcut MOD+Shift+r to reset video capture/encoding (#5432)
• Forward Alt and Super with SDK Keyboard (#5318, #5322)
• Add more details to --list-encoders output (#5416)
• Add option to disable virtual display system decorations (#5494)
• Fix --time-limit overflow on Windows (#5355)
• Fix "does not match caller's uid 2000" error (#4639, #5476)
• Accept filenames containing ':' when recording (#5487, #5499)
• Disable mouse by default if no video playback (#5410)
• Rename --display-buffer to --video-buffer (#5403, #5420)
• Listen to display changed events (#5415, #161, #1918, #4152, #5362)
• Adapt server debugging for Android >= 11 (#5346, #5466)
• Upgrade FFmpeg to 7.1 (#5332)
• Upgrade SDL to 2.30.9
• Upgrade platform-tools (adb) to 35.0.2
• Build releases via GitHub Actions (#5306, #4490)
• Release static builds for Linux and macOS (#5515, #1733, #3235, #4489, #5327)
• Various technical fixes

---

Highlights

Virtual display

By default, scrcpy mirrors the device screen.

With this new feature (#5370), it is now possible to mirror a new virtual display, with a custom size:

bash scrcpy --new-display=1920x1080 scrcpy --new-display=1920x1080/420 # force 420 dpi scrcpy --new-display # use the main display size and density scrcpy --new-display=/240 # use the main display size and 240 dpi

On some devices, a launcher is available in the virtual display.

When no launcher is available, the virtual display is empty. In that case, you must [start an Android app][start-app].

[start-app]: https://github.com/Genymobile/scrcpy/blob/master/doc/device.md#start-android-app

For example:

bash scrcpy --new-display=1920x1080 --start-app=org.videolan.vlc

To list the Android apps installed on the device:

bash scrcpy --list-apps

For convenience, you can also select an app by its name using a ? prefix:

bash scrcpy --start-app=?firefox

However, retrieving app names may take some time (sometimes several seconds), so passing the package name is recommended.

On-device OpenGL filters

Scrcpy can now transform the captured video stream before encoding by applying OpenGL filters directly on the device. This has made it possible to fix several issues and implement new features, as described below (more details in #5455).

Crop

The --crop option was broken for devices running Android >= 14 (#4162). It has been reimplemented using OpenGL filters internally.

Its usage remains the same:

bash scrcpy --crop=800:600:100:100

It now also works for camera and virtual displays.

Capture orientation

The --lock-video-orientation option was broken for devices running Android >= 14 (#4011).

It has been replaced by a more general option --capture-orientation, implemented using OpenGL filters:

bash scrcpy --capture-orientation=0 scrcpy --capture-orientation=90 # 90° clockwise scrcpy --capture-orientation=180 # 180° scrcpy --capture-orientation=270 # 270° clockwise scrcpy --capture-orientation=flip0 # hflip scrcpy --capture-orientation=flip90 # hflip + 90° clockwise scrcpy --capture-orientation=flip180 # hflip + 180° scrcpy --capture-orientation=flip270 # hflip + 270° clockwise

The capture orientation can be locked by using a @ prefix, so that a physical device rotation does not change the captured video orientation:

scrcpy --capture-orientation=@ # locked to the initial orientation scrcpy --capture-orientation=@0 # locked to 0° scrcpy --capture-orientation=@90 # locked to 90° clockwise scrcpy --capture-orientation=@180 # locked to 180° scrcpy --capture-orientation=@270 # locked to 270° clockwise scrcpy --capture-orientation=@flip0 # locked to hflip scrcpy --capture-orientation=@flip90 # locked to hflip + 90° clockwise scrcpy --capture-orientation=@flip180 # locked to hflip + 180° scrcpy --capture-orientation=@flip270 # locked to hflip + 270° clockwise

Now, it also works for camera (fixing #4426) and virtual displays.

Custom rotation

A new option --angle allows to rotate the content by a custom angle. Combined with --crop, this is especially useful for mirroring the Meta Quest 3 (#4135, #4345, #4658).

Virtual display rotation

The new virtual display feature initially could not rotate. The rotation has been implemented using OpenGL filters.

(That is what triggered the development of OpenGL filters.)

Like previously, the current app can be rotated by <kbd>MOD</kbd>+<kbd>r</kbd> (shortcuts).

Screen off timeout

The existing option --stay-awake only keeps the device awake *while it is plugged in, meaning it typically does not work over TCP/IP.

A new option, --screen-off-timeout, modifies the screen-off timeout setting while scrcpy is running and restores it on exit:

bash scrcpy --screen-off-timeout=300 # 300 seconds (5 minutes)

Static builds

For convenience, static builds are now provided for Linux and macOS (#5515).

More targets might be added in the future.

This is still experimental for now, so if you encounter problems, please report them.

Features you might have missed

If you haven't tried scrcpy in a while, here are some features introduced in the 2.x versions that you might have missed (check the release notes to each version for more details):

• scrcpy 2.7: gamepad support
• scrcpy 2.6: audio duplication
• scrcpy 2.5: control-only & mouse improvements
• scrcpy 2.4: UHID keyboard and mouse
• scrcpy 2.3: camera support improvements
• scrcpy 2.2: camera capture
• scrcpy 2.1: microphone capture
• scrcpy 2.0: audio forwarding

---

• BlueSky: @scrcpy.bsky.social
• Twitter: @scrcpy_app
• Reddit: r/scrcpy

anyone tried building android for their device on a sub-stellar PC? my phone doesn't have LOS21/A14 available so I tried the build-it-yourself route... dios mio, this takes eons!

I know it's a huge code base, but I had no concept of the size... I've left it syncing the repo like two hours ago and it's at 10%. no idea if it's gonna build at all and if it takes a day to download the thing and another one to build it (Ryzen 5) maybe I should go look for a $100 replacement that still gets LineageOS.

anyone been down this road?

cross-posted from: https://lemm.ee/post/46066494

> I followed the recommended processes for adding images to my app, and it is being displayed correctly on the layout preview, but not at all on the app. I have vector assets, webp, png images, but none are being displayed. > > The project is too big to put here in its entirety, but please ask for any snippets that could help you solve the issue. I've tried searching the web and asking LLMs and neither could help, so please help me, fellow humans.

The way he just blew off the 50/50 split criticism was pretty gross. Basing it off of Youtube's bad-relative-to-the-rest-of-the-market 45/55 split, and then making it worse is not great, especially when coming from someone who makes YouTube content for a living.

> Over the weekend, Google removed Kaspersky's Android security apps from the Google Play store and disabled the Russian company's developer accounts. > > Users have been reporting over the last week that Kaspersky's products (including Kaspersky Endpoint Security and VPN & Antivirus by Kaspersky) are no longer available on Google Play in the United States and other world regions. > > Kaspersky confirmed the issue on the company's official forums on Sunday and said that it's currently investigating why its software is no longer available on Google's app store.

https://www.bleepingcomputer.com/news/security/google-removes-kasperskys-antivirus-software-from-play-store-disables-developer-accounts/

cross-posted from: https://lemmy.ml/post/21015575

> Hackers Keyboard has that via ctrl+z, but only in horizontal mode. For this only i had my Galaxy S3 in horizontal per default. But can't do that with modern phones' aspect ratio and i'm missing undo since then.

(cross-posted from: https://lemmy.ml/post/20476024)

After more than two years FlorisBoard (an open-source keyboard which respects your privacy) 0.4.0 is finally released with many new features including MDY support, addons store, incognito mode, major smartbar rework and many other bugfixes and improvements.

Regarding the spell checking (from GitHub release notes): > Word suggestions/spell checking are not included in the current releases and are a major goal for the v0.5 milestone.

I have an older Samsung Galaxy A3 with an already unlocked bootloader (it comes pre-unlocked) that I want to clean & root. I have a few apps like firefox, some games, DraStic, notesnook, etc. as well as my music. I want to keep all of this of course bug remove all the other bloat i dont need. I dont want a custom ROM or anything. The samsung ROM is good enough (android 6.0.1) I am very unaure on the process though & I dont want my old phone to get bricked so I'd appreciage it if somebody helped me out here, thanks.

I'm looking for a way to dump raw data from an entire phone or at least the sda block to a PC, using a method other than adb pull.

When I run adb pull /dev/block/sda sdaDump.img, it creates a dump file. To find what I need, I have to search through this raw data using a Hex Editor. If the dump comes from a fully functioning phone, I can usually find what I’m looking for because all the data is still intact.

However, I accidentally wiped the metadata partition on my phone, so the decryption keys/files are gone. Now, because of that, some folders appear empty when checked with TWRP's File Manager, even though the actual files are still there.

If I create a dump now, the raw data in the file won't be the same as when the metadata was present, and those folders weren't showing as empty.

Running adb pull /dev/block/sda sdaDump.img now results in a dump where the Hex Editor shows zeroes (no data) where these files should be.

Is there any alternative method to create a raw data dump of the sda block or entire phone storage, that will capture that data as it is (not empty folders, but the data in them), even if it's encrypted?

I don't want to create the raw data dump onto the phone storage and then transfer it to a PC, but something that works like adb pull, in the sense that it pulls the data from the phone directly onto a PC.

Thanks a lot in advance to everyone!

I need to ask a small favor from the good people of Lemmy.ml Community.

In short, I accidentally wiped the metadata partition on my Poco F3 and now I can't boot into the OS and access my data. I have a lot of pictures, videos and other stuff that I would hate to lose, because of a mistake. But all that is still on the phone, I just can't boot the phone to access it.

Thankfully, there is a way to fix this by creating a full backup of the phone with adb, then using a HEX Editor to manually look through that gigantic file and try to find the files that were in that metadata partition.

A huge thanks to bluet33th, a user from XDA Forums, without whom I would be helpless and couldn't do any of this. It might be a bit complicated and manual process, but it is possible. He explained everything in great detail here, so check it out, especially if you are facing the same problem, this will help you tremendously: https://xdaforums.com/t/how-to-recover-data-if-metadata-partition-was-deleted.4686789/

In order to find these files and put them back where they belong, I need your help, because I have to know their names, exact sizes and at least part of their content, so that I can search for it. Because I'm searching for a specific text in a text file that is 128 GB in size.

I have already tried this on another Xiaomi phone, to make sure this procedure works on Xiaomi phones and it does, but that phone had HyperOS with Android 14 and since every phone and android version is probably different, in order to be sure, I need this information specifically for Poco F3 with Android 13.

It doesn't take long, but if you don't have the time to look inside your metadata partition and tell me which files are inside of that partition and their sizes in bytes, you can just make a backup of the metadata partition and sent it to me, and I'll do the rest of the work.

Here are the steps on how to create a backup:

1. Turn on your phone and boot into TWRP, then connect your phone to a PC, type cmd inside Windows search and run cmd, then position cmd into your platform-tools folder (if you flashed your ROM, you should already have the necessary drivers installed for the next steps to work). For example, if your platform-tools folder on Windows is inside C:\platform-tools, all you need to type into cmd is: cd C:\platform-tools

You can also just go inside your platform-tools folder and type cmd in the address bar and the cmd will start already positioned inside that folder.

2. Then type adb devices and you should see your device, if you do, that means that all the drivers are successfully installed and your phone is detected.

!

3. Type adb pull /dev/block/by-name/metadata

!

4. After that, you should see a file named metadata inside C:\platform-tools. That is the file that I'm looking for and as you can see, it takes just a few minutes to get it.

You can skip the next steps (5 and 6), but I'll explain them, just in case someone wants to extract these files for themselves, so that you have them in case something like this happens to you. Of course, you can also proceed to extract the files and tell me their names and sizes.

Here is what you need to do:

5. Extract the content of the metadata file, you can use a software like 7-Zip. Go inside that extracted folder, then into vold > metadata_encryption > key

6. Inside of that key folder, you should see a few files. These are the important files and save them somewhere safe in case you ever need them. Since I don't have them anymore, in order to recreate them, I need to know their exact names and sizes in bytes. You can check the size of every individual file by right clicking on the file and choosing Properties. Then look under Size, not Size on disk, and in parenthesis, you should see the size in bytes.

!

Please, if you could check the size of every file and write down which file has what size. I would really appreciate it.

I'm specifically looking for someone who has a Poco F3 with Android 13 and MIUI, because I'm not sure if HyperOS changed something, so maybe the number of files or their size is different. But feel free to post the information even if you have HyperOS, but please mention that, so that I am aware of it.

Thanks a lot for your help, it really means a great deal.

(cross-posted from: https://lemmy.ml/post/19917523)

Basically, what the title says. Do you use any app, that is proprietary, but either has no OSS alternatives or they're all not good enough? If there is an alternative, what keeps you from switching?

Hello, I bought my first used phone (Xiaomi Redmi Note 13 Pro) and was wondering what are the best practices taken before using it. I've read the reviews of the merchant selling the phone, looked into ratings and asked some questions about the condition of the phone, so I'm sure of my purchase on that end.

What about after receiving the phone? I know I would run a factory reset, aside from that, is there anything else to do?

Across the world, the biggest smartphone manufacturers are Apple (28%), Samsung (24%), Xiaomi (12%), Oppo (6%) and Vivo (5%). However, there are geographic patterns in popularity, with Apple dominating North America and East Asia, while Samsung leads in South America, Europe, Africa and West Asia in addition to its home turf of South Korea. Xiaomi is the most popular phone brand across South Asia, Spain, Venezuela, Ukraine, Madagascar, Kyrgyzstan and Palestine, while Tecno is popular in West and Central Africa. Oppo, Vivo and Huawei lead in Indonesia, Bhutan and Togo respectively.