How To Capture Screenshots With Your Android Mobile Phone

By Ryan Dube on Dec. 31st, 2009

This month I finally decided to upgrade from my archaic Windows 5.0 Cingular 8125 to the latest and greatest mobile device on the market. Now, I know there are a lot of mobile users out there who have their own personal favorites – the most popular ones being the iPhone, the Blackberry and of course the collection of Windows Mobile phones. All of those mobile devices are powerhouses in their own right, and for a while I was torn between all three. Then, one day, as we I was sitting in front of the TV and watching the premier of the show “V,” a commercial came on that I’d never seen before.

The commercial was for the new Motorola Droid – Motorola’s latest attempt to wipe out the competition with a mobile device that pushes the limits in areas where all other mobile devices fall short. The catch phrase of the Droid is “Droid Does,” and since day one it has struck fear into the hearts of other mobile phone manufacturers, and since I got it, I’ve noticed iPhone fans getting very defensive whenever I show it to them. They’ll repeat the phrase, “Yeah, the iPhone does that.” Until, that is I show them an app or a function that the iPhone can’t do – then I get a grim look and they walk away.

The Droid was everything I wanted. It had the slide-out keyboard I wanted which the iPhone lacked. It had the touchscreen I wanted that most Blackberrys lacked. It accomplished everything I needed and a few things I didn’t even know I wanted until I heard the Droid could do it – voice recognition for Google searches, in-car turn-by-turn GPS with voice, bedside clock with weather and music, a personal MP3 music player and integration with every single social network that I use. Built upon the Linux kernel, the Android mobile operating system stands to gain some significant market ground thanks to this new, powerful device from Motorola. But there was one thing that the Android OS can’t do that all other mobile devices can – take a screenshot with the Android with one simple button press. Even my old Windows 5 device could do that.

Is Taking A Screenshot On The Android Really That Hard?

As an online writer for technology, I found this lacking feature disheartening. And it is possible to run apps that take screenshots on your Android, but you need root access – and for most manufacturers if you do that, you could void your warranty. Also, blocking your apps from root access is one reason Linux users are so proud of their operating systems – they are virtually immune from all viruses. When all other mobile devices get attacked – you’ll be standing strong.

However, despite this drawback, I also discovered that taking a screenshot of the Android screen isn’t really that difficult using a PC or laptop. Other websites lay out the procedure in a ridiculously long and complicated procedure. This is silly – and in this article I’m going to show you how to connect your Android device to your PC via USB and quickly capture a screenshot whenever you like.  The first step of course is to make sure your PC is configured to quickly connect to your Android phone. To do this, you just need to set up the following applications once on your computer.

1. Install the USB driver for your phone onto your PC. You can get the Droid driver for Windows PCs here.
2. The Java SE developers kit.
3. The Android SDK developers kit.

Download and install those three applications, and you’re already halfway to taking screenshots with your Android quickly and easily. After you set up the Android SDK developer kit, you’ll be presented with an update screen that probably has an error saying you need to force download. Just cancel/close that screen and continue to the procedure below.

Setting Up Your PC To Take Android Screenshots (Only Have to Set Up Once)

Keep this in mind – once you go through the following procedure just once, you’ll be set up to instantly take screenshots on your Android with your PC whenever you like. Remember, you don’t have to do this every single time you need a screenshot, only once to configure your PC. Most online instructions don’t make that clear, and most Android users assume the procedure is too annoying and time consuming – it’s not!  Here’s how you set up your PC to take Android screenshots.

First, if you still have the Android SDK developer kit setup screen up (if you don’t just run the SDK Setup in the folder you extracted the files to), then click “Update All.”  However, if you get the error that tells you to do a force download, then just click on the Settings option in the menu.

All you have to do is make sure that the “Force https://…” is selected under the “Misc” section. Click “Save & Apply” and then go back to the Installed Packages screen. Click on the “Update All” button.

Then just click on “Install Accepted,” and wait a while for the app to install all of the packages. It’s a good idea to just install all of them for compatibility. When this is done, go to the “Available Packages” screen and click on “Refresh.”

Now that you’ve updated the Android SDK developers kit, you’re ready to start taking screenshots of your Android device. However, I have one more step that will save you a lot of annoyance later. Create a link to the Dalvik Debug Monitor in the SDK developer kit that you can quickly use to capture screenshots. Just go to the Tools folder in the folder where you downloaded the SDK developer kit. Find the DDMS.BAT file there, and create a shortcut to it that you can place on your desktop whenever you want to take a screenshot.

