Dominik,
Yea, that's right. All it does currently is read; at least via the
Java API. If you look at the kernel source though, a bunch of ifdefs
which allow for emulation were all disabled. So full compliance with
the NFC standard will have to wait for a future kernel release.
On Dec 7, 5:42 am,
/zKZ2ELcw
Seems to be entirely blank which is why I'm wondering if these aren't
some default values it would spit out anyway even if no SmartMX module
existed?
If anyone has any more insights into this, I'd be very happy to hear
them.
-Nemanja
On Dec 19 2010, 7:26 pm, nemik ne...@nemik.net wrote
cards.
On Jan 9, 11:31 pm, Ajith Kamath sjce.aj...@gmail.com wrote:
Hi Nemik
* I have small doubt with current implementation. Is SmartMX a Secure
Element ?If so can you give me examples?
* I have checked libnfc-nxp , enabling P2P parameter was at phnfcconfig.h.
what needs to be done
Sorry for not replying in a while, been very busy with projects at
work.
I posted my diff's to enable the Nexus S to emulate an NFC tag. The
links are below:
http://nemik.net/code/android-nfc/Nfc-app.diff for
http://android.git.kernel.org/?p=platform/packages/apps/Nfc.git;a=summary
and
I've developed both apps and the actual Android system itself from
source just fine on OS X (10.6 on a macbook pro).
Performance is just fine IMO and runs very fast. The only thing is for
building the Android OS, you'll need to create another filesystem on
your mac (I just did it as a file, a
and the
excellent heat transfer properties of the metal material used to build
macbook pro's, they make great hand-warmers.
On Jan 20, 3:14 pm, nemik ne...@nemik.net wrote:
I've developed both apps and the actual Android system itself from
source just fine on OS X (10.6 on a macbook pro
I'm using the Touchatag-branded ACR122 USB NFC reader. It works pretty
great for playing around with Android via the Nexus S.
On Jan 25, 1:18 am, mduffy215 mduffy...@gmail.com wrote:
You do not understand.
I do not want to simply use my NFC enabled phone as a dumb reader.
I want to
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
I think the general trend is that you won't make much money; though
you never know until you try. Remember that all those huge successes
you read about are outliers. The majority of apps just sorta get by or
flop. Just throw your best hat into the ring and see what happens.
What other kind of
Get MiFare UltraLights. They have protection bits that you can set so
that no more writes can occur. I believe this can also be done with
MiFare 1k/4k/etc Classic tags as well but the UL's are cheaper.
On May 4, 4:08 pm, Mark Wyszomierski mar...@gmail.com wrote:
Hi,
I've got some NFC tags and
Please try to imagine the percentage of people you know around you
that would be capable of:
* enabling debug to install apps remotely
* getting the necessary BitTorrent programs
* using them to download this file
* extract that apps and install them to the phone
I can't imagine that is even
Read through the comments in that link. Look how many of them are
asking how to load/install the apps from SD cards and get updates. If
you can't compete with that you're going to be screwed on the Market
anyway; whether your apps are on pirate sites or not.
On May 5, 7:41 pm, Zsolt Vasvari
The ACR122U/Touchatag USB adapter has been pretty great for my
purposes so far. The SCL3711 USB adapter is also pretty good. I use
those in combination with libnfc.
On May 10, 5:02 am, Marcin Orlowski webnet.andr...@gmail.com wrote:
Hi,
We're going to fight with NFC for the next project and
I don't know about a bit vector but most NFC tags (whether type A,
B, Mifare 1k/Ultralight/etc) all have a UID. This is a unique
identifier for the tag and what you're looking for.
But the tags you use will have to be of the 13.56 MHz hi-frequency
variety. You won't be able to read most older HID
Gorka,
Right now, with the Gingerbread 2.3.3 release, it is not possible.
There is no support for emulation or SWP in that distribution. However
you could modify the released source code for 2.3.3 and modify some
macro definitions to compile your own version with SWP support that
would work on
Alberto,
A while back I posted my diff's to the Android source code to get this
working here:
http://groups.google.com/group/android-developers/browse_thread/thread/d5fc35a9f16aa467/dec4843abd73d9e9?lnk=gstq=secure+element+diff%27s#dec4843abd73d9e9
I was able to get the SmartMX secure element to
the modified rom (with the diff you posted
inhttp://groups.google.com/group/android-developers/browse_thread/threa...
).
-Load the new rom.
-Install the app
4) Do you know when all nfc funcionality will be available in the
official SDK?
Thanks!
On 26 abr, 17:22, nemik ne...@nemik.net wrote
I got excited about this supposedly 6LowPAN-powered Android@Home
project shown at Google IO and also here
http://www.youtube.com/watch?v=AL2AJanKrqg
but no new info has come out. The guy presenting it at IO said it
would be out by the end of the year but I have looked hard and have
yet to find
. Maybe it was a cool 20% project and the guy
left or whatever...
On Dec 27, 12:17 pm, nemik ne...@nemik.net wrote:
I got excited about this supposedly 6LowPAN-powered Android@Home
project shown at Google IO and also
herehttp://www.youtube.com/watch?v=AL2AJanKrqg
but no new info has
at 9:56 AM, nemik ne...@nemik.net wrote:
I thought the products presented at Google IO were ones that grew
past that 20% stage and had commitments to them.
Two words: Google Wave.
---
--
TreKing http
Might be best to sell the hardware on your own online store and
through other sites willing to sell it. Then release the app for free
and make it work only with the hardware.
You could also give each HW device a serial number and that number has
to be entered when starting the app to register it
Even if it's not, purchases from the Android store don't ask for
shipping address, postage options/prices, etc. It's just not set up
for physical goods and even if you somehow got it working, I bet it
would be a very painful process for both you and your customers.
On Jul 17, 6:12 pm, cellurl
.
On Jul 18, 10:26 am, Fernando Miguélez Palomo
fernando.migue...@gmail.com wrote:
Hi Nemik,
I just applied your patches to 2.3.4_r1 version (I had to change them a
little bit) but card emulation does not seem to work (an external reader
detects nothing). Could you please tell us what tag
cellurl: https://checkout.google.com/inapppayments/ this might be just
what you're looking for...if you're in the USA.
On Jul 17, 7:13 pm, nemik ne...@nemik.net wrote:
Even if it's not, purchases from the Android store don't ask for
shipping address, postage options/prices, etc. It's just
readable from an external reader after screen
goes off and back on. However if you disable NFC and re-enable it (from
settings) card is discoverable again.
Thanks nemik for your work (you can update your patches with these
corretions to work with gingerbread 2.3.4_r1 at your site if you want
25 matches
Mail list logo
