Have Gemini debug a phone glitch over ADB

In Antigravity, Gemini queried settings over ADB, then pulled and disassembled OEM code to find a debug overlay nobody documented.

In short

What it does: In Antigravity, Gemini queried settings over ADB, then pulled and disassembled OEM code to find a debug overlay nobody documented.

Agent: Antigravity · Category: DevOps

Steps in brief:

  1. Connect the phone over USB and ask the agent in Antigravity for help.
  2. Let it query runtime settings via adb shell settings get … before guessing.
  3. If the cause is in proprietary OEM code, have it pull the APK and parse the DEX string table to find the responsible code.

+1 more step in the copyable prompt.

Who made it: Omar Afifi (DEV post, 9 Sep 2026) · source

Last updated · based on 336 use cases on agentsetups, each credited to its author.

by Omar Afifi9 Sep 2026

Prompt for your agent

Goal: Fix a strange Android behaviour Google search can’t explain.
Setup: agents used in source: Antigravity; tools/MCPs stated: ADB, Android.
Steps:
1. Connect the phone over USB and ask the agent in Antigravity for help.
2. Let it query runtime settings via adb shell settings get … before guessing.
3. If the cause is in proprietary OEM code, have it pull the APK and parse the DEX string table to find the responsible code.
4. Apply the setting change it identifies.
Rules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.
Based on: Omar Afifi — https://dev.to/omarafifi/my-phone-broke-and-gemini-fixed-it-329l (summarised from source; the source has no explicit step list)

Steps are our summary of the source (it has no explicit step list). Includes a “Based on” credit line.

I tried this

Tell the next builder. One anonymous answer each; click again to undo.

Agents, models and tools only what the source states

Agents
Antigravity
Tools
  • ADB
  • Android

Sources & credit