I have the same problem on Ubuntu, but this fix is not working.  It is
detecting the device - showing in Eclipse as ????????? online unknown,
and on the command line as the same.  I have access via a shell to the
device on the command line (see 
http://code.google.com/p/android/issues/detail?id=4365#c2).

In Eclipse:

java.io.IOException: device (????????????) request rejected: device
not found
        at com.android.ddmlib.AdbHelper.setDevice(Unknown Source)
        at com.android.ddmlib.AdbHelper.executeRemoteCommand(Unknown Source)
        at com.android.ddmlib.Device.executeShellCommand(Unknown Source)
        at com.android.ddmuilib.logcat.LogPanel$3.run(Unknown Source)

Installed:
Android SDK Tools Revision 4
SDK Platform Android 1.5 SDK API 3 Revision 3
Google APIs Android API 3 Revision 3

I have tried several things suggested for ubuntu
 
http://groups.google.com/group/android-developers/browse_thread/thread/1c55ed426623e2b8/5c679d04aa6713d3?lnk=raot
but I don't think this is the problem any more since it is actually
connecting.

Any help would be much appreciated,

Peter

On Nov 9, 4:42 am, Faiz <[email protected]> wrote:
> I had the same problem at first. In order for the adb to detect T-
> MobilePulsefrom both command line and Eclipse, the Cupcake (1.5) SDK
> is needed.
>
> 1. Edit the adb.usb.ini (in home directory - ~/.android)
> 2. Add 0x12d1
> 3. Restart adb (adb kill-server / adb start-server)
>
> adb should now be able to detect the device but with incorrect serial
> number (it is listed as ?p on my machine). Eclipse (I'm using 3.5 on
> Mac OS X) can now detect the correct 1.5 API onPulse.
>
> Well, I'd suggest not to upgrade to 2.0 SDK unless you really have to.
>
> On Oct 29, 9:33 pm, Tim <[email protected]> wrote:
>
> > Hmm thought I replied to this.
>
> > 1. You need the latest 2.0 SDK.
> > 2. You need to use 12d1 rather than 0bb4 for the vendor ID. The
> > Android Dev Guide is wrong.
>
> > Even then adb does not pick up the correct serial number for the
> > device, so it will work from the command like if you use ./adb -
> > d   ...   but not from within eclipse.
>
> > On Oct 27, 1:43 am, Jeffrey Blattman <[email protected]>
> > wrote:
>
> > > under settings > applications > development is usb debugging enabled?
>
> > > On 10/26/09 6:09 AM, marktyers wrote:
>
> > > > Hi
> > > > I have purchased a T-Mobilepulsefor the purpose of testing some
> > > > applications but it does not show up when I run ./adb devices or when
> > > > I test my apps using Eclipse. Please can someone help otherwise  Iam
> > > > left with a useless lump of plastic :-(
>
> > > > ps. I am an absolute beginner to this so please be gentle...
>
> > > > Mark
>
> > > --

-- 
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.

NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en

Reply via email to