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 like the tag reader same program) and then use RawTagConnection to send APDU bytes. Btw I think the SE is GP compliant! When I send the select command with zero AID (Select ISD per GP, 00 a4 04 00 00) - it promptly responds back with FCI template! So it looks like we can use install apps into the SE, once we have the keys? Sorry I'm new to GP so learning stuff as I go...
On Jan 27, 10:25 pm, nemik <ne...@nemik.net> wrote: > 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? > > gusdgg, yes, I saw the secure elements using the > getSecureElementList() and just doing logging with those and observing > them using `adb logcat`. I think that is in one of the diffs I posted. > It worked OK for me and I wasn't seeing any permission errors. Though > I never even bothered to do it via reflection on the stock firmware > since I figured it would just deny it. Your findings clearly confirm > that. > As for the SmartMX chip, maybe you're right. But I suppose it could > also be built into the PN544 chip itself. I have no idea, I wasn't > able to find any datasheets that talk about it and have no details on > the NXP chips Samsung's been sourcing for the Nexus S. > > On Jan 21, 11:28 am, gusdgg <gus...@gmail.com> wrote: > > > > > 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 the patched version? I called this method > > (via reflection, no patched yet) but it gets the error message > > "WRITE_SECURE_SETTINGS permission required" > > > As you may know, there are an excelent nexus s teardown > > (http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1) from iFixit. You'll > > see there, in the step 7 - 2nd picture, the NXP PN544NFCchip closely > > located to the UICC slot, but as far I can see there isn't any SmartMx > > chip in that picture, nor in the others. > > > Regards, > > gusdgg -- 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
