Hello Argon,
IMHO you should switch to android-platform, as this kind of question
is out of scope of the android sdk.
And their you should provide by far more details. I.e. from where
comes
your platform, do you have the platform code, is the adbd started by
init.d,
can you see adbd using ps on the device and so on ?
Maybe your platform has no adb support ?
Good luck ! Frank
On 4 Apr., 07:08, argongold <argongol...@gmail.com> wrote:
> Hi,
> I've a mini MID device and I am trying to use it for development/
> debugging purpose. But after all the setting steps( see below) . I am
> still not able to get device listed when I issue 'adb devices'
> command.
>
> Things I have done as follows:
> 1. enable USB debugging on the device under Settings->Applications-
>
> >Development->USB debugging
>
> 2. I have changed the following file on my computer .
> /etc/udev/rules.d/51-android.rules and added the following line.
> SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", ATTR{idProduct}=="0001",
> SYMLINK+="android_adb", MODE="0666", OWNER="MYNAME"
>
> (on Computer)
> Command Issued >> lsusb
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 002: ID 1690:0741 Askey Computer Corp. [hex]
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 002: ID 062a:6301 Creative Labs
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 006: ID 18d1:0001
> Bus 001 Device 003: ID 0408:1fc3 Quanta Computer, Inc.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Note: device is connect to usb bus at Line no. 9 above .
>
> (on Computer)
> Command Issued >> adb devices
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
> List of devices attached
>
> (on Device itself)
> Command Issued >> adbd
> cannot bind 'tcp:5037'
>
> (on Device itself)
> Command Issued >> netstat -a | grep 5037
>
> nothing returns from above command.
>
> If you have experienced such issue please let me know steps to resolve
> it. It seems the problem is on device side for which adbd returns
> 'cannot bind 'tcp:5037'
>
> Thanks for your strong support.
>
> regards,
> argon
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
