Thanks -- dumpsys package gave me what I wanted to know.

For those who may want to do something similar (or just poke around),
"adb shell dumpsys package" dumps info on all the apps/packages on the
box.  "adb shell dumpsys package com.some.package" dumps info on just
the specified app.  Redirecting ("> dumpsys.txt") is recommended, so
you can browse the results in a text file, especially with the first
command above.

On Sep 28, 11:18 pm, Dianne Hackborn <[email protected]> wrote:
> You don't need something that works on the phone.  Just pull the .apk you
> are interested in and run aapt on that.
>
> Or use the package manager APIs.
>
> Or use the Intent flag to turn on the resolver log debug output to see how
> it is matching the intent you are trying to launch against the possible
> targets.
>
> Or you can use "adb shell dumpsys package" to see the top-level maps of the
> resolver tables for the various components (though that doesn't supply
> details of all of the attributes of each filter).
>
>
>
> On Tue, Sep 28, 2010 at 7:07 PM, DanH <[email protected]> wrote:
> > What I'm interested in mostly is figuring out why certain apps already
> > installed on the phone that are supposed to be "listening" for certain
> > file types don't seem to be doing so.  So I need something that works
> > on the phone, on any app, not just my own.
>
> > It looks like I MIGHT be able to muddle my way through starting from
> > PackageManager, but it seems like the sort of thing someone would have
> > written a tool for.
>
> > On Sep 28, 6:34 pm, Dianne Hackborn <[email protected]> wrote:
> > > aapt dump xmltree <path-to-apk> AndroidManifest.xml
>
> > > Or if you have it running in the system, you can use PackageManager to
> > > interrogate most of the stuff the system knows about it.
>
> > > On Tue, Sep 28, 2010 at 4:22 PM, DanH <[email protected]> wrote:
> > > > Is there any way (and preferably a pre-existing tool) to view the
> > > > external features of an app, in particular the MIME types an activity
> > > > supports?
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > > > Groups "Android Developers" group.
> > > > To post to this group, send email to
> > [email protected]
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<android-developers%[email protected]>
> > <android-developers%[email protected]<android-developers%[email protected]>
>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/android-developers?hl=en
>
> > > --
> > > Dianne Hackborn
> > > Android framework engineer
> > > [email protected]
>
> > > Note: please don't send private questions to me, as I don't have time to
> > > provide private support, and so won't reply to such e-mails.  All such
> > > questions should be posted on public forums, where I and others can see
> > and
> > > answer them.
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]<android-developers%[email protected]>
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to