Related
So was anyone able to scan any NFC tags?
some stores has NFC payments enabled, some movie posters or stuff like that has NFC chip build in
in some countries there's NFC tickets for the bus/subway
so, it all really depends how popular or not it's in the are where you live
not even all USA cities are that high tech
I've heard that NYC taxis and some pharmacies and such there support NFC. But I've also heard that the phone's software isn't really setup to use the NFC yet. I know that Sprint and the Google Nexus S 4G have Google Wallet hooked up to their NFC.
I don't know that TMO has a deal with Google Wallet. Are they part of that Isis group?
I've successfully scanned my SFO Clipper card which uses NFC. Pretty cool.
The venture is now developing provisioning systems that will allow existing payments services to be added to any NFC phone owned by a subscriber to any of the Isis founder's mobile networks, says Johnson — and Isis already has a number of banks ready and willing to pay for this service. "When we launch next year we will launch with multiple banks," he explained.
http://www.nfcworld.com/2011/05/24/37652/isis-sets-out-new-nfc-strategy/
I've been testing krohnjw's NFC Task Launcher app. I must say it's pretty damn awesome! It lets you set tags up for doing different tasks. I'll make a video sometime, he has some on his development page. You can set a tag to enable wifi, for example. One idea I had was to use his app to set your phone to toggle bluetooth when you place the phone in your car dock for example. Very neat stuff!
http://forum.xda-developers.com/showthread.php?t=980741
https://market.android.com/details?id=com.jwsoft.nfcactionlauncher
mziol said:
I've been testing krohnjw's NFC Task Launcher app. I must say it's pretty damn awesome! It lets you set tags up for doing different tasks. I'll make a video sometime, he has some on his development page. You can set a tag to enable wifi, for example. One idea I had was to use his app to set your phone to toggle bluetooth when you place the phone in your car dock for example. Very neat stuff!
http://forum.xda-developers.com/showthread.php?t=980741
https://market.android.com/details?id=com.jwsoft.nfcactionlauncher
Click to expand...
Click to collapse
Cool stuff, time to buy some NFC tags.
http://www.tagstand.com/
http://www.buynfctags.com/
http://www.tagage.net/
I'm still looking for the best price on cheap tags to mess around with. I've also read there is some confusion around the net as to which tags will work with our phones/phones in general.
NFC Tags, what works, what does not
I've got two TMO SGS2s, so I did some NFC testing the other night. Here is what I found:
1) Creating a text tag works. Reading it from another phone works. But when read, it put the text into a new post in the Google+ app. Not really what I imagined wanting to do with an NFC tag that I read.
2) Sharing Google maps locations over NFC seems to work. But again when reading the tag, the text and URL is opened up as text in a new Google+ posting.
3) Web page URLs. I used Dolphin HD to share a few web pages. Reading the tag properly brought up the website. This one feature seems to be more or less fully operational.
4) Sharing contacts over NFC did not appear to work at all. It is an option when creating a new tag in the Tags app, but we couldn't get it to work for any type of contact.
Are you able to read arbitrary RFID tags using the T-Mobile Galaxy S 2? I've tried on several different types of RFID tags with no success (NFC was indeed enabled when I tried):
-Passport
-Building entry badge
-DC Metro SmarTrip card
I've tried using the included "Tags" application, in addition to "NFC Reader" and "NFC TagInfo".
Oddly enough, I stopped by my local T-Mobile store, and the representative told me that he was unable to transfer URLs or random tags (or contact information, as you stated) between two Galaxy S 2 devices, or between a T-Mobile Galaxy S 2 and an HTC Amaze. (We then played around with the devices a bit in an attempt to get something working, but to no avail.)
Splaktar said:
I've got two TMO SGS2s, so I did some NFC testing the other night. Here is what I found:
1) Creating a text tag works. Reading it from another phone works. But when read, it put the text into a new post in the Google+ app. Not really what I imagined wanting to do with an NFC tag that I read.
2) Sharing Google maps locations over NFC seems to work. But again when reading the tag, the text and URL is opened up as text in a new Google+ posting.
3) Web page URLs. I used Dolphin HD to share a few web pages. Reading the tag properly brought up the website. This one feature seems to be more or less fully operational.
4) Sharing contacts over NFC did not appear to work at all. It is an option when creating a new tag in the Tags app, but we couldn't get it to work for any type of contact.
Click to expand...
Click to collapse
I haven't tried reading any physical tags. Only between 2 different NFC enabled phones.
I did a whole bunch of research with the Nexus S NFC reader - and so far as I can tell, the SGSIIX has the same capabilities.
I have a bunch of blank 1K, 4K and Ultralite MiFARE tags that are AWESOME to play with. Even just putting your contact card on there, or URLs (you can do anything with a URL) is tons of fun to play with. They don't read proprietary NFC implementations without special software - only tags encoded with an NDEF structure will be automagically picked up by Android.
The good stuff is coming up - I'm 98% sure that Zoompass is coming out with an Android app compatible with the QuickPay/Interact-Flash readers. Next year, pay for small crap with your phone!
BT Tag Writer is application that offers you way to add NFC pairing to your old Bluetooth speakers. NFC pairing allows you to pair, connect and disconnect the device just by tapping the NFC tag with your phone. This application is still under development and this thread can be used to request changes and new features for this application.
Market: https://market.android.com/details?id=fi.siika.bttagwriter
Video: http://www.youtube.com/watch?v=IbuLGsXIvKI
--- original first post ---
Hello everybody.
I have been now writing application for Android devices with NFC capabilities. It basically offers wizard interface for writing new NFC connectivity tags for your Bluetooth speaker(s)/headset(s)/etc. And software that will take care of the actual pairing/connecting, when you tap the tag with your phone. NFC pairing is something Nokia does with N9 and it's Bluetooth speakers, but it looks like Android still doesn't handle this well out-of-the-box. Also I still haven't found easy to use connectivity tag writers for any devices.
Sort demo of application in it's current state: Check youtube video kzoG5VM6VcU (can't have this as a proper link, as I only have less than 8 posts to this forum, sorry)
Before I release this software to market, I would like have some people testing it with their speakers and devices. I really hate alpha level software in market. If you have Galaxy Nexus, some sort of Bluetooth speaker(s)/headset(s) and hopefully some writable NFC tags, and you would like to help me to get this software tested: Please tell it here. I still have some small things to resolve before this is ready for closed testing. If you like to help me to get this tested please also tell what sort of Bluetooth device you have and what NFC tags you have available.
I will most likely release this software as free (gratis) and probably in open source (don't know the license yet). So I am not planning stealing your time and then making money out of it. Only thing I can offer to you is to add your name to application's thanks list.
Also if you know software that already does all this, please tell. If my software does not bring anything new, I have to redesign it little bit.
Thanks.
I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...
i would test as well buddy!
s60mike said:
I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...
Click to expand...
Click to collapse
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
S suxeN said:
i would test as well buddy!
Click to expand...
Click to collapse
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.
Northernmost said:
I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.
Click to expand...
Click to collapse
I will fix few annoying things and then will put link to debug apk-file here (maybe Wednesday). I will try to see if I can make it run in 2.3.5+ too. Anyhow software will be limited to Mifare Ultralight tags (original and C versions). I have to buy other type tags to see what I can do with those, but that's later. Common Ndef writer classes does not work at all with Android or then I'm doing something wrong.
Android also really limits clean ways to do intents for more complex tags. So these tags software now writes are not proper connectivity handover tags. Just the core part of those is used and stored as single NDEF mime item and then this app is marked to handle those NDEF messages/records. Positive side with that is of course that information fits to smaller tags. Also PIN code storing will be probably done little hacky way to the first version.
alump said:
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...
s60mike said:
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...
Click to expand...
Click to collapse
So many different Mifare tags out there. Mifare Classics will not work (for now).
Anyway, pushed software to market after all. In few hours you should be able to find it from there. Offer still stays, if you can try it out and report issues here it would help. I had to drop headset support for now as it didn't work as well as I hoped.
Great! Will try it out today. Here's the market link https://market.android.com/details?id=fi.siika.bttagwriter
Sent from my Galaxy Nexus using Tapatalk
alump said:
Mifare Classics will not work (for now).
Click to expand...
Click to collapse
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) Back when I was on 2.3.7 there was a Bluetooth A2DP widget I used (can't remember the exact name now) that, when you created the widget, would display a list of already paired devices that supported the A2DP profile. Once you'd picked one the widget would attempt to connect to it automatically.
I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with. It's a small thing to do I know, but I'd imagine most users will have already paired with their speakers before ever finding your app. I don't know if you can enumerate paired devices supporting the A2DP profile in ICS though.
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
3) It looks very nice!
Northernmost said:
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) ....I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with...
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
Click to expand...
Click to collapse
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
2. I have seen "no name" issue only once. But yes, that's "stack problem"... I hope
Anyway I think I have to try to add Mifare Classic support first.
alump said:
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
Click to expand...
Click to collapse
Sorry for spam, but finally this will be mine 8th post
Request to list already paired devices is now added to Market version (0.3). So no need to turn already paired devices to pairing mode when writing tags.
Support for other than ultralight Mifare tags might take some time. Thanks to keys etc those tags are not ideal for this use. I think I will try to add headset support first.
Just to confirm that 0.3 is listing my paired A2DP devices
alump said:
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Nexus S, running Brainmasters ICS 4.0.3
Bluetooth devices:
2 headsets
another Xperia ArcS
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!
S suxeN said:
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!
Click to expand...
Click to collapse
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores
alump said:
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores
Click to expand...
Click to collapse
Okay, ima gonna order some and report back to u
music auto start
is there a way to make it so that my music app doesn't auto play my most recently played track when the BT connection is made ... id like for it to simply open the app
Hi there,
right now I am researching for a possibility to emulate a smartcard with a smartphone. As we all know, the standard os and api won't let us do this. What I want to achieve is create a way to use the smartphone for physical access without the need to change the existing infrastructure. o achieve that, the smart phones gets a localy and time limited informationtoken it should present to the reader. In other words, I actually dont realy need access to the secure element, as any data would be temporary.
Right now I am a bit confused about this. Is there a way to use card emulation, without the need of a secure element? I have searched for different ways to acchieve this, but on many ends, I can't seem to find a definitv answer.
For example I stumbled on OpenNFC. They praise that they can acchieve card emulation. Yet, they don't provide any examples on this and fail to actualy deliver some sort of information on the requirements of this. As I understand it, it seems like this method only works when the smartphone uses Inside Secures Chips MicroRead or SecuRead. Anyone knows more about this?
I'm realy open to ideas on this one, as it seems theres little to no documentation or examples to go on.
I'd realy be happy to read about what you guys found out on this issue as of yet.
I've been looking into it too. This is what I have found:
EddieLeeDefcon20.pdf
nfcproxy
(Google them, I can't post links)
So, yeah, it can be done, but you have to modify android to be able to.
I ended up to OpenNFC too, but no sample code!
I have a good background on Mifare Classic 1K and 4K programming using RFM130 under linux and win.
Sent from my HTC One X using Tapatalk 2
Ok, so after browsing the mailinglist like a maniac I found this answer from one of OpenNFCs developers:
Hello,
The OpenNFC stack porting on Android complies to the Google API, as far as the applications are concerned.
Since these API do not allow an APK to do card emulation, it is not possible to use this mode on the Nexus,
nor on any Android phone, with or without OpenNFC.
However, OpenNFC provides card emulation feature for other porting (Win32, linux), depending on the hardware capabilities.
Kind regards,
Stephane
Click to expand...
Click to collapse
Source is on their mailing list on sourceforge, cant post link....
So seems we can forget this one... Only option would be using the Cyanogenmod patch that is used by NFCProxy.
When this message has been posted? I think things has changed (not sure)
Anyway, I posted a message yesterday to have more informations about their projects on Android
The Message is from March 29th, 2012.
Again as I said, if that has changed, they really have to work on their communication to the outside. There seems to be noone but the devs that can say anything about this. And that means quite a lot.
When there is no API for something, we can use native code and directly communicate to NFC hardware. Agree?
Sent from my HTC One X using Tapatalk 2
Well, the way I understand it is, that we could take a build of android and tinker with it to get it to work. We would have to change the NFC softwarestack and its interaction with the rest of the system in order to make software emulation possible. That is quite some pile of nontrivial work to do if you ask me.
Sorry for doing a new reply instead of editing the old one, but I think this is interesting enoug to not get overread.
I got an answer from the OpenNFC Developerteam regarding my question. Part of my question was also if it was possible to emulate for example a Mifare Tag through their NFC Stack. Here is the answer:
Hello XXXXX,
The Open NFC stack is designed to be largely hardware-independent, with a small adaptation module (NAL) for each hardware chipset. However, currently we only provide the NAL module for the MicroRead / Securead chipsets; therefore out of the box we are only compatible with these chipsets.
It is possible to emulate ISO 14443-4A and -4B cards and Type 4 tags from the Open NFC stack; for emulation of MiFare Tag, you’d indeed need to use a Secure Element.
Best regards,
Sebastien.
Click to expand...
Click to collapse
Hope this clears some questions regarding OpenNFC.
NFC-AAAC or NFC Assisted App Access and Control
Pretext:
I have 2 children under the age of 3, all of their content (audio/video) is digital accessed. This created a disconnection for them, as they are not able to play /change the content unless my wife or I change it for them. I know there is an interest for them to be able to change the content themselves as when we have Netflix or Pandora open on the touch enables screens they are all was trying to pick the show/music they like. The few places where they do have a physical medium to play content,
The DVD player/CD player (note we have it backed up digitally), there is much interest with the “desk”. The kids would love nothing more to remove and replace it over and over. Watching this behavior over some time has lead me to believe that a simpler solution would/could be doable.
This brings me to NFC tags, with a few add-on programs the NFC tag can be scripted to perform most complicated input tasks.
Goal:
To provide access to complicated tasks via NFC.
To allow a person of limited physical input abalaty to use smart phone tech.
This can include, the disabled, the young, the old. To allow access to tasks/apps while driving or when attention is needed other places.
Current Scope:
Create tags for a radio station that can be quickly taped to change station/play album.
( Keeping the driver form looking at their phone while driving). Create tags that auto play Netflix/Amazon Prime/YouTube/Google +/etc videos.
This may include second screen casting Create tags to autolaunch/call via Skype/cell phones
Want to call grandma? Or have grandma get on Skype, etc. Create tags to attach to things around the house foods/shapes/flashcards etc.
When was this put in the fridge?
Send text to let people know the item is all gone etc.
What was this called.
Call support.
Where I'm at:
I'm currently gathering URIs / intents for the tasks described.
I will be using a combination of the “NFC task launcher” and “Tasker” to complete the tasks.
I will be following up with more detailed guide on how to set up functions/tasks.What I am looking for:
Help locating the URI / intents to call to complete tasks.
More tasks, Do have someone you know / you yourself finding something more complicated than it should be let me know and we can discuss how to fix.
Current URI list
Note Most if not all the URIs are undocumented aka may stop working, I will try to keep the list up-to-date. Please let me know if any stop working.
Pandora:
Add/Play station: pandorav2:/createStation?stationId=<stationId>
Netflix:
Play Tv Show: nflx://www.netflix.com/Browse?q=action%3Dplay%26movieid=http://api.netflix.com/catalog/titles/series/<ShowID>Play Movie: nflx://www.netflix.com/Browse?q=action%3Dplay%26movieid=http://api.netflix.com/catalog/titles/movies/<MovieID>
Skype:
Audio Call User: skype:<SkypeUser>?callAudio Call Phone / Moble: skype:<Phone#>?callVideo Call: skype:<SkypeUser>?call&video=true
YouTube:
Play Video: vnd.youtube:<VideoID>
Mmm, interesting.
Bye!
! !
interesting ... how did you discover the uri to launch apps with arguments?
I also used a custom URI and NFC Task Launcher to launch my app "Badge NFC" and store custom data inside the app database (look at my signature to get a playstore link) ...
furius said:
how did you discover the uri to launch apps with arguments?
Click to expand...
Click to collapse
All of the custom URIs prefixes are in the apps manifest.
If I'm lucky I can simply type it into google and find someone else that's done the work, (to get the data argument)
If not I used JD-GUI to look over the source code to trace the Android Intent path and see what the app is looking for.
Another way is to see is if the app has a web app interface. Aka if I go to the web site or get a share link, does the app autolunch the content.
I was a little confused with your question, hope this answers it.
Thanks for the interest.
odwdinc said:
I was a little confused with your question, hope this answers it.
Thanks for the interest.
Click to expand...
Click to collapse
Yes sure, that's what I was asking ... Cool!
I'll search in some of my favourite apps manifests to see if I can find something interesting ...
Inviato dal mio HTC One X con Tapatalk 4
Hi all,
I'm new to this forum. I registered here because I'm looking into NFC tags to try and create a certain project... So I would like to pick your brains to see if what I 'm looking to do is possible and if so what it would take...
I'm basically looking if I can use NFC tags in a mentalist effect as I'm into magic as a form of entertainment.
I would like to apply NFC tags to a bunch of small items that are displayed in front of me, all within range of my phone (or if need be another NFC reader). Then, while I am not looking, I would like one of my spectators to pick up any object they choose so the rest of the audience can also clearly see what object has been chosen. Yet by doing that, the chosen object would go out of range for the NFC reader. Obviously the spectator would then place the object back where it was. he or she would also be allowed to slightly move all other objects so it wouldn't be obvious which one was picked, as only one object is not in the exact same spot it started in...
I was hoping that there is a way for an NFC reader to scan multiple NFC tags in a reasonable amount of time and then also detect which tag isn't there anymore when the spectator shows the chosen object to the audience. Because that would then give me the chosen object. (the way I see it with my very limited knowledge by scanning all NFC tags within range and comparing that to a database that holds all tags that should be there. This should result in one that's missing)
So, is the above possible? Can NFC technology be used to scan a known library of tags and then identify the single tag that is missing?
If so: what are the limits? How many tags can be scanned let's say within 30 seconds? (like 5, or 50 or 100?) I truly have no idea.
What reader and tags would I need? How would I be able to have the NFC app tell me what tag is missing? Can this be an audio message I can receive through an earpiece?
What would be the maximum area all remaining objects should be in for the reader to be able to pick all of them up?
Is there a minimum distance needed between the tags to be able to read all individual tags or can they be very close together?
Any other constraints I missed?
Thanks a lot for letting me know,
Kind regards,
Peter