The difference is in the ", Debug" part in the device line. Your 1.5 based device is not a debug build. This means you'll only see application that explicitly say debuggable=true in their manifest (and none of the bundled apps have it obviously)
Just enable debugging in your own app and you'll be able to do anything (with that app) that you'd be able to do on your 1.6-debug build device. Xav On Wed, Oct 14, 2009 at 11:14 PM, Jeremy Slade <[email protected]>wrote: > > I have two phones, one running 1.5 and the other on 1.6. When I > connect the 1.6 device via usb, DDMS recognizes it and in the top-left > pane shows: > HT842....... | Online | 1.6, debug > > It then lists the individual processes, I can select them and use > various tools like allocation tracker. > > But when I connect the 1.5 device, DDMS recognizes it but shows: > HT95A....... | Online | 1.5 > > But it does not show any of the processes on the device, so I am not > able to do use allocation tracker and such. The sysinfo tab works, > and I can monitor logcat with filter and such in the bottom pane. > > What am I missing here? Obviously the 1.5 device has USB debugging > enabled. Why does it not show 'debug' in DDMS? I'm using SDK 1.5_r2 > on linux (Ubuntu 9.04), if that makes a difference. > > > Thanks, > Jeremy > > > > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
