[android-developers] Re: Android@Home status

[nemik]

Touché.

Lighting Science did reply to my contact form though and said they're
going to have another press release about it when more info is
available; and that they're targeting the first half of this coming
year.

On Dec 27, 10:07 am, TreKing  wrote:
> On Tue, Dec 27, 2011 at 9:56 AM, nemik  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://sites.google.com/site/rezmobileapps/treking> - Chicago
> transit tracking app for Android-powered devices

-- 
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

[android-developers] Re: Android@Home status

[nemik]

I thought the products presented at Google IO were ones that grew past
that 20% stage and had commitments to them. Shows what I know I guess.

On Dec 27, 1:05 am, Zsolt Vasvari  wrote:
> AFAIK, there has been no new official communications from Google
> related to Android@Home.  Maybe it was a cool 20% project and the guy
> left or whatever...
>
> On Dec 27, 12:17 pm, nemik  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 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 any of these products or frameworks from Google or
> > Lighting Science.
>
> > Does anyone know what is going on with this? It seems like it has a
> > lot of potential.

-- 
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

[android-developers] Android@Home status

[nemik]

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 any of these products or frameworks from Google or
Lighting Science.

Does anyone know what is going on with this? It seems like it has a
lot of potential.

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

Great job Fernando! Thank you for sharing your diff on this, it's
fantastic news.

On Jul 19, 5:48 am, Fernando Miguélez Palomo
 wrote:
> I got it working on 2.3.4_r1!!!
>
> The key was enabling discoverability but in card emulation mode. The strange
> thing is now I can detect two smart card types with an Arcontia smart card
> reader:
>
>    - ISO14443A tag CL1 tag (This is the Mifare 4K)
>    - FELICA RCS-885 424kbs tag (I suppose this is really the Javacard, not a
>    Felica card)
>
> I managed to write and read a block (4) to the Mifare 4K with default keys.
> Next thing will be investigating wheter 2.3.4 adds support by means of
> nxp-nfc library to directly send APDUs to the SE. You and Michael Roland
> already confirmed it was not possible with prior gingerbread versions.
>
> I post the corrected patch to get card emulation on 2.3.4_r1.
>
> One thing. Card stops being 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).
>
>  Nfc-app-2_3_4_r1.diff
> 31KViewDownload

-- 
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

[android-developers] Re: Can I sell hardware+app together on Android Market?

[nemik]

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  wrote:
> 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  wrote:
>
>
>
>
>
>
>
> > I don't see where it is prohibited 
> > here:http://www.android.com/us/developer-distribution-agreement.html

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

Fernando, the patches were against 2.3.1 or 2.3.2 I believe, a long
time ago (relatively). I have not had a chance to revisit this but I'm
fairly sure it will not work on 2.3.4+.

I'm sure some of the header defines have changed as well but try to re-
enable the ones I had if they exist? Good luck.

On Jul 18, 10:26 am, Fernando Miguélez Palomo
 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 of AOSP gingerbread did
> you use?
>
> Thanks

-- 
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

[android-developers] Re: Can I sell hardware+app together on Android Market?

[nemik]

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  wrote:
> I don't see where it is prohibited 
> here:http://www.android.com/us/developer-distribution-agreement.html

-- 
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

[android-developers] Re: Can I sell hardware+app together on Android Market?

[nemik]

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 so it can be used.
NXP's online-only compiler for its mBed dev kit uses a similar
approach.

On Jul 17, 3:03 pm, cellurl  wrote:
> I want to sell a companion piece of hardware with my app.
>
> Can anyone point me to where this is OK, not-OK
> in the terms.
>
> I need facts only please.
>
> Thanks
> -cellurl

-- 
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

[android-developers] Re: RFID tag detection

[nemik]

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 Prox cards for
example because they operate on the 125 kHz frequency.

