Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

DDMS Not Showing Threads From Device

I'd like to check for memory leaks in my Android app using the DDMS feature in Eclipse. When I launch an emulated device, the threads display properly for the emulated device, starting with 8600 and up.

However, when I connect my Droid to the PC, the device shows up just fine in DDMS. The logcat is generated correctly, and I can view the file structure. However, threads do not display. I get "no client selected" in the Threads pane, and there is no drop-down icon next to the device listing.

Do I need to change some particular setting in Eclipse? Is this maybe a driver issue?

like image 614
polyclef Avatar asked May 22 '10 19:05

polyclef


People also ask

How do I switch to DDMS mode?

DDMS is accessible via Studio > Tools > Android > Android Device Monitor and clicking the DDMS button on menu. You can also place is as a shortcut icon (I do) in your upper panel.

What is DDMS What are the advantages of using DDMS?

The distributed database management system contains the data in multiple locations. That can be in different systems in the same place or across different geographical locations. The database is divided into multiple locations and stores the data in Site1, Site2,Site3 and Site4.

What is DDMS describe some of its capabilities?

Android ships with a debugging tool called the Dalvik Debug Monitor Server (DDMS), which provides port-forwarding services, screen capture on the device, thread and heap information on the device, logcat, process, and radio state information, incoming call and SMS spoofing, location data spoofing, and more.


3 Answers

Eclipse Preferences (OSX) > Android > DDMS > check Thread Updates Enabled by Default

Add Android Device view to get device pan(e) noted above

Set android:debuggable=true (two g's) in app tag as noted above

Run your app in emulator

Select device in device pane

Click the update threads button

Enjoy

like image 110
bassetbob Avatar answered Sep 20 '22 16:09

bassetbob


Make sure you have android:debuggable="true" in you application tag in the manifest file

like image 28
Jason Avatar answered Sep 21 '22 16:09

Jason


This is expected behavior. The issue is your droid is not in debug mode. Notice that in the Devices pane, beside the version number, debug is stated against the emulated device but not in the case of the droid.
From what I have found so far - on the droid, only an app can be run in debug mode; and only this will be listed under your device in DDMS.

I don't know how to run(/boot) the entire droid in debug mode, or if it is possible. So far as it appears, there is no way to boot an entire real device in 'debug' more.

like image 3
Ujjwal Singh Avatar answered Sep 20 '22 16:09

Ujjwal Singh