Harness the capabilities of DDMS to assist in problem solving


Recommended Posts

I'm not a developer, and I don't pretend to be; I'm a test analyst. However, I'm working on an agile product which requires me to use some development tools such as MonoDevelop, Xamarin, ADT, XCode, VS 2012 and a few other bits and bobs. The product is not something I can share details of, however I can say it's going to be cross platform. Anyway, I digress.

My current involvement is to assist in running a proof of concept on Xamarin, and to establish whether it'll fit out needs. Whilst installing all of the bits 'n' bobs I need, I have been spending a lot of time on the Android developer site and stumbled across a useful profiling tool called DDMS (Dalvik Debug Monitor Server). Whilst it's primarily aimed at plugging into the emulator(s), it will also support physical devices provided you have the correct USB driver and the device is in developer mode (don't quote me on that last bit). It seems like a great tool for monitoring CPU & memory usage. I'm one of these people who believes what tools like GoTaskManager and Device Info when it says the CPU is running at > 50%, and the memory consumption is up at 80%+... it seems these apps don't give you a good indication of what is actually happening. DDMS appears to be a better tool to tell you if your device really is chomping up all your resources.

So here's how to get going with DDMS:

1 - Download the SDK (ADT bundle) from here

2 - Unzip it to a location on your machine (doesn't matter where)

3 - Go ahead and run eclipse.exe from ..\adt-bundle-windows-x86_64-20130219\eclipse\

3a - You might get a warning that JDK or JRE is missing, so go ahead and sort that out before re-launching ADT (eclipse.exe)

4 - Once you have ADT up and running, click Window > Open Perspective > DDMS

5 - Put your device into Developer mode by going to Settings > Developer Options and enable USB debugging

5a - If you don't see a Developer option, go into Settings > About Device > touch the Build Number 7 times, and you'll get a toast message telling you that you're now a developer

6 - Attach your device to your PC, and it should appear on the left under Devices. If it doesn't, wait for the ADB Interface driver to install

7 - Once your device is listed, you can start probing it. The most useful tab (I found) is the System Information tab which provides you with CPU load and Memory usage. The LogCat is also very useful, but isn't easy to read.

Because of the way DDMS integrates with Dalvik, you won't be able to get a list of processes and Heap data as you can with an emulator.

My device is running at < 10% CPU whilst idle, and about 50% Memory used with 'standard' apps running (FB, Instagram, K9 mail, Lookout, WhatsApp etc...)

Anyway, enjoy :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      459
    2. 2
      +Edouard
      212
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!