Endi mavjud! Telegram Tadqiqoti 2025 — yilning asosiy insaytlari 
NPatch
Kanalga Telegram’da o‘tish
NPatch is a rootless xposed framework that injects dex and native libraries into the target APK to provide Xposed API support inside the app process. Website: npatch.nkbe.top
Ko'proq ko'rsatish📈 Telegram kanali NPatch analitikasi
NPatch (@npatch) Xitoy til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 17 498 obunachidan iborat bo'lib, Texnologiyalar & Aralashmalar toifasida 7 522-o'rinni va Xitoy mintaqasida 12 888-o'rinni egallagan.
📊 Auditoriya ko‘rsatkichlari va dinamika
невідомо sanasidan buyon loyiha tez o‘sib, 17 498 obunachiga ega bo‘ldi.
06 Iyul, 2026 dagi oxirgi ma’lumotlarga ko‘ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni 682 ga, so‘nggi 24 soatda esa 12 ga o‘zgardi va umumiy qamrov yuqori darajada qolmoqda.
- Tasdiqlash holati: Tasdiqlanmagan
- Jalb etish (ER): Auditoriya o‘rtacha 46.09% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining 10.05% ini tashkil etuvchi reaksiyalarni to‘playdi.
- Post qamrovi: Har bir post o‘rtacha 8 064 marta ko‘riladi; birinchi sutkada odatda 1 758 ta ko‘rish yig‘iladi.
- Reaksiyalar va o‘zaro ta’sir: Auditoriya faol: har bir postga o‘rtacha 19 ta reaksiya keladi.
- Tematik yo‘nalishlar: Kontent npatch, neozygis, port, server=, tg://proxy kabi asosiy mavzularga jamlangan.
📝 Tavsif va kontent siyosati
Muallif resursni shaxsiy fikrni ifoda etish maydoni sifatida ta’riflaydi:
“NPatch is a rootless xposed framework that injects dex and native libraries into the target APK to provide Xposed API support inside the app process.
Website: npatch.nkbe.top”
Yuqori yangilanish chastotasi (oxirgi ma’lumot 07 Iyul, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli bo‘lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Texnologiyalar & Aralashmalar toifasidagi muhim ta’sir nuqtasiga aylantirishini ko‘rsatadi.
17 498
Obunachilar
+1224 soatlar
+1747 kunlar
+68230 kunlar
Postlar arxiv
17 509
https://t.me/onpatch/197
Test more, tell us more~ Please share your feedback—even if it's just to tell us everything works great!
17 509
NPatch 官方網站 npatch.nkbe.top 的指南內容已更新，並且已盡量對齊目前的最新實作。這次不只是補充了原本較缺少的內容，也把目前的架構、使用方式、模式差異與一些常見問題整理得更清楚，希望能讓新使用者更容易上手，也讓已經在使用 NPatch 的朋友更方便查閱。
如果你之前看過舊版說明，現在的內容會更接近目前實際的行為與設計，歡迎大家有空去看看。
The guides on the official NPatch website (npatch.nkbe.top), have been updated and brought in line with the latest implementation as much as possible. This update does not just fill in missing details, but also reorganizes the current architecture, usage flow, mode differences, and common questions so the documentation is easier to follow for both new and existing users. If you have read the older docs before, the current version should better reflect how NPatch actually works today.
17 509
In addition, the Release list display has been updated, allowing users to more easily view published Releases instead of having to do as before by viewing through published tags
除此之外，还更新了 Release list 的显示，用户可以更方便的查看已发布的 Release 而不是只能想之前一样通过发布的 tag 来查看
17 509
For a long time, developers working with open-source projects on GitHub have faced a major challenge when tracking the popularity of various versions: it was not possible to easily see the download counts for each release directly on the web page. In the past, project maintainers or ordinary users who wanted to access download data for a specific version had to either use GitHub’s official API or third-party browser extensions. This not only made it difficult to obtain this information but also made it hard for users to assess a project’s activity level effectively.
Today, this inconvenience is finally a thing of the past. GitHub recently added a new feature to its Releases page, displaying the number of times each file in a repository has been downloaded right on the frontend. As shown in the screenshot, the updated resource list has undergone significant optimization: in addition to the original filename, hash checksum, file size, and upload date in the information bar of each precompiled file, a clear download count has been added.
This seemingly minor interface improvement actually precisely addresses a major need in the open-source community, making data acquisition extremely simple and providing an excellent metric for measuring project reach. However, there is still a significant issue: currently, this feature appears to be limited to project owners viewing their own repositories. If download data remains hidden behind a permission wall, it serves merely as a backend statistical tool for developers rather than a public metric for ordinary users to evaluate software stability and widespread community recognition.
Despite this limitation, GitHub has listened to the long-standing requests of the developer community by bringing key data, which were previously hidden in the underlying APIs, to the forefront. It is our hope that GitHub will eventually make these metrics fully public, making the health of the open-source ecosystem more transparent and visible to all.
17 509
NPatch is now largely compatible with API 102. A test version will be released after the upstream croe merges the necessary compatibility changes.
feat: Implement finalized libxposed API 102 hot reloading #757
17 509
RVX has been officially discontinued
I’m sure I’m not the last person to hear this news. Click this link for details.
17 509
🎉 EvoMap 活动：把你的 GitHub 星星转化为大模型 API 额度！
━━━━━━━━━━━━━━
📌 参与规则：
提交你的公开 GitHub 仓库，按星标数分档拿积分：
⭐️ ≥ 1 → 500 积分 ≈ 518次调用 GPT-5.5 Opus-4.7
⭐️ ≥ 200 → 2,000 积分 ≈ 2074次调用 GPT-5.5 Opus-4.7
⭐️ ≥ 1,000 → 10,000 积分 ≈ 1万次调用 GPT-5.5 Opus-4.7
星标数以提交时为准，锁定后不可更换。仓库拥有者和核心贡献者均可参加，但仓库必须在6月18日前就创建。💝 注册时填入邀请码
VVVXFXVD 即可 额外获得 200 积分 ✔️
━━━━━━━━━━━━━━
❤️ 参与链接： https://evomap.ai/zh/api-grant?invite=VVVXFXVD
━━━━━━━━━━━━━━
🥳门槛极低，有 GitHub 公开仓库的都可以来薅！
😈 小提示：只要有过在6月18日被合并的PR就算数17 509
非官方，使用有风险
这是我的分支的CI版本，供测试以下三个改动的可用性，也就是：
完整实作的 API 102
feat: Implement finalized libxposed API 102 hot reloading #757
启用在线仓库备用地址
feat(repo): Updates backup routes and allows manual selection of warehouse sources #750
优化 dex2oat 包裝器的挂载方式
Improve dex2oat wrapper mounting and add XmlUtils stub
官方版请查看 JingMatrix/Vector 期待 @NeoZygisk 不定时更新
17 509
Android Gradle 外掛程式 (AGP) 9.0 引入了內建 Kotlin 並預設啟用，並將在 AGP 10.0 (2026 年中) 移除停用功能。雖然這是為了統一構建流程，但對需要自訂 Kotlin 版本的專案很不友好。往後升級 Gradle、AGP 就會連動更新內建 Kotlin，必須同步改動 Kotlin 與 KGP，整體升級成本大幅抬升。我我想，這項改動或許會促使我和像我這樣的一群人選擇將專案永久停留在 AGP 8 或 AGP 9。
17 509
Repost from ONPatch
665-668
- 將衝突檢查延後到啟動初始化之後執行，確保啟動流程正確 - 修正 LSPlant 的 rwxp 記憶體權限洩漏所導致的環境異常問題 - 提升 seccomp 重導穩定性並更新 NPatch 的 LSPlant 相容性鉤子 - 加強 I/O 與路徑檢測繞過，補齊 APK 可見路徑與 fd 掛載資訊偽裝更多說明： 這次更新主要針對的是目前 Android 生態圈中中高強度的加固方案（如 360 加固等）以及深度的環境檢測框架（如 Smallcheck）。這些檢測手段不再僅限於簡單的包名比對或 root 偵測，而是深入到 Linux 核心層與 ART 執行緒。 以下為具體「過掉」的檢測機制解析：
1. 提升 seccomp 重導穩定性並更新 LSPlant 相容性鉤子 這個部分的更新主要解決了主動探測防禦與 ART 執行緒逃逸的問題： 過掉「探測性崩潰（Crash-based Probing）檢測」： - 檢測原理： 偵測會故意向openat等系統呼叫傳入「畸形的路徑」或「不可讀的記憶體指標」。如果你的 seccomp 攔截器（SIGSYS handler）直接去讀取（解引用）這些指標，就會觸發 Segmentation Fault，導致外掛進程崩潰，或者暴露出有工具在攔截 syscall 的事實。 - 繞過方式： 更新後，不再於 SIGSYS 中直接解引用指標，而是先讓核心去驗證該路徑是否合法並打開它，再透過/proc/self/fd解析回傳的 fd。這讓惡意探測無法引發攔截器崩潰，完美隱蔽了 seccomp 重導的存在。 過掉「ART 內聯優化逃逸（Inline / AOT Escape）檢測」： - 檢測原理： 現代 Android (特別是 Android 8.0+) 的 ART 虛擬機會頻繁利用 ProfileSaver 進行 AOT (Ahead-of-Time) 編譯，並將部分頻繁呼叫的方法「內聯 (Inline)」。一旦目標方法被內聯，呼叫者會直接執行機器碼，不再經過方法的入口點，這會導致 LSPlant 等依賴入口點替換的 Java Hook 失效。防護系統會利用這一點，透過頻繁觸發特定邏輯並檢查執行時間或路徑，來判斷是否被 Hook。 - 繞過方式： 透過安裝 ProfileSaver 相容性鉤子並強制對dex2oat關閉 inline，確保目標方法永遠不會被編譯成無法攔截的內聯狀態。這保證了 Hook 的絕對覆蓋率，過掉了依賴內聯機制的完整性校驗。
2. 加強 I/O 與路徑檢測繞過，補齊 APK 可見路徑與 fd 掛載資訊偽裝 這部分是針對 VFS (虛擬檔案系統) 級別的深度稽查，特別是 Smallcheck 這類極度吹毛求疵的環境檢測工具： 過掉「Java 層 API 交叉比對檢測」： - 檢測原理： 應用不僅會透過Context.getPackageCodePath()獲取 APK 路徑，還會深入反射讀取LoadedApk、BoundApplication內的ApplicationInfo.sourceDir等欄位，甚至透過java.io.FileAPI 進行交叉比對。如果重導邏輯只覆蓋了表層，底層欄位仍指向你 patch 過的私有目錄，就會被抓包。 - 繞過方式： 啟動後主動將這些深層框架變數恢復為原始 APK 的「可見路徑」，並偽裝 File API，讓所有 Java 層的路徑查詢都得到一致的假象。 過掉「底層 Metadata (中介資料) 檢測」： - 檢測原理： 防護系統不呼叫 Java，直接透過 native 的stat,lstat,statfs或statx系統呼叫，去查驗 APK 檔案的「大小」、「Inode 節點」、「建立時間」或「磁區資訊」。如果讀取到的是補丁 APK 的資訊，大小和時間絕對與原始 APK 不符。 - 繞過方式： 將 native 檔案 hook 擴充到所有涉及 file stat 的 syscall，強制回傳原始 APK 的 Metadata，讓檔案屬性在檢測工具眼中完美無瑕。 過掉「掛載點特徵 (Mount ID / FD) 深度比對」： - 檢測原理： 這是 Smallcheck 的拿手好戲。即使你完美偽裝了路徑與大小，檢測工具會去讀取/proc/self/fd/下打開的檔案描述符，並進一步讀取/proc/*/fdinfo/<fd>裡面的mnt_id(掛載點 ID)。如果你的補丁 APK 放在另一個分區（例如某個私有 data 目錄或 OverlayFS），它的mnt_id會與預期中/data/app/目錄所在的mnt_id不同，重導行為直接曝光。 - 繞過方式： 系統動態追蹤被重導的 fd，並在檢測讀取 fdinfo 時，直接將裡面的mnt_id覆寫篡改為「可見路徑（原始 APK）」應該要有的mnt_id。這直接在 VFS 層面阻斷了掛載點異常洩漏的問題。 過掉「虛擬檔案系統 (FUSE) 探測」： - 檢測原理： 檢查/dev/fuse或相關掛載行為，來判斷系統是否運作在被魔改的模組環境（某些模組會利用 FUSE 來做檔案攔截）。 - 繞過方式： 直接對/dev/fuse的查詢回傳「不存在」，減少異常掛載點暴露的面積。
17 509
libxposed API 102 is currently in the RFC stage. Please provide suggestions on the API design.
https://github.com/libxposed/api/pull/62
