Genymobile / Genymobile/scrcpy
Features implemented in a fork
- Dominant language
- C
- Stars
- 150k
- Forks
- 13.7k
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
Description
Here is a specific thread for https://github.com/Genymobile/scrcpy/issues/495#issuecomment-517322589 (@Lurker00):
> Currently I've forked this project, and merged all my changes into the official 1.9 version. It is [there](https://github.com/Lurker00/scrcpy). I only have Android 8.1 devices, so I'm not sure that all my changes will work for all. It requires additional app (my dirty build of [ADBKeyBoard](https://github.com/Lurker00/ADBKeyBoard)) to type any language and to sync device's orientation by PC. In general, I'm not sure should I try a pull request... But you may build both projects yourself and give it a try...
>
> The full list of my changes (sorry for misuse this thread!):
> User visible changes:
> - 10-fingers multitouch support.
> - Any charset input support with an aid of ADBKeyBoard.
> - Quit command (Ctrl-Q)
> - Ctrl-Shift-O turns device screen on.
> - Connection timeout detector from the device side (useful with connection over wireless network).
> - Screen density and screen size can be set on the device during the session.
> - "Tablet mode": dim device screen, synchronize device screen orientation with PC (requires additional service on the device).
>
> Internals:
> - The server "forks" itself for full life cycle control (adb may kill it instead preventing required cleanup).
> - Full cleanup at exit.
> - Expandable parameters to the server applet, allowing compatibility between versions.
> - Java NIO to simplify network I/O and not be limited to Unix sockets.
> - Different connection type: direct connect to the device instead of "adb forward".
> - Commands: actions with no parameters
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked issue 495 comment and the referenced Lurker00/scrcpy fork, comparing the listed user-visible and internal changes with this repository. The issue names no files or tests and does not define a specific contribution, so a feature and its compatibility and testing criteria would need to be agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c, java
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100