Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFC Tag #191

Open
schloempe opened this issue Nov 1, 2018 · 12 comments
Open

NFC Tag #191

schloempe opened this issue Nov 1, 2018 · 12 comments
Labels
bug General label for all bugs (i.e. things not working as intended) Difficulty 1 Good for Contributor: Difficulty Level 1 enhancement Proposal for enhancing existing functions

Comments

@schloempe
Copy link

schloempe commented Nov 1, 2018

I create an event for specified NFC tag id. But phone will always show "new tag" and Easer does not react. How can I make Easer react for NFC tag?

@renyuneyun
Copy link
Owner

Hi,
Could you clarify that a bit more (e.g. through screenshots)? I don't quite follow what you say...

One think maybe worth asking: did you added that specific tag to Easer on the page waiting for an NFC tag?

@renyuneyun renyuneyun added the more-info-needed Needs more input to pin down or solve the issue label Nov 1, 2018
@schloempe
Copy link
Author

Yes I add the tag with button DETECT TAG. This works and shows tag id. But if I touch the tag later, only NFC service comes up and say NEW TAG. Your app is not react to the same NFC tag.
How can I add screenshots here?

@schloempe
Copy link
Author

screenshot_20181102-113608 1
screenshot_20181102-113645 1
screenshot_20181102-113725 1

@renyuneyun
Copy link
Owner

Seems you are configuring correct.
Does your NFC tag has data / payload? #92 is related to this.

@schloempe
Copy link
Author

Yes, #92 looks similar. But as you can see in my screenshot, I did write text AUDI on this tag. Before I tried an application link. Both is not working well. So I do not understand. I write AUDI in this tag, but Android default NEW TAG DETECTED comes up. Why?

@schloempe
Copy link
Author

Do I need special NDEF to launch easer? Perhaps a predefined MIME?

@renyuneyun
Copy link
Owner

Hi,
Sorry for the long delay.

I don't think you need a special NDEF for the card, at least in theory. But currently, if I understand Android's mechanism and NFC correctly, the NFC Event in Easer works with an NFC tag with an unknown category to Android (e.g. a bank card, a staff/student card, which was not supposed to be read by Android).
(Please do correct me if I'm possibly wrong. This may help me figure out the exact problem.)

IIRC, I think this is due to Android's way of dispatching NFC tag information to apps, and Easer didn't handle this well (i.e. some scanned tags are not catched, because they belong to other categories). I should investigate this more.
As you may already be aware, I'm not an expert on NFC-related things (and I'm completely confused what, how and why the different "technologies" are there). So this may take longer than expected...

@renyuneyun renyuneyun added bug General label for all bugs (i.e. things not working as intended) enhancement Proposal for enhancing existing functions Difficulty 1 Good for Contributor: Difficulty Level 1 and removed more-info-needed Needs more input to pin down or solve the issue labels Nov 25, 2018
@schloempe
Copy link
Author

Hi,
I checked it right now. I test with my bank card and it is working fine. But my NFC21 tokens will always come up with "New Task …" So it depends on tokens you are using. But if I want to buy new tokens, what I have to care about? No idea.
Thank you for your time to check and the hint to test other devices.
Nevertheless, if you have a solution or you find a way, I will be thankful if you could write it here.
Have a good time and thanks for developing easer

@ploth
Copy link

ploth commented May 18, 2019

Same here, "new tag collected" always pops up. easer doesn't react to the tag.

@1e-9
Copy link

1e-9 commented May 22, 2019

Hi.

Same problem with NFC-tags:
A tag with ISO-14443-4 works.
These do not work: ISO 14443-3A
(
I bought this ones:
https://www.nfc-tag-shop.de/en/nfc-sticker/black-white-nfc-tags/111/nfc-sticker-20-x-15-mm-ntag-213-180-byte-white
https://www.nfc-tag-shop.de/en/nfc-keyfobs/nfc-keys-pvc/325/nfc-keyfob-30-mm-ntag-213-180-byte-black
)

Works:
works

Doesnt work:
doesnt_work

@ildar
Copy link

ildar commented May 23, 2019 via email

@renyuneyun
Copy link
Owner

renyuneyun commented May 25, 2019

@1e-9 Thanks for providing more technical info!
Unfortunately I don't currently have much time to learn that thing, so the issue is still postponed...

I'll summarise some information here in case anyone is thinking of help:

  • The component (skill) for hendling NFC scanning is in package ryey.easer.skills.event.nfc_tag
  • There is an Activity (NfcListenerActivity) which handles the NFC scan event (dispatched by Android). The types of NFC tag technologies it handles are declared in the corresponding activity element in AndroidManifest.xml
  • Android classifies different types of NFC tags into different technologies, and handles them in a separate flow (refer to Android dev documentation for NFC)
  • My personal feeling is that this Activity should handle more (all) technologies, in the correct way (which I'm not sure how)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug General label for all bugs (i.e. things not working as intended) Difficulty 1 Good for Contributor: Difficulty Level 1 enhancement Proposal for enhancing existing functions
Projects
None yet
Development

No branches or pull requests

5 participants