Since I wrote this I've create a test app that listens for an NDEF & TECH discovered intent and then, through use of an internal flag variable within the onNewIntent method, either reads or writes to the discovered tag. I've gotten this to work with a normal type 2 tag by performing the first action, then removing the tag from the phone for a moment before bringing it back. Seems to work fine, although I still dont know if it'll work for an active device rather than a normal tag.
Would still like to hear from anyone who's done a similar thing between two active devices though. cheers! LS On Oct 21, 5:16 pm, LS <lsibbald...@gmail.com> wrote: > Hi everyone > > I'm looking in to NFC for a project I have on the table, and one of > the requirements is for an NFC message to be sent from a mobile device > (nexus) to a non-android device (target), which should process the > message and return an NFC response. > > Now, I understand that under normal circumstances this wouldnt be > possible. However, I wondered if some learned person could take a look > at my proposal and suggest any obvious problems with it: > > 1. nexus detects when an nfc connection is made. In this case, when > the device is put in front of the non-android (target) device > > 2. an intent is received and processed in my app and in response the > app writes out an ndef payload > > 3. the target device processes the ndef record and does some > mechanical thing at its side > > 4. in the meantime, having sent its ndef message, the Nexus sets up a > listen intent. > > 5. the target device, having finished doing its thing, *resets its NFC > chip* (I assume for the moment the target device is capable of doing > this) so that the NFC field is effectively broken and then > (presumably) re-established with the nexus > > 6. the nexus re-detects the NFC connection and, because it is in read > mode, receives the ndef message from the target and processes the > data. > > This would all have to be accomplished in the app using the nfc read/ > write modes, rather than any P2P capabilities. I have a question mark > around using the read/write modes between two active devices (i.e. no > passive tags) so if someone could comment on this that'd be real > handy. > > Would this work? > > I was also thinking of using SNEP in Android 4 but I'm not sure > whether this offers any form of challenge/response or if it is just an > updated version of the previous P2P implementation (through the > addition of a couple of useful callback listeners). SNEP would at > least allow me to change modes when I detected my NDEF had been sent, > but i'm not sure what else. > > Would really appreciate any insight. > > Cheers > > LS > > p.s. we are also considering a Bluetooth only approach but for the > purposes of this message I'd really like to focus on NFC only > solutions. -- 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