Please Note: I ran into two significant issues when doing this setup on my 64 bit Vista installation. Running DDMS.BAT may return a few errors. You may need to manually enter the PATH in my system environment variables for the bin folder of your Java installation. You may also need to manually enter the ANDROID_SWT variable for the path to the swt.jar file in your Android SDK installation. You may not need to do either of these things – just pay attention to any errors the DDMS.bat file returns.

Taking Screenshots Of Your Android Device

Now that you’ve configured your PC above once, taking screenshots of your Android from now on is fast and easy. The first thing you’ll want to do when you’re ready to start taking screenshots is to enable USB debugging on your phone. You can do this by going to Settings ->Applications->Development and click to enable “USB Debugging.”

Once that’s done, go ahead and plug your mobile phone into the USB port. Since you’ve already installed the driver for your device, your computer will identify and connect – if it doesn’t then just browse to directly where you downloaded the driver files (again, you’ll only have to do this once.)

Then, from now on all you need to do to take screenshots is as follows:

1. Run the DDMS.BAT file, and the Dalvik Debug Monitor will launch.

You’ll see your device displayed in the left top pane. All of your phone activity is logged below and you’ll see the activity scrolling up the pane.

2. To take your screenshot, just click Device and then Screen Capture…

3. Just save your screenshot!

The screenshot is very high quality (and of course it’s huge, so you’ll need to resize it to use on your blog), and you can just click “Refresh” to get a new screenshot again. Once you’re set up to capture screenshots in this way, you’ll be able to start capturing some of the most amazing screenshots of your Android mobile device in three simple steps – launch DDMS.BAT, click Capture Screenshot on the debug monitor, and save the picture to your hard drive.

While it’s true that the initial setup on your PC can turn into a little bit of work depending on your PC configuration and operating system, it honestly doesn’t take a rocket scientist, and the highly detailed screenshots you can capture make it well worth it.

Do you take screenshots on your Android Mobile and if so, what approach do you take? Do you open root access to screenshot apps or do you prefer using the Debug Monitor approach? Share your own opinion in the comments section below!

ShareThis

(By) Ryan, an automation engineer on the East Coast (U.S.) who enjoys discussing the latest trends of online writing and freelancing. Visit his blog at FreeWritingCenter.com to read up on the latest online writing trends and freelance money-making opportunities.

Eine super Anleitung, sehr detailliert und alles liest sich so, als wenn das auch problemlos klappt. Aber genau die Komplexität ist es auch, wieso das mit ersten Tipps und Reviews zu meinem Android hier noch dauern kann. Denn ich will das Ding nur benutzen und nicht stundenlang pimpen, bevor ich dann drüber schreiben kann.

How to Run a Meeting Like Google

No one wastes time searching for a purpose at Marissa Mayer’s meetings—even five-minute gatherings must have a clear agenda

Meetings get a bad rap in business today and for good reason—very little gets accomplished in them. I can recall a Dilbert cartoon in which several people sat around a table while the meeting organizer said, “There is no specific agenda for this meeting. As usual, we’ll just make unrelated emotional statements about things which bother us…”

That pretty much sums it up. The majority of meetings are unstructured, uninspiring, and unproductive. But they don’t have to be that way.

When I decided to write a column about running effective meetings, I turned to a leader who holds more than anyone I know and who actually credits her meeting structure for leading to some of the most innovative advances in technology today: Marissa Mayer, Google’s vice-president of search products (see BusinessWeek.com, 6/19/06, “Marissa Mayer: The Talent Scout”).

Mayer holds an average of 70 meetings a week and serves as the last stop before engineers and project managers get the opportunity to pitch their ideas to Google’s co-founders, Sergey Brin and Larry Page. Eight teams consisting of directors, managers, and engineers—all at various stages of product development—answer to Mayer.

In a shop like Google (GOOG ), much of the work takes place in meetings, and her goal is to make sure teams have a firm mandate, strategic direction, and actionable information, while making participants feel motivated and respected. Mayer’s six keys to running successful meetings follow:

1. Set a firm agenda.
Mayer requests a meeting agenda ahead of time that outlines what the participants want to discuss and the best way of using the allotted time. Agendas need to have flexibility, of course, but Mayer finds that agendas act as tools that force individuals to think about what they want to accomplish in meetings. It helps all those involved to focus on what they are really trying to achieve and how best to reach that goal.

