Dev Tools Documentation?

by polyclefsoftware » Tue, 10 Nov 2009 06:57:16 GMT

Sponsored Links
 Is there any documentation on the Dev Tools app that is incorporated
into the AVDs?


Dev Tools Documentation?

by Lance Nanek » Tue, 10 Nov 2009 07:48:01 GMT

 Some of the options in it are described here: #additionaldebugging


Sponsored Links

Dev Tools Documentation?

by polyclefsoftware » Tue, 10 Nov 2009 09:59:32 GMT

 Thanks for the pointer, Lance.

However, I was more curious about some of the other items in the app,
in particular Google Login Service and what looks to be new in 2.0,
AccountsTester. These tools don't do a whole lot of good if we don't
know how to use them and there's no documentation. It sounds like the
AccountsTester might be useful in testing the new AccountManager API,
so it would be nice to know how it's supposed to be used. Why couldn't
they just include a help file in the menu options?

Anyway, if anyone comes across anything, or figures out how to use the
AccountsTester on their own, please share any info.


Dev Tools Documentation?

by jotobjects » Wed, 11 Nov 2009 04:02:01 GMT


Hey who need documentation?  It's more productive for several hundred
thousand developers to read the source and reverse engineer how things
are supposed to work (wink, wink, irony).


Other Threads

1. Reason for Monkey crash

Hi All,
Please tell me how to analyse monkey log,to find out reason for monkey
stop,when the monkey abruptly stops while injecting events and no
crash is found after that.


2. abort()-ing HttpGet requests in ThreadSafeClientConnManager


I have an http client based on multi-threaded model of apache http
components in my App. And I want to achieve spontaneous cancellation
of http get requests from my Android app.

A new executor thread is started for each http request and the Thread
and the HttpGet is saved in a thread safe queue. When abort is
requested (on pressing back on the progress dialog and when starting a
new activity) - another thread is started which goes through the queue
of Threads and HttpGet and attempts to terminate them (code below).

While the HttpGet gets aborted successfully, the Threads go into
'native' state. They only time out giving SocketTimeoutException after
a default interval. The threads end up this way on most cancellations.
Is this something to be expected or I am hitting a bug?

The issue is that And as soon as 2 threads enter this state, all
further executor threads go into wait. Only when either of the 2
blocked threads time out, other executors get a chance (this seems to
be the default behavior of http). I have have tried many different
thing but I am unable to budge the 'stuck' threads.

I think the problem can be easily overcome by increasing the total no
of threads and threads per host -- but I am not sure if this will be a
correct thing to do (because the socket resources will stay occupied
till timeout and there is nothing theoretically that can stop a user
to do infinite cancellations)? Even if this is -- for Android, what
should be the number?

Now I am also doubting if my abort strategy is flawed. Can anyone
please commentor let me know of a fool-proof abort strategy?

- - -

Run method of the abort thread is like:
public void run() {
                        while (!stopQueue.isEmpty()) {
                                final List<Object> stopRequest = 
                                HttpGet abortRequest = (HttpGet) 
                                Thread abortThread = (Thread) 

                                // first abort the request
                                if (abortRequest != null && 
!abortRequest.isAborted()) {

                                // if the thread is still stuck -- interrupt it
                                if (abortThread != null && 
abortThread.isAlive()) {



3. child activity does not "finish()" correctly

4. Not able to fecth android coomponents repository through avd manager

5. Calling localhost web service from emulator

6. Calling localhost web service from emulator

7. My reasons not to carry a cell phone