Running the Emulator on Early Look 1.5 SDK

by Pd » Tue, 14 Apr 2009 09:14:01 GMT


Sponsored Links
 Hello,

Noticed the emulator now needs a -avd parameter to run.  I had a look at 
the Early 1.5 docs but there's no mention of the -avd startup option as 
yet. All you need to do is create a virtual device.

cd to the tools directory.  on my linux box this was:  
android-sdk-linux_x86-1.5_pre/tools

For version 1.1 use something like

./android create avd --target 1 --name NormalVM01

For version 1.5 ( Cupcake ) use

./android create avd --target 2 --name CupcakeVM01

the naming can be anything you like.  Then run the emulator with ( on 
linux atleast ):

./emulator -avd CupcakeVM01


Hope this helps some  :-)








--~--~---------~--~----~------------~-------~--~----~



Running the Emulator on Early Look 1.5 SDK

by Xavier Ducrohet » Tue, 14 Apr 2009 09:21:22 GMT


 More information about AVDs, how to create or use them, is available
at  http://developer.android.com/sdk/preview/ #avd

Xav






-- 
Xavier Ducrohet
Android Engineer, Google.

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Running the Emulator on Early Look 1.5 SDK

by Raphael » Tue, 14 Apr 2009 13:05:23 GMT


 


You can also just write:

 ./emulator @CupcakeVM01

This is the syntax used in the document that Xavier pointed out.
R/

--~--~---------~--~----~------------~-------~--~----~



Running the Emulator on Early Look 1.5 SDK

by Pd » Tue, 14 Apr 2009 15:14:31 GMT


 Thank you!





--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. init.<architecture>.rc

I'm not sure, maybe it's a dumb question, but anyway:

When I want to start Android, and I use the images from the
sdk I have to adjust the init.rc file. But what happens with the
init.goldfish.rc file which is in the same directory?

Shall I delete it and make my own init.<architecture>.rc file?

If yes, what shall I write into this file?

Regards,

Stefan

-- 

2. How to intercept when the application is brought to foregroud from background

Hi,
Out Mobile Application required the user to provide username and
password to login. After login, if the user navigates to another
application and tries to come back to our application again, i would
like to intercept this action and redirect the user to login screen
and then lead to where ever he was before.

How can i achieve this?

Currently we are doing it a very crude way by tracking the user's
action in variables and in onResume() we check for the value of the
variable and make a decision if he should continue or be redirected to
login.

Is there something to the order of an "Interceptor" which can use tell
me if the application coming to foreground was actually in the
background and not a new process.

Any assistance is appreciated.

Regards
Hari

-- 

3. How to get call history

4. Camera Preview

5. SlidingDrawer to go full screen

6. call Activity from the BroadcastReceiver.

7. Problem in integration of Facebook with android app