How to test if app is shown on Market for all screensizes

by Marcus » Fri, 27 Nov 2009 22:48:53 GMT

Sponsored Links
 Same with me.

App uses Camera, but is not copy protected.

supports-screens entries in manifest are there and "true".



Other Threads

1. Not sure where to find out how to do this - the "Busy" spinning icon

I have been doing searches for this on Google but I am obviously using
the wrong words to look for it. How does one go about showing the icon
that spins in the upper right hand corner of the screen while
something else is going on?

I was trying to call it a "Spinner" but that is not exactly what it's
called in Android... and then I tried "Busy Icon" and nothing useful
pops up... I tried a few other things but for some reason I am drawing
a blank as to what the real term for it is...


2. some questions about using gdbserver and JNI libraries

I have similar issues as you do. Especially this part is worrying:

warning: .dynamic section for "/build/m2/out/target/product/generic/
symbols/system/lib/" is not at the expected address (wrong
library or version mismatch?)

Fadden, I used the gdbclient to help me set up both host and target
side. I still get the above issue when I'm debugging programs/
processes in the emulator (haven't tried on real device yet).

Some additional questions:
* Would anybody know if the last build settings (to be used by the
gdbclient shell-function i.e.) are somehow remembered? I.e. which
target was built and with which tool-chain e.t.a.. As Michael pointed
out, there's two versions of pre-built tool-chains and one might have
multiple targets.

* Could the configure used by gdbclient shell-function safely be
changed? Say that you have two different targets and you would want to
use the gdblient to debug either one or the other. Could you then run
choosecombo to change the settings *without* rebuilding the complete

* In which out directory are the binaries with symbol information to
be used by the AVD's stored? It would make sense to have an out
directory called ./out/target/product/emulator, but the only thing
that makes sense (to me) is out/target/product/generic. What if you've
built a SDK for another target. Would the binaries still be under out/
target/product/generic ?

In my case when I'm for example trying to debug the mediaserver on the

 gdbclient mediaserver :5039  31

What I get in the end is:

gdb: Unable to get location for thread creation breakpoint: requested
event is not supported
__dl__start () at bionic/linker/arch/arm/begin.S:35
35              mov     r0, sp
gdb: Unable to get location for thread creation breakpoint: requested
event is not supported
Current language:  auto; currently asm

Shouldn't --attach just stop the running process? Is this output
nonsense or is the process actually restarting?



3. ScrollView Layout/Gravity Problem

4. Clear Activity stack?

5. SDK installation problems on Vista

6. ScrollView scrolling.

7. android screen locked, service stop?