I'm stumped simply trying to find out information on the following
intent:

"android.intent.action.SERVICE_STATE"

Now, looking at the naming schema used, it would suggest, since
Android is 'sort of' Java that this would be something found in the
intent class (since action is not a child class) and, while there are
many intents listed there as constants, this intent is not one of
them.

Now, there are other intents, such as:

"android.net.conn.CONNECTIVITY_CHANGE"

This is, shocker, found in the android.net.ConnectivityManager class.
Now, that is still not syntactically matching between intent hierarchy
and class hierarchy, but at least  it's roughly nearby.

The only way I found where SERVICE_STATE was defined was by
downloading the Android Base source code and searching through it.
Bingo, it shows up under "internal\telephony\telephonyintents.java".

What is going on with that?  Shouldn't it be named something more like
"android.internal.telephony.SERVICE_STATE"?

Surely, this is an intent that is meant be used as it is the only
intent I can find mention of anywhere (newsgroups, web, et cetera)
that will notify you of switches in your service state.

Are we not supposed to be aware of when a phone goes in/out of roaming
(as an example)?  If we are, why is this not documented?

How do I find out what is bundled with intents like this (for example,
how do I know if it is roaming that changed if I catch this in a
broadcast receiver?  My broadcast receiver won't have the previous
state information, so how do I know what it is that has changed?

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

Reply via email to