ADB Server & connected devices

[sorex]

Hello,

I have a Ployer Momo11 tablet here.

I installed the USB driver from this location > drivers

And when I look in the device manager of Windows XP all looks fine and no unknow devices are listed.

stuff I can see are:

Android Phone > Android ADB Interface
Diskstations > 2x rockchip _usb USB device
and probably some HID input device which is listed as a regular one


Although when I want to compile to the device B4A keeps telling it can't find an attached device.

When I reattach my phone it compiles straight to the phone.

Is there a way to force the ADB server to connect a certain device? or let it list what it finds?

Or is it just a driver that's malfunctioning? (had some issues to find the right one for the phone aswell)

 

[Erel]

You can try to manually run "adb devices" from the command line (under <android-sdk>\platform-tools). The output may provide more information.

Note that you can also use B4A-Bridge.

 

[sorex]

yes, I tried

"adb devices" which gives an empty list

"adb remount" didn't do much either

strange thing is that I see that odd face icon on the tablet that indicates that usb debugging is active. It's first white and then becomes grey but in the "taskbar" it still says it's active.

the bridge is an option if I was in reach of my wireless access point, don't have bluetooth on this laptop.

 

[Erel]

This means that there is a driver problem. You can try to uninstall the driver and then install it again.

Note that you can use a free tool such as Connectify to turn your computer to a virtual router and then use B4A-Bridge.

 

[sorex]

ok, probleem seems to be resolved

for some reason I had to add part of the device instande ID to c:\documents and settings\%username%\.android\adb_usb.ini

ID was as seen in the device manager USB\VID_2207&PID_0010&MI_01\7&1AE6A44C&0&0001

and I added 0x2207 to the ini file, restarted the ADB server via B4A and it compiled'n run on the tablet!

 

[Roger Garstang]

Hmm, I'll have to try this. I have been having issues and forgot I had to add Vendor IDs for my Motorola Tablet to that file and the USB driver...looks like the last SDK update killed both. Rebooting now to see if it is fixed.