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. performance when passing background data to ui thread

Hi

I've got an app that spawns of a seperate thread. Parses JSON data into a 
structure. And passes it back to the main thread through a handler. Each 
part of data is sent through the handler individually. That worked fairly 
well with my previous XML parser, as XML parses data while it downloads. But 
JSON doesn't (atleast I haven't found a way to get that working). In either 
way the JSON data is much smaller and much faster to parse.

I've recently added a feature that requires me to load several sources of 
json in parallel, parse in the background, and pass all the data back again 
using a Handler. This is a bit slower than I was hoping.

Would it be faster (and possible) for me to do this:
BackgroundThread extends Thread {
    onCreate (Parent) {
        this.parent = parent;
    }
    onData {
        parent.addParsedData(x);
    }
}

Parent extends ListActivity {
    ListAdapter list;
    onCreate {
       setListAdapter(list);
       new BackgroundThread(this);
    }
    public synchronized addParsedData(data) {
        list.add(data)
    }
}

I'm thinking this won't be thread safe, as ListAdapter is in the parent 
thread. Am I right?
Should I instead inside the listadapter (which puts data in an array) have 
synchronized access to it's items?

-- 

2. Froyo porting, vendor & device folder, and build for a device with tapas

Hello,

i try to build Froyo for a given dev board, but i don't know how to
configure the source tree, especially where should put the board
specific code and the board configuration mkf ile, either in vendor or
device ?

I first put my board specific code and config file in the vendor
folder as:

vendor\cpyname\the_product_1\, with BoardConfig.mk that describe my
board configuration.

I then have vendor\cpyname\product\ with the_product_1.mk to start the
source tree build.

can't build with tapas, when giving product name (the_product_1), i
get an error

build/core/product_configuration.mk
the_product_1 not found.
I also try with the device folder, like:

device\the_product_1\ with BoardConfig.mk,
and device\the_product_1\product\ with the_product_1.mk
tapas give the same result.

Note that first configuration can build and generate image with make
PRODUCT-the_product_1-eng

I also personally find the build process quite obscure and missing
documentation. Please help :)

Lionel

-- 

3. System Bar location and height in Honeycomb?

4. lrzsz on android

5. USB: android gadget: issue in interface_number while using USB CV.

6. NDK Toolchain and "Unknown symbol _GLOBAL_OFFSET_TABLE_" in kernel module

7. PreferenceActivity how to display ListPreference value