Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
02-06-2013 04:26 AM - edited 02-06-2013 07:23 AM
Using Blackberry 7.1, in a variety of devices:
We have an application with some screens registered as NDEFMessageBuilder and NDEFPushStatusCallback. They correcty return the NDef message and it all works perfectly and wonderfully in all devices. Once you start using a FilePicker, and access any folder inside the filepicker, the app starts being unable to transmit anything througt NDEF/NFC, even the 'buildNDEFMessages' does not get called.
I tried unregistering and re-registering the NDEFMessageBuilder, placing the NDEFMessageBuilder in another class or even bundle... Tried all the posible combinations about register/unregister, in all possible timeline moments when opening the FilePicker. But nohing helps, the app cannot send NDEF/NFC after opening the filepicker and accessing a folder.
Once I Close/restart the app it sends NDef perfectly but, once you re-open the filepicker and acces a folder inside the filepicker it continues failing.
Curiosity: After the FilePicker breaks the NFC/Ndef, it starts sending FRAME_REJECT LLCP packets throught NFC, and all other applications work just fine... but the one that opened the FilePicker do not...
Solved! Go to Solution.
02-07-2013 05:18 AM - edited 02-07-2013 05:18 AM
It seems that some NFC Responders/devices can handle LLCP Frame reject packets in some way... and then they can recover the NFC of the blackberry device/app.
Altought it seems that the frame reject is malformed contrasting with LLCP NFC Forum specs. It has no reason of the frame reject, which is obligatory.
Now i'm trying to sniff the bytes that those NFC Responders send to recover the frame reject state and replicate them...
But this is not a good solution, the blackberry device should NOT be sending malformed LLCP Frame rejects....
02-07-2013 08:45 AM
After lots of research... it seems that the LLCP was an Aggregated frame with two connect packets inside..... one for the handover and one for the snep connection.....
Maybe when opening the filepicker there where the posibility to use a handover nfc conncetion or use the application registered snep connection, this is why the blackberry device returned an aggregated frame....
Some devices implement those aggregated packets and some dont...
obiously i do not have it implemented in my nfc library...
i will implement it asap.
sorry for the inconvenience...