On May 17, 5:19 pm, Pierre Yaacoub  wrote:
> Hello,
>
> I am trying to build an application that uses the new Android
> capability of detecting RFID (NFC) tags.
> The tags that I have are not NFC tags, that is, they are not of a
> special type (like URI ...).
> For my purposes, I do not care about parsing the tag data in a certain
> way (as would be the case in some NFC tags like URI or SmartText). I
> just need to access the bit vector that the tag sends, and use it as a
> unique identifier.
>
> Is it possible to do this? That is, if the tag is an RFID tag that is
> being detected by the phone, but isn't of any special type, can I
> access its bit vector?
>
> Thank you very much
>
> Pierre

-- 
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

[android-developers] Re: NFC testing rig?

[nemik]

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  wrote:
> Hi,
>
> We're going to fight with NFC for the next project and since I saw a few
> people with much more knowledge on the subject on that list I'd like to ask
> if anyone got any thoughts to share on building testing environment for such
> projects. I mostly need Android mobile and some standalone NFC device to
> test it all with. I did quick research yesterday yet I failed to find
> anything but Nexus S (I do not look for non-Android devices for this phase
> of the project, not sure if any exists anyway - I found some announcements
> but seem these did not turned into products yet). As for standalone device
> some companies seem to offer what I need too, 
> i.e.http://www.insidesecure.com/eng/Products/NFC-Productsso there's a hope :)
>
> Anyway, if anyone who spent some time on the subject and is willing to share
> the lesson, I am all ears. Thanks in advance :)
>
> Regards,
> Marcin Orlowski
>
> *Tray Agenda * - keep you daily schedule handy...
> *Date In Tray*  - current date at glance...
> WebnetMobile on *Facebook * and
> *Twitter
> *

-- 
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

[android-developers] Re: 1380 Paid Applications in One Free Torrent then How to SELL it?

[nemik]

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  wrote:
> > I can't imagine that is even close to 2% or 3%.
>
> I don't agree with the 2-3% at all.  Every time I've tried to send
> somebody a private APK to test something, most of them knew how to
> install it.   It maybe just the demographics of my app, though.

-- 
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

[android-developers] Re: 1380 Paid Applications in One Free Torrent then How to SELL it?

[nemik]

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 close to 2% or 3%. Most of your customers
want nice and easy access to the app through the Market and will pay
for it. I think most of them also believe that this is the only way to
get apps and they don't know what an APK is.

Focus on your customers, there's nothing you can about crap like this.
Make sure their experience with you is much, much better than through
piracy; it's pretty hard to screw this up but the music and movie
industries manage to do it. Try not to make the same mistake. The
people downloading these torrents won't pay you anyway even if you
took it away from them. Concentrate on the people that will.

