I'm updating an app to work with android 4.0.1 and running into a
problem.
The app generates an xml export using the following code (exception
handling removed):
File file = new
File(Environment.getExternalStoragePublicDirectory(XMLExport).toString());
file.mkdirs();
file = new File(
I have not heard anything. I'm hoping these fixes are coming in 4.0.
For long commands I'm forced to use a large FWT which sucks as it
slows all interaction with the tag down. I'm hoping the WTX gets
fixed so I can ask for a timeout extension on only the commands that
need it.
Dean
On Oct 28,
This is for Google NFC engineers (Nexus S, PN544 hardware/firmware
stack), hopefully they will see this. Or perhaps there is a better
why to contact said engineers?
I'm working on a semi passive NFC (ISO14443A) custom sensor tag
(hardware/firmware stack) which I would like to pair with the Nexus
:28 am, Nikolay Elenkov nikolay.elen...@gmail.com wrote:
On Thu, Jun 2, 2011 at 12:47 PM, Dean Brotzel dean.brot...@gmail.com wrote:
Is it possible to receive a message/intent from Android for when a tag is
removed from the smart phone's influence (much like when a tag is brought
Is it possible to receive a message/intent from Android for when a tag is
removed from the smart phone's influence (much like when a tag is brought
into to the smart phone's influence) ?
I noticed from logcat the following log message: D/NativeNfcTag( 3625):
Tag lost, restarting polling loop,
5 matches
Mail list logo
