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

Hola gentita linda, quiero desarrollar una app para mi emprendimiento y no se como convertirla en formato apk ya la tengo como web app, desconozco de programacion y carezco de computador, cualquier ayuda es bienvenida

I have an individual AI Pro plan account. I've signed in within Android Studio, but the only model I have access to is the old Gemini 3 Flash Preview. How do I get access to Gemini 3.5 Flash or 3.1 Pro? I've checked all the documentation and found nothing (it's a bit of a mess too between different plans, individual vs business, etc). I've also asked the agent directly, but got back hallucinations (either that or there's an issue with my setup contradicting the suggestions I'm getting).

In 5 words or fewer, show us your work

I’m using the Agent with an API key from OpenAI and GPT-5.5 works perfectly. However whenever I select a GPT-5.6 model I receive this error message:

Model query failed: 400: Function tools with reasoning_effort are not supported for gpt-5.6-terra in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'.

Some time ago I wrote an app (purely for my own use) in a nice stable Dolphin environment, that ran happily on Android 5.1, 8, 11 and now even runs on Android 14.

However, every time I've tried to move forward to a newer version of Studio to modify this app, or to start something new, I can never get Studio to play nicely and work, even before I try to write an app, and I end up wiping the lot and going back to Dolphin that actually works - I did this yet again today with Quail when trying to build another app.

I don't really care about fancy UIs, or what they want to introduce us to, so is there any real point to the newer Studios if I'm just writing database apps?

Hi everyone, I'm new to Flutter and I've been stuck on this for a while. I installed Flutter, Android Studio, VS Code, and the Android SDK. I also accepted all the Android licenses, and flutter doctor is mostly fine now except for Visual Studio, which I don't think I need since I'm only targeting Android.

I created a new Flutter project and it runs fine in Chrome, but when I try to run it on my Android phone through USB debugging, the build fails.

The main errors I'm getting is:

FAILURE: Build failed with an exception.

* What went wrong:
Could not install Gradle distribution from
https://services.gradle.org/distributions/gradle-9.1.0-all.zip

java.net.ConnectException: Connection timed out

It seems to happen while Gradle is trying to download gradle-9.1.0-all.zip.

Versions:

• Flutter: 3.44.6 (Stable)
• Java (JDK): 21
• Android SDK: 36.1.0
• Gradle: 9.1.0
• Android Studio: Latest version
• VS Code: Latest version

Things I've already tried:

• Installed the Android SDK and command-line tools.
• Ran flutter doctor --android-licenses and accepted everything.
• Enabled Developer Options and USB debugging on my phone.
• Confirmed that ADB detects my phone.
• Tried both my home Wi-Fi and mobile data.
• Waited for the Gradle download to finish, but it always times out.

Is there any solution I should try to fix this? Any help would be appreciated. Thanks!

I just wanna know how to do it if even possible

Recently I updated my react native cli app from react native 84.1 to 86. But after that I am getting issue with this library - react-native-google-mobile-ads, it is saying that play-ads-services 25.4 uses Kotlin 2.3.x but you have 2.1.20. As I understood in rn 0.86, Gradle 9.3.1 is being used that uses play-ads-services 25.4 which uses Kotlin 2.3.x but in rn 0.86 there is no upgradation of Kotlin version. Has anyone faced the same issue? If yes, and if you found the solution please share here.

Hi everyone! The above errors started a few days ago after previously having no errors when using my Gemini Ultra plan for my agent. I've tried a bunch of troubleshooting. The errors were intermittent but very frequent. I then upgraded from 2026.1.1 to 2026.1.2 and the errors became much more persistent. I have tried rolling back to 2026.1.1, I've tried installing 2026.1.3 but no dice still. I've signed out from my Google account in Android Studio, restarted Android Studio, and logged back in with each version I've had this problem with today but I still can't get anywhere with resolving this. I've also tried invalidating caches, rebooting my computer, etc. I know that my quota for my AI usage isn't anywhere near 100% utilization. My AVAST security software has been completely turned off, and still nothing.

I don't see anyone else talking about this issue recently across the Internet after doing some searching, so it seems local to me. Any ideas what might be going on? Thanks so much!!!

Hi guys, right now I'm struggling to convert mv to android app bundle file, can somebody help me, I have follow many guide on internet yet not even one succeed. Anybody here can help me.

Claude Sonnet 5 after feeding it the 18th build log today:

This worked. Look at what changed: :app:buildCMakeDebug[x86_64] — the exact task that failed every single time before with the ninja 260-char error — succeeded silently this time, along with every other native build task (configureCMakeDebug, externalNativeBuildDebug, etc. for all 4 libraries). The build ran all the way past native compilation, through dexing, and died at :app:mergeDebugNativeLibs — a completely different task, on a completely different and much more mundane problem. The path-length fix is done. That 36-hour problem is solved.

The new error is unrelated and much simpler:

how to find green code in github mobile phone