No Pavan, I haven't tried that! I'll check and see if modifying the android_winusb.inf could help...
Thanks, Best Regards On Mar 2, 10:54 am, Pavan Savoy <[email protected]> wrote: > On Wed, Mar 2, 2011 at 3:16 PM, P@AR <[email protected]> wrote: > > Hi Mike > > ... maybe from different reason... but I also had troubles with > > connecting to adb on my device. > > > For solving the problem I was doing do following commands > > > adb kill-server > > adb start-server > > > and after several tries, it succeed > > (sometimes I had to reconnect unplug/plug the USB cable few times in > > order to detect my device) > > > Hope that this would help :-) > > didn't modifying the "android_winusb.inf" file as per the connected > device's VID and PID help ? > > > > > > > > > > > p.s: > > I'm using adb drivers for WindowsXP > > > On Mar 1, 3:06 am, mike digioia <[email protected]> wrote: > >> Hi > > >> I have been successful using adb to debug my kernel work on a new driver, > >> however, adb server and daemon seem to have some problems where they don't > >> detect the device connect with the USB cable anymore. I can fastboot boot > >> my > >> kernel to this device but can't do "adb devices" and get a valid device ID. > >> Only " daemon not running. starting it now", daemon started successfully", > >> "error: device not found". > > >> Did anyone have this problem? I have used different cables and reboot into > >> fastboot many time after taking our the battery, etc. nothing works. Anyone > >> have an idea? (other than making changes to use KGDB) thanks. > > >> /mpd > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-kernel > > -- > --Pavan Savoy -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
