On Jun 3, 12:35 pm, twebb <taliaferr...@gmail.com> wrote:
> On custom hardware, I've recently moved from android-1.0 to
> android-1.5 (cupcake) and seem to not be able to connect between linux
> host and target via adb. I've done this often enough in the past
> without problems using the following command sequence from the host...
>
> adb kill-server
> ADBHOST=w.x.y.z adb devices
> ADBHOST=w.x.y.z adb shell
>
> Now, though I still have IP connectivity (pings work - via usb-to-eth
> dongle), 'adb devices' doesn't find the target. I'm using adb version
> 1.0.20. Has anything in particular changed in this area? Might I
> need a newer adb version?
>
> I've also recently moved to using an omapzoom-based kernel. Could
> this be the source of the problem?
>
> Thanks,
> twebb
Never mind - I figured it out. It was a kernel configuration issue.
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
