Genymobile / Genymobile/scrcpy
Allow scrcpy to be used even when persistent storage is full
- Dominant language
- C
- Stars
- 150k
- Forks
- 13.7k
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
Description
- [x] I have checked that a similar [feature request](https://github.com/Genymobile/scrcpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22feature+request%22) does not already exist.
**Is your feature request related to a problem? Please describe.**
When the device's persistent storage is full, scrcpy fails to push the server binary to the device which prevents scrcpy from being used in this case.
**Describe the solution you'd like**
scrcpy should be usable even if the storage is full. Is there an in-memory temporary storage location that is also executable? If write is needed and there really is no place to write, perhaps fallback to `screenrecord`, see following.
**Describe alternatives you've considered**
As noted in [this SE](https://android.stackexchange.com/a/154328) answer, `screenrecord` can be used to do this. I've confirmed that this works for me. Perhaps scrcpy can fallback to using `screenrecord` (and perhaps some other standard android binary for sending input if needed).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the existing server-binary push path and investigating Android's executable temporary-storage options described in the issue. Compare that approach with the mentioned screenrecord fallback and standard Android binaries for input. Done means scrcpy remains usable when persistent storage is full, with the supported fallback behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100