Ava turns any Android 5+ device into a voice-first Home Assistant kiosk. Native C++ under the hood, so a 10-year-old tablet still listens, talks, and runs the house - with AirPlay-grade audio in every room, all in sync.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 90%
Response Time: 5h
First Timer Success: 100%
knoop7/Ava-Pro has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in knoop7/Ava-Pro respond to incoming external pull requests in approximately 5.1 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 57.3 places knoop7/Ava-Pro in the A tier.
The external contributor pull request merge rate for knoop7/Ava-Pro is 90.0%, based on public PR activity from non-core contributors.
knoop7/Ava-Pro currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Ava turns any Android 5+ device into a voice-first Home Assistant kiosk. Native C++ under the hood, so a 10-year-old tablet still listens, talks, and runs the house - with AirPlay-grade audio in every room, all in sync.
Collaborative maintainer environment in knoop7/Ava-Pro. Reviews community pull requests with focus on project quality.
Discussions in knoop7/Ava-Pro 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/knoop7/Ava-Pro?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~24 hours (40% approval). Keep your diff compact for rapid review.
Pre-flight checks I have searched the existing issues and found no duplicate This is a feature request, not a bug report The problem When I leave a room or run an "everything off" script in Home Assistant, I can only stop media that plays through Ava's own media player (Music Assistant / Sendspin). Media from other apps on the same device (Netflix, Emby, and similar) keeps playing, because Ava has no way to control other apps' playback. I tried the existing options on a wall-mounted tablet: launch_intent with the home intent (intent:#Intent;action=android.intent.action.MAIN;category=android.intent.category.HOME;end). The video app switches to picture-in-picture, and the audio keeps playing. Disabling PiP per app did not fix it, because the picture goes away but the sound continues. launch_intent cannot send a media key or any broadcast. The wiki says broadcast intents are supported since 0.6.3, but in 0.7.7 IntentLauncher.launch() only calls startActivity(), and the service has on
Pre-flight checks I have searched the existing issues and found no duplicate This is a feature request, not a bug report The problem When the browser overlay is running, the only way to get back to the Ava Pro launcher (home screen) is to tap the Browser item in the sidebar, which toggles the browser off. There is no item that clearly means "go to the launcher". For users running Ava Pro as a kiosk/wall panel with Home Launcher mode, this is unintuitive: the launcher is reached only as a side effect of hiding the browser, and the same button is needed again to bring the browser back. As far as I can tell, the sidebar in 0.7.7 only offers a fixed set of items (DeviceControl, TouchPad, VoiceMessage, Browser, Weather, SimpleClock, DreamClock, QuickEntity, VinylCoverDisplay, HomeLock, Camera, MuteMicrophone, DarkMode). None of them navigates to the launcher, and custom entries cannot be added. Proposed solution Add a new sidebar item, e.g. Home / Launcher, that: Hides the browser over
Pre-flight checks I have searched the existing issues and found no duplicate I am running the latest Ava release Bug summary With the Android Intent Executor and "Show in Home Assistant" both enabled, Home Assistant never registers an esphome.<device>_launch_intent action for the device. There is also no Intent Launcher status sensor. The device itself connects fine and exposes its other 32 entities. Steps to reproduce On the tablet, open the Intent Executor settings (German UI: "Intent-Ausführung"). Turn on ADB control, turn on "Intent-Ausführung (Remote Intent-Ausführung, erweitert)", and turn on "In Home Assistant anzeigen (launch_intent remote steuern)". In Home Assistant, reload the ESPHome config entry of the device. Still no service. Disable the ESPHome config entry, then enable it again. The device reconnects. Restart the Ava service on the device, using the "Service neu starten" button entity. The device reconnects. In Developer Tools -> Actions, search for launch_inte
Pre-flight checks I have searched the existing issues and found no duplicate This is a feature request, not a bug report The problem In Ava Pro 0.7.7 the system navigation bar is always hidden. There is no setting to change this. ImmersiveMode() is called unconditionally in HomeScreen.kt and SettingsDetailScreen.kt. It sets SYSTEM_UI_FLAG_HIDE_NAVIGATION together with IMMERSIVE_STICKY. It is re-applied on every onResume. If the bar is swiped in temporarily, an OnSystemUiVisibilityChangeListener hides it again after 500 ms. On devices where the navigation bar is needed (for example for Back/Home/Volume without a hardware button), it can't be kept visible. I couldn't find an existing option in the wiki or release notes. The only related feature is the Portal System Bar Control from 0.6.7, which only applies to Portal devices via portal-support. Proposed solution Add a preference, for example "Hide system navigation bar" (default: on, so current behavior stays unchanged). When the
Pre-flight checks I have searched the existing issues and found no duplicate I am running the latest Ava release Bug summary If an AVA-PRO update is available and installed with esphome update mechanism over HA, the app becomes unresponsive (during download) on an echo show 8 with lineage OS 18.1. Steps to reproduce press update in HA when an AVA-PRO update is available (through esphome) AVA-PRO get's unresponsive during download Also android's ANR (Application Not Responding) dialog comes up Expected vs actual behavior Download should be happen in an background thread and not the UI thread to keep AVA-PRO gui alive during app update. Ava version 0.7.7 Device Echo Show 8 with LineageOS 18.1 image build v5 Feature area Other Logs Additional context No response
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 knoop7/Ava-Pro, 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 knoop7/Ava-Pro acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.0% were successfully merged into the primary branch.
knoop7/Ava-Pro has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. 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 57.3 places knoop7/Ava-Pro in the Welcoming tier.
The external pull request merge rate is 90.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, knoop7/Ava-Pro 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 knoop7/Ava-Pro 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.