📱 Display and control your Android device graphically with scrcpy.
C-Rank Grade: C (Moderate) - 35/100
External PR Merge Rate: 20%
Response Time: 7d
First Timer Success: -
viarotel-org/escrcpy has a recorded first-timer success rate of 0.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in viarotel-org/escrcpy respond to incoming external pull requests in approximately 161.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 34.6 places viarotel-org/escrcpy in the C tier.
The external contributor pull request merge rate for viarotel-org/escrcpy is 20.0%, based on public PR activity from non-core contributors.
viarotel-org/escrcpy currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
📱 Display and control your Android device graphically with scrcpy.
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in viarotel-org/escrcpy.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/viarotel-org/escrcpy?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~105 hours (25% approval). Large PRs (>500 lines) take ~777 hours (15% approval). Keep your diff compact for rapid review.
Describe the problem you confuse 小米的手机无线调试每次开启都会自己换端口，导致设备列表很多同样的设备。有没有办法用什么东西绑定一下？比如mac地址？或者能不能手动绑定也行？
Describe the problem you confuse Currently, when mirroring the device, there is no reliable way to forward the device's internal audio directly to the computer (especially for devices running Android 10 or lower). To hear the sound, I still have to turn on the phone's external speaker or plug headphones directly into the phone. Proposed Solution: Please consider integrating or adding support for sndcpy (Sound Copy) alongside the video mirroring. Benefits: Adding sndcpy would route the phone's audio directly to the PC's audio output. This provides a truly seamless experience, allowing users to listen to the phone's sound through their computer speakers or PC headphones without needing to interact with the phone's physical audio hardware at all. Thank you for considering this feature!
如题并如下图，现在的文件传输窗口，默认文件名是无序排列的，每次打开需要点击一次文件名排序。 另外能否增加按文件类型排序，很难选中同一类文件，并且此时能不能像Windows文件管理器一样，按Shift键鼠标点击时，能选择两次点击之间的所有文件（如果有实现难度可以搁置）。 感谢！
控制结束关闭屏幕，应该是关闭所有应用后才会锁屏对吗？现在，如果你打开2个以上应用（对应会产生多个窗口），任意关闭一个就会导致锁屏。这时控制并没结束，不应该锁手机屏幕对吧？你说这是因为每一个实例都开启了“控制结束关闭屏幕”。 那能否改一下这个参数的调用的逻辑为"只有第一个实例设置控制结束时关闭屏幕，其后再开起的实例不再使用这个参数"，虽然这无法使用真正的关闭所有实例后才锁屏，但是这种体验也应该比每一个实例都会开启要好。因为多开app难免会关掉其中的部分应用。这种逻辑只有在关闭第一个实例的时候才会锁定，也算是一个权宜之计对吗？
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to viarotel-org/escrcpy, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of viarotel-org/escrcpy acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 20.0% were successfully merged into the primary branch.
viarotel-org/escrcpy has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 34.6 places viarotel-org/escrcpy in the Moderate tier.
The external pull request merge rate is 20.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, viarotel-org/escrcpy currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for viarotel-org/escrcpy are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.