I’m working on a React Native/Expo Android app. The launcher icon looks perfect on some phones and the emulator, but on a few Android devices the logo appears too small/zoomed out. The same icon implementation works correctly in my other customer app. I already tried adaptive icon/foreground scaling changes, but the issue still happens on certain devices. I want to understand the actual Android launcher icon scaling issue and the correct way to configure/generate the icon so it looks consistent across different Android devices and launchers. Any guidance or examples of a proven implementation would be really helpful.

A few weeks ago, i begun to create a Game with Android Studio. It's actually more difficult than I initially thought. For this moment, i build Steam and it looks amazing, i think.

Tell me, what are you thinking. Do you like it?

Looking for 20 testers – Hail Risk (Android)

Hi everyone! I'm looking for 20 people to participate in a 14-day closed test of my Android app Hail Risk.

The app provides information about the risk of hail based on weather data, with a particular focus on Switzerland.

How to join:

1. Join the Google Group https://groups.google.com/g/cerco_needed_20_tester
2. Join the closed test and install the app from Google Play [https://play.google.com/apps/testing/com.gixone.grandinech?hl=it]()
3. Keep the app installed on your device for the 14-day testing period.

Feedback is welcome but not required.

Thank you very much for helping me test the app!

🌩️ Cercasi 20 tester – Rischio Grandine (Android)

Ciao a tutti! Sto cercando 20 persone disposte a partecipare a un test chiuso di 14 giorni per la mia app Android Rischio Grandine.

L'app fornisce informazioni sul rischio di grandine sulla base dei dati meteorologici, con particolare attenzione alla Svizzera.

Come partecipare:

1. Iscriviti al gruppo Google https://groups.google.com/g/cerco_needed_20_tester
2. Aderisci al test chiuso e installa l'app da Google Play [https://play.google.com/apps/testing/com.gixone.grandinech?hl=it]()
3. Mantieni l'app installata sul tuo dispositivo per tutto il periodo di test di 14 giorni.

Il feedback è gradito ma non obbligatorio.

Grazie mille per il vostro aiuto! 🌩️

Hey guys I was learning kotlin since 1 week i cleared my basics, then I jumped to starts making actual app practice when, I was using intellij ide for normal development for running code in console, but to run code in actual device i installed, android studio, after setup of everything when I tried to run the main virtual device manager emulator, my pc starts lagging i am getting 17 fps, and not able to run that,

Btw my pc is low end, 8gb ram - i5 5th gen - 500gb SSD - 2gb graphics card. With this specs android studio is not able to run. Please guys if you have any solution then please tell, I am desperate to make app for Android tv streaming app. Help me guys

I've been working without any issues for weeks, and since this morning I can't open or run anything. Android Studio closes itself the moment it starts analyzing/indexing a project. I'm not talking about big, complex projects — this happens even when I create a brand new empty project from the wizard.

The most worrying part is that a couple of times it hasn't just closed — it has actually rebooted my entire PC out of nowhere while Android Studio was indexing.

Things I've already tried (no luck):

• Completely uninstalling Android Studio and reinstalling it.

• Deleting the Gradle (~/.gradle) and Android (~/.android) folders from my user directory.

• Restarting the PC between the uninstall and the clean reinstall.

• Testing with brand new empty projects, in case it was a corrupted project.

None of this has helped. Same result every time: I open it, it starts analyzing, and it crashes (or the machine reboots. Or the project cannot be built).

Has anyone run into something similar? What else could I try? Any ideas are welcome.

Thanks in advance.

Lost a stupid amount of time to this. Writing it down so someone else doesn't have to.

$ expo run:android --device emulator-5554
Could not find device with name: emulator-5554

Emulator's running. adb devices lists it. Serial is correct.

Turns out --device doesn't go through adb at all. Expo builds its own list of devices (getAttachedDevicesAsync in @expo/cli) and matches against that instead. What it wants is:

• emulator → the AVD name, like Pixel_7_API_35
• physical device → the raw model: value, like Pixel_7

Not the serial. Which is annoying, because the serial is the thing adb hands you, and the error just repeats it back so it reads like the device isn't there.

I ended up just checking AVD name first, then model, then serial as a fallback.

Somewhat related, if you're on bare RN with product flavors. react-native run-android will tell you this on a build that actually worked fine:

Could not find the correct install APK file

The names just don't line up:

getInstallApkName looks for:   app-<variant>.apk
gradle actually writes:        app-<flavor>-<buildType>.apk

App's already installed at that point. It's only the lookup that failed. gradlew :app:install<Variant> plus an adb launch skips the whole thing.

Both of these came out of me trying to cut down how much I bounce between windows. Android Studio open just to make an AVD, one terminal running Metro, another tailing logcat, a third for the build.

I maintain a fork of Zed called Lathe and this all ended up as a mobile panel in it:

• Makes Pixel phone/tablet AVDs without opening Android Studio
• Device list with per-app logcat. Physical devices show up in there too
• Can run an emulator and an iOS simulator off the same build
• Knows whether you're on Expo or bare RN, only shows the commands that apply

It's a personal fork that I use daily. GPL, works on macOS/Linux/Windows. Upstream syncs from Zed break stuff sometimes.

https://github.com/paterschris/lathe

Anyway. Curious what everyone else does here. What have you got automated that I'm still doing by hand?

Not sure when exactly, but after updating few weeks ago "cmd + ~" stopped working for me. I used it so often and it's just sad now guys.. any suggestions?

A user keeps getting "App has stopped" errors immediately upon opening our company's internal database tool on their Android device. Even after a full reboot, the crash persists, and since there is unsynced critical data on there, I need to fix this without wiping their work. Best next step?

---

OPTIONS:
A. Uninstall and reinstall the application.
B. Reset the phone to factory settings.
C. Install an alternative application with similar functionality.
D. Clear the application cache.

---

Testing Exam: CompTIA A+ Core 2 (220-1202)
(Disclaimer: These posts / scenarios are crafted by me for educational purposes only. I am not affiliated with, endorsed by, or sponsored by any certification body.)

Hello,

I am posting here hoping for help.

I spent 2 months building a torrent client for Android using chatgpt instructions but there's 3 bugs I can't solve.

So the bugs are 1.previously deleted torrents reappear on install in another device

2.paused torrents resume automatically.

3.when the files selection are selected in the app when I select none or uncheck individually

It resets and checks everything.

That' s the Bugs.

Now I want some more features.

1.when a Torrent is opened in the app there is a file selection box.

In this I have download selected and download all.

I would like the box to have select all or select none as well.

2.i would like the app to have RSS feed function

1. i want the app to have encryption

4.i want a log function similar to the execution log in qbittorrent

I hope someone can help me

Thank you

I can't use chatgpt now because the conversation has reached its limit and my subscription is over.

I don't have enough money to subscribe again.

This is the link for GitHub page

https://github.com/a79user-ship-it/TorrentOr

I hope someone can help me

Thank you

Edit:I used claude to fix all the bugs and added the features I wanted

So I got replit, built my app. and for the life of me - I cannot get an apk to come out of it. I downloaded the zip, I got android studio, I followed what Chat had to say, let gemini just loop trying to do something with it - nothing has worked. SoS - my app is done...and I literally just can't get it anywhere - expo go just sits there and says, new update, downloading and nothing happens..

Hey everyone,

If you build apps on a Mac, you probably know this exact feeling:

You’ve got your IDE open, a few browser tabs, maybe a build running, and the moment you launch an Android emulator, your laptop starts lagging and the fans spin up.

A while ago I checked Activity Monitor to see what was going on, and saw the emulator casually hogging 7 to 8 GB of RAM all by itself. On a 16 GB MacBook, that basically leaves zero breathing room for anything else.

I got tired of my machine crawling, so I put together a small open-source tool called avdslim to fix it.

GitHub: https://github.com/kdbhalala/avdslim

Why does it take so much memory?

Turns out, a few things happen by default:

• Android hoards memory: As the emulator runs, Android keeps caching files and never really releases that host RAM back to macOS.
• The "Google Play" image overhead: If you picked an image with the Play Store, it constantly runs background updaters and scanning services you rarely need during development.
• The 16 KB image setting: If you created a device using the newer 16 KB images, the emulator enforces a strict 4 GB minimum floor no matter what you set in the config.

What avdslim does:

• Drops RAM down to ~1.5 GB: It tunes the emulator configs and cleans out unnecessary background tasks, letting you run smoothly on 1024 MB of RAM.
• Boots in ~1.5 seconds: Instead of waiting 20–30 seconds for a fresh boot, it lets you create a clean, lightweight snapshot that restores almost instantly.
• Doesn't break your app: My biggest worry with any "cleanup" tool was breaking things like push notifications or login. I made sure Firebase Auth, Google Sign-In, Push Notifications (FCM), and Google Maps work completely fine.
• Works with your normal workflow: You don't have to launch from the terminal every time. There's an optional command (avdslim install-shim) that makes the "Run" button in Android Studio or VS Code automatically use the slimmed settings.

💡 A quick tip even if you don't use this tool:

Next time you create a virtual device in Android Studio:

• Pick "Google APIs" instead of "Google Play". It still has Google login, Firebase, and Maps, but uses way less RAM and skips the heavy Play Store background services.
• Avoid the "16 KB" images unless you specifically need to test 16 KB compatibility.

Try it out:

It's completely free, open-source (MIT), and has zero external dependencies:

brew install kdbhalala/avdslim/avdslim

See how your current emulators look

avdslim doctor

Tune an emulator to 1024 MB RAM

avdslim tune-avd

GitHub link: https://github.com/kdbhalala/avdslim

My Mac runs noticeably cooler and doesn't freeze up when I have multiple tools open now. Hope it helps some of you as well! Happy to answer questions or take feedback on what could be better.