This may warrant a new thread, but since most people interested in
NFC and the secure element are posting here, I'll just chime in.
(the whole thread is a bit OT, since none of this stuff is part of the SDK)
So, Google Wallet has been announced, and it does save stuff
to the secure element. A few
Hallo Martin,
it seems you are right. Obviously, my tests were too superficial.
I tested with an Omnikey 5321, but that reader automatically activated
the SMX up to the ISO 14443-4 layer, so it was not possible to transmit
any MIFARE Commands.
I, therefore, switched to an ACR122U. I followed
Hello Michael,
here are the information I promised you yesterday.
Reader: Omnikey 55x3
Software: HID Reader Utility Version 4.0.0.0
Key: it works for each sector.
This is what we found in the api:
// The well-known default MIFARE read key. All keys are set to this at
the
Hello all,
Michael as you already mentioned, it is possible to activate the card
emulation mode and the Secure Element in the Nexus S.
I did that and also changed the permissions from
android.permission.WRITE_SECURE_SETTINGS to android.permission.NFC in
NfcService.java to get access to the Secure
Hallo Martin,
After enabling the card emulation mode on the Nexus S, I am able to
read and write data to the emulated MiFare Classic 4k card by an
external NFC reader. I would like to do that within an android app.
Have you verified that you actually wrote data to the MIFARE Classic? I
really
Hello Michael,
yes I am very sure that I can read and also write persistent data to
the MiFare Classic.
Even if the Nexus S is turned off, we are still able to read and write
data.
I will give you some information about the NFC reader, the software
and the keys we use tomorrow, because I have all
Thank you everyone to share this.
Currently I'm evaluating if it's the case to start to try to enable
the secure element.
I more or less understand how to do it but I don't understand if after
is possible to build application on card emulation.
Moreover some of you speak about authentication,
On May 18, 2:20 pm, benza luca.schia...@gmail.com wrote:
Thank you everyone to share this.
Currently I'm evaluating if it's the case to start to try to enable
thesecureelement.
I more or less understand how to do it but I don't understand if after
is possible to build application on card
On Wed, May 18, 2011 at 9:20 PM, benza luca.schia...@gmail.com wrote:
Moreover, what does it mean And if you improperly authenticate
yourself a certain number of times, there are secure elements out
there that will physically destroy themselves and can never be
recovered? Is related to the
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
Could someone please post the the image with card emulation enabled
for Nexus S?
On May 13, 5:08 am, Markus markus.tau...@gmail.com wrote:
mtk
you wrote after call
phLibNfc_SE_SetMode(seID,phLibNfc_SE_ActModeWired,nfc_jni_se_set_mode_callb
ack,
(void *)nat);
your nexus s was in card
mtk
you wrote after call
phLibNfc_SE_SetMode(seID,phLibNfc_SE_ActModeWired,nfc_jni_se_set_mode_callback,
(void *)nat);
your nexus s was in card emulation
I called it with mode default
phLibNfc_SE_SetMode(seID,phLibNfc_SE_ActModeDefault,nfc_jni_se_set_mode_callback,
(void *)nat);
and get following
Hello,
I was wondering if Google could eventually provide an Android
application that could unlock the Secure Element for developers?
It would allow developers to authenticate to the embedded SE and start
uploading their Java Card applications to see if it works.
For production, this will be
great mtk, my doubts are getting cleared...
So to work on WI mode , i need to set the SE to wired -interface mode like u
said.
After this if i Use RawTagconenction to send GP commands to SE , Will this
work for WI mode?
I mean can u select the 0 AID with this? . Sorry i dont have device yet, so
I added the code to set wired mode in
com_android_nfc_NativeNfcManager.cpp. I also added some additional
methods on NFcService so I can conveniently call it from my test
activity. For sending APDU commands in SWP mode, I use another
activity with TAG_DISCOVERED action in android manifest, (just
hello, I've been looking for a way to turn on nfc card emulation on
the nexus s and I came across the following recent blog post:
http://mobisocial.stanford.edu/news/2011/01/nfc-on-android-for-social-applications/
They found some nfc p2p code that got removed from Gingerbread and
they used it to
mtk, very cool! So when you did that call directly (somewhere in init
of the jni code?) you got it to detect? How are you sending APDU
commands? Also, if I understand wired mode correctly, the tag is not
emulated externally to other readers; it's only available internally
using the NFC API?
Thanks Nemik for posting the patch, I was trying to get the emulation
working without much luck so far, I see you have flipped some
additional flags than what I had, so I'll trying those.
Btw I was able to set the SE to wired mode by calling
phLibNfc_SE_SetMode(seID,phLibNfc_SE_ActModeWired,
Nemik,
Thanks for posting the diff's and great work! I'll patch the codebase
and see what happen. In the meantime and coming back to your question
about the Nexus S hardware containing a secure element like SmartMX,
did you get the secure element list with the method
getSecureElementList() in
Sorry for not replying in a while, been very busy with projects at
work.
I posted my diff's to enable the Nexus S to emulate an NFC tag. The
links are below:
http://nemik.net/code/android-nfc/Nfc-app.diff for
http://android.git.kernel.org/?p=platform/packages/apps/Nfc.git;a=summary
and
According to the NXP documentation of PN544, three SE variants are
supported:
- SIM Card (via UICC)
- Embedded (SmartMX security chip)
- SD Card
Do you know which version is intended to be used by the Nexus S
device?
The above messages describe attempts to enable SmartMX. As soon as
access to
I still dont have nexus s but there is a high probability that its Embedded
Yes Keys are private and most likely needs to be provided by Service
Provider. The same thing has been mentioned in nokia forum
But I am not sure how this will be done for nexus S.(may be there are ties
with Service
Hi Nemik,
Please, could you tell me how do you enable the SMX in the nexus s
configuration and change the mode in the Nfcservice? So far, I can
read and write tags,
Regards
gusdgg
On 10 ene, 04:51, Ajith Kamath sjce.aj...@gmail.com wrote:
Hi Nemik
I'm running over the libnfc code.
I can see
Could you tell me how do you enabled SMX (SmartMX) and set the
cardemulation mode? So far, I was able to read and write tags with the
Nexus S.
Thanks
.gusdgg
On 8 ene, 16:30, nemik ne...@nemik.net wrote:
I was able to enable a secure element the other day by messing around
with this
Hi Nemik
* I have small doubt with current implementation. Is SmartMX a Secure
Element ?If so can you give me examples?
* I have checked libnfc-nxp , enabling P2P parameter was at phnfcconfig.h.
what needs to be done to enable Secure element?
what are MifarePlus, Desfire, Topaz . Is it a Card
Ajith,
According to
http://discussion.forum.nokia.com/forum/showthread.php?199442-6212-device-how-to-work-with-the-secure-element
the CN072 is a secure element in the Smart MX family. I'm not sure the
same one is in the Nexus S, but I presume the one in there is at least
very similar.
Here is
Hi Nemik
I'm running over the libnfc code.
I can see these 4 files to be prominent for communication with SE
phHciNfc_CE_A.c
phHciNfc_CE_B.c
I am thinking the above two might be used for R/W into SE from App
Processor.
And the below two is used for communication between NFC Controller and SE.
I was able to enable a secure element the other day by messing around
with this external/libnfc-nxp library. I enabled SMX (SmartMX) in the
config headers, and upon booting and monitoring `adb logcat` during
boot I saw 1 secure elements (a SmartMX one) had been enabled. I was
then able to change
Dominik,
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.
On Dec 7, 5:42 am,
101 - 129 of 129 matches
Mail list logo
