Reputation: 746
I'm trying to install android sdk and run my first application on my PC (Win7 64 bit). I followed instructions on http://developer.android.com from the beginning to http://developer.android.com/training/basics/firstapp/running-app.html When I try to start emulator (as mentioned on the last url) simply nothing shows up.
5 - Select the new AVD from the Android Virtual Device Manager and click Start.
It doesn't show any error messages. After launching AVD a process named adb.exe appears on task manager.
Below is eclipse console output when try to run my blank app from eclipse. On configurations, I set different target devices and selected starting activity manually. The same problem continues.
When AVD is started from outside of eclipse(\sdk\platform-tools>android avd
):
[2013-03-22 08:50:48 - 1st] ------------------------------
[2013-03-22 08:50:48 - 1st] Android Launch!
[2013-03-22 08:50:48 - 1st] adb is running normally.
[2013-03-22 08:50:48 - 1st] Performing com.example.st.MainActivity activity launch
[2013-03-22 08:50:49 - 1st] Automatic Target Mode: launching new emulator with compatible AVD 'AvdTest'
[2013-03-22 08:50:49 - 1st] Launching a new emulator with Virtual Device 'AvdTest'
When AVD is started from eclipse:
[2013-03-22 09:22:44 - 1st] ------------------------------
[2013-03-22 09:22:44 - 1st] Android Launch!
[2013-03-22 09:22:44 - 1st] adb is running normally.
[2013-03-22 09:22:44 - 1st] Performing com.example.st.MainActivity activity launch
[2013-03-22 09:22:44 - 1st] Automatic Target Mode: Preferred AVD 'AvdTest' is not available. Launching new emulator.
[2013-03-22 09:22:44 - 1st] Launching a new emulator with Virtual Device 'AvdTest'
I also downloaded only sdk and installed eclipse plugin but result is the same.
Tried to use logcat also. Started it then started AVD, but logcat shows nothing. When I kill adb.exe from task manager,it kills logcat too.
\sdk\platform-tools>adb -e logcat
- waiting for device -
\sdk\platform-tools>
After reinstalling IDE/SDK a couple of times I decided to ask it here. What else I can do?
Edit : Folks, I have a virtual device. Please stop suggesting adding a virtual device.
Upvotes: 34
Views: 70513
Reputation: 133
I came here beacuse i have same problem, with Android Studio 3.6 and win 10 OS
I fixed that with this steps:
Virtual device configuration
(pencil icon)show advance setting
Cold boot
finish
If problem remain same,
drop down
near pencil
iconWipe data
refresh button
at the right bottom near question mark buttonUpvotes: 3
Reputation: 2299
I run into this issue at least once every time I try to start a new project, maybe from projects sharing devices. In the following folder:
C:\Users\.android\avd\ (e.g. Nexus_5_API_23.avd)
I had to delete the following files pictured. I tried deleting the .qcow2
files as one user mentioned without luck. Notice all the files deleted are the newest modified files/folders (see the Date Modified column) that are not .ini
or .conf
files.
UPDATE: It seems if I delete just the snapshots
directory (pictured above), that does the trick too.
Upvotes: 3
Reputation: 704
In my case I had to delete the file cache.img.qcow2 from my avd device folder (C:\Users\User_Name.android\avd\Device_Name.avd).
Upvotes: 5
Reputation: 6859
I had the similar problem on OSX. My emulator works fine, but after some runs it won't start. I've solved that by :
.android
directory (in my case it was Users/<username>/.android
avd
folder.img
files from there. Do not remove .ini
files.Upvotes: 75
Reputation: 746
I found it. In event viewer(Control Panel\All Control Panel Items\Administrative Tools\Event Viewer) clicked on Windows Log>Application on left menu and read error logs.
I googled dll file mentioned in log (aticfx32.dll
) and found the dll file belongs to ATI graphic cards. My PC has an Intel graphic card. While searching for solution I also found this web page and applied solution they used. It works like a charm.
Steps:
Upvotes: 9
Reputation: 328
Have you installed any "Target" API?. Have you configured any "Virtual Device"?
The Log tells you that it can't find 'avdTest' device, it could be because you didn't configure it, or just, it's not present.
Try to setup a device at the Eclipse's "Virtual Device Manager", then, start the virtual device from this menu ( AVD devices -> Start... ) and if it works, then run your code on it.
I don't recommend you using command line for the first time. Also I recommend you trying with Android 2.3.3 (API 10) for first, because it takes less time time to start the emulator.
Upvotes: -1