Hot answers tagged android-emulator
76
I had the same issue after upgrading the developer tools (v20.0.0v2012...). All of a sudden none of my android virtual devices would accept any input from my physical PC/Mac keyboard.
This is how I fixed it:
Eclipse > Window menu > AVD Manager
Select your virtual device and click Edit
Under Hardware, Click New
Select Keyboard Support then click OK
Edit ...
15
I guess what you mean is to install applications from the market on the Android emulator. Well, normally this is not possible and also not suggested. The emulator is mainly intended for development purposes. The problem is also that you'd need to get the Android market in order to be able to download apps (Angry Birds in your case), but the emulator doesn't ...
13
Try Android x86 as a virtual machine on Virtual Box. this is by far the best working android I have seen...
It has the basic, default Android UI.
It is fully functional.
It works 4 times faster than my HTC Sensation
Android X86 ISO files: http://code.google.com/p/android-x86/downloads/list
How to install it: ...
10
Have you given the Amazon Appstore's Test Drive feature a try? Super simple, runs in most browsers - simply find an app in the store for which Amazon has Test Drive available then click the big green Test Drive button (a list of Test Drive apps is here). Once you have a Test Drive session open click the home button on the bottom of the emulator to access the ...
10
You can call between AVD's. Run 2 AVD, each will have diffrent number - it is placed on window title bar, example 5558. Call from one to other using this numbers. You can also text ;]
In your AVD you simply cannot use real celluar network because your PC/Mac do not have built-in GSM modem (even if, AVD is not supporting this kind of feature).
9
You can certainly install the Amazon App Store app on the emulator. First go to the settings and allow installation of apps from unknown sources, then open the browser and go to http://amzn.to/getamazonappstore. This will download the app store .apk, which you can then install.
However, if you are planning to download and run Angry Birds (or other ...
7
If you're doing development in Eclipse, you don't need to turn off the emulator. If the debug/run button in Eclipse is set up properly, then Eclipse will close the current instance of your program inside the emulator, install your new program to the emulator, and start the program on the currently running emulator -- all without rebooting the emulator.
Yes, ...
6
Lie Ryan makes a good point that once you start the emulator you don't need to close it when you are done testing a build. Leave it open and each time you run or debug your app it will automatically be re-loaded and launched.
If you are having trouble with the size of the emulator you can modify the settings and have it display the actual size of the ...
6
Launch the emulator from the command line so that you can specify a /system partition size using the -partition-size <MB> option. For example, I use this to launch an emulator running Android 1.6 with a /system partition of 512 MB:
emulator -avd Donut -partition-size 512
...where "Donut" is whatever you named your AVD (you can check in Eclipse's AVD ...
6
You need to create a port forwarding to your Android device. This can be done with ADB.
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
...
6
The Android emulator doesn't currently support this, unfortunately. There is a configuration file in the build system that determines whether or not to enable the user accounts feature, and it is disabled in the emulator images distributed by Google. You can star this issue on the bug tracker in the meantime.
However there are two alternatives you can look ...
5
Note that although Android OS itself is free (gratis and libre), Google's Android Market is not a free application (proprietary and device manufacturers have to pay license fee to Google if they want to legally include Market on their device); so installing Market on an emulator have a shady legality (though I doubt Google would knock on your front door, ...
5
Unfortunately the emulator is extremely slow on all platforms. Better hardware will only get you so far.
Edit: Since there are now native x86 versions of the emulator, performance should be considerably improved. You should be able to get them through the SDK (or through Intel's website, see this Stack Overflow post).
4
The emulator is slow because it's an qemu that emulates a whole different CPU architecture as it's used by consumer PCs: ARM (vs. x86(_64) on your PC)
This means that every CPU instruction on the emulator's ARM CPU has to be emulated, which is per se slow. Also the emulator is AFAIK single-threaded. This means that speed-up can only be achieved by fast CPUs ...
4
When you create a new AVD (Android Virtual Device).
Under Hardware, click New:
From the drop down list of Property, select Device ram size. Click OK.
You can now put a value beside of Device ram size of how big you want it to be.
Note: You have to create a new AVD. You can't edit them as far as I know.
4
The Android emulator is resetting the system image when rebooting. You can find the changed version of the system.img in your /tmp here:
/tmp/android-username/
It usually has a name like emulator-*. Copy that file before shutting down the emulator.
4
You already have a working vCard file (.vcf), just import it using GMail's web interface. If this VCF is still bad, you can apply simple text processing (regex search & replace) to it before importing it to Google.
Here are the steps to import a vCard file into GMail using the web interface.
Here's an excerpt from Google's help:
Click Gmail at the ...
4
1. Using command line: Here's how you can copy files to an SD card image.
You have to use adb push to copy files from Desktop to Emulator and adb pull for the reverse. Here's the syntax to copy files to or from an Emulator/Device Instance:
Copy from desktop to emulator:
adb push <local> <remote>
Copy from emulator to desktop:
adb pull ...
3
Installing the market in the emulator is not that simple because by default the system partition is resettet on every reboot of the emulator.
If you want to make the changes permanent you have to delete the file /system/app/SdkSetup.apk
If you copy afterwards the two necessary files GoogleServicesFramework.apk and Vending.apk to /system/app/ you will have ...
3
The system images system.img are located in the android SDK install directory under system-images/android-<platform-version>/<platform-type>.
Once you create the AVD, in the %USERPROFILE%/.android/avd/<AVD_NAME>.avd you will find the img files for /sdcard/ and /data/, but /system and such are loaded from the SDK path mentioned above.
In ...
2
I believe /data/data/com.android.providers.telephony/databases/mmssms.db is an SQLite DB, so you can use this firefox add-on, SQLite Manager and that should let you merge whatever backups you have lying around rather easily.
After you merge them, you can just replace /data/data/com.android.providers.telephony/databases/mmssms.db with the resultant merged ...
2
There is a feature build into the Emulator, named Snapshot. Snapshot, basically saves an image of the emulator (in it's current state) when you close it. Then next time, you can start it from the same place. The emulator will start almost immediately, since it doesn't need to go through the boot process. Using Snapshot, I consistently can start my ...
2
If you're using a multicore machine, you could try to force the emulator to use more cores. The Android emulator uses a single core by default, and on some processors it can be really slow. However, this decreases the stability of the emulator.
To do this, launch the emulator and press Ctrl+Shift+Esc to open Task Manager. Go to the Processes tab and ...
2
In addition to the other great answers here, this is sort of an obvious answer.
Anyhow, I figured I'd add it to the list here. If you increase hardware specs on the development computer your running this on (most specifically RAM or hard disk spindle speed) you'll see an increase in the speed at which the Emulator starts up and runs.
My development ...
2
You could try to use a third party emulator which by my experience, works very well.
I'm not going to tell you that it won't lag from time to time, but take the trial and you will see how much better this emulator runs.
It's not a free application, but it's not expensive either.
You can find it at YouWave Android Emulator.
Give the trial a try and get back ...
2
There is a minimum possible processor speed for Android to run correctly. If you don't get that speed, part of the system thinks another part has crashed (it gives it about 5 seconds to finish initialising and panics if it doesn't) and terminates it, which leaves the system in an unusable state. On the emulator, processors slower than about 2.4GHz Pentium ...
2
You need to change the config.ini file in your .android directory. This file is found under the main hard drive directory. From there, open the avd file and you will see a list of virtual devices. Open the desired device and then open the config.ini in notepad. Then copy this text: "hw.keyboard = yes" (minus the quotes) and then save and close. The next time ...
1
You could also take a look at the Contact Cleaner app for an initial cleanup. Not sure how much help that will be in your case (with the LinkedIn stuff it doesn't care about).
Another thing to consider: temporarily remove the LinkedIn "provider" from your configuration->accounts (if it is still left there after you uninstalled the connected app) may get rid ...
1
kernel panic
When a kernel panic occurs all user space programs are immediately stopped, preventing a user from detecting the cause of the panic: logcat; dmesg and /proc/kmsg will do you no good.
You can still check the /data/dontpanic/ folder for any files present, like:
apanic_console or apanic_threads
kernel boot
Method of logging kernel messages:
...
1
This answer is for those who built the emulator from source (i.e. Following instructions from source.android.com). You need to modify a property in the following file:
external/qemu/android/avd/hardware-properties.ini
In the following section of that file change the default value from no to yes:
# Keyboard support (qwerty/azerty)
name = ...
Only top voted, non community-wiki answers of a minimum length are eligible
