Long term, for most tablets, android.hardware.telephony with <uses-feature> or hasSystemFeature() on PackageManager should work.
Some Android 2.x tablets, like the Galaxy Tab, may claim to have telephony even if they do not have a dialer, in order to qualify for the Android Market. Short of using android.os.Build to identify these by manufacturer and model, I do not know how else you can tell. On Sun, Apr 3, 2011 at 1:34 PM, ole! <olub...@gmail.com> wrote: > I have not been able to detect whether a dialer executes correctly on > a tablet. > The ACTION_CALL intent does nothing. > The problem arises on the T-Mobile Galaxy, but I suspect other tablets > have the same problem. > > What I have tried: > 1. catching an exception from start_activity using the ACTION_CALL > intent (no exception generated) > 2. TelephonyManager.getPhoneType() returns a valid state (GSM) > 3. TelephonyManager.getCallState() return a valid state (IDLE) > > Any ideas? > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.3 Available! -- 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
