I installed android studio 1.5.1. Running windows 10 on an AMD, so no hardware acceleration on the emulation. Googling it, I find I can use ARM instead of x86 emulation. But whenever I try to add a device using it, the Actions column shows "repair device". If I click View Details, nothing happens. There is an image showing that there's some kind of error (yield sign with !) but I can't seem to do anything with it to see the error. Double clicking on it just opens it in edit mode but gives me no information about what's wrong.
Any ideas?
This happened to me in 2022! I solved it by clicking the edit button on the emulator device and changing the emulated hardware(phone) to something else. It refreshed and the error sign left.
Do close the running emulator before doing this though. If the error persists, you may want to remove the particular AVD and get a different one.
Related
I am developing an Android app in Android Studio. When I try to run it on an AVD, the AVD screen shows nothing.
The device frame is visible, but there is nothing inside it. The message "waiting for target device to come online" doesn't show up either.
Furthermore, I am unable to edit the graphics in the AVD settings. I have tried running the program both normally and from the AVD manager, but it doesn't work either way.
Other solutions which I have tried (and failed) are removing C:\Windows\System32\Wbem from the PATH environment variable, ending the ADB process in Task Manager, and wiping data from the AVD in AVD manager. Oh, and I even uninstalled and reinstalled Android Studio but it still doesn't work, even for a basic Hello World program. Any help would be greatly appreciated.
https://imgur.com/a/rzMmz3E
I faced this problem due to my ram several times and even after upgrading I had to make several changes. The best solution is to set up a new avd. use Nexus S, and a light image. Start with API 16 and when it works go ahead and create your desired AVD. Keep your eye on the pop up errors AVD shows like HAXM
It may seem silly but have you checked if the emulator is not locked?
Ok, when Emulator is not displaying anything and saying like, waiting for online,
after click on power button then what you have to do is Go to,
AVD Manager then in Actions section click on bottom triangle button and click on "Cold Boot Now" to make working your Emulator.
The genymotion emulator starts from AndroidStudio. It shows its white screen but never goes beyond that. It never comes to the home screen. Tried running the app. does not work. I have tried API 18 emulator. does not work. I have tried changing sdk path, setting android_home. does not work??
Did you checked logs for errors or possible explanation? Do you have both VirtualBox and Genymotion configured properly? It is hard to answer your question more accurately cause you did provide little information.
Going into my BIOS and enabling Intel Virtualization Technology under the CPU Options, and then going into GenyMotion and changing the device's # of virtual processors fix this issue for me.
Some time ago i also faced the same problem ... you can try above all suggestion but what worked for me is :-
Downloading Oracle VM VirtualBox
Here is the link , DOWNLOAD and install it.
http://www.oracle.com/us/technologies/virtualization/virtualbox/overview/index.html
I often have the same problem. If I delete the virtual device and then reinstall it, it usually fixes the problem for me.
To delete it, open the genymotion desktop application
Delete the device that's giving you the white screen - select the device and then click on the trash can icon
After it's deleted, reinstall the device - press add, search for the device, select it and press next twice
The device will be installed again, and it may start properly this time around.
I use android studio 0.4.2 and logcat does not work (its just empty). USB debugging is enabled, filters are disabled and log level is verbose. Any ideas?
In logcat, try going to the bottom right corner where there is a ">>" and select that. It restarts it.
Click on the "Debug App" Icon next to the "Run App" Icon or press SHIFT + F9. That seems to do the trick for me.
Try going to developer settings on the phone, and scrolling to the "Monitoring" then "Enable OpenGL Traces" and select LogCat.
I tried everything. I unintentionally found that empty tags never show. If you are using empty tags, like me, try filling with some letter (blank spaces didn't work for me).
On your android monitor:
Restart your LogCat.
Set no filters because Android studio 2.2 has Firebase.
Clear your searching filter.
Select your running device.
If not work clear Android studio caches. File->invalidate caches/restart
When apply all way but still not working then use Android device monitor. Tools -> Android -> Android device monitor.
In my case, restarting Android Studio works for me.
Go to "Window -> Preferences"
From the left panel, expand "Android" and select "Logcat". Check if "Show logcat view if message priority is atleast:" is equal to "VERBOSE". If needed, select "VERBOSE" and apply.
Now you can see your device events in LogCat.
In my case, it usually takes 20 or more seconds for my logcat to display anything. After it does, I see "debugger waiting to settle" messages. This happens every single time.
Try waiting a while to see if it ends up showing up.
Old question, but the issue seems to occur frequently while running Android Studio 1.1.0. This often happens after I clear all existing log.
When it does, I tap the restart icon (green curved arrow on top of a grey square) and it start working again.
I had the same problem and solved it in the device developer options by disabling and enabling Usb debugging.
To add to this thread of solutions,
Check for if you have multiple devices connected. Than select the device that you want logs from (upper left corner on logcat window). Sometimes, different device is selected rather than one you are debugging your app on. Hope this helps.
In my case, I had two Android phones plugged in for debugging. Switching phones, using the drop down box, didn't do a thing, so I:
-unplugged both
-restarted Android Studio (and the project)
-plugged in the (one) device for which I wanted to see the logs
That did it for me. Logs were back ... now just to fix the code.
In case you make it down here, #Maarten's comment above worked for me. Close Android Studio then adb devices at Ubuntu terminal:
ewan#xxxx:~/AndroidStudioProjects/projectx$ adb devices
List of devices attached
adb server version (41) doesn't match this client (39); killing...
* daemon started successfully
FA7Bxxxxxx2 device
Restarted Android Studio and logcat window worked again.
UPDATE: d'oh I found that I was inadvertently using version 39 from the terminal window whereas Android Studio was using 41
I can't work emulator in eclipse in ubuntu.I clicked window->avd manager and I selected my_device than clicked start button. But emulator is not working.
How can I do for run it?
You need to be patient. Depending on the AVD you select, API level and the hardware you are running it on, it can take a LONG time to start. If you are seeing no window appear at all, then that is a different matter. What errors do you see in the console?
first remove your devices such as 'my_device' and then remove the folder with name '.android' in your home folder.
Then again make your own devices such as 'my_device' and try again for running the emulator.
This may solve your problem.
I'm a newbie that needs some help on getting the AVD running with my app. I've been developing C code for decades, but I have to admit the Eclipse/AVD setup has me stumped! I'm following the 'HelloWorld' tutorials on the developer.android website (and some others) and everything seems to be working OK, up to the point where I try to run it on the AVD simulator. I'm not getting any warnings, the Eclipse build/run output window says that everything is installed OK and the AVD does startup and run. Eclipse says that my app is loading, but it never runs. All I get is the simulator window with "ANDROID" on the screen and the buttons on the right-hand side.
I've got Eclipse Indigo and r18 of the Android PlugIn (I tried to install Helios, but the Eclipse website directed me to Indigo!). Is Indigo OK for running the simulator, or do I specifically need Helios? I also have Java 1.7.
The API level I have installed is Level 15 (v4.xxx of Android, I think). Don't know if I need a lower version to get my tutorial app to run, but level 15 is the only one I can select when setting up a device in the AVD manager.
I've been trying to get this going for days, trying all sorts of switches and buttons, but to no avail. Before I start uninstalling everything and reinstalling, can anyone advise if there is anything I might be missing, or has tripped over this problem themselves and found a way around it? Something that always trips up new starters maybe? Or do I need to go back to scratch?
Any help would be much appreciated.
How long are you leaving your emulator running after you attempt to launch your application? The Android OS can take a long time to boot up in the emulator. If it's stuck on the "ANDROID" screen then you're either not waiting long enough or there's something wrong with your emulator. It should eventually boot into the normal Android lock screen or home screen just like a device.
You can launch your emulator ahead of attempting to run your app by opening the Android Virtual Device Manager (toolbar icon in Eclipse, if installed properly) and then selecting an emulator and clicking the "Start" button. If you don't have any emulators listed, then you need to create one by clicking the "New..." button.