Is it possible to print available Intents installed on phone?

by Eric » Thu, 19 May 2011 07:56:46 GMT


Sponsored Links
 I installed an app today that I would like to call out to from my app,
if it turns out the app I installed has a public intent published.  Is
there a way for me to determine this information, either
programmatically or through a facility on the system?   I fooled
around a bit with PackageManager, but it only seems to report on
system-level intents, not installed applications.

In general, I think it would be useful to know all of the public
Intents installed on a phone, and the data-structure those Intents
expect.  I see there's an 'openintents' website, but I'm wondering if
it's possible to check a given phone for available intents?

-- 



Re: Is it possible to print available Intents installed on phone?

by Mark Murphy » Thu, 19 May 2011 08:07:43 GMT


 


You can call queryIntentActivities() or similar methods on
PackageManager to see what responds to a given Intent.


queryIntentActivities() and kin support any Intent, AFAIK. If you have
evidence to the contrary, that's probably a bug, so please post a
sample project and symptoms to  http://b.android.com .


The latter is impossible; the former is merely not supported.


No, sorry.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://github.com/commonsguy 
 http://commonsware.com/blog  |  http://twitter.com/commonsguy 

Android App Developer Books:  http://commonsware.com/books 

-- 


Sponsored Links


Re: Is it possible to print available Intents installed on phone?

by Eric » Thu, 19 May 2011 08:20:30 GMT


 Thank you.

-- 



Re: Re: Is it possible to print available Intents installed on phone?

by Dianne Hackborn » Thu, 19 May 2011 09:26:40 GMT


 Note there is not really a concept of "published intents."  An app describes
intent filters, which match intents.  An intent filter is not an intent --
it is a rule for matching intents.  It generally matches an arbitrary number
of intents, and may be used to specify multiple flavors of an intent
together.  They really only provide information given some intent you
already have, asking whether it matches the filter.







-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

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.

-- 



Re: Is it possible to print available Intents installed on phone?

by MarcoAndroid » Thu, 19 May 2011 18:16:52 GMT


 Not programmatically but you can look here for published intents for
apps:  http://www.openintents.org/en/intentstable 
Maybe the app you refer to is in the list. Else, you could maybe ask
the app builder to add their Intents to that site?





-- 



Other Threads

1. Accessing External Database

Hi folks,

Im new bie to android.. i want to access external database from my
android application..
I've searched so much time in the internet but could not get exact
idea how to implement??

Please help me If any one is having idea on that and post if u have
any code related to it...

Thanks for the information in advance..


Cheers
Uday

-- 

2. GK: Urgent -- Combine all the multiple apks in one APK file

> On Android portal there is option to upload single APK for all

Since I think Mark's answer is clear about the fact that ONE APK = ONE
GAME, and that if you want all your games under one APK, you need to
recombine them all into one single app, that you will ship as one APK,
maybe we just don't understand your problem.

Maybe it as more of a market question : You can upload as many apk as
you like, but one at a time. They will be seen on the market as
several apps. But you are not limited to one game on the market, you
can upload as many as you want, just one at a time.

Yahel

-- 

3. Load Kernel Module

4. Can't connect to SPP device

5. How-To write a custom filter for ListView with ArrayAdapter

6. cannot see my own paid app on the market place?

7. Crashing while playing m4a file.