On May 5, 4:54 am, Marcin Orlowski  wrote:
> On 5 May 2011 09:34, mot12  wrote:
>
> - Limit the lifetime of your app so the app requires updates every few
>
> > months (this is a tricky one, you are likely to lose a lot of users if
> > you don't alert them well in in advance that an update is required).
>
> My experience with this approach is that it's better to use two "deadlines".
> One is "soft expiration" where you pops someting (dialog/notification etc)
> that there's update and user have to update as the current version is no
> longer supported and "hard expiration" (perfectly at lest 2 or 3 weeks
> later than "soft") which enforces upgrade by simply halting current version.
> And make sure you do not push that too frequent. Each version shall
> live no less than 1,5-2 months or your (l)users will rant.
>
> Regards,
> Marcin Orlowski
>
> *Tray Agenda * - keep you daily schedule handy...
> *Date In Tray*  - current date at glance...
> WebnetMobile on *Facebook * and
> *Twitter
> *

-- 
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

[android-developers] Re: NFC tags with write protection?

[nemik]

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  wrote:
> Hi,
>
> I've got some NFC tags and have written some data into them using the
> NXP Tag Writer app available from marketplace.
>
> After writing some data in the tag, I'd like to remove write-access to
> it so people can't overwrite the tag data. Using the Tag Writer app, I
> get a message stating that write protection is not available for the
> tags I have.
>
> Does anyone know of any tags I can order which are writeable and have
> write protection available too?
>
> Thanks

-- 
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

[android-developers] Re: Making SmartCard feature available in Google Nexus S

[nemik]

1. There are no examples, this is green territory.

2. Again, it's new and up to you. Personally though, not sure I would
bother. When an API does come out, it'll be different from yours and
you'll need to re-do things. I'm also pretty sure that no end-users
are going to want to install your custom ROM for some of this
functionality. Unless you're just doing it for yourself or internal
phones you control, this isn't worth developing to sell or distribute
to 'regular' users.

3. Pretty much, though you might not need to install any app. You can
just let it emulate the entire time and key off of that UID from the
emulated tag. You can talk to it as if it were a MiFare card though if
you don't do wired emulation mode.

4. No clue and Google isn't saying anything either.

On May 3, 11:27 am, Alberto González  wrote:
> Hi,
>
> I'm back to ask a little questions about nfc.
>
> I have a NFC tag reader and Google Nexus S. I want to create an app
> for Google Nexus S that emulates a nfc tag.
>
> 1) Where I could find example code in java? Because there isn't no
> info about this.
>
> I think it could be similar to:
> -Creating the nfc tag to emulate (give him a value)
> -Activating emulation of nfc tag
> -Wait for a NFC tag reader signal (NFC tag reader sends a message
> telling to the phone, msg received?)
> -Desactivating emulation of nfc tag
>
> My NFC reader is CPR40.30-USB (More 
> info:http://www.toptunniste.fi/topshop/product_details.php?p=264&c=76).
>
> 2) Should I create new functions to use it and create a new SDK? Did
> you know any tutorial to modify SDK and create other functions? Or
> should I create it in NDK using native code?
>
> 3) The steps to enable Google Nexus S Smart Card functionality will
> be:
>
> -Unlock the boot loader
> -Root Google Nexus S
> -Create 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  wrote:
>
>
>
>
>
>
>
> > 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/threa...
>
> > I was able to get the SmartMX secure element to be exposed in both
> > wired mode and visible to other NFC readers. Other than that though,
> > I'm not sure much else can be done to the SE such as loading
> > applications to it because it is locked down and you need the secret
> > keys to write to those parts of its memory. I'm pretty sure only
> > Google and NXP know what those keys are.
>
> > I did not make my changes to the Cyanogen source though; but rather
> > the plain Android source base. After unlocking the bootloader on the
> > Nexus S and loading my version of the OS, NFC emulation mode was
> > working.
>
> > On Apr 26, 5:51 am, Alberto González  wrote:
>
> > > Hi all,
>
> > > I undestand that smartcard feature is not available for developers.
>
> > > I readed in this website that is possible to available 
> > > it:http://www.nearfieldcommunicationsworld.com/2011/02/13/35913/uncovere...
>
> > > The clues that I get to make it available is:
> > > "Download the source (actually from CyanogenMod 7 to have the full
> > > build environment for the new Nexus S), make the appropriate changes
> > > to the code, recompile everything and put it back into the phone and
> > > it works — Nexus S supportscardemulation and SWP!"
>
> > > Also I need to root it... I know..
>
> > > The question is: are there anybody who could provide more info about
> > > this?
>
> > > Thanks in advantage

-- 
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

[android-developers] Re: Making SmartCard feature available in Google Nexus S

[nemik]

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=gst&q=secure+element+diff%27s#dec4843abd73d9e9

I was able to get the SmartMX secure element to be exposed in both
wired mode and visible to other NFC readers. Other than that though,
I'm not sure much else can be done to the SE such as loading
applications to it because it is locked down and you need the secret
keys to write to those parts of its memory. I'm pretty sure only
Google and NXP know what those keys are.

