I set the following parameters in Eclipse to go to the emulator command in Window → Settings → Android → Launch → Default emulator parameters: "-cpu-delay 0 -no-boot-anim - cache / my / custom / path / to / androidcache / "(without quotes). Do they seem to be ignored?
I understand from Android Emulator startup options not working in the Eclipse plugin? that I can also set the parameters of the user emulator in Run → Run configurations , but this carries a different set of inconveniences.
Any thoughts? I considered replacing the emulator binary with a script that reflects it with the desired parameters. Any harm in this (maybe it will interfere with updates)?
I am using Eclipse 3.6 (Helios), ADT 10.0.1, SDK 10.
Refresh . I see from the same link above that perhaps this parameter exists only to pre-populate Run Cofigurations as new projects are created that look poorly documented and only moderately useful, since emulators were launched from the AVD manager to ignore it (if I had something lacks)?
Update2 : I created a script to replace the emulator binary and reflect it with the right parameters. Works great. I assume that it will be overwritten during the upgrade. This is what I did by moving the binary emulator to the real_ emulator (linux environment):
#!/bin/sh
/path/to/android-sdk-linux_x86/tools/emulator_real -cpu-delay 0 -no-boot-anim $@ >> /home/myusername/emulator_out.txt
I was not able to use an alternative directory for the cache (as shown above) ... this caused errors related to the use of the cache, etc., which, I think, have something to do with android, do not seem to work well on heterogeneous file systems.
source
share