I'm new with Android studio (2.0) and android app. I downloaded android studio 2.0 two days ago and started my first application "Hello world".
When I start the application on my tablet, the application work fine and evrything seems valid.
When I start the emulator nothing happend and I don't have error messages. The emulator start but no popup windows appear. I try to understand why but without error messages it's not easy (and I'm a starter :-( )
My pc is Intel R Core CPU 3.00Ghz with 8Gb ram. Windows 7 (system type 64 bit)
I use Android studio 2.0.
The option Tools- Android - enable android ADB integration is check.
The application compile.
When I start the application with the emulator, I have this message:
c:...\AppData\Local\Android\Sdk\tools\emulator.exe -netdelay none
-netspeed full -avd TAB.
After a short time, I have the message
Waiting for target device to come online
(I cann see a process when I start the task manager" but nothing appear and I expect a popup windows to test my app.
This is the info from the sdk manager:
Can you help me ?
(sorry for my english, I'm Belgian)
Related
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.
I'm a new Android Studio user, but I've already done something in the last few days.
I have only a problem with the emulator. I tried to run my code with a normal Virtual Device, but every time I always got the same error:
Emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration!
Emulator: Process finished with exit code 1
I tried to find a solution in the internet, and I found that the problem was my computer (it is an AMD) and I had to download the "armeabi" version when I created a new virtual device.
It worked (I have no more errors), but my emulator is always black and I cannot see anything. I was forced to use Debug USB on my personal phone, to plug in and use it (and it works) but I'd like to solve the problem with the Android Studio emulator. My Android Studio version is 3.3.1, the latest.
Obviously when I have a preview clicking on the file "activity_main.xml" I can see the right output.
Normally I use Nexus 5 and I've tried with Marshmallow and Nougat.
Increase your VM Heap & try it again.
Tools -> Android -> AVD Manager.
Select a virtual device and click on its pencil icon (edit)
Click on Show Advanced Settings.
Under "Memory and Storage" change "VM Heap"
If above is not helpful, Please Check "Wipe user data" in the Launch Option
Go to Android Virtual Device Manager->Select your device->Start->Check "Wipe user data"->Launch
make sure that Intel x86 Emulator Accelerator is active
I am trying to run my app on canary build of the android emulator from android studio on AMD processor but I am getting the following error
1:47 PM Emulator: [2440]:INFO:android/android-emu/android/verified-
boot/load_config.cpp:236:Verified boot params were not found.
1:47 PM Emulator: **
1:47 PM Emulator: ERROR:/usr/local/google/buildbot/src/android/emu-master-
dev/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be
reached
1:47 PM Emulator: Process finished with exit code 3
I got to know about the canary build of the android emulator for AMD processor from here. My virtual device' CPU/ABI is armeabi-v7a. I searched for what the 'exit code 3' for the emulator mean but I didn't get any solution.
Can someone help me please!
I got the android emulator working today.
I have done the instalation process for canary build of android studio from the beginning:
1. Enabled "Hyper-V" and "Windows Hypervisor Platform" in "Turn Windows features on or off" settings of Windows. This has been explained in here.
2. Downloaded the latest Canary build of Android studio from here.
3. After downloading the zip file I followed the guidelines in here under "Install alongside your stable version" heading. The guide lines are:
a. Unpack the ZIP file.
b. Rename the resulting folder to something unique like "Android Studio Preview."
c. Move it to a permanent location, such as next to your existing Android Studio install in C:\Program Files\Android.
d. Inside C:\Program Files\Android\Android Studio Preview\bin\, launch studio64.exe (or if you're on a 32-bit machine, launch studio.exe).
4. After launching studio64.exe I got a pop-up message to update Android emulator. After the update I created a new virtual device with an image of x86 with android 9.0. I started the android emulator to test my app. Though I got the
Verified boot params were not found
popup error message initially, the emulator started functioning well.
I am a very new Android developer and was until today having the same issue as yourself. Here is how I got it to work (Please note I am also on an AMD system).
Make sure you have enabled Hyper-V and Windows Hypervisor Platform. If you type "turn windows features on" in your run bar you should be able to locate it. Also enable virtualisation in the Bios. Mine comes under "SVD".
(Please note after this step I was still experiencing the problem but this is a pre-requisite).
Delete all devices from the AVD manager.
Install a new x86 device from the AVD manager. What I did here was select a version down from the one I was previously getting issues on so Oreo from Pie. When it asks to confirm if you want to wipe the user data please confirm positive.
Once setup, run the device from the AVD manager. It may ask you if you wish to enable Instant Run. I elected to disable this. (I had enabled it when I first was trying to run a device).
You will still receive the 1st error regarding no boot parameters but the emulated environment should load. You can now run the APP and it should install the APK. Previously due to the device not coming online properly, the APK would not install. I can also now setup a device on Pie without experiencing the issue so I think it may have been the wiping of the previous data that helped.
I wish I could tell you WHY this worked for certain and previously it would not work, sadly I cannot but hopefully this will get you working.
Android Studio 2.3.2
Emulator 4.3
In prompt show list devices:
adb devices
List of devices attached
emulator-5554 device
But when I try to run app from Android Studio I get black screen on emulator (Android 4.3) and nothing happened. Here screen:
On another emulator (e.g. 7.1) I success deploy and run app.
Here my sdk settings:
I suggest using other emulators like Genymotion or Memu, or on an actual device[best], for running apps built on AndroidStudio if you are working in Windows. The default emulator is very very slow in my experience, you need a PC with some real high specification.
Well you do have the APIS and other things necessary, so I think your emulator is just too slow to load, or not compatible with your PC , so its not loading.
The IDE does not let me open more than 2 AVD simultaneously. After 2 are already running and attempting to start 3rd AVD - Android Studio displays the message "Starting AVD", but when loading ends nothing happens. No logs, no errors.
If, for example, you choose to close one of already running AVD, and start another - it starts properly, i.e. all AVDs behave well individually.
If matters, I use:
Nexus 6 API 23 (Android 6.0 Google APIs), x86;
Nexus S API 22 (Android 5.1 Google APIs), x86;
Pixel API 25 (Android 7.1.1 Google APIs), x86;
Android Studio 2.3.1
Have same problem today and found it related to RAM usage limit for HAXM
Found answer at here
Why launching more than 2 AVDs works only under specific conditions
Reinstall HAXM and set more ram to fit your need
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager