blob: 15ed7549a7b26297f00e37be9763b3e7b2c9d325 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright (C) 2013 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file defines which AIDs this application should emulate cards for.
Vendor-specific AIDs should always start with an "F", according to the ISO 7816 spec. We
recommended vendor-specific AIDs be at least 6 characters long, to provide sufficient
uniqueness. Note, however, that longer AIDs may impose a burden on non-Android NFC terminals.
AIDs may not exceed 32 characters (16 bytes).
Additionally, AIDs must always contain an even number of characters, in hexadecimal format.
In order to avoid prompting the user to select which service they want to use when the device
is scanned, this app must be selected as the default handler for an AID group by the user, or
the terminal must select *all* AIDs defined in the category simultaneously ("exact match").
-->
<!-- BEGIN_INCLUDE(CardEmulationXML) -->
<host-apdu-service xmlns:android="http://schemas.android.com/apk/res/android"
android:description="@string/service_name"
android:requireDeviceUnlock="false">
<!--
If category="payment" is used for any aid-groups, you must also add an android:apduServiceBanner
attribute above, like so:
android:apduServiceBanner="@drawable/settings_banner"
apduServiceBanner should be 260x96 dp. In pixels, that works out to...
- drawable-xxhdpi: 780x288 px
- drawable-xhdpi: 520x192 px
- drawable-hdpi: 390x144 px
- drawable-mdpi: 260x96 px
The apduServiceBanner is displayed in the "Tap & Pay" menu in the system Settings app, and
is only displayed for apps which implement the "payment" AID category.
Since this sample is implementing a non-standard card type (a loyalty card, specifically), we
do not need to define a banner.
Important: category="payment" should only be used for industry-standard payment cards. If you are
implementing a closed-loop payment system (e.g. stored value cards for a specific merchant
or transit system), use category="other". This is because only one "payment" card may be
active at a time, whereas all "other" cards are active simultaneously (subject to AID
dispatch).
-->
<aid-group android:description="@string/card_title" android:category="other">
<aid-filter android:name="F222222222"/>
</aid-group>
<!-- END_INCLUDE(CardEmulationXML) -->
</host-apdu-service>