Why did android studio change Nexus 6 to sdk gphone x86 arm? - android-studio

Here are the phones
Here is the error message when I hover over the Nexus 6 phone
"Not applicable for main.dart configuration"
Image system is R. API is 30. Flutter doctor says there are no issues.
Running on macOS Catalina. Android Studio 4.0.1.
How do I get it to work?

Flutter in Android Studio doesn't use the regular Android Studio device selector (the one on the right that's grayed out) because you can also select iPhones as target, which Android Studio's selector cannot do. Disregard that device selector for Flutter development, it's not used. The first one alone determines the phone your Flutter app will run on.
sdk_gphone_<architecture> is the device fingerprint of an official Android emulator. Select your phone's fingerprint (it should be either "Nexus 6", or the Nexus 6's code name, which is "shamu") in the left dropdown menu instead to run it on that, or make sure you have no emulators running.

Related

Android Studio shows " (Unavailable)" for Android Virtual Device choice

I think the image is not clear but when I trying to choose Android virtual device they write next to it it's unavailable.
How can I solve this?
This problem shows up in Android Studio setup in SDK component Setut:
It's just a warning, after completing the wizard the Android Emulator will be downloaded and the AVD available.

How to run Android Studio emulator on M1 Mac?

I'm having a devil of a time using the Android Emulator on my new M1 Mac. My Android project compiles fine, and I can run it on a hardware device. But I'm not able to run it on the Emulator.
I followed instructions carefully, and set up an arm64-based emulator running API 31. When I press the "Run" button in Android Studio, the emulator opens and boots normally. However, Android Studio is never able to launch my app on it. I see a message "Waiting for all target devices to come online", and that's it.
I have of course tried restarting the emulator, restarting Android Studio, rebooting my computer, and wiping the data from the emulator. I have also made sure that Developer mode is enabled in the emulated Android environment and "USB Debugging" is turned on.
Another suggestion I saw was to un-check "Enable ADB Integration" in Android Studio. This option doesn't exist in my copy of Android Studio, although I did some further research and found that it is now called "Use libusb backend" instead. It is unchecked by default. I tried checking it anyway, and that didn't help.
I'm at a loss as to what to do next. I really need to be able to test my app in the emulator as my inventory of physical devices is fairly limited.
Thanks,
Frank
Download Android Studio Preview, create emulator (API 30 or S), now you can use emulator on both preview or stable Android Studio.

android studio is not able to recognize my device

I am using Flutter for developing my android apps but for some my android studio is not able to recognize my device even though my device is detecting that fully. Is there a way to fix this?
And also for the record, I have tried all the possible methods available on stack overflow and internet like Enabling USB debugging, MTP Transfer, Installing universal USB Driver.
Some phones like OPPO, VIVO, etc is having an extra drivers. It will be shown when you connect your phone with pc. You have to install that driver too. Also check whether this phone is working with another computer or any other phones works in your computer too(to check both your phone and PC is ok). Also check in normal android app development instead of flutter, like checking your phone connection in android studio with java or kotlin.
if all this didn't works then install Visual Studio Code and check the same thing it it. may be this is some issues in Android studio. please inform the details here after all this.
Go to file> Invalidate cache/Restart > click invalid cache and restart button in android studio.
Then run.
If still cannot connect device:
goto file>settings> appearance & behaviour > Android SDK > sdk tools >deselect android sdk platform tools > apply>ok.
It installed the requested components.
then goto app > edit configuration> uncheck allow parallel run in right corner>ok

flutter: run panel doesn't detect my emulators on mac in android studio

i am new to mac and i wanna test my flutter code on emulators first, i have just downloaded android studio and build my AVD's, however the run panel on the top wont read my emulators, altho i run flutter doctor and it says (one connected device found) and i also can run my code on the emulator via the terminal of android studio when i type flutter run, whats causing this issue of the run then?
The 'run panel' will not list emulators that you have not already executed.
An icon on the upper right side of the main tool bar is AVD manager. Select that icon or go to the tools menu and select AVD maanger. From the AVD manager select the 'run' icon on the right side for the emulator your wish. Once execution begins, the emulator will show in your 'run panel'. It may have a name that looks odd but it is there.
Also note that while the Android Studio 'run panel' will list iOS simulators by the device name (eg. iPnone SE2), it will list Android emulators with odd names with no relation to the device name in AVD.
i downloaded Xcode and set up a simulator. that made both the emulator and simulator work.

Android Studio selects wrong target device: always runs app on first selected one

How can I debug other than the first device in Android Studio?
I have two Genymotion devices Nexus 5 and Nexus 6, I can run both successfully but when I try to run/debug app from android studio no matter what device I choose it always runs first selected device.
Initially I thought it is genymotion issue but, it was not the case because same happens if I connect real device. Even though device appears in device chooser dialog but it looks like android studio internally doesn't see it.
Stopping debugging for current device before selecting new device helped me. (Red square)
Here is the solution
First: Go to run configuration in android studio
Then: Select the emulator you want
Finally: Run it
It's a bug in Android Studio, supossedly fixed in 1.5.1 but I have 1.5.1 and the bug is still present. Suggested workaround from Google dev is to "close the debug tab once it is done":
https://code.google.com/p/android/issues/detail?id=195167

Resources