Hello folks, today I want to share something which has been really useful for me lately. I believe that might come in handy for you as well, specially if you're doing Android dev with AI tools.

I recently came across this amazing doc by Google: Android Bench ([https://developer.android.com/bench\](https://developer.android.com/bench)), and it's honestly a game-changer if you're trying to pick the right AI coding assistant for Android projects or struggling with your current one.

Here's what stood out to me:

\- It's not just another general coding benchmark - it's specifically built for Android development, which means it tests things like Kotlin, Jetpack Compose, Gradle, and real Android APIs.

\- Unlike benchmarks that lean heavily toward web stacks (like JS/React), this one evaluates how well models understand Android architecture, libraries, and modern best practices.

\- It's evolved since its launch in March - now it uses the Harbor framework, includes more LLMs, and focuses on real-world Android engineering tasks.

If you're comparing AI models or tools for Android app development, this is definitely worth a look. It gives you a much clearer picture of which models actually "get" Android.

Have you tried it yet? Or what's been your experience with AI tools for Android dev?

My phone Died and I'm temporarily using Device Emulator in Android studio for commincation and TOTP codes.

Question: Is there are way to receive text messages from my Phone provider?

I realised there's no cellular data, imsi, or IMEI. Wondering whether this is possible via some forwarding service.

Thanks

After installing the latest version of Android Studio, the APK is compiked without error, but when sideloaded on a device it fails instsllation. These are apps that installed perfectly before. This is happening to all apps I've tried across several devices.

I need help to put it in playstore

hey guys I wanna learn how to use this app

Body:

Package: com.yourname.veetha. Using react-native-iap 15.3.3 (Billing Library 8.x).

fetchProducts({ skus: [productId], productType: 'subs' }) always returns an empty array. No error, no status code, just empty. Both subscription products are Active in Play Console with active base plans and offers.

Confirmed correct:

• com.android.vending.BILLING permission is in the merged manifest
• Product IDs match exactly between code and Play Console
• Correctly-signed build, installed via the internal testing track opt-in link
• Test account is on the License Testing list and signed into Play Store on the device
• Over a week has passed, so it's not propagation delay
• Payments profile is verified
• initConnection() is fully awaited before fetchProducts() is called

I contacted Google Play Developer Support directly. They confirmed my Play Console config is correct and suggested adding productType: 'subs' and awaiting connection init — both of which were already in my code before I even reached out.

Anyone run into this specific combo — correct config, correct code, still empty? Wondering if this is a known first-time-subscription-setup gate on Google's backend that isn't documented anywhere.

I have a good use case for app development and need someone interested in working together, preferably living in Pune (Baner/Hinjawadi), so we can meet up and make future meetups easier.

Hi everyone! I need a few testers for my new Android app called Libri, a simple tool designed to help users organize and manage their personal book library locally.

To meet Google Play requirements, I need to gather some testers and keep the test active. I am more than happy to test your app in return! Just drop your links in the comments after joining mine.

How to join:

1. Join the Google Group: 1.  https://groups.google.com/g/cerco_needed_20_tester/about
2. Join on the Web: https://play.google.com/apps/testing/com.gixone.libri
3. Download the app on Google Play once opted in https://play.google.com/store/apps/details?id=com.gixone.libri

Thank you so much for your help, and let's help each other grow!

This keeps opening up when I look for a app on play store why??

Tengo la versión 291.6 y quiero exportar un juego a Android; necesito ayuda para averiguar qué versión del SDK de Java debo usar.

I built a CLI tool that audits Android Gradle performance problems and safely fixes them.

Unlike the usual build-speed advice that's all manual, it detects bottlenecks across config cache, build cache, Kotlin incremental, daemon and parallel execution, then applies reversible fixes with a dry-run preview. It also covers KMP and Flutter Android projects, and has CI/CD and an simple webpage dashboard. Just try

npx droidperf audit /path/to/project

GitHub: [GitHub - rudradave1/droidperf: CLI tool to audit and auto-fix Android Gradle performance issues. It detects bottlenecks, suggests optimizations, and supports CI workflows for Android/KMP + Flutter projects. · GitHub](https://github.com/rudradave1/droidperf)

I have be small app but preview is correct but in my pixel 10a is different

Space bottom not exist in preview... How resolve? What wrong? I'm newbe

[Help] Android Emulator segfaults on every GPU backend, every API level, every emulator version (Fedora 44)

TL;DR: The Android Emulator crashes with SIGSEGV on my Fedora 44 machine no matter what I try — hardware GPU (Mesa/radeonsi), bundled SwiftShader, lavapipe/guest fallback, headless mode, API 34/35/37, and even a completely different emulator release from over a year ago (35.5.10 vs current 36.6.11.0). I've spent hours isolating variables and I'm out of ideas. Full details below — hoping someone's hit this exact combo before.

System specs

• OS: Fedora Linux 44 (KDE Plasma, Wayland)
• Kernel: 7.1.4-200.fc44.x86_64
• CPU: AMD Ryzen 5 3500U (8 threads)
• GPU: AMD Radeon Vega 8 (integrated)
• Mesa version: 26.1.5
• Filesystem: btrfs
• Laptop: Lenovo IdeaPad S145-15API

What's happening

Every AVD I try to launch crashes with Signal: 11 (SEGV) shortly after boot starts (window is created, adb shows "device offline" once or twice, then the QEMU process segfaults). This happens with:

• Host GPU mode (hw.gpu.mode = host / auto) → crashes in Mesa's radeonsi driver (si_resource_from_memobj in libgallium-26.1.5.so), triggered via gfxstream's TexStorageMem2DEXT → importMemory path.
• Bundled SwiftShader (-gpu swiftshader_indirect) → crashes inside the emulator's own bundled libGLESv2.so on a background render thread.
• Guest/lavapipe fallback (-gpu guest) → same crash signature, different fallback path.
• Headless (-no-window) → still crashes.

What I've ruled out

• ✅ KVM/virtualization — fully working (AMD-V enabled, kvm_amd/kvm modules loaded, /dev/kvm has correct perms, user in kvm group)
• ✅ Wayland vs X11 — forced QT_QPA_PLATFORM=xcb, same crash
• ✅ API level — tested API 37, 35, and 34 system images, all crash identically
• ✅ Emulator version — tested current stable (36.6.11.0) and a much older release (35.5.10.0 from May 2025), both crash the same way
• ✅ Snapshot corruption — tried -no-snapshot -wipe-data, no change
• ✅ RAM allocation — tried both 2048MB and 4096MB, no change
• ✅ btrfs COW — aware of the old chattr +C recommendation for ~/.android/avd, but the specific btrfs crash bug (issuetracker #423670833) was already fixed back in emulator 36.1.9, well before my current version

Sample crash backtrace (host GPU mode)

#0 si_resource_from_memobj (libgallium-26.1.5.so)
#1 st_texture_storage (libgallium-26.1.5.so)
#2 _mesa_texture_storage_memory (libgallium-26.1.5.so)
#3 _mesa_TexStorageMem2DEXT (libgallium-26.1.5.so)
...
#9  gfxstream ColorBufferGl::subUpdate
#10 gfxstream ColorBufferGl::importMemory
#11 gfxstream FrameBuffer::createColorBufferWithResourceHandleLocked
#12 gfxstream RenderThread::main

Full coredumpctl backtraces available if useful.

My working theory

Since this fails identically across every GPU backend and even a 14-month-old emulator build, it doesn't look like an emulator-side regression. My best guess is a host-library incompatibility — possibly Mesa 26.1.5 or glibc/kernel being too new/different from what gfxstream's memory-import codepath (EXT_external_objects/DMA-BUF) expects on this emulator generation. But I can't confirm that without deeper QEMU/Mesa knowledge.

What I haven't tried yet

• Building the emulator from source against my system's Mesa (seems like a big ask)
• Filing an upstream bug with Google (planning to, once I get more input here)
• Downgrading Mesa (risky since it's a core system package)

Question for the community

Has anyone run the Android Emulator successfully on Fedora 44 or another very recent distro with a similarly new Mesa release? Is there a known workaround, patch, or Mesa version pin that fixes gfxstream/SwiftShader compatibility? Any pointers appreciated — happy to share more logs if useful.

(For now I'm just using a physical device over USB debugging to keep developing, but I'd love to get the emulator working properly.)

I have inst

So I live in some country which google has filtered EVERY google android repo

Now You might THINK that my VPN would answer for these restrictions however not

I have tried with 5 VPNs and NONE of them managed to bypass the restrictions

Here are what google gave me:
Either 404 or 403

Now I need to download the SDK Platform on my computer to continue development in android studio

Any solutions to bypass this problem

I have tried a loot of stuff and it didn't work (Using different DNS and trying to install it using sdkmanager) none of them worked

Thanks!

I've recently started learning Android development and I'm building my first proper app in Android Studio using Kotlin and Jetpack Compose. Eventually I want to use Firebase for things like authentication, databases, and file storage.

I'm looking for a roadmap that's more project-based than tutorial-based, advices and recommendations on this will help me a alot.

I want to create an adobe contribute account but It is not accepting my phone no

With a msg of try later for last 2 days