I did not make my changes to the Cyanogen source though; but rather
the plain Android source base. After unlocking the bootloader on the
Nexus S and loading my version of the OS, NFC emulation mode was
working.

On Apr 26, 5:51 am, Alberto González  wrote:
> Hi all,
>
> I undestand that smartcard feature is not available for developers.
>
> I readed in this website that is possible to available 
> it:http://www.nearfieldcommunicationsworld.com/2011/02/13/35913/uncovere...
>
> The clues that I get to make it available is:
> "Download the source (actually from CyanogenMod 7 to have the full
> build environment for the new Nexus S), make the appropriate changes
> to the code, recompile everything and put it back into the phone and
> it works — Nexus S supports card emulation and SWP!"
>
> Also I need to root it... I know..
>
> The question is: are there anybody who could provide more info about
> this?
>
> Thanks in advantage

-- 
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

[android-developers] Re: SIM NFC (card emulation). SWP support?

[nemik]

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 the phone.
This has been done if you search around, but you have to then run your
own version of Android.

On Mar 28, 8:52 am, Gorka Hernando  wrote:
> Hi,
>
> I have just get a SIM card where a MIFARE Classic 1k tag has been
> emulated. I put it into the Samsung GT-5230N mobile phone and I can
> read it with my NFC reader as a common tag. This is possible because
> the 5230N has full SWP (Single Wire Protocol). Moreover, I can connect
> to the applet running in the SIM and check the values as I can do with
> the reader and show the values on the screen, e.g. the tickets
> remaining.
>
> As far as I see in the Internet, the Nexus S has SWP support. Is that
> true? I mean, right now is the SWP available? If I insert the SIM into
> the Nexus S would it work as well as it does with the S5230n? Is it
> possible to access the applets and read the values to show them on the
> screen??
>
> Thanks a lot.

-- 
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

[android-developers] Re: Android Application Sold to 100,000 Users

[nemik]

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 answer are you looking for?

On Mar 20, 11:03 pm, varinag gold  wrote:
> > You realize this is going to vary wildly between different apps and will
> > give you absolutely no indication how your own app will perform ... right?
>
> I agree with it but I want to see general trend of Android Market and
> users for priced applications.
>
> On Mar 21, 11:48 am, TreKing  wrote:
>
>
>
>
>
>
>
> > On Sun, Mar 20, 2011 at 10:43 PM, varinag gold wrote:
>
> > > I am looking data for applications with some price tag such as 1.00 USD or
> > > 0.99 USD.
> > > with a market access all over the world (provided selling/purchasing is
> > > permitted in those countries).
>
> > You realize this is going to vary wildly between different apps and will
> > give you absolutely no indication how your own app will perform ... right?
>
> > --- 
> > --
> > TreKing  - Chicago
> > transit tracking app for Android-powered devices

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

mtk, very cool! So when you did that call directly (somewhere in init
of the jni code?) you got it to detect? How are you sending APDU
commands? Also, if I understand wired mode correctly, the tag is not
emulated externally to other readers; it's only available internally
using the NFC API?

gusdgg, yes, I saw the secure elements using the
getSecureElementList() and just doing logging with those and observing
them using `adb logcat`. I think that is in one of the diffs I posted.
It worked OK for me and I wasn't seeing any permission errors. Though
I never even bothered to do it via reflection on the stock firmware
since I figured it would just deny it. Your findings clearly confirm
that.
As for the SmartMX chip, maybe you're right. But I suppose it could
also be built into the PN544 chip itself. I have no idea, I wasn't
able to find any datasheets that talk about it and have no details on
the NXP chips Samsung's been sourcing for the Nexus S.

On Jan 21, 11:28 am, gusdgg  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 containing a secure element like SmartMX,
> did you get the secure element list with the method
> getSecureElementList() in the patched version? I called this method
> (via reflection, no patched yet) but it gets the error message
> "WRITE_SECURE_SETTINGS permission required"
>
> As you may know, there are an excelent nexus s teardown 
> (http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1) from iFixit. You'll
> see there, in the step 7 - 2nd picture, the NXP PN544NFCchip closely
> located to the UICC slot, but as far I can see there isn't any SmartMx
> chip in that picture, nor in the others.
>
> Regards,
> gusdgg

