Store a tag without writing it

[mclear]

Store a tag without writing it

[xxv]

If it supported unlocking just based on RFID, I'd be able to use my Charlie Card (subway system card; Mifare Classic, fully-locked). That'd be a great backup in case something happened to my ring, as I keep it in my wallet.

[r2DoesInc]

This is not possible. I had a thought a while back when this was mentioned to basically create a third party nfc handler that would allow multiple records worth of data to be written to the tag inside one actual record. The app would then split that record and parse the data into its corresponding records allowing somthing like this to work, but that is a discussion for another time. This is not possible with the current technology and apis we currently have.

[JohnMcLear]

Ugh, Everything is possible, please never say "This is not possible" to me, that's my least favorite saying in the world.. I agree it's a bigger job though than what we have the resources for right now so I will leave this open but as an enhancement request.

[xxv]

If the app is in the foreground (e.g. the lockscreen is showing), it can listen for any and all NFC interactions. See https://github.com/xxv/rfid_front_door/blob/master/src/TagScanner/src/info/staticfree/android/taguid/TagUidActivity.java#L206 for an example of how to do it.

[r2DoesInc]

No, I'm sorry but it is not possible. Mimetype MUST be written to the tag,
otherwise the app will not be launched. There is NO way around this.
Services CANNOT register an nfcadapter to listen for foreground tags,
meaning that they MUST be triggered another way. The mimetype on the tag
triggers an activity launch that triggers the actual unlock.

This is not possible with the way the OS currently functions.

On Fri, Jan 10, 2014 at 10:42 AM, John McLear [email protected]:

Reopened #21 #21
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

[xxv]

Ah, gotchya. Not having the lockscreen as an activity would certainly add all sorts of limitations on what you can do, so I see the challenges you need to work around here.

[ententeak]

so.. why can Tasker with "NFC Locale" plugin work without writing any data to tag, just by reading his ID ? (For example)
I'm using this almost half year with Samsung Tec Tiles with my own data writen on them..
One screen is from Tasker, the second one from NFC Reader...

and i'm using third party program - Tag Writer by NXP - to write data

[r2DoesInc]

These are completely different applications that function in absolutely
different ways. Behavior between the two apps will not be analogous.
On Jan 12, 2014 1:10 AM, "ententeak" [email protected] wrote:

so.. why can Tasker with "NFC Locale" plugin work without writing any data
to tag, just by reading his ID ? (For example)
I'm using this almost half year with Samsung Tec Tiles with my own data
writen on them..
One screen is from Tasker, the second one from NFC Reader...
[image: 2014-01-12 06 07 55]https://f.cloud.github.com/assets/6324786/1895671/140c26c2-7b50-11e3-89cd-9251583ed824.png
[image: 2014-01-12 06 07 40]https://f.cloud.github.com/assets/6324786/1895672/140de570-7b50-11e3-82cc-aac6f12132d4.png

and i'm using third party program - Tag Writer by NXP - to write data

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-32116196
.

[ententeak]

sorry, but i dont understand why is problem reading "Tag ID" instead of writen data. It's just different variable to call from the tag/ring

[r2DoesInc]

The tag id is used. Data written to tag is mime type data. Again, the
differences are vast and the behavior is not comparable.
On Jan 12, 2014 7:45 AM, "ententeak" [email protected] wrote:

sorry, but i dont understand why is problem reading "Tag ID" instead of
writen data. It's just different variable to call from the tag/ring

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-32121672
.

[jasok2]

Plus 1 for this feature if its ever possible :)

[r2DoesInc]

this feature is not possible.