[0] command (0x60 for key A, 0x61 for key B)
[1] block number (will authenticate entire sector)
[2-5] last 4 bytes of uid
[6-11] 6 byte key
Also, here's how Android does the authentication:
doSelectSecureElement *should* work for the UICC. (code
herehttp://android.git.kernel.org/?p=platform/packages/apps/Nfc.git;a=blob;f=jni/com_android_nfc_NativeNfcManager.cpp;h=7f000885e7c286f3fa90209220b5936d0c62b8c9;hb=HEAD)
I haven't got a SWP compliant SIM handy though so I can't test it,
Note that the uid is contained inside the first sector, which is a read-only
sector and is therefore impossible to modify. As such, it's impossible to
fully reproduce your badge. If the system you wish to reproduce it for
depends on the card's uid for identification, the procedure won't work.
Are you guys sure it's a MIFARE 4k card it's emulating?
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
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
Similar - but
An android device establishes a P2P connection over the NPP (NDEF Push
Protocol) by Google, which is an openly specified protocol:
http://source.android.com/compatibility/ndef-push-protocol.pdf
NPP is a protocol on top of LLCP, which is a protocol on top of NFCIP-1, so
you'd need to have those
If you could post the log that would be swell.
--
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
No.
libnfc lacks LLCP and NPP support.
I read they're working on LLCP support though, but am unsure of recent
advances on that protocol. When it's implemented, NPP should be a breeze to
add on top.
Only open LLCP implementation I know of is NFCPy,
https://launchpad.net/nfcpy .. heard they've
Hey Joe,
As I understand it, *both *MAY be available.
The PN544 controller has an embedded smartcard, so there's that, and it also
supports SWP (for compliant SIMs). Which is used depends on the application,
applications on the smartcard would be 'linked to your phone', while
applications on
.
It is enough to be useful in practice. It may not be enough for what
*you* want to do, and we understand that it does not do everything for
everyone at this point, but this is what is there so far.
On Wed, Mar 30, 2011 at 3:03 AM, JMC114 jorncruij...@gmail.com wrote:
Greetings
:45 JMC114 wrote:
Hey Michael,
Why - may I ask - do you think this possibility will not be made
available to android phones? It seems to me it's a rather important
part of NFC. The part where it makes phones compatible to existing
infrastructures based on RFID (without changing
Hey Michael,
Why - may I ask - do you think this possibility will not be made
available to android phones? It seems to me it's a rather important
part of NFC. The part where it makes phones compatible to existing
infrastructures based on RFID (without changing those
infrastructures), namely those
Greetings,
After sifting through documentation and building NFC test applications
on a Nexus S, I've come to the conclusion the Android SDK still lacks
the functionality that NFC applications truly need in order to really
be useful in practice.
What's possible now:
- Reading and writing tags.
-
12 matches
Mail list logo
