How to disable NDEF tag discovery permanently in an Android app not just for an Activity?
We have an app that is used to simulate POS terminal, i.e. it communicates with debit/credit cards via NFC.
In all the app activities I am using:
nfcAdapter.enableReaderMode(this,
nfcCallback,
NfcAdapter.FLAG_READER_NFC_A |
NfcAdapter.FLAG_READER_NFC_B |
NfcAdapter.FLAG_READER_NFC_F |
NfcAdapter.FLAG_READER_NFC_V |
NfcAdapter.FLAG_READER_NO_PLATFORM_SOUNDS |
NfcAdapter.FLAG_READER_SKIP_NDEF_CHECK,
null
);
in order to disable NDEF discovery because it interferes with the card communication. It works well, but ONLY in the activity, i.e. when starting new activity or finishing one that was called with startActivityForResult
there is obviously this intermediate state where the OS is sending one NDEF tag discovery message like:
2018-11-14 09:07:11.794 802-3109/? D/NxpNciX: len = 16 > 00000D00A4040007D276000085010100
2018-11-14 09:07:11.794 802-3109/? D/NxpTml: PN54X - I2C Write successful.....
The main problem is that this is not repeatable, i.e. sometimes it happens, sometimes not. This is a big problem.
Is there a way to disable the NDEF tag discovery on app level, not just for activity?
OR
Is there a workaround for this problem?
android nfc ndef
add a comment |
We have an app that is used to simulate POS terminal, i.e. it communicates with debit/credit cards via NFC.
In all the app activities I am using:
nfcAdapter.enableReaderMode(this,
nfcCallback,
NfcAdapter.FLAG_READER_NFC_A |
NfcAdapter.FLAG_READER_NFC_B |
NfcAdapter.FLAG_READER_NFC_F |
NfcAdapter.FLAG_READER_NFC_V |
NfcAdapter.FLAG_READER_NO_PLATFORM_SOUNDS |
NfcAdapter.FLAG_READER_SKIP_NDEF_CHECK,
null
);
in order to disable NDEF discovery because it interferes with the card communication. It works well, but ONLY in the activity, i.e. when starting new activity or finishing one that was called with startActivityForResult
there is obviously this intermediate state where the OS is sending one NDEF tag discovery message like:
2018-11-14 09:07:11.794 802-3109/? D/NxpNciX: len = 16 > 00000D00A4040007D276000085010100
2018-11-14 09:07:11.794 802-3109/? D/NxpTml: PN54X - I2C Write successful.....
The main problem is that this is not repeatable, i.e. sometimes it happens, sometimes not. This is a big problem.
Is there a way to disable the NDEF tag discovery on app level, not just for activity?
OR
Is there a workaround for this problem?
android nfc ndef
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
1
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41
add a comment |
We have an app that is used to simulate POS terminal, i.e. it communicates with debit/credit cards via NFC.
In all the app activities I am using:
nfcAdapter.enableReaderMode(this,
nfcCallback,
NfcAdapter.FLAG_READER_NFC_A |
NfcAdapter.FLAG_READER_NFC_B |
NfcAdapter.FLAG_READER_NFC_F |
NfcAdapter.FLAG_READER_NFC_V |
NfcAdapter.FLAG_READER_NO_PLATFORM_SOUNDS |
NfcAdapter.FLAG_READER_SKIP_NDEF_CHECK,
null
);
in order to disable NDEF discovery because it interferes with the card communication. It works well, but ONLY in the activity, i.e. when starting new activity or finishing one that was called with startActivityForResult
there is obviously this intermediate state where the OS is sending one NDEF tag discovery message like:
2018-11-14 09:07:11.794 802-3109/? D/NxpNciX: len = 16 > 00000D00A4040007D276000085010100
2018-11-14 09:07:11.794 802-3109/? D/NxpTml: PN54X - I2C Write successful.....
The main problem is that this is not repeatable, i.e. sometimes it happens, sometimes not. This is a big problem.
Is there a way to disable the NDEF tag discovery on app level, not just for activity?
OR
Is there a workaround for this problem?
android nfc ndef
We have an app that is used to simulate POS terminal, i.e. it communicates with debit/credit cards via NFC.
In all the app activities I am using:
nfcAdapter.enableReaderMode(this,
nfcCallback,
NfcAdapter.FLAG_READER_NFC_A |
NfcAdapter.FLAG_READER_NFC_B |
NfcAdapter.FLAG_READER_NFC_F |
NfcAdapter.FLAG_READER_NFC_V |
NfcAdapter.FLAG_READER_NO_PLATFORM_SOUNDS |
NfcAdapter.FLAG_READER_SKIP_NDEF_CHECK,
null
);
in order to disable NDEF discovery because it interferes with the card communication. It works well, but ONLY in the activity, i.e. when starting new activity or finishing one that was called with startActivityForResult
there is obviously this intermediate state where the OS is sending one NDEF tag discovery message like:
2018-11-14 09:07:11.794 802-3109/? D/NxpNciX: len = 16 > 00000D00A4040007D276000085010100
2018-11-14 09:07:11.794 802-3109/? D/NxpTml: PN54X - I2C Write successful.....
The main problem is that this is not repeatable, i.e. sometimes it happens, sometimes not. This is a big problem.
Is there a way to disable the NDEF tag discovery on app level, not just for activity?
OR
Is there a workaround for this problem?
android nfc ndef
android nfc ndef
asked Nov 14 '18 at 7:16
OgnyanOgnyan
10.4k34862
10.4k34862
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
1
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41
add a comment |
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
1
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
1
1
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41
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%2f53294909%2fhow-to-disable-ndef-tag-discovery-permanently-in-an-android-app-not-just-for-an%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%2f53294909%2fhow-to-disable-ndef-tag-discovery-permanently-in-an-android-app-not-just-for-an%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
See my answer here: stackoverflow.com/a/36990511/2425802 I don't think there is much you can do about this on affected devices.
– Michael Roland
Nov 14 '18 at 8:37
1
@MichaelRoland Yep, I saw your answer yesterday. I just hoped that someone found a workaround...
– Ognyan
Nov 14 '18 at 8:41