Atemu

joined 5 years ago
MODERATOR OF
[–] Atemu@lemmy.ml 1 points 4 months ago (3 children)

That is not relevant here in any way. That's a distro made to easily run one app at a time without really caring about data security w.r.t. that app.

[–] Atemu@lemmy.ml 1 points 4 months ago

Note that even with this it'll be quite likely that games don't work. WineD3D is much less compatible than DXVK.

You need a device that can do Vulkan properly. The best for that are AMDGPUs and Nvidia ones but I wouldn't recommend the latter. Newer Xe Intel GPUs should also work but they're quite a bit behind anything AMD has to offer in terms of performance.

The newer of your GPUs meanwhile is a design from ~2015. Vulkan released in 2016. Just to get you an idea.

The issue here is not Linux, it's that neither of your GPUs was made for modern gaming. On windows that might sometimes work, especially with games targetting older graphics APIs that your GPUs were made with in mind but on Linux everything is Vulkan (a very modern graphics API), even games that only use older APIs.
A modern Vulkan-capable card is a requirement for painless gaming on Linux.

[–] Atemu@lemmy.ml 3 points 4 months ago

It uses the same technology but that's it.

[–] Atemu@lemmy.ml 2 points 5 months ago* (last edited 5 months ago) (1 children)

Right I can see where you're coming from but that incentivises using Kagi less which IMV is a really bad incentive for all parties involved.

[–] Atemu@lemmy.ml 4 points 5 months ago (3 children)

What if they made it so that a single search per month was fine too? You'd be back complaining that it'd be $5 if you only made 2 searches that month.

It's really hard to set a cut-off here.

[–] Atemu@lemmy.ml 6 points 5 months ago

On the one hand yes but on the other hand this would also kind of set wrong incentives: to use Kagi search less because you'd need to pay more.
That's not an incentive they or you would want.

I think what I'd like is how my mobile carrier handles their data limits: It's not an entirely fair comparison because in that case, contrary to Kagi, there is no real cost associated with my degree of usage of the service, making them entirely arbitrary and unnecessary but besides that the unused data rolls over to the next month and that's something Kagi could mirror.

I hover around 600-1000 searches per month but sometimes exceed 1000. If I could pay for 1000/month and accumulate a little buffer in the months where I search less, that would work for me. Though perhaps I'd still want to just simply pay for unlimited usage for peace of mind.

[–] Atemu@lemmy.ml 1 points 5 months ago (1 children)

This sounds like FUD. Do you have a source for that?

As a paying member, I know that they started charging (and presumably transferring) VAT last year.

