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 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 handle. If I try to open SecureElement parallel y, the call 
> throws error that "External RF Field is detected", when this channel is 
> open, I believe there must be a way to wait until this mode is finished and 
> communicate back to SecureElement or use the same channel to communicate.
>
> In fact, If I view the ice-scream sandwich code, there is new event 
> subscription  APDU_RECIEVED in the secure element callback.  It looks like 
> the PICC interface is open now. Hopefully we should be able to communicate.
>
>
>
Le vendredi 10 février 2012 20:47:18 UTC+1, malls a écrit :
>
> 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 handle. If I try to open SecureElement parallel y, the call 
> throws error that "External RF Field is detected", when this channel is 
> open, I believe there must be a way to wait until this mode is finished and 
> communicate back to SecureElement or use the same channel to communicate.
>
> In fact, If I view the ice-scream sandwich code, there is new event 
> subscription  APDU_RECIEVED in the secure element callback.  It looks like 
> the PICC interface is open now. Hopefully we should be able to communicate.
>
>
>
Le vendredi 10 février 2012 20:47:18 UTC+1, malls a écrit :
>
> 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 handle. If I try to open SecureElement parallel y, the call 
> throws error that "External RF Field is detected", when this channel is 
> open, I believe there must be a way to wait until this mode is finished and 
> communicate back to SecureElement or use the same channel to communicate.
>
> In fact, If I view the ice-scream sandwich code, there is new event 
> subscription  APDU_RECIEVED in the secure element callback.  It looks like 
> the PICC interface is open now. Hopefully we should be able to communicate.
>
>
>
Le vendredi 10 février 2012 20:47:18 UTC+1, malls a écrit :
>
> 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 handle. If I try to open SecureElement parallel y, the call 
> throws error that "External RF Field is detected", when this channel is 
> open, I believe there must be a way to wait until this mode is finished and 
> communicate back to SecureElement or use the same channel to communicate.
>
> In fact, If I view the ice-scream sandwich code, there is new event 
> subscription  APDU_RECIEVED in the secure element callback.  It looks like 
> the PICC interface is open now. Hopefully we should be able to communicate.
>
>
>

-- 
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

Reply via email to