Русская версия

A curated collection of Android tools, apps, fixes, workarounds, and practical step-by-step guides for power users.

Last manually audited: 2026-10-01

The goal is simple: document useful Android software that solves real, often oddly specific problems — especially the kind of tools that can take hours of forum, GitHub, Reddit, and search-engine digging to discover.

This repository contains both:

• a catalog of useful apps with short, problem-oriented descriptions and trusted download/source links;
• detailed guides for setups that need several apps, special permissions, or non-obvious workarounds.

Principle: whenever possible, links point to the original source repository or the developer's official website, and installs point to Google Play or the project's official release channel.

See the full Android-to-Android wireless secondary display guide.

• ⭐ v2RayTun — recommended general-purpose Android client when you already have your own proxy/VPN subscription or server configuration. It supports common Xray/V2Ray-style protocols and imports configs/subscriptions.
• ⭐ ByeByeDPI — recommended local DPI/censorship-bypass tool when the problem is ISP filtering rather than the need for a remote VPN endpoint. It is not a remote VPN service and does not hide your public IP by itself.

Android normally allows only one active VpnService-based tunnel at a time. Many of the clients below therefore compete for the same Android VPN slot even when they are technically proxy clients rather than commercial VPN services. When combining tools, check whether one of them can run in proxy mode instead of VpnService mode.

RKNHardering is a diagnostic tool, not a VPN and not a guarantee that a setup is undetectable. The project documents both confirmed checks and community/research findings, so read its confidence labels and upstream documentation before treating a result as definitive.

Android Auto behavior for sideloaded/non-standard apps is version-sensitive. Fermata's releases and issue tracker document compatibility changes as Android Auto evolves, so check the project's current release notes/issues before assuming Fermata Auto or Fermata Mirror will appear and work on your Android Auto version.

Only use RFID/NFC read/write tools on cards, tags and systems you own or are explicitly authorized to test.

Hardware matters: Android NFC capabilities depend on the phone's NFC controller and firmware. For example, not every phone can perform every MIFARE Classic operation even if the app itself supports it.

Official project documentation should be the first source for downloads and security-sensitive setup, but many Android edge cases are documented much better by the community.

• 4PDA forum — especially useful for Russian-language device-specific threads, firmware quirks, Android Auto, head units, root/Shizuku, networking and obscure Android utilities.
• XDA Forums — one of the strongest English-language sources for ROM/device-specific guides, bootloader/root topics, Android Auto, ADB, system tweaks and troubleshooting.

A useful search pattern is: exact app/tool name + device model + Android/firmware version + the symptom.

Treat forum attachments, modified APKs and old instructions as untrusted until verified. Prefer upstream GitHub/official releases for installation, and use 4PDA/XDA mainly to discover device-specific fixes, compatibility notes and troubleshooting paths.

This is not intended to be a dump of every Android app. A tool belongs here when it does at least one of these well:

• solves a specific problem that Android or an OEM does not solve cleanly;
• replaces a paid/cloud-locked workflow with a strong free or open alternative;
• exposes useful system functionality normally hidden from users;
• bridges Android with PCs, cars, audio systems, displays, NFC/RFID hardware or other devices;
• is unusually useful but difficult to discover without knowing its exact name.

• Shizuku: some devices/ROMs have reported UserService regressions with 13.6.0. Our MediaTek test device could run Shizuku itself and use Mirror/Extend, while MagicDesk UserService binding timed out; 13.5.4 fixed it. See the secondary-display guide for exact symptoms and upstream issues.
• Android Auto: Google can change what sideloaded apps are allowed to do or how third-party head-unit software connects. Treat Fermata Auto and HUR behavior as version-dependent and check their current upstream notes.
• Secondary displays: Android/OEM firmware can override standard multi-display behavior. A tool supporting a feature does not guarantee every OEM ROM will allow it.

• Prefer the developer's official repository, official website, Google Play, F-Droid, or official GitHub Releases.
• Avoid random APK mirrors and pre-patched packages when the original project provides a trusted distribution channel.
• Privileged tools such as Shizuku, root utilities, Android Auto workarounds and RFID writers can change system behavior or data. Read the upstream documentation first.
• Some techniques are firmware- and Android-version-dependent. Guides in this repository state the hardware/OS on which they were actually tested.

The original editorial content, documentation, structure, and curation in this repository are licensed under the Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) license.

You may copy, share, remix, translate, and adapt this repository for non-commercial purposes as long as you provide appropriate attribution and indicate changes. A practical attribution format is:

Android Power User Toolkit by lgg — https://github.com/lgg/android-power-user-toolkit — CC BY-NC 4.0

Third-party app names, trademarks, logos, screenshots, linked source code, and other third-party material remain subject to their respective owners' licenses and rights.

See LICENSE for details.

PRs and issues are welcome. A useful contribution should ideally explain the problem the tool solves, not just the app name.

Suggested entry format:

Tool:
Problem it solves:
Why it is useful:
Source / official site:
Official install:
Requirements / caveats:
Tested on (optional):

If a tool saved you hours because it solved a weird Android problem nobody documents well, it probably belongs here.