Hi, Fernando!
Recently I started working with Nexus S concerning Mifare Card Emulation. I
was searching for manual to do this, but haven't found anything.
I would like to know, if you have detailed instructions on how to emulate
Mifare Classic 1K/4K cards. Thanks in advance.
вторник, 19
Might take a look at this
url:
http://intrepidusgroup.com/insight/2011/09/a-brave-new-wallet-first-look-at-decompiling-google-wallet/
He notices a debug menu in a old version of google wallet.
On Friday, April 6, 2012 4:16:12 PM UTC+2, Nikolay Elenkov wrote:
On Fri, Apr 6, 2012 at 10:06 PM,
Am Mittwoch, 11. April 2012 09:05:34 UTC+2 schrieb Alexander Sytnik:
Great work!
It helped me very much. My current goal - to download into the Secure Element
a
cardlet, which can securely manage MIFARE part and communicate with our own
TSM
through an additional application in a phone. But
Hi!
So is possible that the phone ( I have Galaxy S III) acts like a Mifare
card and with him I can comunicat with the infraestructure of NFC of one
office to use the phone to open dors ?
I'm trying to develop this applicacion for the University but I'm not sure
that the comunicacion with
Great work! It helped me very much. My current goal - to download into the
Secure Element a cardlet, which can securely manage MIFARE part and
communicate with our own TSM through an additional application in a phone.
But this possibility, that can be used even in old Nokia 3220 with NFC
Hi everyone,
Firstly I'm extremely sorry for hijacking this thread, but this appears to
be where all the activity regarding NFC on Android is occuring, and so
should reach the relevant audience.
I've recently read through a lot of information regarding the
implementation of NFC, Google
On Fri, Apr 6, 2012 at 10:06 PM, xanium4332 xanium4...@gmail.com wrote:
I've recently read through a lot of information regarding the implementation
of NFC, Google Wallet, card emulation etc.. on the Galaxy S
Nice write up, you should put it in a blog post somewhere. Sounds about
right, but
Someone wrote that you can't emulate cards on Nexus S (or maybe only mifare
ultralight cards), even if you have the opennfc driver and the rest of it
set up.
Any comments on this?
On 6 April 2012 17:16, Nikolay Elenkov nikolay.elen...@gmail.com wrote:
On Fri, Apr 6, 2012 at 10:06 PM, xanium4332
Anyone tried it on ICS yet?
And are there new patches or something?
On Friday, February 10, 2012 9:47:18 PM UTC+2, malls wrote:
When the card emulation is detected, the call is routed
to nfc_jni_transaction_callback() of SecureElement. From here the event is
posted to NfcService for example
Hi all,
Before digging deeply in all this. I wonder if it will be worth it. My aim
is to emulate the key I have to enter my building.
It is a Mifare 1k, 16secrots, of which I have the keys.
Would this be possible ?
Le vendredi 10 février 2012 20:47:18 UTC+1, malls a écrit :
When the card
is *nfc_jni_transaction_callback() *inside the (HAL)Libnfc-nxp or
framewrok code.?Where is it?Which Android Version?*ICS?? PLz post *
*
*
*Rgds,*
*Saurabh
*..pain is temporary.quitting lasts forever..
On Sat, Feb 11, 2012 at 5:11 PM, Michael Roland mi.rol...@gmail.com wrote:
Hallo
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
When the card emulation is detected, the call is routed
to nfc_jni_transaction_callback() of SecureElement. From here the event is
posted to NfcService for example AID_SELECTED events are all posted to
NfcService. I was wondering if there is way to communicate to SecureElement
through this
I am not sure if anybody explored NfcExecutionEnvironment class. There
are APIs to communicate to secure element. I don't see any key
requirement.
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
Any comments...plz respond if you are reading this mail !
rgds,
Saurabh
..pain is temporary.quitting lasts forever..
On Wed, Feb 1, 2012 at 1:21 PM, p z ymdo...@gmail.com wrote:
I think maybe you can.
and plesae share your rom when you finished.thx.
On 2月1日, 上午8时15分, malls
Hi Nemik,
You wrote :
*Yea, that's right. All it does currently is read; at least via the
Java API. If you look at the kernel source though, a bunch of ifdefs
which allow for emulation were all disabled. So full compliance with
the NFC standard will have to wait for a future kernel release. *
Hi All,
Recently I have tried with another Card reader , I got this message.
MIFARE 4K card on reader
ATR : 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 02 00 00 00 00 69
00 02 -- Shows the *Mifare *4K
Earlier with another Card I was getting -- *3B 8A 80 01 00 31 C1 73 C8 40
00 00 90 00 90* and I
And besides that, Google took out microSD from the major NFC phones,
so, basically, we won't be able to do nothing when it comes card
emulation - as for an obvius reason, the SE keys are not available.
As far as I can gather from the giants in this matter (like our friend
Michael Roland), SWP is
I think maybe you can.
and plesae share your rom when you finished.thx.
On 2月1日, 上午8时15分, malls masubha...@gmail.com wrote:
Fernando,
I was wondering if I can emulate the card in my application and send it to
the terminal.
regards
malls
--
You received this message because you are
theoritacally is it possible to change the chip with one that we know
the key ? Will it be difficult to access to the chip ?
On Feb 2, 7:19 am, Fernando Miguélez fernando.migue...@gmail.com
wrote:
Keys are used in raw communication through APDUs
On Wed, Feb 1, 2012 at 7:46 PM, malls
I don't see any interface of passing the keys to open secure element in the
android code. I am not sure how many people claims that you need google
Keys to open SecureElement. May be I am missing something.
--
You received this message because you are subscribed to the Google
Groups Android
Keys are used in raw communication through APDUs
On Wed, Feb 1, 2012 at 7:46 PM, malls masubha...@gmail.com wrote:
I don't see any interface of passing the keys to open secure element in
the android code. I am not sure how many people claims that you need google
Keys to open SecureElement.
Fernando,
In that case, what's api to send apdu to external SE and how can we have
external SE added to the phone.
regards
malls
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Fernando,
I was wondering if I can emulate the card in my application and send it to
the terminal.
regards
malls
--
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
Fernando,
Here is the logcat output that I am getting. Is libpn544.so supposed to be
built as part of this build process or am i missing something. I have
checked, there were no errors during the compilation anywhere.
D/NFC JNI ( 4179): NFC Service : loading JNI
I/NfcService( 4179): Starting
Dear Fernando
I tried to patch as per your instructions and root the device. I get error
saying libpn544.so not found. I don't see this file created after the
compilation. Where is it trying to load from.
regards
malls
--
You received this message because you are subscribed to the Google
Softy
Could you please share android client code snippet to send APDU command to
SE after the patch.
regards
malls
--
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
Thanks Saurabh and Fernando, that worked just adding the library. Just
Curious is it supposed to be part of android build, not sure why am I
missing that file.
On Jan 26, 11:09 pm, s.rawat imsaurabhra...@gmail.com wrote:
Hi,
I faced this issue.Plz paste the file attached in the mail to the *
Fernando,
Thanks I could create custom image with nfc enabled by using your
help.
Just to clarify myself, if we are connected to external reader, I
should be able to directly read/write APDUs from my app right.
should I be using NFCService.transceive(..) method to read/write from
the external
Could you please share android client code snippet to send APDU command to
SE after the patch.
Well actually I haven't got here yet , but still trying , if you happen
to find this ,do plz share it.
I checked in other devices this shared library is present there, i think
somehow it got deleted by
No, you cannot read/write APDUs from your application while working with an
external reader. When card emulation is enabled APDUs are routed directly
to SE from NFC Controller. APDU communication with SE has other objective,
main application processor can not emulate a PICC, that is the task of
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
There must be an error with patches since other person had the same issue.
Just copy it manually to the /system/lib directory of the phone (you have
to remount the system partition as RW).
2012/1/27 malls masubha...@gmail.com
Dear Fernando
I tried to patch as per your instructions and root
Hi Michael* ** *.
Yes i have followed the aforesaid method but as soon as I execute these
commands.:
*Step 1) Polling for the MIFARE 1K/4K Tags, 106 kbps*
FF 00 00 00 04 D4 4A 01 00
* d5 4b 00 90 00* ( I am getting this)
- which shows no NFC tag.
and 63 00 for rest of the of the commands.
I am
Hi, Tommy!
Could you, please, build a new version your Nexus S ROM of Card Emulation with
fresh patch from m0rtadelohttp://forum.xda-developers.com/member.php?u=3284560
?
http://forum.xda-developers.com/showthread.php?t=1281946
Many thanks!
--
You received this message because you are
Hallo Saurabh,
You mean page 12 , section *5.3 Reading Binary Block*.
I didn't find any section *5.3 Reading Binary Block* on that page. In
fact, I mean have you tried the whole command sequence described for
Card Access -- How to access MIFARE Classic Tags? on that page.
You have to do the
Hi All,
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.
I am looking into writing onto it but so far I am getting 63 00
response(which means error)
I am trying to load., authenticate the keys and then read -write
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
Hi Michael ,
You mean page 12 , section *5.3 Reading Binary Block*.
I tried that, i found as soon as I send the command the green light on the
card reader turns Red for the time being(which I fear is some operation
failed signal) , accompanied by the 63 00 response .I am using the *TestResMan
HI,
I am gettign an ATR : A card is present. ATR: 3B 8F 80 01 80 4F 0C A0 00 00
03 06 03 *FF 40* 00 00 00 00 D4 .
I dont htink it emulated the card.Does it.For 1k/4k Mifare Classic Card it
has to be 00 01(Mifare 1k) or 00 02(Mifare 1k) instead of *FF 40* .PLz
correct my understanding.I have used
I did re-flashing from the patched Android Source and again the same
thing.Here are the logcat logs on clicking the NFC Settings :
D/dalvikvm( 298): GC_EXPLICIT freed 91K, 45% free 3160K/5703K, external
4731K/5234K, paused 290ms
I/ActivityManager( 106): Starting: Intent {
Hi Saurabdh,
I reviewed my notes and I definetly built the image with lunch
full_crespo-eng. Try building in engineer mode so the traces can be more
verbose. Apart from that the process to compile the firmware is the same
you described in your blog.
On Thu, Jan 5, 2012 at 9:31 AM, s.rawat
Saurabh,
After reflashing my phone and verifying that the NFC toggle option was
available also in main Wireless Settings Screen, and after examining your
problem I reached the conclusion that your generated image does not include
NFC support, only the settings screen. I reviewed the patches and
Sure I will try that and post the results !
..pain is temporary.quitting lasts forever..
2012/1/5 Fernando Miguélez fernando.migue...@gmail.com
Saurabh,
After reflashing my phone and verifying that the NFC toggle option was
available also in main Wireless Settings Screen, and
Hi All,
Thanks Fernando Miguélez Palomo for posting the patches.I have applied it
to 2.3.4-r1 Android gingerbread and compiled /flashed it on Samsung Nexus S
and was able to see the NFC Settings changed(though i cant select them,
they are disabled)
I have blogged the whole steps
Great work.
Obviously there is something wrong with the compilation. Have you tried to
connect in debug mode the phone to a computer with Android Development
Tools and see what the traces look like. They may offer a clue. My
suspicion is that NfcService is crashing. I will review my notes
Thanks !
I will also try from my side recompiling it.So you mean I should get the
Check boxes enabled for
*Only Card EmulationMode*
and
*Use External SE*
My main aim is to write to the NFC card in card emulation mode so that it
can be read by any Card Reader.is it possible after your patches
Well, options are enabled in cascade. The problem comes because the first
option is not enabled. Besides, if you look at the Wireless Settings
screen, there is only the NFC Settings option, but not the one that lets
you enalbe/disable NFC directly from that screen. That is beacuse the Nfc
service
Hi,
I would like to know if it's possible to wirte data on the card with an
android application ? Or is it the problem that you have been talking about
a secret key that no one know ?
Thx for the answer,
--
You received this message because you are subscribed to the Google
Groups Android
I only have a checkbox 'NFC', to activate the NFC reader.
Activated (or not), the phone doesn't act as a Mifare tag on every Mifare
test system I own.
Is there something else I can check ?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To
Then the patches are not correctly applied.
On Tue, Nov 29, 2011 at 9:56 AM, fuful ludwig.fulg...@gmail.com wrote:
I only have a checkbox 'NFC', to activate the NFC reader.
Activated (or not), the phone doesn't act as a Mifare tag on every Mifare
test system I own.
Is there something else I
OK, understood.
Now my next question will be about this patch : how can I apply it ?
I'm totally new at Android, and I have no idea how to add this patch to my
phone.
Is there some information on the web somewhere I can follow do perform this
?
Thank for your answer.
--
You received this
Dear all,
I've downloaded rom from Tommy, but I don't see the option Fernando is
speaking of, about card emulation.
Wherre these options are placed ?
Thanks in advance.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group,
There should be an option in Settings Screen (NFC Settings)
On Fri, Nov 25, 2011 at 11:41 AM, fuful ludwig.fulg...@gmail.com wrote:
Dear all,
I've downloaded rom from Tommy, but I don't see the option Fernando is
speaking of, about card emulation.
Wherre these options are placed ?
Thanks in
I polished the patches so now you have some options from Settings
application:
Card Emulation Only Mode. This disables reader function. Card emulation mode
is always enabled. Be careful because P2P mode may not work (not tested)
Use External Secure Element if Available. This makes the phone to
For the time being I can not share the ROM but you can compile it yourself
with the supplied patches. Take a look at the last ones:
https://groups.google.com/d/msg/android-developers/1fw1qfFqpGc/pvhc11jVDEUJ
--
You received this message because you are subscribed to the Google
Groups Android
On 9月19日, 下午5时20分, Rames P rame...@gmail.com wrote:
Hi Fernando Miguélez Palomo
Did you get the ROM working for Nexus S with NFC card emulation enabled? I
so can you please share the rom? Your answer might be very useful
to achieve a position in my carrer.
Thanks
Here is my Nexus S ROM
Hi Fernando Miguélez Palomo
Did you get the ROM working for Nexus S with NFC card emulation enabled? I
so can you please share the rom? Your answer might be very useful
to achieve a position in my carrer.
Thanks
--
You received this message because you are subscribed to the Google
Groups
hi all:
Now i modified the download android source code 2.3.4 for card
emulation like Fernando's diffs.I make the modified source code on my
vmware+ubuntu success,make the sdk success,and make the download
samsung kernal code success.But now how can i use these changes on my
Nexus S phone?What
hello
You did as reading and writing a block in Mifare 4K Nexus emulates inside S
with
a external card reader.
You can post the step by step or guide us in this process
thanks
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
Hi.
Now i modified the source code like the nemik's diffs before for my
Nexus S.But when i make the source code i got errors
packages/apps/Nfc/src/com/android/nfc/NfcService.java:47: cannot find
symbol
symbol : class INfcSecureElement
location: package android.nfc
import
Hi,
Thanks for the information and patches for manually enabling the card
emulation in Android. I am able to read and write a block into the
Mifare 4K emulated inside Nexus S using an external card reader. Is it
possible to read the data inside the Mifare 4K from Android
application? Is SEEK
If you follow the complete thread you will answer yourself to both
questions, no.
El 05/08/2011 00:15, Xiang xiang...@gmail.com escribió:
Hi,
Thanks for the information and patches for manually enabling the card
emulation in Android. I am able to read and write a block into the
Mifare 4K
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
Hi Michael,
Correct, for the SE connected through NFC-WI/S2C, the NFC controller has
three modes: off, wired and virtual mode. Off means that there is no
communication with the secure element. Wired mode means that the secure
element is visible to the application processor as if it was a
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
Hi Michael,
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
Great job Fernando! Thank you for sharing your diff on this, it's
fantastic news.
On Jul 19, 5:48 am, Fernando Miguélez Palomo
fernando.migue...@gmail.com wrote:
I got it working on 2.3.4_r1!!!
The key was enabling discoverability but in card emulation mode. The strange
thing is now I can
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
I got it working on 2.3.4_r1!!!
The key was enabling discoverability but in card emulation mode. The strange
thing is now I can detect two smart card types with an Arcontia smart card
reader:
- ISO14443A tag CL1 tag (This is the Mifare 4K)
- FELICA RCS-885 424kbs tag (I suppose this is
Hi Nemik,
I just applied your patches to 2.3.4_r1 version (I had to change them a
little bit) but card emulation does not seem to work (an external reader
detects nothing). Could you please tell us what tag of AOSP gingerbread did
you use?
Thanks
--
You received this message because you are
Fernando, the patches were against 2.3.1 or 2.3.2 I believe, a long
time ago (relatively). I have not had a chance to revisit this but I'm
fairly sure it will not work on 2.3.4+.
I'm sure some of the header defines have changed as well but try to re-
enable the ones I had if they exist? Good
Yes I know. I revised them manually and adapted to 2.3.4_r1. However I must
be missing something.
I see the Secure Element SMX selected, the embedded Mifare card is not
detected by means of external readers. The external reader detects a memory
card but it can not read the CSN (UID). It seems
For convenience I post the filtered NFC related I can see after
initialization. As I said the card is detected on reader but only after
phone restarts (however it can not read any UID). If I approach it latter it
is not recognized.
07-18 17:01:54.800: DEBUG/NFC JNI(283): NFC Service : loading
Do any of you have an image that can be applied directly to a Nexus S?
--
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
Have somebody activate the Card Emulation with UICC?
Yes.
I tryed it, with SmartMX SE it was no problem Card Emulation was
running.
When I tried the ID of my UICC in the Method doSelectSecureElement
from NFC Service,
then the Card Emulation was not running, Reader dont detect a
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
Interesting.
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.
2011/7/14 Michael Roland mi.rol...@gmail.com
Hallo,
Do you mean
Hello all,
Any has customer rom 2.3.4 to support card emulation.
Thanks in advance!
CK
On May 20, 1:51 am, Martin martin.buellesb...@googlemail.com wrote:
Hello all,
Michael as you already mentioned, it is possible to activate the card
emulation mode and theSecureElementin the Nexus S.
I
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:
Hello Michael,
So now we would only need to find a way to access the MIFARE area from
within an application on the phone.
I'm currently testing with a modified version of the 2.3.4 firmware. But
as with the smart card readers, the SmartMX is automatically activated
up to the ISO
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.
[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:
Hello,
I cant load the key ff ff ff ff ff ff to the 4k MIFARE.
If my Nexus S is in Card Emulation I tried with JCShell to do
something.
Reading UID and ATR is no problem it works.
But by loading the Key, occurs an error:
/send FF82201A06
= FF 82 20 1A 06 FF FF FF FF FF FF
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,
Hi Michael,
On 19 Mai, 00:59, Michael Roland mi.rol...@gmail.com wrote:
Regarding an external secure element on the UICC (SIM card): Partly
yes. You can activate an SWP-UICC as secure element. But access is
limited to external readers for the moment. Until now, there is no known
way to get
Ok thanks for advices Michael,
I will try to modify the mifare area of the Nexus in order to
reproduce my badge.
Best regards
Marcus
On Jun 11, 11:33 am, Michael Roland mi.rol...@gmail.com wrote:
Hallo Marcus,
At time, I'm able to put my devices into emulation mode.
I'm getting ATR and
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.
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
Hello,
I'm in university and i'm working on NFC in Nexus S for three weeks.
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
- The ID of the emulated card is constant even
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
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,
Have anyone read this?
2.3.4. adds hidden classes for secure element and related:
http://gibraltarsf.com/blog/?p=247
On Jun 2, 2:55 pm, Jorn Cruijsen jorncruij...@gmail.com wrote:
Hey Michael,
Oh, it seems I failed terribly.. That's the value I thought to receive when
the device is in
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. if I leave the connection
open and run multiple
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
Hi JMC,
I can not check this at the moment, because I do not have the device
at the moment.
After some changes in the the android cpp sources, I got additional
information about the Secure Element, when I open a secure element
connection via reflection. So there I can see that it has the Mifare
1 - 100 of 129 matches
Mail list logo
