Which radio are you interested in? Wifi, cellular, bluetooth?
In case of cellular look in the telephony package of android. The package supports a listener PhoneStateListener. For example for listen to Signal strength changes you would use onSignalStrengthChanged(int) Find the API description at http://developer.android.com/reference/android/telephony/package-summary.html Here is a summary of classes supported in the telephony package. Be aware of that Android offers another package specifically for GSM and CDMA (package name is android.internal.telephony.gsm). For being able to use the telephony functionality make sure that you define the needed permissions in your Manifest. • ATParseEx extends RuntimeException and is thrown by methods of the ATResponseParser class • The ATResponseParser class parses part of the AT command syntax used to communicate with the mobile radio hardware in a mobile handset. This is, in fact, a command syntax very much like the AT command syntax used by modems, a standard described in the 3GPP document number TS 27.007 and related specifications. This protocol for controlling mobile radios is widely used. • The Call class is an abstract base class used by other classes as a basis for objects that represent phone calls and the state of those calls. • The CallStateException class extends Exception and is thrown by methods that maintain call state in cases where state is inconsistent. • The CallerInfo class holds information about the party that originated an incoming call. This class starts with called ID information from the mobile network interface and looks up other information about a caller in the database of contacts. • The CallerInfoAsyncQuery class enables asynchronous database queries for information that could be found about a caller based on the caller ID information. • The Connection class is an abstract base class used by other classes and is a basis for objects that represent connections on the mobile network and the state of these connections. Connection objects can be associated with a Call object, but they can also exist independently. The data in a Connection object can be especially useful in diagnosing the reason a call failed. • The DefaultPhoneNotifier class implements the PhoneNotifier interface in order to receive notifications from a Phone object. It then uses the Android service system to communicate state to Activity instance that have registered to receive those notifications. See the Handler and Mailbox classes for information on how to receive notifications. • The IPhoneSubInfo interface us used to obtain subscriber information. • The ITelephony interface defines the inter-process interface used in TelephonyManager to enable applications to communicate with PhoneApp. • The ITelephonyRegistry interface is the callback interrface from the RIL daemon. • The MmiCode interface defines callbacks related to "MMI codes." These are special numbers a user can dial, and key sequences that a user can enter during a call, to access, control, and administer supplementary services, such as call waiting, call hold, etc. MMI codes and related functionality are described in the 3GPP document number TS 22.030. • The Phone interface includes callbacks and methods for accessing the state of a mobile phone. • The PhoneBase class is an abstract base class that implements the Phone interface. • The PhoneFactory class contains methods used to create instances of the GSMPhone class, a subclass of the Phone class. • The PhoneStateIntentReceiver class handles Intect objects that have intent types specified in the TelephonyIntents class. This class enables Android applications to use the Intents system to obtain phone state information. • The PhoneSubInfo class contains methods for obtaining information about a mobile service subscriber such as the unique identifying number for the handset (IMEI), the unqiue identifying number for the subscriber (IMSI), the serial number of the SIM card, etc. • The SimCard interface offers the information in a SIM card. • The TelephonyIntents class defines the constants for Intent types that enable other applications to access information from the Android telephony internals. However, these intents should be used directly by other applications. These are defined in the undocumented internals package because these intents are used by the TelephonyManager class's methods to implement a simpler API for acquiring information about the state of calls, the phone, the network, etc. • The TelephonyProperties class defines the constants used with the SystemProperties class for setting and getting telephony-related properties. In case of Wifi look check out the WifiManager package. Find more information at http://developer.android.com/reference/android/net/wifi/WifiManager.html -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Jun 27, 1:05 pm, craft <[email protected]> wrote: > Is there an URL where I can find documentation on how to get radio > interface stats (signal level, registered BTS's / Node B's in the > area.... ) > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
