On Wed, Nov 24, 2010 at 1:43 PM, Dan <[email protected]> wrote: > On Nov 24, 9:48 am, Mark Murphy <[email protected]> wrote: >> content://telephony/carriers is not part of the Android SDK. There's >> no telling what it does or does not do on any given device. > > So pretty much outside of contacts, media store, and sync state, > portable programs shouldn't use any other content providers?
Those are the main ones from Android proper. Third parties might have documented and supported content providers. Now, frankly, I've been somewhat stumped as to why android.provider.Telephony is in this strange state, where it is not part of the SDK yet is critical for various things (e.g., receiving SMS). I've been waiting for this to get cleaned up one way or another, yet I still wait. > And since I already know that the apn extra attached to the > network state change intent is even less predictable than the > content://telephony/carriers provider I'm stumped as to what > is the portable way to find the current apn string. > > Any suggestions? I can barely spell ANP. PAN. NAP. Whatever. :-) I'm certainly not aware of any way to work with the APN values in Android that stays within the SDK bounds. I poked around ConnectivityManager and TelephonyManager and nothing much leapt out at me. -- 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 -- 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
