NFC Ring Control - NOT NFC RING
-
@yash now you've confused me... is one side of the ring not readable/writable or do you have problems with getting the verification code for the unlock app (registration in the NFC control app)?
-
I'm also having issues with the Ring Control App telling me my ring is not an NFC ring. Emails to support tell me I have to use the forums, yet the forums tell me to email support.
How do you fix this problem?
What does the account/password have to do with the control app / NFC ring?
What is the setup process (the paper I got just says to follow the on screen instructions, but the "instructions" are just explaining what each section in the app does, not how to do initial setup)Phone version: SCH-I605 (Samsung Galaxy Note 2)
The ring is the Titanium ring with transparent bottom/black top.
I was a kickstarter backer but the original ring was the wrong sizeTag info is reporting the following:
Info:
IC manufacturer is NXP Semiconductors
IC Type is MIFARE Ultralight (MF0ICU1)Extra
64 bytes total memory
16 pages with 4 bytes per page
48 bytes user memory (12 pages)When I scan the ring outside of the control app I get a "New tag scanned" window that has "Empty tag" on it.
How is this fixed?
-Bryan -
@bbushvt the NFC Ring should show up as an NTAG203, with 137 bytes available.
Is the replacement ring from the nfcring.com web shop? -
It was a replacement ring, how do I fix this issue?
-
Also where should I see NTAG203 and 137 bytes available?
-
Where you're currently seeing mifare ultralight and 64 bytes.
Original NFC|Rings don't actually use mifare, they use an NTAG203 so that's a touch confusing.
Reckon you could take a screenshot of the NXP taginfo data for me? -
Here is a link to the screenshot
-
ok, that's not a replacement ring from http://store.nfcring.com/
Which website did it come from? -
The original ring I received was for being a kickstarter backer. When I received it I had picked the wrong size so I returned it using the instructions found here
http://nfcring.com/returns/
I paid the admin return fee and mailed the original ring toReturns @ McLear Ltd,
158 evergreen rd,
boulder creek, CA 95006, United StatesA few weeks later I received the replacement ring from
McLear Ltd
Newby School House
Ryan Street, Bradford
BD5 7QD
UKThrough out the process I was emailing support@nfcring.com, and they directed me to this forum for help.
-
I have seen the rings register as "MIFARE" issue when something goes wrong, I think it's due to a partial IC detach or lack of coupling.
The best thing to do is return the ring again and let us take a look however I'm going to get you to do some tests before we send it back for a replacement.
- Can you consistently get the same read across multiple devices?
- Have you tried doing an "Clean" in NXP Tag writer? If not, please try that, it should fail.
- Does your ring work? As in can you use it for reading/writing to?
-
Apologies, @bbushvt. I've never seen that happen before!
Thanks, @johnyma22 for clearing that up for us. -
@johnyma22 said:
I have seen the rings register as "MIFARE" issue when something goes wrong, I think it's due to a partial IC detach or lack of coupling.
The best thing to do is return the ring again and let us take a look however I'm going to get you to do some tests before we send it back for a replacement.
Do I just send the ring back to:
Returns @ McLear Ltd,
158 evergreen rd,
boulder creek, CA 95006, United StatesDo I need to include anything along with the ring?
- Can you consistently get the same read across multiple devices?
I only have one phone that has NFC is the Galaxy Note II.
- Have you tried doing an "Clean" in NXP Tag writer? If not, please try that, it should fail.
It failed the first time, but after doing #3 it no longer fails
- Does your ring work? As in can you use it for reading/writing to?
I appear to be able to read/write to both the transparent and black sides of the ring.
-
Sounds like cleaning it has fixed it then? No need to return if that's the case...
-
Ok, new phone, app is still telling me its not an NFC ring when I try and register.
Exact message is "Uh oh This might not be a genuine NFC Ring, please try the other side of your Ring"
When I try the other side, same message. Also this message appears multiple times, this time it was 16 times (the number appears to go up each time I test the ring" Other applications (NFC Tag Writer) can read the NFC tags on the ring. Why does the app not think my ring is genuine? Please fix your app!