Use Anland in Termux (especially Termux native, PRoot and Chroot)
C-Rank Grade: C (Moderate) - 27/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
lfdevs/anland-termux 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 lfdevs/anland-termux respond to incoming external pull requests in approximately 0.0 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 26.5 places lfdevs/anland-termux in the C tier.
The external contributor pull request merge rate for lfdevs/anland-termux is 0.0%, based on public PR activity from non-core contributors.
lfdevs/anland-termux currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in lfdevs/anland-termux. Reviews community pull requests with focus on project quality.
Discussions in lfdevs/anland-termux focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/lfdevs/anland-termux?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
It's great that the keyboard covers partially work (the touchclick works naturally!, something that requires some adjustments in Termux:x11), but the mouse cursor can only be moved with two fingers on the touchpad, and the right-click isn't working either ( and also the scroll movement , which isn't working because of the moving cursor with two-finger) Termux x11 has some fixes for this, that might help and if you need help testing any fix, I can test it on my touchpad. The S Pen seems to be working 100% ( I even drew inside it! lol), which is a good sign, since Anland is better than termux:x11 for daily use now (x11 had monstrous lags) Even with Wobbly Windows, Anland performs excellently! (It becomes extremely fluid) One idea for the future is support for higher hz rates ( I think this is more a limitation of the Anland protocol than of the implementation ), but for now it's competing directly with Termux:x11!
Device: Lenovo Yoga Tab Plus (Snapdragon 8 Gen 3 / SM8650), tested with the Lenovo Keyboard Pack touchpad accessory (vendor=0x17ef, product=0x61ba) Symptom: On the physical trackpad, tap-to-click and two-finger scroll do not work at all. Physical click (pressing the pad's button), an external Bluetooth mouse, and cursor movement via drag all work correctly. Reproduced on two independent setups: *DroidSpaces (Fedora, KDE) *Manual rootful Termux chroot (Ubuntu 26.04, Plasma, native Turnip/Freedreno driver) Same symptom on both — rules out a container-specific misconfiguration. Diagnostics performed: getevent -pl on the touchpad's evdev device confirms correct kernel/HID reporting: INPUT_PROP_POINTER, INPUT_PROP_BUTTONPAD, and proper ABS_MT_SLOT/ABS_MT_POSITION_X/ABS_MT_POSITION_Y axes. dumpsys input shows Android's native InputReader classifies the device as Sources: MOUSE, running in Touch Input Mapper (mode - POINTER). dumpsys input also shows a Lenovo/ZUI vendor extension with tpTap
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 lfdevs/anland-termux, 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 lfdevs/anland-termux acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
lfdevs/anland-termux 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 ~-. 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 26.5 places lfdevs/anland-termux in the Moderate tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lfdevs/anland-termux currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lfdevs/anland-termux 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.