Android 4.4 problem with start dial from background
I have app what makes calls in some cases(this logic works).
But some time ago I found what on devices with android 4.4 there is issue.
When my app in background and some other app(for instance Chrome) in foreground my app can't make call. After I resume my app it start dialer.
If my app only in background works like a charm.
Other versions works fine(tested on android 5.1.1, 7, 8), only problem with 4.4.
Checked what happens in the ADM, it seems when app in background and other app in foreground my intents are not handling.
I think it is some kind of limitations, but i didnt find any proof of this.
this is my code for calling
public void Call(string phoneNumber)
{
var intent = new Intent();
intent.SetData(Android.Net.Uri.Parse("tel:" + Uri.EscapeDataString(phoneNumber)));
intent.SetAction(Intent.ActionCall);
intent.SetFlags(ActivityFlags.FromBackground);
if (Build.VERSION.SdkInt < BuildVersionCodes.Lollipop)
intent.SetPackage("com.android.phone");
else
intent.SetPackage("com.android.server.telecom");
getContext.StartActivity(intent);
}
May be somebody have any idia why it is like this.
add a comment |
I have app what makes calls in some cases(this logic works).
But some time ago I found what on devices with android 4.4 there is issue.
When my app in background and some other app(for instance Chrome) in foreground my app can't make call. After I resume my app it start dialer.
If my app only in background works like a charm.
Other versions works fine(tested on android 5.1.1, 7, 8), only problem with 4.4.
Checked what happens in the ADM, it seems when app in background and other app in foreground my intents are not handling.
I think it is some kind of limitations, but i didnt find any proof of this.
this is my code for calling
public void Call(string phoneNumber)
{
var intent = new Intent();
intent.SetData(Android.Net.Uri.Parse("tel:" + Uri.EscapeDataString(phoneNumber)));
intent.SetAction(Intent.ActionCall);
intent.SetFlags(ActivityFlags.FromBackground);
if (Build.VERSION.SdkInt < BuildVersionCodes.Lollipop)
intent.SetPackage("com.android.phone");
else
intent.SetPackage("com.android.server.telecom");
getContext.StartActivity(intent);
}
May be somebody have any idia why it is like this.
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37
add a comment |
I have app what makes calls in some cases(this logic works).
But some time ago I found what on devices with android 4.4 there is issue.
When my app in background and some other app(for instance Chrome) in foreground my app can't make call. After I resume my app it start dialer.
If my app only in background works like a charm.
Other versions works fine(tested on android 5.1.1, 7, 8), only problem with 4.4.
Checked what happens in the ADM, it seems when app in background and other app in foreground my intents are not handling.
I think it is some kind of limitations, but i didnt find any proof of this.
this is my code for calling
public void Call(string phoneNumber)
{
var intent = new Intent();
intent.SetData(Android.Net.Uri.Parse("tel:" + Uri.EscapeDataString(phoneNumber)));
intent.SetAction(Intent.ActionCall);
intent.SetFlags(ActivityFlags.FromBackground);
if (Build.VERSION.SdkInt < BuildVersionCodes.Lollipop)
intent.SetPackage("com.android.phone");
else
intent.SetPackage("com.android.server.telecom");
getContext.StartActivity(intent);
}
May be somebody have any idia why it is like this.
I have app what makes calls in some cases(this logic works).
But some time ago I found what on devices with android 4.4 there is issue.
When my app in background and some other app(for instance Chrome) in foreground my app can't make call. After I resume my app it start dialer.
If my app only in background works like a charm.
Other versions works fine(tested on android 5.1.1, 7, 8), only problem with 4.4.
Checked what happens in the ADM, it seems when app in background and other app in foreground my intents are not handling.
I think it is some kind of limitations, but i didnt find any proof of this.
this is my code for calling
public void Call(string phoneNumber)
{
var intent = new Intent();
intent.SetData(Android.Net.Uri.Parse("tel:" + Uri.EscapeDataString(phoneNumber)));
intent.SetAction(Intent.ActionCall);
intent.SetFlags(ActivityFlags.FromBackground);
if (Build.VERSION.SdkInt < BuildVersionCodes.Lollipop)
intent.SetPackage("com.android.phone");
else
intent.SetPackage("com.android.server.telecom");
getContext.StartActivity(intent);
}
May be somebody have any idia why it is like this.
asked Nov 20 '18 at 14:11
Dmitry ZinovievDmitry Zinoviev
328313
328313
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37
add a comment |
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394901%2fandroid-4-4-problem-with-start-dial-from-background%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394901%2fandroid-4-4-problem-with-start-dial-from-background%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you please post more detailed codes? or maybe share a basic demo that can reproduce the problem through online repo?
– York Shen
Nov 21 '18 at 5:37