Forum Replies Created

  • Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    27. April 2015 at 13:47
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    David,

    That's good news if we can select a tag type. That'll help.

    Don't be sorry. Thanks for your kindness.

    June will be pretty late. I guess we have to work with datasheets again. :-)

    Thanks A Lot.
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    27. April 2015 at 11:15
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    Thanks David.

    I forgot to monitor my reply and didn't get any notification about your response.

    Anyways, if that is the case, I need to find out some work around indeed.

    This also raises a question, is NXP Tag Writer application based on this MiFARE SDK? If yes then that application should also behave same but it does not. :-)

    I have implemented NFC adaptor logic before in another application and it does not ever say that card is lost.

    We really need it fast. Current behavior is not accepted under any circumstance. We can't request users to keep the tag attached for couple of seconds.:-|

    Once android phone notify using the tone, user should be able to detach the tag and data should be read every time. This is the best case scenario we are looking for.

    Thanks for help.
    Good Day.
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 17:47
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    It's okay. :-)

    At least someone has same issue reproduced, enough for today.

    And
    We live to fight another day.

    Thanks,
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 16:25
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    David,

    Tag is recognized faster (recognized in onNewIntent) but MiFARE SDK(Intent filter) takes almost 200 milliseconds to make callback that contains my logic.

    I have more than 10 tags and couple of devices Galaxy Nexus, ASUS Nexus 7 tab etc.

    The sooner i'll get the call back, the sooner i'll be able to perform my logic. Is there any work around?
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 15:33
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    Try to read tag with NXP TagWriter from google play store. It works amazing. Seldom fails to read if recognized. We want our application reliable like that one.
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 15:13
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    David,

    I appreciate your help but my callback was defined as a separate variable like,

    protected void onNewIntent(Intent intent) {
    libInstance.filterIntent(intent, callback)

    }

    Nxpnfclibcallback callback = new Nxpnfclibcallback()
    {
    @Override
    public void onNTag203xCardDetected(NTag203x arg0) {
    Log.i(TAG,"NTAG 203x card Detected" );
    arg0.connect();
    }
    }

    I don't think android dislike this notation. Anyways, tried your code and its behaving same.:-|
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 14:40
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    Also, NTag203x don't have any personalize method. I think it doesn't need this process.

    Secondly, i only format NFC tag if its not already T2 formatted. Otherwise i just overwrite the NDEF message. So, it should not return "Tag Lost" exception if it works the way you say.
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 14:36
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    Hi,

    I'm using exact copy of sample application code. On new intent , following line throws the exceptions,

    protected void onNewIntent(final Intent intent)
    {

    libInstance.filterIntent(intent, callback); This is non-reachable code. I don't have source code for this one.

    super.onNewIntent(intent);
    }


    Sometimes, Unknown Error or IO Exception.

    Good thing is that i can read my data successfully even after these exception if i keep the tag attached to phone for 2-3 seconds.

    I'm just concerned about late response of application after the tag is recognized.

    99% my Nexus 7 5.1 is able to recognize the tag with the notification sound but read operation does not happen because either the NXPnfclib has crashed due to some "IO Exception or Transcive exception" or even spent too much time returning to callback so that i can continue my logic.

    From new intent to callback method it takes 150 milliseconds on ASUS Nexus 7.
    Rest of my logic takes 15 milliseconds.

    So, in my understanding of this issue, MiFARE library is doing alot of processing.


    This issue is easily reproducible with sample app.
    + 0  |  - 0

    Re: Re: Unknown Error Exception Thrown For NTag203x Tags

    23. April 2015 at 11:16
    in reply to: Unknown Error Exception Thrown For NTag203x Tags
    As a result of this delay ~300 milliseconds,

    When i read NDEF, mostly it says, "Tag Lost". Now, other applications successfully read immediately once tag is recognized no matter how quick Tag is attached and detected.

    I don't know what are development people processing while detecting card type and returning the appropriate call back. it should not take this much time.

    I don't want to write my own call back logic after reading card type my self.

    Please help!
    + 0  |  - 0

    Re: Re: DESFire NDEF Write Exception with SDKLite

    8. April 2015 at 14:03
    in reply to: DESFire NDEF Write Exception with SDKLite
    Thanks David for your response.

    I'm already doing authentication and personalize. Also, i'm able to successfully write bytes data using the public void write(byte[] data) method.

    Above exception was only happening while using

    public void writeNdef(byte[] masterKey, NdefMessage msg)

    Anyways, we yesterday bought Advanced SDK. It's clearly different from the lite version. I hope we will not face this issue in Advanced version. :-)

    Thanks.
    Bilal
    + 0  |  - 0
Viewing 10 posts - 1 through 10 (of 10 total)