Dont know if you've already solved this or not yet, but I've seen problems 
like this when occasionally adb server starts up after compilation... and 
have been able to solve it,  by

adb kill-server
sudo adb start-server

continue business as usual

Weston

On Friday, September 21, 2012 2:11:19 AM UTC-7, Matt Bloomfield wrote:
>
> Hi everyone
>
> I'm new to building and Linux etc, but am starting to learn all the basics!
>
> I have built CM10 and Evervolv from source, both of which have no ADB 
> functions. The cmd comes up with <waiting for device> when trying to run 
> logcat, and when adb devices I get an empty list of devices.
>
> I have also built ParanoidAndroid from source, and that does have ADB, 
> which is weird as it pulls the CM source!!
>
> I did open up another post in Android Building group which can be found 
> here - 
> https://groups.google.com/forum/?fromgroups=#!topic/android-building/RDv3oLHc8-g
>  
>
> Kind regards,
> Matt
>
> Devices;-
> HTC One X (EndeavorU - Internation Tegra Device) - CM10 - no ADB
> Nexus 7 (Grouper) - Built from Google source, Had ADB) (now running an 
> already built CM10)
> Asus eeePad Transformer TF101 - ParanoidAndroid (built from source) Has ADB
>

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to