Android emulator start up error ?

by android.vinny » Thu, 17 Sep 2009 13:39:11 GMT


Sponsored Links
 can any body give the solution for this....

when i am running the project in eclipse ......

at finally showing this message ...

ActivityManager: - exec '/system/bin/sh' failed: Bad address (14) -

app is installing but not starting first time automatically.....


TIA

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



Android emulator start up error ?

by mydoghasworms » Sat, 19 Sep 2009 02:00:15 GMT


 Like me, it appears you missed a step in the installation. See
file:///C:/android-sdk-windows-1.6_r1/docs/sdk/1.6_r1/installing.html

You need to add the /tools directory from the ADK installation to your
PATH environment variable. After that, try again.




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


Sponsored Links


Android emulator start up error ?

by mydoghasworms » Sat, 19 Sep 2009 02:02:20 GMT


 My last post didn't seem to appear to have saved.

You need to follow the instructions here:
file:///C:/android-sdk-windows-1.6_r1/docs/sdk/1.6_r1/installing.html

The /tools directory of your Android SDK installation must be added to
your PATH environment variable as per the instructions.




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



Android emulator start up error ?

by David M. Lee » Sat, 03 Oct 2009 05:49:20 GMT


 €
You need to follow the instructions here:
file:///C:/android-sdk-windows-1.6_r1/docs/sdk/1.6_r1/installing.html
The /tools directory of your Android SDK installation must be added
to
your PATH environment variable as per the instructions.




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



Android emulator start up error ?

by GK Gupta » Thu, 08 Oct 2009 00:31:04 GMT


 I have added the /tools directory path to my PATH environmental
variable, but even then I am facing this kind of problem frequently.
Can anyone help me.





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



Android emulator start up error ?

by BWrightson » Thu, 08 Oct 2009 02:14:37 GMT


 When I first set up the SDK I added the entire path, with "\tools" at
the end, and I got the error message.  Then I removed the "\tools"
part from the end of the path I had entered and it worked.  Hopefully
that helps.

-Brian






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



Android emulator start up error ?

by Dorian » Tue, 10 Nov 2009 02:08:09 GMT


 yes,I removed the "\tools" part from the end of the path ,It
worked ,thank Bwrightson.







--



Other Threads

1. Not receiving c2DM message

I am trying to build a test app for C2DM message.

Here is what I've
Registration:
package name: myapp.test
published on the market: no
contact email: my gmail account (all emails are same, lets say
x...@gmail.com)


Phone:
I've signed up to sync google account (in fact with the email account
I've registered x...@gmail.com)
I am using the google package for C2DM. So, i am using the registered
gmail account x...@gmail.com in the C2DMBaseReceiver.java.
When I run my app, I get the registration id at C2DMReciever.java.
I've the following set in my AndroidManifest.xml:

  <permission android:name="myapp.test.permission.C2D_MESSAGE"
android:protectionLevel="signature" />
<uses-permission android:name="myapp.test.permission.C2D_MESSAGE" />

<uses-permission
android:name="com.google.android.c2dm.permission.RECEIVE" />

Server side:
I run JBoss on my local machine.

I send the message to: https://android.clients.google.com/c2dm/send
parameters:
registration_id: the id I recieved
collapse_key: None
data.message=test  <== this is the message I expect to be sent.
data.account_name=x...@gmail.com <== I am not sure, if this is required.

conn.setRequestProperty("Authorization", "GoogleLogin auth=" +
authToken); <== authtoken uses the email I registered with
(x...@gmail.com) and the password for the same.

The response to the HTTP post is 200. and the response line is:
id=0:1297724645037768%c7a1f70d00252358

So, I am assuming it is successful.

However, I never receive the message on the phone.

Am I doing it right? I feel I am so close, but yet so far :-( Your
help is appreciated.




-- 

2. ActivityGroup and activity lifecycle

Hello all:

I have a question about ActivityGroup and lifecycles. In my app, I
have a tabbed interface where each tab starts a new activity. The
first tab acts as a Media Player with two buttons for playing one of
two different music streams. This activity extends the ActivityGroup
because there is a third button on the page that launches an activity
that acts as an information page. I'm using an Activity Group because
I wanted the tab navigation to stay on top when I switch to the
information activity.

The information activity has several buttons on it, one of which looks
like an X which will switch back to the first activity with the Media
Player buttons. I found examples online using the following code to
switch between the two using Activity Group:

Code that's in the MediaPlayer Activity, this function is used in the
info button onClick listener:

public void replaceContentView(String id, Intent newIntent) {
     View view = getLocalActivityManager().startActivity(id,
newIntent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP))
                                   .getDecorView();
     this.setContentView(view);

Code that's in the Information Activity in the closeButton's onClick
Listener:
Intent parent = new Intent(v.getContext(), Home.class);     NOTE:
Home.class is the MediaPlayer Activity
Home parentActivity = (Home)getParent();
parentActivity.replaceContentView("info", parent);


This code works properly in the sense that my tab navigation stays on
top and it gives the impression that the Information is "sliding" on
top of the Media Player stuff and then "sliding" off screen again when
the X button is pressed. However, I've noticed some weird behavior.

If one of the streams is playing, and then the information button is
pressed, the stream continues to play, but when you click the close
button on the information page to go back to the media, the Media
Player gets re-initialized so that if I try to click the button to
stop the currently playing stream, another instance of the stream
starts playing on top of the one that's already playing. There's no
way to stop the original one.

I've been putting Log statements in each of the lifecycle methods
(onPause, onStop, onDestroy) and yet it seems that none of these
methods are being called when I switch to the Information Activity as
none of my log messages are appearing in the de{*filter*}.

I originally thought that by saving the state using something like
onSaveInstanceState would fix it, but it doesn't seem to be calling
this method either.

Upon reading on the Android Developer site about LocalActivityManager
and the startActivity method it states: "...If the new intent is the
same as the previous one and the new intent does not have the
FLAG_ACTIVITY_CLEAR_TOP set then the current activity will remain
running as is.....Otherwise, the current activity will be finished and
a new one started".

Basically it's my understanding that according to the rules defined
here and the way in which I'm using this, my first activity should be
finished which I assume means it's killed, but could be wrong, and
then the second activity starts. But as I stated earlier it seems this
is not the case. If I call finish() in the Information activity for
the close button it kills the entire app and takes me back to the Home
screen of the device.

Is there a better way to do this or how can I save the state of my
MediaPlayer objects and buttons so that they're not re-created every
time you return from the Information page?

Hope this all makes sense and thanks for the help,
DanielleM

-- 

3. Help Desk Software

4. Display map overlay always on top

5. Density independent values through code for views

6. Display Radio Buttons when you click a button in the same page

7. multi platformed android native apps