❤1👍1
👍2❤1🔥1
📢 Regarding Vector/LSPosed API Compatibility
Stop the panic. ReVanced Xposed is NOT affected by the recent API 101 updates in LSPosed 2.0 or future Vector updates.
1. ReVanced Xposed is NOT Affected
ReVanced Xposed uses the Legacy API. This is the "classic" Xposed standard. Whether the framework uses API 100 or API 101, it MUST maintain the Legacy layer to function as an Xposed framework.
The broken modules are built for the experimental API 100 (a beta version of Modern Xposed API) , they are failing because LSPosed 2.0 dropped support for that specific "beta" layer.
2. The "Modern API" Myth
The so-called "API 100" was never a formal standard. It was a slow-moving beta that some developers adopted prematurely. LSPosed recently finalized the specs as API 101 and wiped the slate clean of API 100. Since we never used that experimental API, there is nothing to "fix."
3. The Conclusion
ReVanced Xposed works perfectly on:
✅ LSPosed 1.x (Legacy)
✅ LSPosed 1.x (API 100)
✅ LSPosed 2.0 (API 101)
✅ Vector 2.0 (API 100)
✅ Future Vector (API 101)
Stop asking if it "supports API 101." It already works via the Legacy layer. If it ain't broke, don't fix it.
https://t.me/modulostk/5627
☬ @ModulOStk | Lean | Donations | +
Stop the panic. ReVanced Xposed is NOT affected by the recent API 101 updates in LSPosed 2.0 or future Vector updates.
1. ReVanced Xposed is NOT Affected
ReVanced Xposed uses the Legacy API. This is the "classic" Xposed standard. Whether the framework uses API 100 or API 101, it MUST maintain the Legacy layer to function as an Xposed framework.
The broken modules are built for the experimental API 100 (a beta version of Modern Xposed API) , they are failing because LSPosed 2.0 dropped support for that specific "beta" layer.
2. The "Modern API" Myth
The so-called "API 100" was never a formal standard. It was a slow-moving beta that some developers adopted prematurely. LSPosed recently finalized the specs as API 101 and wiped the slate clean of API 100. Since we never used that experimental API, there is nothing to "fix."
3. The Conclusion
ReVanced Xposed works perfectly on:
✅ LSPosed 1.x (Legacy)
✅ LSPosed 1.x (API 100)
✅ LSPosed 2.0 (API 101)
✅ Vector 2.0 (API 100)
✅ Future Vector (API 101)
Stop asking if it "supports API 101." It already works via the Legacy layer. If it ain't broke, don't fix it.
https://t.me/modulostk/5627
☬ @ModulOStk | Lean | Donations | +
👍3❤1
❤2👍2🥰2
Encore Tweaks v5.2.2
https://t.me/modulostk/5627
☬ @ModulOStk | Lean | Donations | +
Changelog
• Fix binder resolver for Android version newer than A12
• Fix binder resolver for jailbreak users
• Various UI/UX optimization and translation update on WebUI
• Other misc changes and optimizations
https://t.me/modulostk/5627
☬ @ModulOStk | Lean | Donations | +
👍3❤2
Tools
Tricky Store manager: a complete port of KOWX712's Tricky Addon: Update Target List, for whichever keystore module is active:
Tricky Store: config.ini with per-app modes (pkg, pkg!, pkg?) and per-app policy, and the legacy target.txt + security_patch.txt layout.
TEESimulator: config.json profiles (mode, patch levels, identity, auto-include).
OhMyKeymint: injector.toml scoop and every config.toml [trust] key.
It has the same features as upstream:
Target list with search, select all, deselect all and refresh.
Mode sheet on long press, and per-app policy.
Actions: select from DenyList (Magisk), deselect unnecessary apps (online list plus Xposed modules), add system apps, auto-add new apps.
Keyboxes from AOSP, generated "unknown", a local file, the keybox repository (the same iframe protocol) or custom providers (add, edit, remove, reset, import, export).
Prop handler and Verified Boot hash, schema-driven default policy with Today, help.
Keyboard shortcuts (Ctrl+A/D/F/S, Esc), the back gesture closing dialogs, and upstream's 23 translations, including right-to-left languages.
Optionally, a WebUI entry on the keystore module itself, and the TSupport-Advance auto-target stop flag.
RKP Workbench: Remote Key Provisioning.
Builds AuthenticatedRequest CSRs (DICE + COSE, per the AOSP IRemotelyProvisionedComponent HAL) and talks to the RKP server.
Verifies CSRs offline and exports keybox.xml, which the Tricky Store manager can install directly.
Device values are read from AOSP build properties.
Device ID Provisioner: writes attestation device IDs into the Qualcomm Keymaster trusted app through libQSEEComAPI.so, with a dry-run mode.
Module & updates: version and device summary, stable and canary updates with changelog, output files, command history, uninstall and reboot.
Every tool is translated into 14 languages: English, Simplified and Traditional Chinese, Japanese, Korean, Spanish, French, German, Italian, Brazilian Portuguese, Russian, Arabic, Vietnamese and Indonesian. Tricky Addon's other translations cover the strings the Tricky Store manager shares with it.
https://t.me/modulostk/5630
☬ @ModulOStk | Lean | Donations | +
Tricky Store manager: a complete port of KOWX712's Tricky Addon: Update Target List, for whichever keystore module is active:
Tricky Store: config.ini with per-app modes (pkg, pkg!, pkg?) and per-app policy, and the legacy target.txt + security_patch.txt layout.
TEESimulator: config.json profiles (mode, patch levels, identity, auto-include).
OhMyKeymint: injector.toml scoop and every config.toml [trust] key.
It has the same features as upstream:
Target list with search, select all, deselect all and refresh.
Mode sheet on long press, and per-app policy.
Actions: select from DenyList (Magisk), deselect unnecessary apps (online list plus Xposed modules), add system apps, auto-add new apps.
Keyboxes from AOSP, generated "unknown", a local file, the keybox repository (the same iframe protocol) or custom providers (add, edit, remove, reset, import, export).
Prop handler and Verified Boot hash, schema-driven default policy with Today, help.
Keyboard shortcuts (Ctrl+A/D/F/S, Esc), the back gesture closing dialogs, and upstream's 23 translations, including right-to-left languages.
Optionally, a WebUI entry on the keystore module itself, and the TSupport-Advance auto-target stop flag.
RKP Workbench: Remote Key Provisioning.
Builds AuthenticatedRequest CSRs (DICE + COSE, per the AOSP IRemotelyProvisionedComponent HAL) and talks to the RKP server.
Verifies CSRs offline and exports keybox.xml, which the Tricky Store manager can install directly.
Device values are read from AOSP build properties.
Device ID Provisioner: writes attestation device IDs into the Qualcomm Keymaster trusted app through libQSEEComAPI.so, with a dry-run mode.
Module & updates: version and device summary, stable and canary updates with changelog, output files, command history, uninstall and reboot.
Every tool is translated into 14 languages: English, Simplified and Traditional Chinese, Japanese, Korean, Spanish, French, German, Italian, Brazilian Portuguese, Russian, Arabic, Vietnamese and Indonesian. Tricky Addon's other translations cover the strings the Tricky Store manager shares with it.
https://t.me/modulostk/5630
☬ @ModulOStk | Lean | Donations | +
❤2👍2