Geminiman WearOS Local ADB App-Analysen für 23. September

⌚ Geminiman WearOS Local ADB Run ADB commands directly from your Wear OS watch — no phone or PC needed after setup. Built for developers, testers, and power users who want quick local ADB access from the watch itself. Enable wireless debugging, pair or connect from the watch, then run saved or pending commands directly on Wear OS. ✨ Key Features 🔌 Local ADB on Wear OS Run ADB shell commands directly from your watch using a bundled local ADB setup. 📡 Pair & Connect from the Watch Pair with wireless debugging or reconnect to an existing debugging session without needing a computer every time. ⚡ Saved Commands Create reusable commands for common tasks such as checking device info, listing packages, or running shell commands. 📥 Pending Command Queue Commands received from external links are not executed blindly. Review them first, then choose whether to save, discard, or run them. 🧩 Batch Pending Commands Review multiple pending commands at once, select what to run or discard, then execute selected commands together. 📄 Command Output on Watch View command results directly inside the app after execution. 🛡️ Spam Guard Protection Repeated external command requests are limited to reduce unwanted prompts. 🎛️ Watch-Friendly Interface Designed for small Wear OS screens with clear controls, full-screen dialogs, and rotary scrolling support. 📱 Optional Phone App The phone companion app is optional. The watch app can work on its own. The phone app simply makes it easier to manage, edit, and organize watch commands from a larger screen. 🧑‍💻 Developer Integration Other apps can send commands to Geminiman WearOS Local ADB using a deep link Intent. Example: developers that need special permission that can be granted via ADB, can send the command to my application, and it will run once adb is connected. Syntax: geminiman://command?title=TITLE&cmd=COMMAND&args=ARGS&description=DESCRIPTION&caller=CALLER_NAME Parameters: • cmd: required command to run • args: optional extra arguments • title: optional readable title • description: optional explanation shown to the user • caller: optional app/tool/developer name Example link: geminiman://command?title=SDK%20Version&cmd=getprop&args=ro.build.version.sdk&description=Show%20Android%20SDK%20version&caller=My%20App Java: ~~~~~~~~~~~~~~~~~~~~~~~ Uri uri = new Uri.Builder() .scheme("geminiman") .authority("command") .appendQueryParameter("title", "SDK Version") .appendQueryParameter("cmd", "getprop") .appendQueryParameter("args", "ro.build.version.sdk") .appendQueryParameter("description", "Show Android SDK version") .appendQueryParameter("caller", "My App") .build(); Intent intent = new Intent(Intent.ACTION_VIEW, uri); intent.addCategory(Intent.CATEGORY_BROWSABLE); startActivity(intent); ~~~~~~~~~~~~~~~~~~~~~~~ Kotlin: ~~~~~~~~~~~~~~~~~~~~~~~ val uri = Uri.Builder() .scheme("geminiman") .authority("command") .appendQueryParameter("title", "SDK Version") .appendQueryParameter("cmd", "getprop") .appendQueryParameter("args", "ro.build.version.sdk") .appendQueryParameter("description", "Show Android SDK version") .appendQueryParameter("caller", "My App") .build() val intent = Intent(Intent.ACTION_VIEW, uri).apply { addCategory(Intent.CATEGORY_BROWSABLE) } startActivity(intent) ~~~~~~~~~~~~~~~~~~~~~~~ Note: Use URL encoding when building links manually. Incoming commands are treated as pending requests and require user approval before execution. ⚠️ Important Notice This app is intended for users who understand ADB and wireless debugging. ADB commands can affect apps, settings, and device behavior, so only run commands you trust. Requirements: • Wear OS device • Developer options enabled • Wireless debugging enabled • Basic knowledge of ADB commands Found an issue or have a suggestion? Github: https://github.com/ITDev93/Geminiman-WearOS-Local-ADB ~ Category: Application