bmax121/apatch

The patching of Android kernel and Android system

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 8th, 2026
Created on August 21st, 2023
Open Issues & Pull Requests: 49 (-1)
GitHub issues: Enabled
Number of forks: 774
Total Stargazers: 7,922 (+0)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 45.0 days
90th percentile: 181.9 days
Tracked items: 335

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 11% of issues opened in the past year have been closed. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 42
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 229 days
Stale 30+ days: 29
Stale 90+ days: 26

Recent activity

Opened in 7 days: 3
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (213)
  • enhancement (89)
  • wontfix (17)
  • invalid (15)
  • question (4)
  • help wanted (3)

Most active issues this week

Detailed Description

APatch is a kernel-based root solution for Android devices that enables system-level patching and code injection.

APatch addresses the need for deep system modification on Android by operating at the kernel level rather than relying solely on user-space root access. It provides two module systems: APM for Magisk-like modules and KPM for kernel-level code injection with inline-hook and syscall-table-hook capabilities. The tool relies on KernelPatch as its core component and derives its user interface and module architecture from existing Android customization projects.

The tool is suitable for developers and advanced users working with ARM64 Android devices running kernel versions between 3.18 and 6.12. It requires specific kernel configurations including CONFIG_KALLSYMS enabled, with full support requiring CONFIG_KALLSYMS_ALL. Potential adopters should be aware that Samsung devices with security protection are not yet supported. The project explicitly notes that SuperKey, its privilege mechanism, carries higher privileges than standard root access and requires careful key management to prevent unauthorized device control.

The project maintains active communication channels through Telegram for updates and discussions in both English and Chinese. Documentation exists but is acknowledged as incomplete and subject to change, with the project actively seeking volunteer contributions for documentation in additional languages. Translation management is handled through automated systems with Chinese and English as reference languages.