Re: [android-developers] Re: NFC Secure Element
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. May be I am missing something. -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 SE. When communicating main processor with SE you can theoretically load/remove cardlets, interact with them and so on. For the time being Mifare embedded inside SmartMX chip can not be accessed from an application. At least AFAIK. On Tue, Jan 31, 2012 at 2:22 AM, malls masubha...@gmail.com wrote: 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 reader. regards malls On Jan 4, 6:17 am, Fernando Miguélez fernando.migue...@gmail.com wrote: 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 in not available. Connection to a computer in debug mode will draw some light. Instead of compiling the whole image again I suggest you to compile just the Nfc.apk system application and replace the original one. You must remount /system partition in read/write mode and overwrite the apk inside /system/app. Then you must kill the nfc service by means of DDMS view of the ADT (you must connnect the phone in debug mode and since you have compiled in userdebug mode you will see all the running proccesses). The service will restart automatically. When it comes to read/write the card by means of an external reader, any Mifare Classic 4K compatible RFID reader will do. If you try to access directly to the SE from an Android application I am afraid to disappoint you but that is not possible, at least I wasn't successful at it and nobody I know either. The reasons are well described in other posts and on stackoverflow. Regards On Wed, Jan 4, 2012 at 2:56 PM, s.rawat imsaurabhra...@gmail.com wrote: 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 are applied using teh android SDKs or do we have to write some native application. Rgds, Softy ..pain is temporary.quitting lasts forever.. 2012/1/4 Fernando Miguélez fernando.migue...@gmail.com 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 tomorrow if I find something different to the steps you followed to build the image. On Wed, Jan 4, 2012 at 9:17 AM, softy imsaurabhra...@gmail.com wrote: 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 here http://techshek4u.blogspot.com/2012/01/applying-card-emulation-patch-Plz let me know if I miss something. @ Fernando Miguélez Palomo What next after that.How can i test this.Any source code or tool /card reader description will be enlightening. Rgds, softy -- 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 -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 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 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
Re: [android-developers] Re: NFC Secure Element
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 imsaurabhra...@gmail.com wrote:
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 {
act=android.intent.action.MAIN cmp=com.android.settings/.WirelessSettings }
from pid 493
D/dalvikvm( 493): GC_EXTERNAL_ALLOC freed 55K, 50% free 2933K/5831K,
external 2878K/3220K, paused 20ms
E/NFC ( 493): could not retrieve NFC service
I/ActivityManager( 106): Displayed
com.android.settings/.WirelessSettings: +351ms
D/dalvikvm( 493): GC_EXTERNAL_ALLOC freed 43K, 49% free 3022K/5831K,
external 3171K/3241K, paused 21ms
I/ActivityManager( 106): Starting: Intent {
act=android.intent.action.MAIN cmp=com.android.settings/.nfc.NfcSettings }
from pid 493
I/ActivityManager( 106): Displayed com.android.settings/.nfc.NfcSettings:
+261ms
Any clue on this.
Rgds,
Saurabh
..pain is temporary.quitting lasts forever..
2012/1/4 Fernando Miguélez fernando.migue...@gmail.com
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 in not available. Connection to a computer in debug mode will draw
some light.
Instead of compiling the whole image again I suggest you to compile just
the Nfc.apk system application and replace the original one. You must
remount /system partition in read/write mode and overwrite the apk inside
/system/app. Then you must kill the nfc service by means of DDMS view of
the ADT (you must connnect the phone in debug mode and since you have
compiled in userdebug mode you will see all the running proccesses). The
service will restart automatically.
When it comes to read/write the card by means of an external reader, any
Mifare Classic 4K compatible RFID reader will do. If you try to access
directly to the SE from an Android application I am afraid to disappoint
you but that is not possible, at least I wasn't successful at it and nobody
I know either. The reasons are well described in other posts and on
stackoverflow.
Regards
On Wed, Jan 4, 2012 at 2:56 PM, s.rawat imsaurabhra...@gmail.com wrote:
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 are
applied using teh android SDKs or do we have to write some native
application.
Rgds,
Softy
..pain is temporary.quitting lasts forever..
2012/1/4 Fernando Miguélez fernando.migue...@gmail.com
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 tomorrow
if I find something different to the steps you followed to build the image.
On Wed, Jan 4, 2012 at 9:17 AM, softy imsaurabhra...@gmail.com wrote:
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
herehttp://techshek4u.blogspot.com/2012/01/applying-card-emulation-patch-to_03.html.Plz
let me know if I miss something.
@ Fernando Miguélez Palomo
What next after that.How can i test this.Any source code or tool /card
reader description will be enlightening.
Rgds,
softy
--
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
--
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
Re: [android-developers] Re: NFC Secure Element
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 *there
was a bug. *The NFC was not enabled in building proccess because the wrong
file was patched (device.mk instead of device_base.mk). Sorry for the
incovenience.
I have just updated the patches and uploaded to
http://forum.xda-developers.com/showthread.php?p=17965091 . Could you
please check from the beginning that now the patches are completely correct
by rebuilding the image? It is safe to apply again over the patches files,
since the changes apply to another file.
On Thu, Jan 5, 2012 at 9:31 AM, s.rawat imsaurabhra...@gmail.com wrote:
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 {
act=android.intent.action.MAIN cmp=com.android.settings/.WirelessSettings }
from pid 493
D/dalvikvm( 493): GC_EXTERNAL_ALLOC freed 55K, 50% free 2933K/5831K,
external 2878K/3220K, paused 20ms
E/NFC ( 493): could not retrieve NFC service
I/ActivityManager( 106): Displayed
com.android.settings/.WirelessSettings: +351ms
D/dalvikvm( 493): GC_EXTERNAL_ALLOC freed 43K, 49% free 3022K/5831K,
external 3171K/3241K, paused 21ms
I/ActivityManager( 106): Starting: Intent {
act=android.intent.action.MAIN cmp=com.android.settings/.nfc.NfcSettings }
from pid 493
I/ActivityManager( 106): Displayed com.android.settings/.nfc.NfcSettings:
+261ms
Any clue on this.
Rgds,
Saurabh
..pain is temporary.quitting lasts forever..
2012/1/4 Fernando Miguélez fernando.migue...@gmail.com
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 in not available. Connection to a computer in debug mode will draw
some light.
Instead of compiling the whole image again I suggest you to compile just
the Nfc.apk system application and replace the original one. You must
remount /system partition in read/write mode and overwrite the apk inside
/system/app. Then you must kill the nfc service by means of DDMS view of
the ADT (you must connnect the phone in debug mode and since you have
compiled in userdebug mode you will see all the running proccesses). The
service will restart automatically.
When it comes to read/write the card by means of an external reader, any
Mifare Classic 4K compatible RFID reader will do. If you try to access
directly to the SE from an Android application I am afraid to disappoint
you but that is not possible, at least I wasn't successful at it and nobody
I know either. The reasons are well described in other posts and on
stackoverflow.
Regards
On Wed, Jan 4, 2012 at 2:56 PM, s.rawat imsaurabhra...@gmail.com wrote:
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 are
applied using teh android SDKs or do we have to write some native
application.
Rgds,
Softy
..pain is temporary.quitting lasts forever..
2012/1/4 Fernando Miguélez fernando.migue...@gmail.com
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 tomorrow
if I find something different to the steps you followed to build the image.
On Wed, Jan 4, 2012 at 9:17 AM, softy imsaurabhra...@gmail.com wrote:
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
herehttp://techshek4u.blogspot.com/2012/01/applying-card-emulation-patch-to_03.html.Plz
let me know if I miss something.
@ Fernando Miguélez Palomo
What next after that.How can i test this.Any source code or tool /card
reader description will be enlightening.
Rgds,
softy
--
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
Re: [android-developers] Re: NFC Secure Element
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 tomorrow if I find something different to the steps you followed to build the image. On Wed, Jan 4, 2012 at 9:17 AM, softy imsaurabhra...@gmail.com wrote: 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 herehttp://techshek4u.blogspot.com/2012/01/applying-card-emulation-patch-to_03.html.Plz let me know if I miss something. @ Fernando Miguélez Palomo What next after that.How can i test this.Any source code or tool /card reader description will be enlightening. Rgds, softy -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 in not available. Connection to a computer in debug mode will draw some light. Instead of compiling the whole image again I suggest you to compile just the Nfc.apk system application and replace the original one. You must remount /system partition in read/write mode and overwrite the apk inside /system/app. Then you must kill the nfc service by means of DDMS view of the ADT (you must connnect the phone in debug mode and since you have compiled in userdebug mode you will see all the running proccesses). The service will restart automatically. When it comes to read/write the card by means of an external reader, any Mifare Classic 4K compatible RFID reader will do. If you try to access directly to the SE from an Android application I am afraid to disappoint you but that is not possible, at least I wasn't successful at it and nobody I know either. The reasons are well described in other posts and on stackoverflow. Regards On Wed, Jan 4, 2012 at 2:56 PM, s.rawat imsaurabhra...@gmail.com wrote: 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 are applied using teh android SDKs or do we have to write some native application. Rgds, Softy ..pain is temporary.quitting lasts forever.. 2012/1/4 Fernando Miguélez fernando.migue...@gmail.com 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 tomorrow if I find something different to the steps you followed to build the image. On Wed, Jan 4, 2012 at 9:17 AM, softy imsaurabhra...@gmail.com wrote: 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 herehttp://techshek4u.blogspot.com/2012/01/applying-card-emulation-patch-to_03.html.Plz let me know if I miss something. @ Fernando Miguélez Palomo What next after that.How can i test this.Any source code or tool /card reader description will be enlightening. Rgds, softy -- 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 -- 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 -- 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 -- 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
Re: [android-developers] NFC Secure element in SIM vs internal!
Well, if you work with a SE embedded in a SIM card, if you change your phone you just have to change the SIM that is all. When working with NFC using the SIM approach you have basically two options. On one hand you can create applications that communicate directly with SIM to carry out operations with the embedded SE, i.e. recharging the balance of a transportation ticket or just finding out the current balance. From my experience this approach works well for Blackberry or any other J2ME phone supporting SATSA-APDU API. Android is just another different world, since such low level access to SIM is not allowed from user applications. In this case main processor and baseband firmware must be changed to support a similar functionality already found on several-year-old J2ME phones. This technique has not acquired much market adotion. On the other hand we have the TSM operation. In this case the carriers, who control de SIM and have other means to access remotely to the SIM (OTA), set up TSM services a provide third parties (transportation companies such as RENFE, etc.) a access to SIM (well, actually to a part inside the SE that holds that third party's own applications). In this case the user applications inside the mobile phone do not have direct access to SIM, but they operate with it through a business service that usually proxies to carrier's TSM server. On Fri, Dec 23, 2011 at 1:14 PM, jesquinas jesqui...@renfe.es wrote: I work at RENFE,the national railways company.We have developping NFC projects.Here,in Spain,the main NFC model is SIM-centric.There are only a few NFC models available.Our project is developed with Vodafone and all our mobiles are with a NFC SIM.The main argument who mobile operators say is that you change more the mobile that the SIM and that the reason for adopting the SIM centric model.The question that the mobile operators say in Spain is : if you have your credentials in the SE in the phone and you want to change the phone ,for example fro Google Nexus to Blackberry,how can you do it? Can you give me arguments for knowing more about this subject? Thanks. -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 can check ? -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 advance. -- 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 -- 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
[android-developers] Re: NFC Secure Element
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 use the SE of the UICC if available instead of embedded one. I posted the patches on xda-developershttp://forum.xda-developers.com/showthread.php?t=1281946 As a bonus I also removed the stupid time-limit when enable discoverable option of Bluetooth. -- 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
[android-developers] Re: NFC Secure Element
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 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
Re: [android-developers] Re: NFC Secure Element
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 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 patches able to perform that? Thanks again. Regards, Xiang On Jul 19, 6:48 pm, 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 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 really the Javacard, not a Felica card) 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 versions. I post the corrected patch to get card emulation on 2.3.4_r1. One thing. Card stops being readable from an external reader after screen goes off and back on. However if you disable NFC and re-enable it (from settings) card is discoverable again. Thanks nemik for your work (you can update your patches with these corretions to work with gingerbread 2.3.4_r1 at your site if you want). Nfc-app-2_3_4_r1.diff 31KViewDownload -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 (contactless) smartcard connected to the RF reader. Virtual mode means that the secure element is visible to external readers as if the phone were a contactless smartcard. That's right. 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). Usually for the wired mode, the contact interface of the UICC would be used so it wouldn't really make sense if the NFC controller allowed for an additional* channel between the UICC and the application processor. *) Additional once the RIL supported APDU exchange with the UICC. Well, here is where the *phHal4Nfc_Switch_Swp_Mode() *comes*. *It is analog to the *phHal4Nfc_Switch_SMX_Mode() *which is used to set the wired mode to work with the SmartMX. In function *phLibNfc_SE_SetMode() *when told to enable wired mode it ignores to enable it if secure element is UICC instead of SmartMX. In this last case it uses *phHal4Nfc_Switch_SMX_Mode() *with the parameter *eSmartMx_Wired. *I modified the function to use *phHal4Nfc_Switch_Swp_Mode() *with parameter *eSWP_Switch_On *(this parameter has an incorrect value by default, it must be enabled by using nemik's patches). This function (phHal4Hnfc_Switch_Swp_Mode()) succeeds, which makes me think there could be a wired SWP mode. Although the SWP mode is enabled, no SE seems to be detected this way. When opening SMX in wired mode from *com_android_nfc_NativeNfcSecureElement_doOpenSecureElementConnection() *the callback is called twice after calling *phLibNfc_SE_SetMode(). *However if SWP is enabled (using external SE element) callback is only called once after *phLibNfc_SE_SetMode(). *If we avoid waiting for second callback * phLibNfc_RemoteDev_Connect()* always fails (internally no SE has been discovered). When it comes to RIL issue. I patched the sources with SEEK diffs too but rild daemon crashes. SEEK mantainers say it is due to baseband processor not implementing required (AT+CSIM, AT+CCHO, AT+CCHC, AT+CGLA) commands ( http://code.google.com/p/seek-for-android/wiki/UICCSupport). Is there any way to reverse engineer baseband firmware or get access to a modified version implementing those commands? Or has anyone discovered whether Samsung has other propietary commands achieving the same results (raw APDU exchange with SIM/UICC)? regards, Fernando -- 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
Re: [android-developers] Mifare Classic emulation using NFC on Android 2.3.4
Yes it is possible. Check this thread out: https://groups.google.com/d/topic/android-developers/1fw1qfFqpGc/discussion On Wed, Jul 27, 2011 at 9:12 AM, Ankit Maheshwari lkoan...@gmail.comwrote: Hi , has anybody tried for the Mifare Card Emulation using NFC .??? i will be really grateful if anybody could helo me on this . Thanks Ankit -- 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 -- 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
Re: [android-developers] Re: NFC Secure Element
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 *phLibNfc_SE_SetMode()).* * * Wouldn't it be possible to use the SWP channel to send APDUs to UICC SE through NFC Controller in an wired mode from an application the same way it is performed when sending APDUs to the SmartMX element? Or is SWP only supposed for raw RF Communication and has no such equivalent capabilities used by NFC-WI? Taking a look at the libnfc-nxp library theare are some SWP related functions that are not being used.Maybe *phHal4Nfc_Switch_Swp_Mode() *could be used in a similar fashion to *phHal4Nfc_Switch_SMX_Mode()*? * * * * -- 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
[android-developers] Re: NFC Secure Element
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 really the Javacard, not a
Felica card)
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 versions.
I post the corrected patch to get card emulation on 2.3.4_r1.
One thing. Card stops being readable from an external reader after screen
goes off and back on. However if you disable NFC and re-enable it (from
settings) card is discoverable again.
Thanks nemik for your work (you can update your patches with these
corretions to work with gingerbread 2.3.4_r1 at your site if you want).
--
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=endiff -urBNp Nfc.orig/jni/com_android_nfc_NativeNfcManager.cpp Nfc/jni/com_android_nfc_NativeNfcManager.cpp
--- Nfc.orig/jni/com_android_nfc_NativeNfcManager.cpp 2011-07-19 12:32:17.545611859 +0200
+++ Nfc/jni/com_android_nfc_NativeNfcManager.cpp 2011-07-18 10:50:27.665620770 +0200
@@ -341,6 +341,7 @@ static int nfc_jni_initialize(struct nfc
/* == CONFIGURE DRIVER === */
TRACE(phLibNfc_Mgt_ConfigureDriver(0x%08x, 0x%08x), gDrvCfg.nClientId, gDrvCfg.nLinkType);
+ LOGD(phLibNfc_Mgt_ConfigureDriver(0x%08x, 0x%08x), gDrvCfg.nClientId, gDrvCfg.nLinkType);
REENTRANCE_LOCK();
status = phLibNfc_Mgt_ConfigureDriver(gDrvCfg, gHWRef);
REENTRANCE_UNLOCK();
@@ -364,6 +365,7 @@ static int nfc_jni_initialize(struct nfc
/* == INITIALIZE === */
TRACE(phLibNfc_Mgt_Initialize());
+ LOGD(phLibNfc_Mgt_Initialize());
REENTRANCE_LOCK();
status = phLibNfc_Mgt_Initialize(gHWRef, nfc_jni_init_callback, (void *)cb_data);
REENTRANCE_UNLOCK();
@@ -373,6 +375,7 @@ static int nfc_jni_initialize(struct nfc
goto clean_and_return;
}
TRACE(phLibNfc_Mgt_Initialize returned 0x%04x[%s], status, nfc_jni_get_status_name(status));
+ LOGD(phLibNfc_Mgt_Initialize returned 0x%04x[%s], status, nfc_jni_get_status_name(status));
/* Wait for callback response */
if(sem_wait(cb_data.sem))
@@ -433,6 +436,7 @@ static int nfc_jni_initialize(struct nfc
// Update EEPROM settings
TRACE(** START EEPROM SETTINGS UPDATE **);
+ LOGD(** START EEPROM SETTINGS UPDATE **);
for (i = 0; i EEDATA_SETTINGS_NUMBER; i++)
{
gInputParam.buffer = EEDATA_Settings[i];
@@ -440,6 +444,7 @@ static int nfc_jni_initialize(struct nfc
gOutputParam.buffer = resp;
TRACE( EEPROM SETTING: %d, i);
+ LOGD( EEPROM SETTING: %d, i);
REENTRANCE_LOCK();
status = phLibNfc_Mgt_IoCtl(gHWRef, NFC_MEM_WRITE, gInputParam, gOutputParam, nfc_jni_ioctl_callback, (void *)cb_data);
REENTRANCE_UNLOCK();
@@ -461,6 +466,7 @@ static int nfc_jni_initialize(struct nfc
}
}
TRACE(** ALL EEPROM SETTINGS UPDATED **);
+ LOGD(** ALL EEPROM SETTINGS UPDATED **);
/* == SECURE ELEMENTS === */
@@ -511,6 +517,7 @@ static int nfc_jni_initialize(struct nfc
/* LLCP Params */
TRACE(** NFC Config Mode NFCIP1 - LLCP **);
+ LOGD(** NFC Config Mode NFCIP1 - LLCP **);
LlcpConfigInfo.miu= nat-miu;
LlcpConfigInfo.lto= nat-lto;
LlcpConfigInfo.wks= nat-wks;
@@ -529,6 +536,8 @@ static int nfc_jni_initialize(struct nfc
}
TRACE(phLibNfc_Mgt_SetLlcp_ConfigParams returned 0x%04x[%s], status,
nfc_jni_get_status_name(status));
+ LOGD(phLibNfc_Mgt_SetLlcp_ConfigParams returned 0x%04x[%s], status,
+ nfc_jni_get_status_name(status));
/* Wait for callback response */
if(sem_wait(cb_data.sem))
@@ -602,6 +611,7 @@ void nfc_jni_restart_discovery_locked(st
struct nfc_jni_callback_data cb_data;
TRACE(Restarting polling loop);
+ LOGD(Restarting polling loop);
/* Create the local semaphore */
if (!nfc_cb_data_init(cb_data, NULL))
@@ -614,6 +624,7 @@ void nfc_jni_restart_discovery_locked(st
/* Restart Polling loop */
TRACE(** Start NFC Discovery **);
+ LOGD(** Start NFC Discovery **);
REENTRANCE_LOCK();
ret = phLibNfc_Mgt_ConfigureDiscovery(NFC_DISCOVERY_RESUME,nat-discovery_cfg, nfc_jni_discover_callback, (void *)cb_data);
REENTRANCE_UNLOCK();
@@ -626,7 +637,16 @@ void
[android-developers] Re: NFC Secure Element
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 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
[android-developers] Re: NFC Secure Element
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 as if the card emulation
were enabled but then disabled.
This is my init sequence as seen by logcat: http://pastebin.com/XpyLUGaJ
I can see the following sequence. So I assume the embedded secure element is
enabled:
I/NFC JNI ( 198): NFC Initialized
D/NfcService( 198): NFC-EE routing ON
D/NFC JNI ( 198): ** Select Secure Element **
D/NFC JNI ( 198): phLibNfc_SE_SetMode(0x00abcdef, ...)
D/NFC JNI ( 198): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
What is the correct message sequence?
I attach your patches modified to compile against 2.3.4_r1. Someone could
find them useful. By the way in this tag Nfc is disabled by default. So the
patch device_base_2_3_4_r1.diff must be also applied.
--
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=endiff -urBNp libnfc-nxp.orig/inc/phNfcConfig.h libnfc-nxp/inc/phNfcConfig.h
--- libnfc-nxp.orig/inc/phNfcConfig.h 2011-07-18 18:15:27.215614224 +0200
+++ libnfc-nxp/inc/phNfcConfig.h 2011-07-18 18:20:33.823504089 +0200
@@ -286,6 +286,7 @@
#ifndef NXP_UICC_RD_RIGHTS
#define NXP_UICC_RD_RIGHTS 0x00U
+//#define NXP_UICC_RD_RIGHTS 0x0FU
#endif
@@ -367,7 +368,7 @@
#define RECONNECT_SUPPORT
/** Macro to Enable the Card Emulation Feature */
-/* #define HOST_EMULATION */
+#define HOST_EMULATION
/** Macro to Enable the Download Mode Feature */
#define FW_DOWNLOAD
diff -urBNp Nfc.orig/jni/com_android_nfc_NativeNfcManager.cpp Nfc/jni/com_android_nfc_NativeNfcManager.cpp
--- Nfc.orig/jni/com_android_nfc_NativeNfcManager.cpp 2011-07-18 18:03:05.825613188 +0200
+++ Nfc/jni/com_android_nfc_NativeNfcManager.cpp 2011-07-18 10:50:27.665620770 +0200
@@ -341,6 +341,7 @@ static int nfc_jni_initialize(struct nfc
/* == CONFIGURE DRIVER === */
TRACE(phLibNfc_Mgt_ConfigureDriver(0x%08x, 0x%08x), gDrvCfg.nClientId, gDrvCfg.nLinkType);
+ LOGD(phLibNfc_Mgt_ConfigureDriver(0x%08x, 0x%08x), gDrvCfg.nClientId, gDrvCfg.nLinkType);
REENTRANCE_LOCK();
status = phLibNfc_Mgt_ConfigureDriver(gDrvCfg, gHWRef);
REENTRANCE_UNLOCK();
@@ -364,6 +365,7 @@ static int nfc_jni_initialize(struct nfc
/* == INITIALIZE === */
TRACE(phLibNfc_Mgt_Initialize());
+ LOGD(phLibNfc_Mgt_Initialize());
REENTRANCE_LOCK();
status = phLibNfc_Mgt_Initialize(gHWRef, nfc_jni_init_callback, (void *)cb_data);
REENTRANCE_UNLOCK();
@@ -373,6 +375,7 @@ static int nfc_jni_initialize(struct nfc
goto clean_and_return;
}
TRACE(phLibNfc_Mgt_Initialize returned 0x%04x[%s], status, nfc_jni_get_status_name(status));
+ LOGD(phLibNfc_Mgt_Initialize returned 0x%04x[%s], status, nfc_jni_get_status_name(status));
/* Wait for callback response */
if(sem_wait(cb_data.sem))
@@ -433,6 +436,7 @@ static int nfc_jni_initialize(struct nfc
// Update EEPROM settings
TRACE(** START EEPROM SETTINGS UPDATE **);
+ LOGD(** START EEPROM SETTINGS UPDATE **);
for (i = 0; i EEDATA_SETTINGS_NUMBER; i++)
{
gInputParam.buffer = EEDATA_Settings[i];
@@ -440,6 +444,7 @@ static int nfc_jni_initialize(struct nfc
gOutputParam.buffer = resp;
TRACE( EEPROM SETTING: %d, i);
+ LOGD( EEPROM SETTING: %d, i);
REENTRANCE_LOCK();
status = phLibNfc_Mgt_IoCtl(gHWRef, NFC_MEM_WRITE, gInputParam, gOutputParam, nfc_jni_ioctl_callback, (void *)cb_data);
REENTRANCE_UNLOCK();
@@ -461,6 +466,7 @@ static int nfc_jni_initialize(struct nfc
}
}
TRACE(** ALL EEPROM SETTINGS UPDATED **);
+ LOGD(** ALL EEPROM SETTINGS UPDATED **);
/* == SECURE ELEMENTS === */
@@ -511,6 +517,7 @@ static int nfc_jni_initialize(struct nfc
/* LLCP Params */
TRACE(** NFC Config Mode NFCIP1 - LLCP **);
+ LOGD(** NFC Config Mode NFCIP1 - LLCP **);
LlcpConfigInfo.miu= nat-miu;
LlcpConfigInfo.lto= nat-lto;
LlcpConfigInfo.wks= nat-wks;
@@ -529,6 +536,8 @@ static int nfc_jni_initialize(struct nfc
}
TRACE(phLibNfc_Mgt_SetLlcp_ConfigParams returned 0x%04x[%s], status,
nfc_jni_get_status_name(status));
+ LOGD(phLibNfc_Mgt_SetLlcp_ConfigParams returned 0x%04x[%s], status,
+ nfc_jni_get_status_name(status));
/* Wait for callback response */
if(sem_wait(cb_data.sem))
@@ -602,6 +611,7 @@ void nfc_jni_restart_discovery_locked(st
struct
[android-developers] Re: NFC Secure Element
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 JNI 07-18 17:01:54.847: INFO/NfcService(283): Starting NFC service 07-18 17:01:54.992: DEBUG/NFC JNI(283): Set NFC DISCOVERY A to 1 07-18 17:01:54.992: DEBUG/NFC JNI(283): Set NFC DISCOVERY B to 1 07-18 17:01:54.992: DEBUG/NFC JNI(283): Set NFC DISCOVERY F to 1 07-18 17:01:54.992: DEBUG/NFC JNI(283): Set NFC DISCOVERY 15693 to 1 07-18 17:01:54.992: DEBUG/NFC JNI(283): Set NFC DISCOVERY 15693 to 1 07-18 17:01:55.089: DEBUG/NFC JNI(283): phLibNfc_Mgt_Initialize returned 0x000d[NFCSTATUS_PENDING] 07-18 17:01:55.113: DEBUG/NFC JNI(283): NFC client started 07-18 17:01:55.250: DEBUG/NFC JNI(283): NFC capabilities: HAL = 8150100, FW = a70414, HW = 620003, Model = 0, HCI = 1, Full_FW = 104, FW Update Info = 0 07-18 17:01:55.582: DEBUG/NFC JNI(283): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING] 07-18 17:01:55.597: DEBUG/NFC JNI(283): ** NFC Config Mode NFCIP1 - LLCP ** 07-18 17:01:55.597: DEBUG/NFC JNI(283): phLibNfc_Mgt_SetLlcp_ConfigParams returned 0x000d[NFCSTATUS_PENDING] 07-18 17:01:55.644: INFO/NFC JNI(283): NFC Initialized 07-18 17:01:55.644: DEBUG/NfcService(283): NFC-EE routing ON 07-18 17:01:55.644: DEBUG/NFC JNI(283): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING] 07-18 17:01:55.664: DEBUG/NfcService(283): NFC-C discovery OFF 07-18 17:01:55.664: DEBUG/NFC JNI(283): ** Stop NFC Discovery ** 07-18 17:01:55.746: DEBUG/NFC JNI(283): phLibNfc_Llcp_Socket() returned 0x[NFCSTATUS_SUCCESS] 07-18 17:01:55.750: DEBUG/NFC JNI(283): phLibNfc_Llcp_Bind() returned 0x[NFCSTATUS_SUCCESS] 07-18 17:01:55.750: DEBUG/NFC JNI(283): phLibNfc_Llcp_Listen() returned 0x[NFCSTATUS_SUCCESS] -- 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
Re: [android-developers] Re: NFC Secure Element
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 Tag. Somebody knows why doSelectSecureElement Method dont working with UICC? If the UICC supports SWP, the doSelectSecureElement method works just fine here. (ID is 11259376 for UICC) Hi Michael, I am new to this forum and I am impressed of the level your mastership and the rest of the members. 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? -- 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
[android-developers] Re: NFC Secure Element
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 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 external card emulation for secure elements connected through SWP, I could only access the smartcard from an external reader but not through an Android app. br Michael -- 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
[android-developers] Re: Problem getting Bluetooth RSSI (Signal Strength)
It may not work because EXTRA_RSSI value is a short type instead of
int. This works great for me:
short rssi = intent.getShortExtra(BluetoothDevice.EXTRA_RSSI,
Short.MIN_VALUE);
Take into consideration that rssi values are usually negative (it
could be dBm but I am not sure).
On 28 ene, 20:47, Chris crystalredve...@gmail.com wrote:
I'm trying to determine location via bluetooth beacons and while I can
discover and find all of the devices around me, when I try to grab the
EXTRA_RSSI that's supposed to come through it doesn't work. Here's
the code I'm using and I get a 0 every time.
private final BroadcastReceiver mReceiver = new BroadcastReceiver() {
@Override
public void onReceive(Context context, Intent intent) {
Toast.makeText(ScannerActivity.this, In BroadcastReceiver,
3);
String action = intent.getAction();
// When discovery finds a device
if (BluetoothDevice.ACTION_FOUND.equals(action)) {
// Get the BluetoothDevice object from the Intent
BluetoothDevice device = intent.getParcelableExtra
(BluetoothDevice.EXTRA_DEVICE);
int rssi = intent.getIntExtra
(BluetoothDevice.EXTRA_RSSI, 0);
// Add the name and address to an array adapter to
show in a ListView
if (device.getBondState() !=
BluetoothDevice.BOND_BONDED) {
//do something
}
}
}
}
--
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
