Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by theRise » Tue, 07 Oct 2008 00:57:23 GMT

Sponsored Links
 I'm trying to get the HelloAndroid app up and running. I can run the
emulator from the command line just fine, but there seems to be an
issue from running it within eclipse when i'm ready to launch my app.
I tried searching for some of these terms and found no luck, anybody
else with this issue or some advice?
My console reads as follows:
[2008-10-06 16:11:07 - HelloAndroid] ------------------------------
[2008-10-06 16:11:07 - HelloAndroid] Android Launch!
[2008-10-06 16:11:07 - HelloAndroid] adb is running normally.
[2008-10-06 16:11:07 - HelloAndroid] Launching:
[2008-10-06 16:11:07 - HelloAndroid] Automatic Target Mode: using
existing emulator: emulator-5554
[2008-10-06 16:11:07 - HelloAndroid] WARNING: Unknown device API
[2008-10-06 16:11:07 - HelloAndroid] Failed to upload HelloAndroid.apk
on device 'emulator-5554': Unable to open sync connection!


Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by Evan... » Tue, 07 Oct 2008 08:19:39 GMT

 Hey man
are you waiting a long time when the dummy Android runing??
or if you did't configure right your SDK in you Eclipse...
please check it!  luck for you!
That's problem,so easy!


Sponsored Links

Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by Evan . . . » Tue, 07 Oct 2008 08:26:03 GMT

 So sorry I can't help you !
Hope some super-man can do that!!
lucky All!!!!

2008/10/7 Evan... <[EMAIL PROTECTED]>


Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by Ena » Tue, 07 Oct 2008 08:32:59 GMT

 may it helps u....restart pc....delete folder Android from C:\Documents and
Settings\Administrator\Local Settings\Application Data.....


Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by theRise » Tue, 07 Oct 2008 16:10:49 GMT

 i've run a clean install of both android and eclipse, still no luck.


Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by theRise » Thu, 09 Oct 2008 14:21:39 GMT

 Here's a follow up on the issue.

I've run a completely clean install of eclipse and the sdk in a
separate dir. The issue is still the same. I've also installed it
successfully on a separate machine and run the emulator just fine. I'm
sure it's an isolated issue possibly to this particular machine and
some sort of windows configuration issue. If anyone (google devs?) has
seen this issue or know what may be causing it, i would greatly
appreciate a constructive reply. I've been hacking away at this for a
few days now, and has numerous alternate sources for help, i just
can't seem to get this one working.


Hello World Emulator Problem - SDK 1.0 r1 Eclipse Version: 3.4.1

by theRise » Fri, 10 Oct 2008 19:31:55 GMT

 Resolved, kind of.

The issue that is causing this is when i run eclipse, the DDMS
perspective shows emulator-5554 in an offline state under the devices
list. In order to get a new emulator instance running i have to first
go to Run Configurations > Target tab > Manual radio button. Then when
i run the project DO NOT click the emulator on the list, and select
Run. This will instantiate a new emulator, and will run the project.
As of now i can not find another workaround, or a way to delete this.
If anyone has a solution to deleting an old emulator reference or
knows where to find it (not in the registry, i checked) then please
follow up.


Other Threads

1. Is ProgressBar correctly handling padding-values?

onkeydown: make sure your view is focusable and focused.

Padding: known bug, fixed in cupcake.

Sorry for being terse, sent from my phone :)

Here is a skeleton of the class I'm currently working on.
Unfortunatly, i'm stuck on two problems and it's driving me mad !

The first problem is about the onKeyDown(KeyEvent) : I don't
understand why this method isn't called while I pressed a key on the
The second problem deals with padding. Indeed, I'm always creating
widget using fake paddings in order to be sure my widget correctly
handle those values. Unfortunatly, I tried to extend a ProgressBar and
I had some problems because my ProgressBar is clipped.

My code is :

package com.niji.android.myhouse;

import android.content.Context;
import android.graphics.Canvas;
import android.graphics.Color;
import android.graphics.Paint;
import android.graphics.drawable.Drawable;
import android.util.AttributeSet;
import android.util.Log;
import android.view.KeyEvent;
import android.view.MotionEvent;
import android.widget.ProgressBar;

public class ProgressWheel extends ProgressBar {

       private static final String TAG_LOG = "ProgressWheel";
       private static final Paint mPaint = new Paint();

       private float oldX;

       public ProgressWheel(Context context, AttributeSet attrs) {
               this(context, attrs, 0);

       public ProgressWheel(Context context, AttributeSet attrs, int
defStyle) {
               super(context, attrs, defStyle);


               setPadding(5, 15, 40, 10)


       protected synchronized void onDraw(Canvas canvas) {
                * I'm not sure the onDraw(Canvas) method from ProgressBar is
                * implemented. Indeed. With padding values, The progressBar
may be
               canvas.drawRect(0, 0, getWidth()-1, getHeight()-1, mPaint);

   public boolean onKeyDown(int keyCode, KeyEvent event) {
                * I don't understand why this method is not called
       int progress = getProgress();
       Log.d(TAG_LOG, "onKeyDown");
       switch (keyCode) {
           case KeyEvent.KEYCODE_DPAD_LEFT:
               Log.d(TAG_LOG, "KEYCODE_DPAD_LEFT");
               if (progress <= 0) break;
               setProgress(progress - 1);
               return true;

           case KeyEvent.KEYCODE_DPAD_RIGHT:
               Log.d(TAG_LOG, "KEYCODE_DPAD_RIGHT");
               if (progress >= getMax()) break;
               setProgress(progress + 1);
               return true;

       return super.onKeyDown(keyCode, event);

       public boolean onTouchEvent(MotionEvent event) {
               Log.d(TAG_LOG, "onTouchEvent");
               int progress = getProgress();

               switch (event.getAction()) {
               case MotionEvent.ACTION_DOWN:
                       oldX = event.getX();
               case MotionEvent.ACTION_MOVE:
                       if (event.getX() > oldX) {
                               setProgress(progress + 1);
                       else setProgress(progress - 1);
                       oldX = event.getX();


               return true;


and here is my XML layout :

<?xml version="1.0" encoding="utf-8"?>

       xmlns:android="http://schemas.android.com/apk/res/android" >

               android:progress="35" />



2. Cupcake Release end March


I have a so called reliable resource who works in the T-mobile store,
and so far he has been right about anything to do with G1.  He
predicted the OTA release, and that was right, but he has also said T-
mobile will be releasing the cupcake to t-mobile customers in uk end
of March.

Of course all i/we can do is wait...if anyone has any information to
back that claim it would be appreciated.
I know there's loads of cupcake talk that has been going on for
months...but i believe this is the real thing, else he wouldn't
jeapordise these claims to get people to buy the G1 and then get
hundreds of complaints if it didnt happen

3. How are Android/G1 sales doing?

4. while loop in main thread blocks listener updates?

5. Android with RFID reader

6. Setting clickable on individual ListView's ChildViews

7. how to know the status of the MediaPlayer?