Hi Vasek,
see ISO/IEC 18092 (or its freely available Ecma version ECMA-340) for a
detailed description of the NFC protocol.
During the link activation phase, NFC devices perform an anticollision
mechanism. For active mode communication this is done by collision
aviodance (i.e. the targets
Hi Eliseo,
so Nexus S, Galaxy Nexus and Galaxy S III have a fixed UID?
These phones have an embedded secure element that has a fixed UID.
it is due to the NFC NXP controller or to the secure element?
Secure Element. The NFC controller uses random UIDs for all other cases.
Which secure
Hi Eliseo,
What I want to do is to use the UID received from the phone to read/write
the tag emulated on the phone. Another application possible is to use the
phone in access control applications, but a fixed UID is necessary. The
UID
is random for security reasons? How Card Emulation can
on this.
Thoughts?
Gr,
JMC
On Mar 23, 11:03 am, Michael Roland mi.rol...@gmail.com wrote:
Hallo,
the current SDK does not allow you to use card emulation.
Anyways, with card *emulation* you will not be able to simulate an
*NFC tag* (i.e
Hi,
i have wonder on web to find the answer can android-NFC can read RFID tag
data or not
That depends on what type of RFID tag you want to read. NFC devices can
read a subset of RFID tags.
br,
Michael
--
You received this message because you are subscribed to the Google
Groups Android
Hi Nikolay,
That is my understanding too, so I am not too far off :) I still
don't get the intent when I send APDUs but that may be a problem
with my libnfc setup. When I have a IsoPcdA activity in the foreground
nfc_initiator_select_passive_target() return 0, i.e. no tags found, but
this
Hi Nikolay,
Maybe Doug can give some more hints on how to properly use IsoPcd?
Does he hang around here :)
I don't know, but I had BCC'd him on that message, so here is what he wrote:
|| Sure guys,
|| ISOPCDA/B is just another tag type.
|| The only difference is that the intent won't fire
Hi Nikolay,
Since you wrote the paper on this, any hints on how to activate software CE
in CyanogneMod? Looking at the code, the app should get a notification for
a IsoPcdA tag and be able to transceive() with it, but I don't get this when
sending reset, select etc. with an external NFC
Hi,
Thanks for the series of fascinating posts and NFCTagInfo (I just
installed it today!).
:-)
There's still a few things that are unclear to me about why card
emulation isn't possible. I realize that applets within the secure
element can't be modified without the vendor crypto key, but
Hi,
This just made the news :)
http://www.cyanogenmod.com/blog/cyanogenmod9-1-and-simplytapp
Thanks for the info.
It is probably only visible from Japan, but here it is:
https://play.google.com/store/apps/details?id=com.mobilesuica.msb.android
Does it really work with stock Android?
Hello,
this is certainly not related to Android development, so you might be on
the wrong list.
However, I have an idea what could have gone wrong. Some versions of the
ACR122U need to be activated from power-down mode before bringing them into
initiator/target mode. You can try this by
Hello Shekhar,
I am already aware of the fact that a NDEF message can have multiple NDEF
records in it and payload data allowed is maximum of 2^32-1 bytes.
If I have a payload data of 100 octets which is inside the range of
default MIU, in that case should I send the data in one record
Hi Alistair,
I'm attempting to get into NFC on Android by communicating with a custom
PN532 device, however I'm a little confused as to my options and the
Android protocol.
- NFCIP-1, is it possible to place my device as a target into this
mode, for Android to automatically detect
Hi Shailen,
I see that you created the NFCTagInfo App, available on the market. This
app is, by far, the best Tag reader, because of all the little information
it can give us, for example the HEX/ASCII values of the sectors.
Thanks!
Anyway, I just wanted to point out that it is possible
As far as I understand it, HID iClass does not use all ISO 15693 layers and
is, thus, not compatible to the Nexus S's NFC hardware.
br
Michael
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Hallo Roman,
I have another question regarding card emulation. Do you know whether
the UICC is physically connected to the NFC controller (SWP) on the
Galaxy Nexus or not?
Unfortunately, I don't know for sure. I would assume that the SWP pin
is connected to the NFC controller (just as it is
Hallo Roman,
Are you interest in investigating this assumption with me? Another
option would be to ask Samsung. That reduces a lot of overhead
regarding compiling, flashing, debugging etc.
I assume that it will be easier to modify the firmware than to get a
definitive answer from Samsung^^.
Hallo Anatoly,
I Suppose SE is Secure Element am i Right?
Right.
Is there any way to communicate with reader, without modyfing
firmware?
No. Android has no support for card emulation from software. From an
external ISO 14443 reader you can only access the secure element. With
a reader that
Hallo Paul,
card emulation is officially supported since Android 2.3.7 (?) and is
used by Google Wallet. However, there is no way (unless you use a
modified ROM) to access card emulation capabilities from your own
applications.
br
Michael
On Feb 15, 5:35 pm, Paul pabloisb...@gmail.com wrote:
Hallo,
How to write these information in smart poster programmatically?
1) URL of the discount offer
That one is easy: use the smart poster's URI record.
2) Count value (like offer for first 200 entries)
That depends on what you want to achieve:
a) Should every smart poster should have a
Hallo,
to get your app into the activity chooser for URLs you could possibly
use an intent filter that matches the one that is used by the web
browser: (I have no Android 4.0* at the moment, so I could not test
if this works.)
intent-filter android:priority=-101
action
Hallo malls,
I could listen to AID_SELECTED event from NfcService. I am trying to
send data to SE. I get error that External RF Field detected, what
does this mean.
It means that you are trying to access the secure element from two sides
simultaneously (from an external reader and from the
Hallo Saurabh,
What is the significance of this :
I just looked through my code and found that I also explicitly disabled
ISO 14443-4 activation (before polling) using this command:
FF0003D41224
See page 9 of the reader API manual:
Some Type A Tags may support both ISO14443-3 Type A
Hallo,
When sharing a virtual tag using the enableForegroundNdefPush of an
NfcAdapter instance object, i try to read the so-shared ndef message
with my desktop reader (ID ISC CPR 40.30 USB).
Well, it won't work.
Correct. Foreground NDEF push Android Beam don't use tags to
exchange data.
this behavior (reader automatically performed protocol selection up to
ISO 14443-4 / APDU layer)
The ACR 122U was the only reader with which I successfully accessed the
MIFARE area of the SmartMX so far.
br,
Michael
On Thu, Jan 19, 2012 at 6:14 PM, Michael Roland mi.rol...@gmail.com
Hallo Saurabh,
I am getting This ATR now : *3B 8A 80 01 00 31 C1 73 C8 40 00 00 90 00
90* , which I have read in this group that it is for SmartMX.
Correct, that's the PC/SC ATR for the SmartMX.
I am looking into writing onto it but so far I am getting 63 00
response(which means error)
I
Hallo Tarun,
NdefRecord textRecord = new NdefRecord(NdefRecord.TNF_MIME_MEDIA,text/
x-vCard.getBytes(),new byte[] {}, textBytes);
Although MIME types are -- according to the RFC -- case-insensitive,
you should consider using only lower case letters, e.g. text/x-vcard.
intent-filter
action
Hallo,
intent-filter
action android:name=android.nfc.action.TECH_DISCOVERED/
/intent-filter
meta-data android:name=android.nfc.action.TECH_DISCOVERED
android:resource=@xml/tecnologia /
/activity
I thought that a TECH_DISCOVERED launch my application but it does not
Hallo Sathish,
see the nfcpy project at https://launchpad.net/nfcpy/
br
Michael
On Oct 20, 3:53 pm, Sathish Kumar sathishna...@gmail.com wrote:
Hi Team,
I need your help for the connection and exchange of Nexus
S Device and ACR122U NFC card reader exchange through NFC, Is
Hallo,
Android provides an API for access to MIFARE Classic cards:
http://developer.android.com/reference/android/nfc/tech/MifareClassic.html
Use the readBlock, writeBlock, increment, decrement, transfer and
restore methods to operate on value blocks.
For more information on MIFARE commands and
Hallo,
as a start I would strongly suggest that you read the NFC Forum's
specifications on the NDEF format and the record type definitions
(RTDs). You can find them here: http://www.nfc-forum.org/specs/spec_dashboard/
Second I would suggest that you make use of the NDEF helper classes in
Android
Hallo Eliseo,
see this thread on more information regarding card emulation:
http://groups.google.com/group/android-developers/browse_frm/thread/418c9b370f08a9f7
br
Michael
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this
Hallo Scott,
My other question is with messaging, how can I get the sms: URI to
attach the body with the message?
I can get a href=sms:0123456789Request A Call/a to work
but when I add the body a href=:sms:0123456789?body=Callback
%20RequestRequest a Call/a returns Please correct the
Hallo,
byte[] commandAPDU= new byte[]{
(byte)0x00, (byte)0xA4, (byte)0x04, (byte)0x00, (byte)7,
(byte)0xAB, (byte)0xE5, (byte)0xBC, (byte)0x08, (byte)0x85,
(byte)0x01, (byte)0x00};
byte[] responseAPDU = tag.transceive(commandAPDU);
String m1=Hex.byteArrayToHex(responseAPDU);
But the
Hallo Reddy,
I am planning to write a full duplex peer 2 peer application in 2.3.3.
Can any one please tell me how it can be possible.
the P2P communication capabilities of Android on current devices
(Nexus S, Galaxy SII) are limited to the NDEF Push Protocol (i.e. you
can exchange a single
Hallo,
I need to read and write ISO 14443-4 smart card .
In this case you won't need NfcA at all. You only need the IsoDep class.
In general you shouldn't care whether your IsoDep card uses NfcA or NfcB
as low-level technology.
I had used
mTechLists = new String[][] { new String[]
{
Hallo,
NfcA tag=NfcA.get(tagFromIntent);
and i can get the ATQA,SAK,but i don't know how to use
transceive(byte[] data),and how i can read the card??
There is no simple answer to that question. FIrst you need to know
what card/tag technology you have. (E.g. Topaz/Jewel, MIFARE
Hallo Adiga,
http://developer.android.com/guide/topics/nfc/index.html
Using this link , I can read MyFare Classic card , but unable to read
RFID tags.
MIFARE Classic *is* one type of RFID tag. Anyways, the refered API
allows much more that accessing MIFARE Classic cards. It gives you
Hallo Sumit,
So there is no way at present in Android by which one can perform card
emulation from Nexus S?
Watch out that this thread is about *ISO/IEC 15693* (vicinity) card
emulation (as opposed to proximity card emulation). There is no way the
PN544 NFC controller (which is used in the
Hallo Dominik,
What do you mean by all three NFC intents *have* three extras? I
ask, because the documentation at
http://developer.android.com/reference/android/nfc/NfcAdapter.html
states, that EXTRA_ID and EXTRA_NDEF_MESSAGES are optional (which is
obvious for the latter) and only EXTRA_TAG
Hallo,
first of all, the prefered method of receiving tag detection events is
the android.nfc.action.TECH_DISCOVERED intent, the intent
android.nfc.action.TAG_DISCOVERED is only used for fall-back tag
detection.
All three NFC intents (NDEF_DISCOVERED, TECH_DISCOVERED,
TAG_DISCOVERED) have three
Hallo Musfiq,
it might help if you posted some of the relevant code.
br,
Michael
On Aug 9, 3:46 am, musfiq musfiqu...@gmail.com wrote:
Hi:
I am trying to share a string between mobile phones using NFC. I want
the same application to send the tag and another to receive the tag in
two
On 8月5日, 下午4时25分, Michael Roland mi.rol...@gmail.com wrote:
Hallo,
the tag object's getId() method should work just fine for most
cases[1]. I.e.
byte[] uid = tagFromIntent.getId();
[1] Note that some tag platforms use random UIDs. For some others the
method may return only a partial UID
Hallo,
the tag object's getId() method should work just fine for most
cases[1]. I.e.
byte[] uid = tagFromIntent.getId();
[1] Note that some tag platforms use random UIDs. For some others the
method may return only a partial UID. Like NFC Forum Type 1 tags,
where the method returns only 4 bytes
Hallo Fernando,
From what I've read in the PN544 User Manual, I don't think that there
is an equvalent for the wired mode with SWP/HCI (I would be happy to be
proven wrong).
Well, here is where the phHal4Nfc_Switch_Swp_Mode() comes. It is
analog to the phHal4Nfc_Switch_SMX_Mode() which is
Hallo,
when i try to write to a mifare classic 1k card ,
Ndef.get(tag) returns null, upon searching, i find that tag is not
listed in tech list. but when i issue getTechList() command, i am able
to find
MifareClassic , NdefA and Ndefformatable are listed, so where am i
missing.
So you are
Hallo,
Does anyone know if there is a way to lengthen the time of a NfcA card
timeout for receiving a response from the card after sending it a
command? I saw that there was a way to do it with iso-dep type cards.
Or does anyone know how long the timeout is on a NfcA type card?
According to
Hallo,
My question is very simple: does Android v. 2.3.4 support ISO 15693
card emulation?
No, the NFC hardware with current NFC phones (PN544 on Nexus S) does
not support card emulation with ISO/IEC 16693 protocols. As a
consequence this type of card emulation is not possible with current
Hallo,
first of all, there is no code in your catch statements. Second, for
instance the writeNdefMessage() would throw a TagLostException if the
tag is no longer available during write. None of your catch statements
handles this type of exception. You could use a try-catch block like
this to
Hallo Kev,
However, when I return from the home screen I get the
android.intent.action.MAIN action, which I think makes sense.
When you launch your app through the launcher screen you should receive
the intent action android.intent.action.MAIN with category
android.intent.category.LAUNCHER.
Hallo Fernando,
As far as I understand sending APDUs to the SmartMX SE element is
possible because the NFC Controller (PN544) is told to enable the NFC-WI
interface with SE. This is carried out by calling
phHal4Nfc_Switch_SMX_Mode(), with parameter eSmartMx_Wired (function
Hallo Kev,
I wouldn't call that odd behavior but rather an exact match what you
have written in your code.
NfcAdapter.ACTION_NDEF_DISCOVERED.equals(getIntent().getAction()) will
not return true if the intent received from getIntent() does not
contain that action.
So if your app is started for
Hallo,
Did you get it tweaking the code by yourself as described above or you
used SEEK patches? I am currently trying to get some results myself but
I am new to Android platform development and I am a little bit lost.
I tweaked the code by myself. The SEEK patches won't enable card
emulation
Hallo,
I managed to write and read a block (4) to the Mifare 4K with default
keys. Next thing will be investigating wheter 2.3.4 adds support by
means of nxp-nfc library to directly send APDUs to the SE. You and
Michael Roland already confirmed it was not possible with prior
gingerbread
Hallo,
Do you mean you could enable card emulation mode from UICC? Could you
read the contents of a smartcard through an external reader and also
from an android application?
Yes, I managed to enable card emulation mode with a SWP-UICC as secure
element. As the NFC controller allows only
Hallo,
I was thinking S2C is an NXP implementation (e.g. the commercial name)
of the NFC-WI. Both,S2C and NFC-WI, looks pretty similar. So in fact,
even they using similar approach, we are talking about two different
technologies?
No, same technology. S2C was there *before* NFC-WI was
Hallo,
On the enhanced SD card is then besides the normal flash storage also
the secure element (smart card). To access the smart card the file I/O
based interface is re-used, i.e. if you write something and it starts
with 'magics' in header and it is valid APDU command it is send to the
Hallo,
I understand that there are no NFC-WI enabled microSD cards on the
market. Anyway I think the SD Card Association has some standards,
which specify two additional 13.56Mhz RF antenna pins complaint with
ISO 10373-6 (check here
Hallo Sumit,
Can you please tell me how can read data from this type of card?
Also, is there any way to find the type of card from coding?
Well, that depends on what type of card you have. Knowing that the
card is ISO 14443 Type B is certainly not enough to figure out how
this card's data can
Hallo,
the Nexus S device NXP PN544 NFC controller supports not only SWP for
UICC based SE, but also the S2C (aka NFC-WI)
Correct.
for the external, e.g.
micro SD card SE. Does anybody know how this can be enabled and what
it means for the SD card?
Well, as you mentioned yourself there is
Hallo,
Stringurl= http://example.com;;
byte[] payload =url.getBytes();
NdefRecord ndefRecord = new NdefRecord(NdefRecord.TNF_ABSOLUTE_URI,
NdefRecord.RTD_URI, new byte[0], payload);
this works, however I am not sure whether it completely follows the
NDEF spec.
You are correct. This
Hallo Dominik,
What would be the use-case which requires access to the emulated
Mifare card from within an android application?
Or asked another way round: What could be done additionally compared
to NDEF Push?
Have a look at my reply a while ago in this thread:
Hallo Dominik,
In the definition of the intent-filter I cannot
use the android:path part as this one matches only if it is an exact
match, i.e. in the above example only if the tag contains the URL
http://commonsware.com/nfctest. It is not possible to add wildcards in
the path part. But
Hallo Markus,
You are sure its not possible to access it [SWP-UICC] from an android
application?
In Madlmayers Blog he wrote, its possible because of the additional AT
Commands in RIL since 2.3.2.
Where did you find this information in Gerald's blog? I only found When
Android switched from
Hallo Markus,
But by loading the Key, occurs an error:
/send FF82201A06
= FF 82 20 1A 06 FF FF FF FF FF FF ..
(407461 nsec)
= 69 86 i.
Status: Command not allowed (no current EF)
Actually this response
Hallo,
Opening a connection with it - using doOpenSecureElementConnection, like
you can with the Smart-MX - will most definitely not work for a UICC SE
though. As
the NativeNfcSecureElement will only open a connection with the Smart-MX
SE - completely ignoring a UICC even if it is detected.
Hallo Tommy,
1. i send the ndef data by the enableForegroundNdefPush(this,
mMessage)function in onResume,but how can i known that the mMessage is
send over,can i got the notification or Intent?
You don't. Even if another device's NPP server picks up the NDEF
message from the NPP client,
Hallo Ferit,
i'm working on some simple NFC-Applications and i want to realize a
simple scenario, where the Nexus S sends some Text / URI / SmartPoster
to a desktop NFC-Reader.
Have a look at nfcpy ( https://launchpad.net/nfcpy ) and which readers
it supports. For the moment, nfcpy is the
,
Shekhar
On Apr 25, 5:09 pm, Michael Roland mi.rol...@gmail.com wrote:
Hallo lal,
I'm trying to Read Track data for Payment cards (PayWave, PayPass). As
per my understanding they follow ISO 14443 B. With new NFC API,
byte[] b1 = myTag.getHiLayerResponse(); //b1 is not null
Hallo Tommy,
For NPP, the NPP server creates a listening LLCP socket and waits for
pushed NDEF messages. The NPP client is invoked by the foreground NDEF
push and sends NDEF messages to NPP servers.
From your replys,i has some doubt about NPP.You mean the NPP server
and NPP client both on
Hallo Ferit,
as an alternative you could use a pending intent like this:
PendingIntent pi =
caller.createPendingResult(PENDING_INTENT_NFC_TECH_DETECTED, new
Intent(), 0);
nfcAdapter.enableForegroundDispatch(caller, pi, intentFilters,
techLists);
(where caller is the calling *activity*,
Hallo Marcus,
At time, I'm able to put my devices into emulation mode.
I'm getting ATR and UID throuth my OMNIKEY CardMan 5321 :
- ATR: 3B 8A 80 01 00 31 C1 73 C8 40 00 00 90 00 90
Correct, this is the ATR generated for the SmartMX.
- The ID of the emulated card is constant even if i
Hallo Steve,
I can confirm the ATR's as Michael pointed and add an interesting
follow on. When I do scardconnect and then scardsttus to get uid I get
the 5 byte (4 byte dynamic first by 08 static e.g. 080A97A6) from the
phone whenever the NFC service is running.
The UID (or actually the
Hallo JMC,
Are you guys sure it's a MIFARE 4k card it's emulating?
Yes, I'm very sure it is emulating a MIFARE Classic 4K card and an APDU
based smart card (depending on the protocol activation level).
When I put the device in emulation mode and read its ATR, I'm getting:
3B 8F 80 01 80 4F
, which I found on page eleven at the
following pdf document:
http://www.nfc-reader.com/NFC-smart-card-reader/ACR122-API-Manual/API_ACR122.pdf
But I always get back 6E 00.
Best wishes!
Martin
On 19 Mai, 20:18, Michael Roland mi.rol...@gmail.com wrote:
Hallo Martin,
After enabling
Hallo bebenza,
yes, you can use the Nexus S to communicate with various types of
contactless smart cards. Besides MIFARE, FeliCa and some other memory
card protocols, the Nexus S also supports IsoDep (APDU based
communication on top of ISO 14443-4).
If you can use the Nexus S to communicate with
Hallo Johannes,
the byte-order in the UID array exactly matches the byte-order defined
in ISO/IEC 15693-3:
MSB LSB
+--+--+--+--+--+--+--+--+
|64 57|56 49|48 1|
and external access?
Yes, they would be the same for internal and external access.
br,
Michael
On 19 Mai, 00:59, Michael Roland mi.rol...@gmail.com wrote:
Hallo,
I more or less understand how to do it but I don't understand if after
is possible to build application on card emulation
Hallo Shekhar,
NDEF is a data exchange format for NFC (NDEF = NFC Data Exchange
Format). It can be used with NFC tags (reader-writer mode) and in peer-
to-peer mode.
The NFC Forum Type tag formats specify a standardized way to store
NDEF data (and possibly other data) onto certain tags. So these
these technology specific classes.
// Check which type of tags was discovered
switch(tagtype)
{
// do operation as per your need using the [specific] Class
Apis
break;
...
}
Am I correct?
Correct.
br
Michael
On 18 May 2011 10:10, Michael Roland mi.rol...@gmail.com
Hallo,
I more or less understand how to do it but I don't understand if after
is possible to build application on card emulation.
Regarding the internal secure element (SmartMX): No. Even if you
activate this chip as the secure element, you could only use its UID for
your application. To edit
Hallo,
And Tech_Discovered:
intent-filter
action android:name=android.nfc.action.TECH_DISCOVERED
meta-data android:name=android.nfc.action.TECH_DISCOVERED
android:resource=@xml/nfc_tech_filter /
/action/intent-filter
This intent filter seems to be wrong. The meta-data should be placed
as
Hallo Gorka,
for the moment Android provides no means to directly dispatch your
application based on an NFC Forum External Type (btw, your external
type name does not follow the RTD specification, The External Type
Name MUST be formed by taking the domain name of the issuing
organization, adding
28, 2011 at 8:50 AM, Michael Roland mi.rol...@gmail.com
mailto:mi.rol...@gmail.com wrote:
Hallo,
What exactly is low level access?
With low-level access (as compared to APDU based access) I mean some
vendor specific (proprietary) protocol according to the ISO/IEC 14443-3
Hallo John,
the manifest file have the following filters:
intent-filter
action android:name=android.nfc.action.TECH_DISCOVERED/
/intent-filter
The program can't go through reading process because the follwoing condition
is always false:
if
Hallo,
What exactly is low level access?
With low-level access (as compared to APDU based access) I mean some
vendor specific (proprietary) protocol according to the ISO/IEC 14443-3
standard. Thus, instead of sending high-level APDU commands a more
simple protocol is used (such a protocol is
Hallo Azahara,
thanks for your answer. So that means Android 2.3.3 does not provide
the possibility to send many messages per connection established,
however internally it uses a more complex scheme to communicate in p2p
mode that is not available yet?.
Right. Actually it is internally it
Hallo lal,
I'm trying to Read Track data for Payment cards (PayWave, PayPass). As
per my understanding they follow ISO 14443 B. With new NFC API,
byte[] b1 = myTag.getHiLayerResponse(); //b1 is not null, but
length == 0
[...]
result = myTag.transceive(b1);
It will
Hallo Johannes,
Unfortunately, I can't make a lot out of the RFC 2046
specification (http://www.ietf.org/rfc/rfc2046.txt).
a MIME type is basically a string in the format top-level-type/
subtypeoptions (all 7bit US-ASCII). Typical values for top-evel-
type are text, image, video, audio or
Hallo,
take a look at the IsoDep class. It allows you to exchange APDU
command-response pairs with contactless smartcards.
br,
Michael
On Apr 21, 6:59 am, comsta6 ms...@komsco.com wrote:
I am a new about android phone.
Especially,,,I am a smartcard developer such as e-Passport, e-ID card.
Hallo Perumal,
I am having Nexus S and a Mifare Tag. Using TagWriter application I am
write and read from the Tag. Now I want to try sending an APDU command
to the Tag.
if you tag is a MIFARE Classic or MIFARE Ultralight tag, you won't be
able to communicate with it using APDU commands. These
Hallo Wilson,
I am facing an issue with a Mifare Classic card (this is a dual
interface smart card; contact and contactless).
Alright, then it is most likely not a MIFARE Classic card but a
contactless (dual interface) smart card (with ISO 14443-4 interface)
that additionally provides a MIFARE
Hallo Azahara,
Does anybody know why should I have to tap many
times the phones in order to send continuously data in p2p mode?.
This is because the current Android NFC API does not provide any
furhter P2P (LLCP) communication features. Internally, Android already
uses more sophisticated LLCP
Hallo,
have a look at the thread:
http://groups.google.com/group/android-developers/browse_frm/thread/fe9956bb2a6529ca
For the moment Sony's nfcpy project ( https://launchpad.net/nfcpy/ )
seems to be the only freely available open-source LLCP implementation
for the desktop platform. You might
Hallo,
Only open LLCP implementation I know of is NFCPy,
https://launchpad.net/nfcpy.. heard they've established some
communication with an Android device, but it only works for
one type of reader.
Sony had a pretty impressive demo of their nfcpy at WIMA this week. As
the python module is
Hallo Nick,
Understood. There was no choice but to create a new protocol, since the
rules of the NFC Forum are that you cannot implement a protocol until it
is ratified. And SNEP is not yet ratified. Rather than wait for ever, we
want to put it in the hands of users and application developers
Hallo Domnic,
could you show the complete AndroidManifest? And are you sure that your
tag is MIFARE Classic?
br
Michael
On 13.04.2011 12:29 androidom wrote:
Hello Michael,
I tried this with the intend filter. I am not getting my app
triggered. somehow it is still landing on the Tags app.
Hallo,
Just another question, I would like to start scanning for a tag inside
an activity on press of a button say - Start Scanning. In which
case, the scanning of the tag must be triggered after that button
press. Once a tag is scanned, then it must get the ID of the tag back
to the
Hallo Domnic,
Strange, the manifest looks good to me.
uses-sdk android:minSdkVersion=9 /
Your phone is Android 2.3.3 (i.e. API version 10, right?). Otherwise,
the TECH_DETECTED intent is not available.
activity android:name=verifytagscanact
Hallo Domnic,
I've just re-read through the code you posted before and found another
problem:
Did you place the action inside an intent-filter?
Like this:
intent-filter
action android:name=android.nfc.action.TECH_DISCOVERED /
/intent-filter
meta-data
1 - 100 of 115 matches
Mail list logo