Before that, they claimed they were simply too insignificant to even be eligible for VAT.
I looked it up and there appears to be an exception for such cases where VAT is charged in the company's jurisdiction rather that the customer's (it's usually the other way around) until you reach 10000€ annual turnover. Information on this is extremely intransparent however, so this might be wrong.

[–] Atemu@lemmy.ml 15 points 5 months ago* (last edited 5 months ago) (2 children)

They do. The $10/month search plan is unlimited.

The only LLM stuff in their search product is the quick answers which can be turned off and page summaries which you have to explicitly click on in a submenu in any case.

As someone aware of how limited LLMs are, I've actually found both of these features to be useful for gauging whether a site is worth visiting or not at times which is part of the core feature set of a search engine IMHO.

A good while back they claimed that Google search index fees make up the vast majority of their costs, so I doubt any of your money is going towards LLM BS unless you actually pay for their assistant product.
I doubt Google has given them any discounts since then.

I'd expect the development of all of their product to be mostly funded by VC. If they can get VC idiots who fell for the """AI""" hype to subsidise building an actually useful thing (the search product), that's a win in my book, even if they also have to build the AI crap on the side to keep said VC idiots happy.

[–] Atemu@lemmy.ml 7 points 5 months ago (1 children)

Even with root it's not anywhere near trivial.

You can't, for instance, make a backup of the userdata partition block device and expect to be able to restore it because it must be decrypted by a key in the phone's security module that gets wiped when you boot a new ROM.

[–] Atemu@lemmy.ml 5 points 5 months ago

Should have just been a reply.

[–] Atemu@lemmy.ml 3 points 5 months ago

I don't often search for videos but I did attempt it recently and it was already better YT did by itself. Perhaps that was mostly because it didn't attempt to shove extremely irrelevant shorts down my throat though but that's already feature enough tbh.

I guess they're spending so much time on the share feature because it's basically free marketing.

Unfortunately though it seems there's a bug since this update where changing a search doesn't actually apply it most of the time when you hit enter or click the button.

[–] Atemu@lemmy.ml 8 points 5 months ago

Someone started working on a Vulkan driver for TeraScale GPUs a few years ago:

https://gitlab.freedesktop.org/Triang3l/mesa/-/tree/Terakan

I believe it can run some demos add even works on windows.

 

Use Kagi Translate to translate search results

You can now use Kagi Translate to translate search results directly from the search results page. An icon will appear if we detect that the search result is in a language other than your interface language (inspired by #5809 @KamilKurde)

Click the icon and we will open Kagi Translate to translate the search result.

Ever since we launched Kagi Translate last month we've been getting nothing but praise for the service. It exploded in use, especially in Asia.

And we truly see the value of high quality, privacy respecting translation. So we continued building upon it.

  • We've introduced speech input, making it easier to use Kagi Translate on the go or when navigating unfamiliar languages
  • We introduced romanization for non-Latin languages as well as pronounciation for all supported languages
  • The new Proofreading feature helps identify spelling and grammar issues in any text or even web page !

Just prefix any URL with translate.kagi.com/proofread to proofread any web page. Try it here on a random Kagi Small Web page.

New user onboarding experience

We've reintroduced our onboarding experience to help setting up Kagi to your liking. I guess you already went though onboarding so it won't matter as much to you, but it will to friends and family you send our way.

We also added some helpful tips to help maximise key features.

New model and LLM privacy guide

With this release, we've introduced the Deepseek v3 model to the Assistant. Alongside it, we've published a new privacy guide to provide full transparency about the LLM providers used by the Assistant and their data privacy policies. Check it out!

You can share your Kagi searches with anyone!

Simply click the share icon in the search options bar to share your search with anyone when you post online or in an email, even for people without a Kagi account!

Search improvements and bug fixes

Assistant

  • We've added the Deepseek model to the Assistant
  • No daily AI token usage counter shown on jan 1 #5834 @daffodil
  • Assistant 'Show Keyboard Shortcuts' Keyboard Shortcut Doesn't Work #5842 @forward
  • Providing image without prompt on a customer assistance is broken #5663 @Thibaultmol
  • Assistant does not remember custom assistant settings when changing threads #5813 @theDoctor
  • Assistant copy mouseover not appearing or cut off #5781 @Thibaultmol
  • Kagi assistant is unusable on my iphone se3 #5779 @Lees
  • Assistant Scroll Bar Regression #5588 @emptyjar

Kagi Translate

  • Added 5 new "fun" languages - Pirate speak, Elvish, and a few more... see if you can find them!
  • Add Pinyin to Mandarin Chinese translations #5311 @cas9

Kagi for Android

We crossed 5,000 installs goal and we submitted a request with Google to add Kagi to the Android choice screen in EU!

  • Password field on mobile app is not detected bitwarden #5262 @Arnaud
  • Android assistant doesn't allow downloading conversations #5715 @sapourli
  • OAuth login does not work on android mobile app #5428 @awfixer
  • Mobile app: selecting text and sharing to kagi (translate) doesn't auto select origin language #5642 @Thibaultmol

Kagi on Socials

Here is this week's featured social media post.

Tag our account or use #Kagi when mentioning us in your posts!

 

I recently got my Kobo Elipsa 2E and it's better than I expected, especially the simplicity of OS and how well handwriting generally works were a surprise to me.

Given that its handwritten notes features are surprisingly capable, I've been trying to use it to take notes for learning physics but quite soon ran into an issue in trying to use the advanced notebook:

In physics, there's a notation where you can write dx/dt as an x with a dot above it (), adding more dots the more often you take the derivative w.r.t. time though you typically only need 2 max. The handwriting recognition for formulas does not know this notation however and therefore converts any attempts to stupid stuff instead.

Additionally, I quite frequently write sentences that also contain some "math symbols" such as δ or θ or even just mathematical expressions such as L(x). Formula fields would recognise these just fine but no such luck with regular text fields; it tries to make normal letters or words out of these.
The maths formula mode cannot be used for annotating equations either as it garbles words into symbol structures.

The fall-back would be to just use raw drawing plots but my handwriting is quite poor and I'd rather have text because that really works quite well otherwise. I could write text mode until I need a sentence with a symbol in it but I don't know ahead of time whether I'll need it and by the time I know, it's already too late and I'd need to write the entire sentence again inside a raw canvas.

Are there any solutions or potential workarounds to my problems?

Is it possible to make the formula recognition aware of this notation somehow? I'll likely need further such niche notations in the future too.

Is it perhaps possible to have sections of text (or even formulas) that contain small raw canvases which don't get converted to text? That would also be a nice escape hatch.

Is there an alternative note-taking app one could side-load that works better perhaps? The hardware is surprisingly capable as mentioned; these issues are purely in software.

 

I recently got my Kobo Elipsa 2E and it's better than I expected, especially the simplicity of OS and how well handwriting generally works were a surprise to me.

Given that its handwritten notes features are surprisingly capable, I've been trying to use it to take notes for learning physics but quite soon ran into an issue in trying to use the advanced notebook:

In physics, there's a notation where you can write dx/dt as an x with a dot above it (), adding more dots the more often you take the derivative w.r.t. time though you typically only need 2 max. The handwriting recognition for formulas does not know this notation however and therefore converts any attempts to stupid stuff instead.

Additionally, I quite frequently write sentences that also contain some "math symbols" such as δ or θ or even just mathematical expressions such as L(x). Formula fields would recognise these just fine but no such luck with regular text fields; it tries to make normal letters or words out of these.
The maths formula mode cannot be used for annotating equations either as it garbles words into symbol structures.

The fall-back would be to just use raw drawing plots but my handwriting is quite poor and I'd rather have text because that really works quite well otherwise. I could write text mode until I need a sentence with a symbol in it but I don't know ahead of time whether I'll need it and by the time I know, it's already too late and I'd need to write the entire sentence again inside a raw canvas.

Are there any solutions or potential workarounds to my problems?

Is it possible to make the formula recognition aware of this notation somehow? I'll likely need further such niche notations in the future too.

Is it perhaps possible to have sections of text (or even formulas) that contain small raw canvases which don't get converted to text? That would also be a nice escape hatch.

Is there an alternative note-taking app one could side-load that works better perhaps? The hardware is surprisingly capable as mentioned; these issues are purely in software.

 

I've been gifted a Sony PRS-T3 over a decade ago. I've recently gotten into reading again and used it to read a manhwa/webtoon/web novel (or whatever the Korean ones are called) and most recently a light novel.
It's functional and perhaps even decent (especially given its age) but my main gripes with it are:

  • Size: It's much too small to fit an entire manga page with readable text, so you need to use hacks like kcc which is suboptimal. I'd like the display to be the size of a typical manga or slightly larger.
  • Lack of customisation: It has this ugly indented paragraph style in books which I don't like and the selection of fonts aswell as font rendering isn't great.
  • Artifacts in images: When anything more complex than text is on display (and even with text it's subtly noticeable), you always see ghosts of the previous image. This is perhaps the most critical flaw for the purpose of reading Manga. Image quality in pictures isn't great to begin with either.
  • Slow: Page turning is fast enough but doing anything else it turns into a slog. Switching between "books" (the manhwa had each chapter as a separate book) was annoying to say the least.
  • Bad UI: It's just generally poorly organised and common things required way too many interactions (which, mind you, are slow).
  • No light: I appreciate not requiring a light but I'd sometimes like to have the option.
  • Ergonomics: It's light but not very comfortable to hold. I think I've seen readers that have a thicker end on one side so that you can better hold onto it? I'd appreciate advice here.

It's also showing its age; I had to tape the lid already as the material started to disintegrate.

I did very much appreciate how simple it is though. Open the lid, it immediately turns on, (I enter my PIN) and I can continue to read my book where I left off. Just like a real book but more convenient. I'd like to retain that property.
Battery life is also still great, even after all these years. I can close the lid and leave it sitting around for weeks and return to it with barely any battery drained. Again like a book where I don't have to worry about any battery charge either.
It's also quite light which I like, though a little bulky but totally acceptable.

Deal breakers:

  • Enshittification: If the primary purpose of the reader is to sell books rather than read them, I don't want it.
  • Espionage: I don't want Google, Amazon or anyone else spying on when I read what books. I'm probably going to have its networking off anyways but I don't want anyone spying on me offline either.
  • Gesture-only page navigation. Physical buttons please.
  • Ads of any kind.
  • Any power/data connector other than USB-C

I don't care for DRM. I'll be loading epubs onto the reader from another machine.

I don't think I need colour. I mean, it'd be nice I guess (especially for manhwa, those appear to frequently be coloured?) but if that compromises on greyscale or text clarity, no thank you. I also don't know whether e-ink can reproduce colour accurately enough that it's even an upgrade over greyscale and doesn't just look ugly.

FOSS firmware would be amazing but my research suggests that's not really a thing? I'd settle for a decently customisable proprietary firmware as long as it doesn't suck donkey balls or needs to be connected to the internet.

I don't need to draw on it.

Price is secondary but I don't like wasting money either.

I'm in Germany/EU.

I don't have a single clue about the e-reader market. I'd appreciate any advice on what I want and, more importantly, don't want given the constraints and desires I described.

 

Kagi for Teams

We're excited to announce Kagi for Teams, bringing our unmatched search quality and AI tools to organizations worldwide. Whether you're leading a research team, running a startup, or managing enterprise knowledge workers, you can now equip your entire organization with ad-free search and AI capabilities that respect both your time and privacy.

Visit kagi.com/teams to get started.

End of year community event on December 20th

As we conclude a remarkable year, we invite you to join our End-of-Year Community Event 2024 on December 20th at 09:00 PST. This 90-minute session will feature a "Year in Review" presentation followed by a Q&A session with our community.

  • The event will be hosted as a Zoom webinar. You can register in advance for a reminder or join the webinar on the day of the event

  • Please submit and upvote questions in advance for the Q&A portion of the event

We look forward to sharing this special event with you. See you on December 20th!

Kagi Search

We've introduced a debug tool for everyone helping localize Kagi into as many languages possible and contributing Kagi translations. This toggle is located at the bottom of your Settings > General page and displays string IDs across the UI, providing better context for translations.

We grant official contributor status to our translators, providing access to early products and features. Thank you to all who have contributed.

Improvements and Bug Fixes

Assistant

  • 'searching with kagi' in Assistant #5552 @Thibaultmol
  • Kagi Assistant fails to parse pdfs which render in viewers and other libraries support #5052 @tboby
  • Latex block is not correctly rendered in Kagi Assistant #5483 @oxlvlnle
  • When asking for markdown formatting advice, it does not display the markdown code block at all #5390 @IsaacThoman
  • Unclear max characters in custom assistant context #5526 @jvo
  • Unable to upload files on Kagi Assistanct macOS Web App #5280 @dreifach
  • Assistant fails to summarize YouTube video #5421 @azdanov
  • Assistant can't access website #4809 @azdanov
  • Add exact citation text tooltip to Quick Answer citations #4309 @Prostagma

Kagi for Android

We're just under 1,000 installs away from being eligible for inclusion in the Android Choice Screen. Help us reach this milestone by downloading the Kagi Android app and sharing it with your friends and family!
You can download the app here: Kagi Android App.

An iOS app is also in development, stay tuned for updates!

With this release you can now hold the Kagi Android icon to add shortcuts for Assistant, Translate, Smallweb, or Universal Summarizer directly to your home screen ( #5014 @Thibaultmol)

  • Location Permission not available for android app #5313 @1j4lzsjs
  • We've tweaked a few things to ensure password managers work in the Kagi Android app
  • When you select text or a URL, you now can (a) Summarize with Kagi, (b) Discuss with Kagi Assistant, or (c) Translate with Kagi
  • Mobile app flashes yellow on launch #5147 @Jesal
    Plus we fixed several other bugs and improved performance for a better mobile experience!

Kagi Translate

  • Translate as you type for Ultimate members
  • Instant translation without page reloads
  • Added language search to Kagi Translate, no more scrolling through the list

Visit translate.kagi.com to try Kagi Translate!

This week on social media

Join the growing Kagi community online! Follow us and use #Kagi to share your experience and connect with fellow users.

Here is this week's featured social media mention:

 

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:

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.

For example:

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

To list the Android apps installed on the device:

scrcpy --list-apps

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

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:

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:

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 MOD+r (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:

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 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:

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.

For example:

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

To list the Android apps installed on the device:

scrcpy --list-apps

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

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:

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:

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 MOD+r (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:

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):


view more: ‹ prev next ›