-- 
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

[android-developers] Re: NFC Reader / Transmitter

[nemik]

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  wrote:
> You do not understand.
>
> I do not want to simply use my NFC enabled phone as a dumb reader.
>
> I want to programmatically control an interaction between my NFC phone
> and my computer.
>
> I want a true information exchange.
>
> I do not want a simple one way read.
>
> Mike
>
> On Jan 24, 8:22 pm, Agus  wrote:
>
>
>
>
>
>
>
> > use RFID tag
>
> > On Mon, Jan 24, 2011 at 9:16 PM, mduffy215  wrote:
> > > I am planning ahead for the next release of Android.
>
> > > Does anyone know of a product that is an NFC reader and also a
> > > transmitter (i.e., can it send information to and NFC phone and read
> > > information from and NFC phone)?
>
> > > Thx!
>
> > > Mike
>
> > > --
> > > 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

-- 
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

[android-developers] Re: Does Any one Building Android source code in Mac

[nemik]

Oh and to answer the last question:

No, it is not better than Ubuntu. The package managers on OS X suck
pretty bad. There is nothing like 'aptitude' on there and the
replacements for it (MacPorts and Homebrew) are IMO pretty mediocre.

Though thanks to Macports' and Homebrew's high CPU usage 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  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).
>
> 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 sparsebundle thing) that is case-
> sensitive (the default OS X FS (HFS+) is not). I followed this
> tutorial:http://www.quietlycoding.com/?p=1
>
> Note that for building 'gingerbread' you don't need Java 1.5, the 1.6
> included on OS X works just fine, so just start at step 2.
>
> Good luck.
>
> On Jan 20, 9:59 am, Desu Vinod Kumar  wrote:
>
>
>
>
>
>
>
> > Hi All,
>
> > Does any one using Mac Os for Building Android Source code.
>
> > How was performance & is it better compare to Ubuntu ?
>
> > I am planning to buy Mac Book Pro, please let me know your opinions.
>
> > TIA
>
> > --
> > Regards
> > ---
> > D Vinod Kumar
> > R & D Engineer - Android Platform
> > Mobile : 09916009493http://in.linkedin.com/in/desuvinodkumar

-- 
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

[android-developers] Re: Does Any one Building Android source code in Mac

[nemik]

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 sparsebundle thing) that is case-
sensitive (the default OS X FS (HFS+) is not). I followed this
tutorial: http://www.quietlycoding.com/?p=1

Note that for building 'gingerbread' you don't need Java 1.5, the 1.6
included on OS X works just fine, so just start at step 2.

Good luck.

On Jan 20, 9:59 am, Desu Vinod Kumar  wrote:
> Hi All,
>
> Does any one using Mac Os for Building Android Source code.
>
> How was performance & is it better compare to Ubuntu ?
>
> I am planning to buy Mac Book Pro, please let me know your opinions.
>
> TIA
>
> --
> Regards
> ---
> D Vinod Kumar
> R & D Engineer - Android Platform
> Mobile : 09916009493http://in.linkedin.com/in/desuvinodkumar

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

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
http://nemik.net/code/android-nfc/libnfc-nxp.diff for
http://android.git.kernel.org/?p=platform/external/libnfc-nxp.git;a=summary

These are just based on the on the open source, plain vanilla Android
Gingerbread codebase. If you patch it with the diffs above, you can
build the OS, upload the images to the phone's bootloader (make sure
to unlock the bootloader first) and then see it for yourself.

It is pretty badly broken and this is just to prove that it can kinda
work, I hacked it up pretty hard.

