-47
submitted 1 week ago* (last edited 1 week ago) by ghorbelhamdi@lemdro.id to c/android@lemdro.id

I've been building Buddy, a free, open source (Apache 2.0) Android app. You type or say what you want in a floating bubble, and an AI agent reads the screen, taps and types through your apps to do it.

  • Your choice of agent: Claude Code, Codex, OpenCode, Antigravity or Grok, running inside the app (Alpine Linux via proot) on your own plan. OpenCode's free models need no account.
  • No root, adb or PC: it reads the screen and taps through the accessibility service.
  • Asks first: before anything is sent, posted, bought or deleted. It pauses when you touch the screen and never types passwords or payment details.
  • Builds apps: with Linux tools on, it builds real APKs on the phone. This week I drew a maze on a paper towel, took a photo, and it made it a tilt game. The first build crashed on launch; it found the bug and fixed it.

To be upfront:

  • What the agent reads on your screen goes to the AI service you pick.
  • It's early (2.2), tested most on a OnePlus 12 with Android 16.
  • It's not on Play (Google rejected the accessibility use), so it's an APK from GitHub releases, built by GitHub Actions from the source.

Source and releases: github.com/ghorbelhamdi/buddy-android

Happy to answer questions here.

you are viewing a single comment's thread
view the rest of the comments
[-] ghorbelhamdi@lemdro.id 1 points 1 week ago* (last edited 1 week ago)

Done: 2.2.25 makes this easy. Ollama, LM Studio and llama.cpp are in the service list, plain http works on your own network and over Tailscale, and no key is needed. README has a section now: https://github.com/ghorbelhamdi/buddy-android#local-models

Honest results so far, on a PC with an RTX 2060 Super: Qwen3 8B and 4B handle simple one-step requests (battery, phone status), but multi-step tasks on the screen failed. The 4B tapped the wrong buttons in the calculator and then claimed it worked. So for real tasks you'll want a bigger model; I'm trying gpt-oss 20B next.

[-] Shatur@discuss.tchncs.de 2 points 1 week ago* (last edited 1 week ago)

It's is expected, they're small models. But something like Qwen 3.8 27B or Qwen 3.8 Flash Next should handle it.

How much VRAM do you have? If it's a 12GB card and you also happens to have 64 GB of RAM, you should be able to run Qwen 3.8 Flash Next with Q3. It's one of the most "hyped" local models right now (because it's quite capable and has somewhat realistic HW requirements).

[-] ghorbelhamdi@lemdro.id 2 points 1 week ago* (last edited 1 week ago)

Update: you were right. Qwen3.8 27B (unsloth UD-IQ3_XXS) did the calculator task correctly (1234×5678 = 7,006,652), but took 18 minutes on my 8 GB card, almost all of it reading the prompt and screen on the CPU.

Qwen3.5 9B is the interesting one: one run typed the wrong numbers and claimed success, the next did it right in about 2 minutes. So small models can do it, just not reliably yet.

[-] Shatur@discuss.tchncs.de 2 points 1 week ago* (last edited 1 week ago)

Yeah, 27B only usable if you can fit it entirely in VRAM. Only MoE models are fine to split, like the mentioned Qwen 3.8 Flash Next. Even though it's large, only the active 6B parameters needs to be located in VRAM, the rest can be in RAM and SSD.

[-] ghorbelhamdi@lemdro.id 2 points 1 week ago

Good call. Qwen3.6 35B-A3B runs fine split between my 8 GB card and RAM, and gets the task right. Flash Next is too big for 32 GB. The latest Buddy (2.2.27) also fixes local models with Codex, which your suggestion helped me find.

this post was submitted on 07 Nov 2026
-47 points (23.6% liked)

Android

22365 readers
220 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 3 years ago
MODERATORS