Today is Samstag, 23rd März 2019

Posts Tagged ‘android’

SEEK/OMA is now available Android SDK

Four years after the SEEK Project was started by G&D, the library for accessing the SIM Card from an android application is finally available for Android SDK. At API Level 17, G&D is now providing the Library in a way that it can be integrated into various apps. The library is actually the key for a bunch of application doing so call „OTA-Transactions“ (Over-the-Air) in order to install applications on the UICC or make changes to parameters in applets with could be used for payment or ticketing.

How to read a contactless credit card such as Visa paywave or MasterCard paypass

RFID enabled creditcards such as MasterCard paypass or Visa paywave have been in the news in the recent time due to the Forbes article on cloning of RFID creditcards as well as the Analysis from viaForensics. The vulnerably of these types of cards is not new. Already in 2006 researchers were able to read creditcard data form such cards as shown by the RSA labs. So far the reading of such cards was demonstrated with creditcard reads such as Vivopay or Verifone Terminals. Thru a new Android app reading of RFID creditcard is now possible for everyone with an NFC enabled phone.

Development with Android Beam and NFC Peer-2-Peer

NFC offers three different operating modes:

  • Card Emulation Mode
  • Reader Writer Mode
  • Peer-2-Peer Mode

Reader Writer Mode is already available in Android since the first Gingerbread release in December 2010. Card Emulation Mode, which is actually required for Google Wallet, is not yet available for public. Peer-2-Peer Mode as defined in ISO 18092 is now finding its way into Android devices, also known as „Android Beam“.

Cutting edge mobile app for Easybank and BAWAG/PSK

Austria’s largest direct bank easybank and BAWAG/PSK launched their mobile banking apps for Android and iOS today. Both apps come with a sophisticated user interfaces as well as all neccessary banking features required by the customer. The apps have a playful approach in order to lift mobile banking experience to a next level.

GSMA recommends Standard for UICC Secure Element Access Control

The GSMA has published the latest releases of its technical NFC documents (version 2). With these documents the GSMA underlines its strong support for UICC (SIM card) based NFC services.

The handset API requirements document focuses on APIs that enable mobile apps to directly access secure NFC applications on the UICC. An example for this function: A mobile phone user wants to have a look into his mobile train tickets stored in the UICC. The transport app must be able to read the ticket information via API from the UICC.

Since malware could misuse this API to run denial of service attacks on UICC application (eg send wrong PIN codes to payment application and thus lock down the application) the access to this API must be secured in a way that only legitimate mobile apps may access specific secure UICC applications. Eg a payment app may only talk to the UICC payment application but must not be able to access a transport application on the very same UICC.

In feature phones with J2ME support this API is well defined in JSR177. But Android is so far not supporting direct UICC access for mobile apps. Therefore OEMs/ODMs have to integrate proprietary SW components into their Android variant for UICC based NFC support.

GSMA and a growing number of its members strongly favor and support existing standards to avoid fragmentation of UICC APIs and its access control mechanisms: The UICC itself will store a list of credentials and thus control which mobile app may access a specific UICC NFC application.

GSMA NFC Handset APIs & Requirement Specification V2.0

GSMA NFC UICC Requirement Specification Version 2.0

Nexus Galaxy comes with NFC for Android Beam

Today Google and Samsung announced the new Android phone Nexus Galaxy. The phone comes with Google’s new version of Android aka Ice Cream Sandwich (ICS). The highlight of the phone is the 4,65″ display with a resolution of 1280 x 720 pixel. Besides a dual core CPU from Texas Instruments, 1 GB of RAM the phone contains a 5 M pixel camera. With regard to Flash, there are two versions: 16 GB and 32 GB. The phone is very thin (max. 8,4 mm) and curved as we already know it from the Nexus S. The phone will ship in November.

The phone as a special NFC feature called Android Beam. In this case NFC is used for service initiation of a Bluetooth pairing process. The Bluetooth Bridge between the two phones is then used in order to exchange data such as photos, links or business cards. Android beam is also available for NFC version of the Samsung Galaxy S II. To initiate the connection the phones have to be touched back-to-back, as the NFC antenna in located in the battery of the phones.

NFC in Android 4.0

New developer APIs in ICS

Announcement of Google’s next NFC phone – Nexus Prime – deferred

Google and Samsung planed to announcement „something big“ on October 11th. Of course, they are talking about the next generation of the Nexus phones: the Nexus Prime. The date actually was deferred at short notice. The reason for this change was according to Google „That at the moment it is not the right time to announce a new phone.“ It seems that this is due to the dead of Steve Jobs. Samsung and Google want to announce the new date shortly.

SMS NDEF on Android.

Since Android 2.3 (Gingerbread) Google phones are able to use the embedded NFC chip to read external tags. Such tags contain a data format called NDEF (Near Field Communication Data Exchange Format). This data format acts as a container for different data types such as SMS, URLs or Connection-Pairing Information. Up to now Android is not able to interpret the format of SMS stored on the tags correct. Also the most current version 2.3.4 does not fix the issue, although the bug has been reported through multiple channels.

When reading a tag with an NDEF SMS record, the tag is detected correctly.

But when opening the SMS application the content is not interpreted correctly. The message payload is attached to the MSISDN and therefore the SMS cannot be sent.

Countries and companies which have a tag infrastructure with SMS records in the field cannot casino pa natet be used with the Google phones. This is also true for the tags that are used for the service in Austria, but with a major difference: It seams that the NDEF data on tag itself was customized for Nokia phones that were available in the last years (which are able to decode the tags corretly) and therefore the Android phone is not able to read the information correctly. Thus the Android phone only indicates a „unknown tag type“.


Google-Code Bug Report (12142)

Google-Code Bug Report (15866)


Welcome at