Also, I added a lot of LOGD()'s in the NFC app's JNI so I could see
what was going on when trying things out on the phone so I could read
it when doing an 'adb logcat' on the computer with the phone attached
over USB.

Have fun!

On Jan 17, 9:11 pm, Ajith Kamath  wrote:
> I still dont have nexus s but there is a high probability that its Embedded
>
> Yes Keys are private and most likely needs to be provided by Service
> Provider. The same thing has been mentioned in nokia forum
> But I am not sure  how this will be done for nexus S.(may be there are ties
> with Service Provider)
>
> If anyone can explain OTA agent and its communication with TSM, it would be
> very helpful. Since this too is not clear (w.r.t android)
>
> Regards,
> Ajith
>
>
>
>
>
>
>
> On Tue, Jan 18, 2011 at 5:41 AM, Dominik  wrote:
> > According to the NXP documentation of PN544, three SE variants are
> > supported:
> > - SIM Card (via UICC)
> > - Embedded (SmartMX security chip)
> > - SD Card
>
> > Do you know which version is intended to be used by the Nexus S
> > device?
>
> > The above messages describe attempts to enable SmartMX. As soon as
> > access to this SE is possible:
> > Which keys do you use to access the SE? Such keys should be private
> > and not generally be known.
>
> > I am at a loss.
>
> > - Dominik

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

Ajith,

According to 
http://discussion.forum.nokia.com/forum/showthread.php?199442-6212-device-how-to-work-with-the-secure-element
the CN072 is a secure element in the Smart MX family. I'm not sure the
same one is in the Nexus S, but I presume the one in there is at least
very similar.

Here is the info on it:
http://www.nxp.com/acrobat_download2/other/identification/SFS107710.pdf

I'm still trying to figure out how to get access to it as well, for
reading or writing. I doubt there are any specific commands for it
though, it just takes regular commands over ISO14443 just like other
MiFare cards.

On Jan 9, 11:31 pm, Ajith Kamath  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 to enable Secure element?
> what are MifarePlus, Desfire, Topaz . Is it a Card type or Secure Element?
>
> * Also where is the general read-write methods for entry of Secure element.
> All I can see is phLibNfc_SE.c is methods for getting list of secured
> element, selecting secure element, deselecting.
> * But method for exchange of data is not present. Can you tell me where can
> I find this?
>
> * In libnfc-nxp There are files like  phFriNfc_NdefMap.c,
> phFriNfc_MifareULMap.c,  phFriNfc_TopazMap.c, phFriNfc_TopazDynamicMap.c,
> phFriNfc_DesfireMap.c, phFriNfc_FelicaMap.c.
> Can you tell me what these files are used for. The current comments in the
> file do not provide sufficient information
>
> * I am trying to use Wired Mode, Hence phHciNfc_WI.c will be used to
> communicate between Controller and Secure element right?
>
> Please advice.
>
> Regards,
> Ajith
>
> Hi
>
>
>
>
>
>
>
> On Sun, Jan 9, 2011 at 1:00 AM, nemik  wrote:
> > I was able to enable a secure element the other day by messing around
> > with this external/libnfc-nxp library. I enabled SMX (SmartMX) in the
> > config headers, and upon booting and monitoring `adb logcat` during
> > boot I saw 1 secure elements (a SmartMX one) had been enabled. I was
> > then able to change the mode in NfcService.java to card emulation
> > mode.
>
> > The Nexus S is now emulating a MiFare Classic 4k card. However, I am
> > not able to read sectors from the card directly. I've been trying to
> > use the micmd tool to do that but things act pretty strangely. For
> > example, I tried to read block 0 and micmd tells me "Could not read
> > the data block! Tag halted, reconnecting..." but what's even stranger
> > is that at that point, 'adb logcat' shuts itself off. As if that read
> > command somehow interfered with USB or logging?
> > However trying `a` commands to authenticate in micmd always works for
> > some reason and it'll even pretent to write and persist data to
> > blocks; but of course that data never actually gets persisted to the
> > emulated card. Maybe this is a bug in micmd?
>
> > Does anyone know if the Nexus S hardware (or its PN544 NFC chipset)
> > even contains a hardware secure element like SmartMX? I tried also
> > enabling UICC but that didn't seem to work at all and NFC service
> > wouldn't even start in that case. Plus my SIM card is MANY years old
> > and not sure it'd even work...
>
> > Either way, I used libnfc.org's `nfc-mfclassic` tool to dump out the
> > contents of that emulated 4k card. It is here:
> >http://pastebin.com/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  wrote:
> > > 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
> > > theNFCstandard will have to wait for a future kernel release.
>
> > > On Dec 7, 5:42 am, Gruntz Dominik  wrote:
>
> > > > Hi everyone,
>
> > > > Do I see it right, that the Android 2.3NFCAPI does not provide
> > functionality to access a secure element? A secure element is a smartcard
> > connected to theNFCcontroller, i.e. a secure storage in the device, either
> > embedded in the mobile phone, on the SIM card or on a SD card.
>
> > > > With JavaME access to the secure el

