The app also supports basic NDEF Push (Android Beam) for people who don't have any tag to read but happen to have two NFC enabled phones.
The source code of this app is published at https://github.com/nadam/nfc-reader.
Files can be browsed, deleted, downloaded and emailed so you can send the data to your client before leaving the farm.
Note: This app does NOT turn your phone into an RFID reader, it allows you to read BCF OVI-Scan 6 files stored on your NEDAP panel reader via Bluetooth.
- NFC P2P communication between an Android Phone and the AS3911 reader chip.
- NFC Forum Tag Type 4 communication with the AS3953 ISO14443a-4 tag chip
The App is used to upload and download content (URL, images, text).
Please note that you need to create a folder named ams in the local storage of your phone and copy images (PNG) there to enable picture transfer.
Operating Frequency : UHF / HF
Dimensions : 63 x 9 x 88(mm)
Host Interface : Bluetooth
Charge Interface : Micro USB
This is Ceyon Technology's Application for SkyBlu.
SkyBlu is a RFID Reader.
This Application uses Bluetooth to connect to Sky900Blu.
Please send me an email with bug and errors.
Ceyon Technology CO., LTD.
With this app, users will be able to share information of the NFC tags and benefit from convergence opportunities. Many NFC related applications are moving towards NFC enabled smart phones thus enabling mobile payments, asset tracking, digital signage, access control, sharing of digital information, etc. Users will also be able review the data in a personalized NFC Tag and use this information to program their own tags. The analysis of the NDEF based command written on personalized NFC tags can be also be incorporated into their NFC based applications.
We have some known issues with certain devices. We generally classify them as with “Devices with NXP NFC hardware” and “Devices with non-NXP NFC hardware”
NFC TagExplorer on “Devices with NXP NFC hardware”
HTC One (Android v4.2.2)
- The device's antenna drops tags randomly. It reports "Tag Lost" while the read / write operations are being done. This may be due to low battery or voltage to NFC antennae not regulated or something else. We are still trying to understand the issue and would then report this back to HTC One team. We look forward to resolve this issue at the earliest.
- It takes a relatively longer time to read MIFARE Classic 4K due to a higher number of sector authentication and block reads. This has been noticed in all devices. Approx time is about 5-8 seconds to read the full card.
- NFC TagExplorer on “Devices with non-NXP NFC hardware”
Samsung S IV, Nexus 4 & Nexus 7
- The devices have Broadcom NFC hardware
- The Android OS displays the status for MIFARE Classic family tags as "This tag is not supported"
- We have defined a mechanism in our app to mute the MIFARE Classic Read / Write feature in these devices with non-NXP hardware.
App has been tested for error free operations on these devices: Samsung Galaxy S III, Samsung Galaxy S IV, Nexus 4, Nexus 7 and HTC One. While we test our apps thoroughly for errors prior to release, there could be some errors that cause unexpected exit of the application. If you find any such occurrences, please help us by providing a screenshot with some explanation about the tag being scanned and send it to firstname.lastname@example.org. Your assistance in helping us debug specific issues is highly appreciated.
Last Updated: November 01, 2012