2. Assign a note-taker.
A Google meeting features a lot of displays. On one wall, a projector displays the presentation, while right next to it, another projector shows the transcription of the meeting. (Yet another displays a 4-foot image of a ticking stopwatch.) Google executives are big believers in capturing an official set of notes, so inaccuracies and inconsistencies can be caught immediately.

Those who missed the meetings receive a copy of the notes. When people are trying to remember what decisions were made, in what direction the team is going, and what actions need to be taken, they can simply review the notes.

3. Carve out micro-meetings.
Mayer sets aside large blocks of time that she slices into smaller, self-contained gatherings on a particular subject or project. For example, during her weekly two-hour confab with the co-founders and CEO Eric Schmidt, she sets aside five- to 10-minute segments—or longer, depending on the subject—devoted to such specific areas as weekly reports on how the site is performing, new product launches, etc.

This method offers enough flexibility to modify the agenda just before the meeting, should anything pressing occur. It also instills discipline that keeps the meeting tightly focused. Mayer does the same with members of her teams who might need only five or 10 minutes of her time instead of 30 minutes—the shortest block of time her calendar permits. By setting aside micro-meetings within a larger block of time, she accomplishes more.

Mayer, who has a background in engineering and computer science, jokingly refers to micro-meetings as “reducing latency in the pipeline.” That means if she has an employee with an issue that comes up Tuesday, he or she can schedule a 10-minute micro-meeting during Mayer’s large time block, instead of waiting for her next 30-minute opening, which might not be available for two weeks.

4. Hold office hours.
Mayer brought this idea from her experience teaching computer science at Stanford, where she first met the two guys who would go on to revolutionize how the world gets its information. Beginning at 4 p.m., for 90 minutes a day, Mayer holds office hours.

Employees add their name to a board outside her office, and she sees them on a first-come, first-serve basis. Sometimes project managers need approval on a marketing campaign; sometimes staffers want a few minutes to pitch a design (see BusinessWeek.com, 6/30/06, “Inside Google’s New-Product Process”).

Says Mayer: “Many of our most technologically interesting products have shown up during office hours. Google News, Orkut [Google’s social networking site], Google Reviews, and Google Desktop all showed up first in office hours.” During office hours, Mayer can get through up to 15 meetings, averaging seven minutes per person.

5. Discourage politics, use data.
One of Mayer’s “Nine Notions of Innovation” is “Don’t politic, use data” (see BusinessWeek.com, 6/19/06, “9 Notions of Innovation”).

This idea can and should apply to meetings in organizations in which people feel as though the boss will give the green light to a design created by the person he or she likes the best, showing favoritism for the individual instead of the idea.

Mayer believes this mindset can demoralize employees, so she goes out of her way to make the approval process a science. Google chooses designs on a clearly defined set of metrics and how well they perform against those metrics. Designs are chosen based on merit and evidence, not personal relationships.

Mayer discourages using the phrase “I like” in design meetings, such as “I like the way the screen looks.” Instead, she encourages such comments as “The experimentation on the site shows that his design performed 10% better.” This works for Google, because it builds a culture driven by customer feedback data, not the internal politics that pervade so many of today’s corporations.

6. Stick to the clock.
To add a little pressure to keep meetings focused, Google gatherings often feature a giant timer on the wall, counting down the minutes left for a particular meeting or topic. It’s literally a downloadable timer that runs off a computer and is projected 4 feet tall.

Imagine how chaotic it must look to outsiders when the wall shows several displays at once—the presentation, transcription, and a mega-timer! And yet, at Google, it makes sense, imposing structure amidst creative chaos. The timer exerts a subtle pressure to keep meetings running on schedule.

Mayer does have one caveat when it comes to the timer—maintain a healthy sense of humor about it. (The timer was counting down to the end of my interview with Mayer—but she turned it into a fun and friendly reminder instead of an abrupt end to our discussion.)

Please keep in mind that these meeting techniques work well for Google. They may or may not be appropriate for your place of business. But these six keys should give you some new ideas about how to transform your meetings from a waste of time to time well spent.

Eine schöne Anleitung und zugleich eine schöne Utopie. Was dort so drin steht, ist alles richtig und wenn sich alle Teilnehmer an die Vorgaben hielten, wären die Sitzungen auch effektiv. Aber in der Bürowelt sieht das dann doch immer anders aus. Viel zu viele Menschen hören sich selber gern reden und vor allem: Niemand verliert gern, auch nicht gegen Fakten.

huch, was schick. Das könnte mir zum Arbeiten auch gefallen.