Capturing Screenshots on Sprint HTC Hero (Problems)

by Sidepart » Tue, 10 Nov 2009 02:08:09 GMT


Sponsored Links
 I've seen a few guides around that show that people are able to
capture screenshots of their phone using the Android SDK tool 'ddms'.
I personally haven't been able to accomplish this successfully.  I've
tried it on 5 different computers running Windows XP Pro, and also
with Windows Vista Business and Windows 7 Pro.  Each time I'm met with
the following:

Phone is recognized in ddms.  I try to capture the screen, the
screenshot box comes up and says "screen is not available".

The ddms console window shows "W/ddms: got partial reply from ADB fb:"
and then dumps a bunch of zeros on the next line (HEX patterns I
believe).

I KNOW some of you have been able to capture screens with the Sprint
HTC Hero.  If that's the case, let's see some information here to try
and troubleshoot this.  Post operating systems, SDK versions, java
versions, and maybe any identifying things about your HTC Hero (Evdo
Rev. A or 0?  I don't think it'd matter though).

 Here are a few things I've tried:

1. Several different computers.
2. All 3 32-bit Windows Operating Systems.
3. Rebooting the phone while connected to the PC.
4. Removing the HTC USB driver and installing the one included with
the SDK.
5. Factory resetting my phone (in case an app was causing a problem).

I really want to see if this is a common issue.  App developers need
to be able to make these kinds of screen captures, and so do people
who run websites and perform other types of press work.  I know there
are a few programs out there that screen capture if you root your
device.  I haven't really found a reliable guide for rooting the Hero
and I would prefer not to void a warranty here.

--



Other Threads

1. help for chart/graph?

Hi,

Take a look at AChartEngine. Since version 0.6.0 it supports pinch
zoom.

Regards,

Dan


On May 14, 1:41pm, Hitendrasinh Gohil <hitendra.virtuei...@gmail.com>



-- 

2. Crash Reports - ACRA v4 beta started

Hi all,

I had promised it months ago... and it's finally here!

I published one week ago the first beta release of ACRA v4. It finally is a v4, 
because there have been so many changes since ACRA 3.1 that a simple 3.2 
version was just not realistic enough!

The archive can be downloaded here:
http://code.google.com/p/acra/downloads/detail?name=acra-4.0.0b.zip

Some documentation:

   - Setup instructions: 
   http://code.google.com/p/acra/wiki/BasicSetup
   - Advanced usage: 
   here: http://code.google.com/p/acra/wiki/AdvancedUsage
   - Reports fields (old and new): 
   here: http://code.google.com/p/acra/wiki/ReportContent
   - For maven users, a repository is now available: 
   are listed here: http://code.google.com/p/acra/wiki/Maven
   
What are the most significant changes ? Full details are available in the 
ChangeLog (http://code.google.com/p/acra/wiki/ChangeLog) but lets sum this 
up:

   - New data added to reports:
      - logcat: default, events, radio (requires READ_LOGS permission)
      - result of 'dumpsys meminfo' for your application process
      - application version code
      - phone device id (requires READ_PHONE_STATE permission)
      - text events from the system dropbox (requires READ_LOGS)
      - application start date
      - device features
      - report unique id
      - application installation unique id
      - external storage state
      - settings (system and secure)
      - is silent ?
   - As requested by many, a report should only be notified once to the user. 
   Reports which could not be sent due to bad network are still sent but 
   without annoying the user anymore.
   - You can now implement your own Report Sender and do whatever you want 
   with reports data on the device.
   - Basic HTTP Authentification is available for those using the formUri 
   parameter to send reports to a custom script
   - Reports can be sent by a mail Intent, for applications where INTERNET 
   permission is not wanted
   - New SharedPreferences items:
      - include system logs (may contain private data)
      - include Device ID (IMEI) (this a private identifier)
      - include user email (the user inputs his email address in the 
      preference field)
      - always accept sending reports
      - The crash report dialog can now include an email field. The content 
      of this field is saved in SharedPreferences.
   - All android build related fields have been merged in a single BUILD 
   field
   - You can define which fields will be collected and sent. This can 
   improve performance and allow you to get rid of the fields you never read.

Lots of things have been rewritten, so this beta phase will last around a month 
so that we can ensure that there is no major issue using ACRA v4 instead of 
ACRA v3.

As I have really limited time to do deep testing, ACRA relies on your 
testing and bug reports!

Thank you all!

Kevin

-- 

3. Contacting customers via the email address in Google Checkout?

4. Judul Skripsi

5. URGENT!!! The application Samsung Home has stopped unexpectedly

6. Open Source Chart

7. Image Picker and Cropper