Skip to main content

Screen capture in Android 2.2.1 "Froyo"

My Android Desktop snapped with this method
I took a screen capture by mistake once but then struggled to repeat the behaviour.  After Googling for a solution I found some very complicated solutions.  Probably the best way to do this is to buy an application on the Market, but I don't want to spend money on a toy.

If you look in your "Settings » Applications » Running Services" menu you should see a service called "ScreenCaptureService".

This allows you to take a screenshot by pressing the "Back" and "Home" buttons simultaneously.

What works for me is to press and hold "Back" and then to press and release "Home" (while holding "Back").  This makes a snapshot noise and displays a message.  Files are saved to the ScreenCapture directory on your SD card and should appear in your gallery.

Of course this is a problem if you try to take a snapshot of a running application because pressing "back" causes it to quit.  I could not find a workaround for this and there doesn't seem to be anything much on Google.  I'm not sure if they did this deliberately or if for some reason the developers didn't consider this when implementing the system.  It seems too obvious an oversight to be anything but deliberate to me.

UPDATE:
For more recent versions of Android you should press the Power and Volume Down buttons together for 2-4 seconds.

If your phone has a physical button for the home button then you may need to try pressing power and your (physical) home button together for 2-4 seconds.  Make sure you press them together.
Labels:

Comments

  1. Ara Bk23 April 2013 at 09:21

    "Pressing and holding" doesn't elicit the same behaviour--much like a single click vs. a drag or hold with normal computer mouse. So, pressing and holding the Back button doesn't necessarily exit the application, actually.

    SO, YOUR KEYSTROKES WORKED FOR ME JUST AS YOU DESCRIBED THEM.

    ReplyDelete
  2. The Geeks9 December 2013 at 06:25

    hi..Im college student, thanks for sharing :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Using Fail2Ban to protect a Varnished site from scrapers

I'm using Varnish to cache a fairly busy property site.  Varnish works like a bomb for normal users and has greatly improved our page load speed. For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site. I decided to use fail2ban to block IP's who hit the site too often. The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with. This means setting up varnishncsa.  Add this to your /etc/rc.local file: varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log: /var/log/varnish/*log { create 640 http log compress ...
Post a Comment
Read more

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred.  The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change.   Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal.   One way to decouple your domain logic from both persistence and controller is to use the "repository pattern".   Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...
Post a Comment
Read more

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer.  Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted.  This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel.  A thorough comparison of the patterns is available  here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework.  It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database.  Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its ...
Post a Comment
Read more