[android-developers] Re: NFC Secure Element

[nemik]

I was able to enable a secure element the other day by messing around
with this external/libnfc-nxp library. I enabled SMX (SmartMX) in the
config headers, and upon booting and monitoring `adb logcat` during
boot I saw 1 secure elements (a SmartMX one) had been enabled. I was
then able to change the mode in NfcService.java to card emulation
mode.

The Nexus S is now emulating a MiFare Classic 4k card. However, I am
not able to read sectors from the card directly. I've been trying to
use the micmd tool to do that but things act pretty strangely. For
example, I tried to read block 0 and micmd tells me "Could not read
the data block! Tag halted, reconnecting..." but what's even stranger
is that at that point, 'adb logcat' shuts itself off. As if that read
command somehow interfered with USB or logging?
However trying `a` commands to authenticate in micmd always works for
some reason and it'll even pretent to write and persist data to
blocks; but of course that data never actually gets persisted to the
emulated card. Maybe this is a bug in micmd?

Does anyone know if the Nexus S hardware (or its PN544 NFC chipset)
even contains a hardware secure element like SmartMX? I tried also
enabling UICC but that didn't seem to work at all and NFC service
wouldn't even start in that case. Plus my SIM card is MANY years old
and not sure it'd even work...

Either way, I used libnfc.org's `nfc-mfclassic` tool to dump out the
contents of that emulated 4k card. It is here: http://pastebin.com/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  wrote:
> 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
> theNFCstandard will have to wait for a future kernel release.
>
> On Dec 7, 5:42 am, Gruntz Dominik  wrote:
>
>
>
>
>
>
>
> > Hi everyone,
>
> > Do I see it right, that the Android 2.3NFCAPI does not provide 
> > functionality to access a secure element? A secure element is a smartcard 
> > connected to theNFCcontroller, i.e. a secure storage in the device, either 
> > embedded in the mobile phone, on the SIM card or on a SD card.
>
> > With JavaME access to the secure element was provided with JSR177 which 
> > supported the communication with smart card applications usind APDU 
> > commands. I have not seen comparable functionality in package android.nfc.
>
> > Thanks for any hints
> > Dominik

-- 
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

[android-developers] Re: NFC Secure Element

[nemik]

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, Gruntz Dominik  wrote:
> Hi everyone,
>
> Do I see it right, that the Android 2.3NFCAPI does not provide functionality 
> to access a secure element? A secure element is a smartcard connected to 
> theNFCcontroller, i.e. a secure storage in the device, either embedded in the 
> mobile phone, on the SIM card or on a SD card.
>
> With JavaME access to the secure element was provided with JSR177 which 
> supported the communication with smart card applications usind APDU commands. 
> I have not seen comparable functionality in package android.nfc.
>
> Thanks for any hints
> Dominik

-- 
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