Hi Mr. Piren,
Thanks for your helpful suggestion, I will consider your suggestion in
future.
But how can we achieve these native dialer things. if you have any sample
code to do this task please share with us .
On 4 December 2013 13:13, Piren gpi...@gmail.com wrote:
Although i agree with
That i do not know... I wouldn't do it myself as android is designed to
allow that selection and bypassing it at the moment will be a hack.
If anything i wish there was an API to do that since i got stuck in a
similar situation... Personally i think that hijacking the dial-out is
horrible, if
*At first I thought we would just be friends. A little did we know, our
friendship would bend To a love that’s so big for the world to see that you
and me are meant to be. Sun or snow, rain or shine forever, forever you
will be mine Mine for me, mine to be Mine for all eternity. *
On Wed, Dec 4,
While that package name may be correct on the devices you tested, there is
no guarantee that it will be correct on ALL Android devices. Here is an
example from StackOverflow where the OP was having a problem using the
com.android.phone package:
Although i agree with your statement that such an app can be really
annoying, depending on what needs to be done. this might be mandatory.
A good example of that is a number verification process, where the app
needs to verify the phone number used on the device. The best way to avoid
getting
Perhaps you should rethink forcing the user to use the native dialer...
especially where you are hard-coding the package name. Not only is that
just plain bad practice and really annoying for your end user, but the
native dialer may not have the same package name on all devices...
Here is a
Hi Mr. Anderson,
Thanks for your reply,
I think the package name (com.android.phone) is same on all devices as I
checked or debug but the dialer package names are different. As I got this
package name have one OutgoingCallBroadcast class which broadcast the
Intent.ACTION_CALL and android system
7 matches
Mail list logo
