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,
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
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
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
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
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
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
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
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
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
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
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
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 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.
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
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
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
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
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
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
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.
55 matches
Mail list logo
