cinit/QAuxiliary

QNotified phoenix - To make OICQ great again

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 29th, 2022
Open Issues & Pull Requests: 270 (+0)
GitHub issues: Enabled
Number of forks: 416
Total Stargazers: 5,746 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 130
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 488 days
Stale 30+ days: 123
Stale 90+ days: 117

Recent activity

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

Top labels

  • Bug (208)
  • Feature (122)
  • invalid (7)
  • won't impl (6)
  • Too difficult (5)
  • can't repro (5)
  • dev (5)
  • UI/UX (2)

Most active issues this week

Detailed Description

QAuxiliary is an open-source Xposed module that extends the functionality of QQ and TIM messaging applications on Android.

The tool addresses the limitation of QQ and TIM's built-in features by injecting custom functionality through the Xposed framework. It operates as a module that, once activated, integrates a settings page directly into QQ or TIM's native settings menu. The project supports Android 7.0 and later, with compatibility for QQ 8.2.0 and above, TIM 2.2.0 and above, and other variants. For systems without a Xposed environment, the tool can alternatively be loaded through Frida with root access.

Adoption is suited for Android users running compatible versions of QQ or TIM who want to customize their messaging experience through additional features. The project emphasizes that all development is intended for learning purposes and explicitly prohibits use for illegal activities. The tool is distributed freely with no paid versions, and the team reserves the right to remove features that are widely misused or significantly disrupt normal user experience. Users should be aware that the project operates under a rolling update model with two release channels: a CI version that updates automatically after each commit and may contain unstable changes, and a recommended CI version released at the team's discretion for significant updates or accumulated fixes.

The project maintains a substantial user base that actively reports issues, with almost all open issues originating from external users rather than the core team. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug reports, feature requests, and decisions not to implement certain functionality.