Re: [android-developers] Re: does NFC in gingerbread support card simulate?

2012-06-15 Thread Jorn Cruijsen
Only by putting the device in emulation mode would it be possible to
(contactlessly) read and write to the emulated mifare card, which will be
persisted to the SE. While sending NDEF data over P2P is perfectly
possible, it would not be persisted to the SE and would instead
(ultimately) be handled by the Android App Framework.

With the device in emulation mode, another device with NFC TagInfo or
comparable would be able to identify the targeted phone as a mifare card
and read/write from/to it. In this case a plain text NDEF message, as I
understand it.

And just to point out; the emulated mifare card would have NDEF data stored
on it, it would not 'simulate' an NDEF _tag_. This is a fundamental
difference, as Michael pointed out earlier.

Also, as Gorka mentioned, so long as card emulation is not adopted by the
Android Application Framework, it's not feasible to publish an app doing
this on the Android Market. (Putting a device in emulation mode, that is.
For a device to do this, it requires changing Android Source code,
recompiling and flashing a device with it).

Regards,

JMC
On Jun 12, 2012 9:03 AM, JoeAranda joeara...@gmail.com wrote:

 Gorka,
   if NFC taginfo app can provide all 16 sectors of the MIFARE
 couldn't shailen have sent this to another phone via peer to peer and
 avoided card emulation?

  Shailen, can you share some insight into how you did this using NFC
 taginfo?

 thanks,

 joe

 On May 17, 8:37 am, Gorka gork...@gmail.com wrote:
  Hi Shailen,
 
  I guess you have emulated your MIFARE4k tag rooting your mobile phone
  and applying any of the patches that are available on the Internet. Am
  I right? I ask you because this solution is fine for research
  purposes, but it cannot be applied if you want to publish your app or
  sell it.
 
  Regards.
 
  On 8 mayo, 01:20, Shailen Sobhee s.sob...@gmail.com wrote:
 
 
 
 
 
 
 
   Hello Michael,
 
   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.
 
   Anyway, I just wanted to point out that it is possible to simulate an
 NFC
   Tag with card emulation. I was able to turn on card emulation on my
 Samsung
   Nexus S phone which sports a PN65 (=PN544+SmartMX) chip. The emulated
 card
   was a MIFARE 4K, which is a Type 4 NFC Tag. Using another Nexus S and
 the
   NXP TagWriter app, I was able to write a plain text message on the
   card-emulated Nexus S.
 
   Examining the HEX data, the latter was clearly an NDEF message.
   Furthermore, the NXP Tagreader app was able to extract the plain text
   message.
 
   That said, full card-emulation is possible on the Nexus S!!
 
   br
   Shailen
 
   On Wednesday, March 23, 2011 10:03:39 AM UTC+1, Michael Roland 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. a tag where you store simple NDEF messages). Card
emulation mode allows to emulate a contactless smartcard (typically
used for applications with high security requirements, like credit
cards). While such a card (emulated or real) can be used to carry
 NDEF
messages, I really doubt that this possibility will be made available
for the Android phones.
 
br,
Michael
 
On Mar 23, 5:14 am, Zhihong GUO gzhh...@gmail.com wrote:
 Hi all,
 
 about NFC in Gingerbread, is it possible to simulate a tag by the
 SDK? I
 have found the support for tag read/write and P2P push message, but
haven't
 found any support on card simulate.
 
 thanks
 
 James

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: NFC Secure Element

2011-06-02 Thread Jorn Cruijsen
Hey Michael,

Oh, it seems I failed terribly.. That's the value I thought to receive when
the device is in peer-to-peer mode. I confused the two.

Thanks for the clarification.

--
Met vriendelijke groet, | Best regards,
Jorn Cruijsen
jorncruij...@gmail.com
(+31) (0)6 272 492 91



On Thu, Jun 2, 2011 at 1:15 PM, Michael Roland mi.rol...@gmail.com wrote:

 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 0C A0 00 00 03 06 03 00 00 00 00 00 00 6B

 Decoding this PC/SC ATR gives this:
 3B ... Contactless card
  8F ... Number of historical bytes: 0xF (15)
  80
  01
80 ... Category indicator: A status indicator may be present
   in an optional COMPACT-TLV data object.
4F ... Application identifier Presence indicator
0C ... Length of application identifier: 0x0C (12)
  Application identifier:
A0 00 00 03 06 ... RID: PC/SC Working Group
03 ... Byte for Standard: ISO 14443 A, part 3
00 00 ... Bytes for Card Name: not in standard
00 00 00 00 ... RFU (Shall be set to zero)
  6B ... Checksum

 This is a typical ATR if the card emulation mode is not activated. I
 receive that ATR if I put the phone in peer-to-peer communication mode
 (which is the default if card emulation is disabled).


  While I'm actually expecting:
  3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 02 00 00 00 00 69

 With the phone you would not normally receive such an ATR for the card
 emulation mode either. Usually a contactless smart card reader (like the
 Omnikey 5321) activates the contactless smart card up to its highest
 supported protocol layer. For the SmartMX, this means that ISO 14443-4
 protocol layer is activated for APDU based communication with the
 JavaCard. Thus, the ATR generated by the smart card reader would reflect
 the properties of the APDU-based JavaCard and not those of the MIFARE 4K
 area. This is the value I recieve when card emulation is on:
  3B 8A 80 01 00 31 C1 73 C8 40 00 00 90 00 90


 Best regards,
 Michael



-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en