This is the message I receive always (100%) if I try to start the emulator with an existing snapshot. The system is Windows 7 32bit, ADT14 and SDK14.
I need to start every emulator session with "wiped user data". Whenever I try to reload the emulator with a snapshot Windows prints this message (in German: emulator-arm.exe funktioniert nicht mehr) and the only option available is to close the application (emulator-arm.exe).
I can reproduce that at will. Even with fresh installs of Eclipse (Helios and Indigo), SDK, ADT. I could see that with all versions in the last year. I can reproduce that on three different machines in my house (all Windows 7 32bit) at will. There's not much software on my machines. On one machine is the Android Development environment only. All three computers are no gaming machines and don't have much power. I mean, just to use the Eclipse editor, it must be enough.
All applications (Eclipse, etc.) are not configured to special needs. I always use the Android development as is out of the box.
Any help is highly appreciated. It's not funny to always go for lunch or coffee just to switch from one emulator to the next one - lasts for approx. 10 minutes here.
Personally I suggest not to use Snapshot features. Just having a normal reboot is totally fine, it doesn't take much time, just one or two minutes.
The Snapshot thing really troubled me in the past, and resulted in a newly-fresh installation of SDK. Don't know why it is exactly but it is better not to use Snapshot, first, it doesn't speed up your emulator speed; second, it is a emulator stuff, not on a real device.
Correct me if I'm wrong or mistaken something!
Launch your AVD Device via the AVD Manager, ensure not to wipe user data or use launch from snapshot.
If your application is not deployed to AVD Device:
Right click your eclipse project select run as => run configuration. Ensure under the target tab deployment mode is set to manual. Click Run, from here you can select the current running AVD you started earlier.
To redeploy your application to AVD Device
Leave the AVD Device up and running, use the Application Manager on the AVD Device to uninstall the app from the AVD Device. Next, right click your eclipse project select run as => run configuration. Ensure under the target tab deployment mode is set to manual. Click Run, from here you can select the current running AVD you started earlier.
Related
First post, and new developer.
I installed on my Mac (10.6.8) the complete package from Google and proceeded to open the SDK Manager and downloading everything. I then installed the IntelHAXM_1.0.8.dmg and rebooted. I created a couple of virtual devices (VD) in the AVDM and attempted to start them. They are not set to use GPU acceleration and have the skin to the first option (Skin with dynamic hardware controls).
When I click 'Start', the progress bar in that windows shows me its starting. Upon reaching the end, the window with the progress simply disappear, and I'm back at the list of my Virtual Devices. I thought, maybe its an update I did. So I deleted and started from scratch with no SDK updates. Same results. Tried Different devices, with or without GPU.
The virtual android never shows up.
I also installed the Android Studio and the same thing happened. On the virtual Windows 7 I have setup on that Mac, the virtual devices load up fast. But on the mac itself, they never appear?
Why?
I think it does not matter to be on mac or windows, it is related with android emulator configurations.
emulator takes a while, from 30 sec till few Minutes, so be patient.
if it did not work, try to use configurations like one of these to start up.
or
When I connect an external device through USB it does not appear in the ADVM
I was previously using Eclipse on a 32bit Win 7 build and had no problems, when a device was connected it appeared in the ADVM.
I have since clean installed the machine with 64bit Win 8 and installed Eclipse and the SDKs from scratch.
When I connect a device LogCat records a load of information about the device and what it is doing. but when I open ADVM the device is not present so I can't use it as the run target.
Any ideas?
(I am a dabbler writing silly apps for my kids devices not a fully fledged coder)
What is happening to me is that the name of the device is not being shown, but it will still be the first device when it asks me to choose. Try clicking on the first list item in the "running devices" when you have to pick which one to launch from. If you can pick it (it'll be a blank item), and Run, it should/might work.Try it out, it's exactly what's happening to me. I suspect this could be it just because your LogCat seems to be working.
i m starting (or at least trying to) developing android application(s) and I m using eclipse for it along the android sdk.
Now I m wondering if there's a faster way to "test" and tryout something newly writen in the code than starting it in the emulator?
I'm wondering because I m running on 8gb ram and q9550 (quadcore) and it takes some time (let's say 20secs) to upload and start the apk and now
I'm wondering if this really is the only way to test since it requires huge amount of time, especially when I'm trying something new which doesn't work and thus I'm always gotta run it like this let's say like 20 times until I figure out what's wrong with my code...
You can connect your android phone using USB debugging mode and debug your code. If you can't do that, you can export an apk file (which is quick) and use dropbox/gmail to send it to your phone. I am not a big fan of emulator :)
Here's how to enable usb debugging
http://www.groovypost.com/howto/mobile/how-to-enable-usb-debugging-android-phone/
I would recommend running on your device rather than the emulator.
http://developer.android.com/tools/device.html
In short:
Turn on "USB Debugging" on your device.
On the device, go to Settings > Applications > Development and enable USB debugging (on an Android 4.0 device, the setting is located in Settings > Developer options).
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If you're developing on Ubuntu Linux, there is a detailed guide in the link above.
Now in eclipse, your device should be available to run on.
In the eclipse toolkit, you have the option to run it directly on a device. It's rather quick to do so.
Enable USB debugging as well as installation of apk from sources other than the market. Then assuming you have already setup the required drivers/settings to connect to your phone via ADB, you should be able to run it on the device and debug. In the run dialog, it will list all available devices and you can simply select the one you want to use.
If you already have a run entry (i.e. you've already run your application),
select your project
click Run -> Run Configuration
You should be in your application run configuration (on the left under Android Application -> Your_App).
In the Target tab, you should be able to select your device. It will likely already be in "Automatically pick compatible device...". On my setup, it will run directly on my phone if it's the only available device. You can select Always prompt to pick device which will let you choose every time.
Eclipse plugin (ADT) information: http://developer.android.com/tools/help/adt.html
Information about setting up your device: http://developer.android.com/tools/device.html
I know android emulator is too slow.
You can either use device or
try bluestacks it saves lots of time.
User device only when you want to test your app for particular device.
Here is what you are looking for :
http://developer.android.com/tools/device.html
To summarize:
Plug your phone to your computer with a USB cable.
Make sure the drivers are installed and your phone properly connected.
Make a Ctrl + F11 from eclipse.
It will build the apk, transfer it to your phone and then launch it automatically.
If you have unit tests, Robolectric lets you run them without using the emulator or the device.
you can download bluestacks as emulator, as it is really fast.
after then make settings in eclipse as window->preferences->android->build -> then uncheck the 3rd checkbox written as "skip packaging and...", then apply and restart the eclipse to take effect.
now open the bluestacks in background and just double click the apk file in bin folder of eclipse and bluestack will install it in 2 to 3 secs and you can directly see the result.
NOTE here that you have to only save the file ,you working on in eclipse and only double click on apk, and result will directly appears to bluestacks. Without uninstalling and reinstalling apk in bluestacks.
and you can delete your apk also, it automatically immediately create
a fresh version of apk (thus not required) as soon as you save all your files apk will be updated.
Google BlueStacks.
It runs on Windows and it's really fast.
I have installed Mono for Android setup, I was able to follow through the Hello World example, I have the Android SDK Manager working with my AVM's I can even start an emulator when prompted during deploy -> select device selection. Howerver, once the emulator starts it never shows in my Select Device list, so I can't really test anything by pushing it to the emulator.
Am I missing anything? Is there any other way to deploy a compiled package to android emulator when using VS2010/Mono setup?
Thanks a lot for your insight.
I had similar behaviours in Netbeans. Here is what I do:
After the emulator has started the first time, it is "locked". Just unlock it by dragging the green thingy from left to right. Then just press "RUN" again in the IDE.
Sometimes, it works to just hit "Run" again without changing anything. Just wait a minute after trying the first time.
I discovered that being patient with the emulator often helps :)
In my case, I had to be running VisualStudio as an admin in order to get the running emulators to appear in the list.
I'm using the Android emulator running API version 15 from the SDK tools and in the console I'm getting this error:
[Date - Emulator] ##KBD: Full queue, lose event
I can't click on anything obviously. I googled it and the only solution is to delete the emulator and recreate it. This works for a while but then I have the same problem again.
Does anyone know what causes this error and how to fix it?
You can try the following to clear the old data and applications (your emulator will return to its default settings and data)
Tools --> Android --> AVD Manager
Then select your Emulator
From Actions column hit the arrow and select Wipe Data
I was facing same problem, There is Nothing RAM problem.
Solution is here's
Go to Tools -> AVD Manager ->Find the emulator which you are having this error -> Right click on your emulator and click on COLD BOOT NOW.
i probably figured it out. try this:
While creating the android virtual device, you must have given its size in KIBs or upto 32 mibs as shown in one of the tutorials on web.
now delete the previous device and make a new device giving its size as 512 MIB. It solved my problem.
Hope it'll work for you also, just give it a try.
I have ran into the same problem and I realized that I had dedicated only 256 MB of RAM for the virtual device. It had simply run out of memory.
Here's the solution:
-Go to Tools -> Android -> AVD Manager
-Find the emulator you are having this error on.
-Click to the "edit" button next to it. (In 3.0, this appears as a green pencil)
-Click "Show advanced settings"
-Scroll down and assign some more RAM to the device, 1GB should cut it, 2GB is definitely enough if you are running a simple app. I would also recommend assigning 512 MB of heap.
-Hit finish. Exit the emulator and restart it.
You should be good now, I hope it's been helpful. Happy coding!
this is a bug in android emulators. i also had the same problem. use 64bit linux for development to minimize such issues.
** freezing problem is there on 64-bit linux machines also, but the frequency of such problems is highly reduced. also emulators behave notably faster.
Sorry, I don't know whether this will help you... I had many problems when I try to run the emulator in Apple Mac mini. Whenever I run the emulator, machine asked me to restart. When contact Apple support, they told me it's a problem with less Memory. Just check and see how the memory is utilized by the emulator.
This is a common issue if you not provide enough resources to your virtual device or your virtual device is stuck some how.
Any one of these solutions should work
if you don't have anything useful in your virtual device, you can wipe it. by simply going to
Tools > Android > AVD Manager
Then select your virtual device
Right click select Wipe Data
Each time you start a virtual device it maintain state and pre installed apps in its memory so a cold boot will also be a good option.
to cold boot simple follow first two steps from above and select Cold Boot Now.
Now you are good to go!