open-mobile-api

List of OMAPI supported devices

由 流过昼夜 提交于 2019-12-29 05:35:07
问题 I'm developing with the Open Mobile API but so far haven't found a list of devices that support the API by default (by default being using the OEM ROM). I realise that since API level 21, Android telephony supports sending APDUs via basic and logical channels dirctly through the TelephonyManager. But I'd like to know about devices running pre-API level 21 too. So, has a list already been compiled of devices with built-in support or is there a way to find out for myself? 回答1: I'm not aware of

Android Open Mobile API Release Difficulties

由 你离开我真会死。 提交于 2019-12-20 07:44:32
问题 I am using the "org.simalliance.openmobileapi.jar" file from SDK. I copied it to my libs folder and added the dependency like this Case #1: working fine (in debug mode) In app Gradle file I have: provided files('libs/org.simalliance.openmobileapi.jar') Case #2: not working (in release mode - without minifyEnabled) In app Gradle file I have: compile files('libs/org.simalliance.openmobileapi.jar') In case #2 I get the following exception: (java.lang.SecurityException: Access Control Enforcer:

Phones that can support Open Mobile API

由 瘦欲@ 提交于 2019-12-12 20:02:24
问题 I understand that to access SIM/eSE from an Android app we need to install Open Mobile API addon on Android Studio. However, is it true that it will not work on all NFC phones? For example, do some OEM limited access to SIM/eSE? Or are there phones where only custom firmware will work with Open Mobile API? Also, is there a list of phones that support Open Mobile API by default? 回答1: That's correct. The phone needs to implement the Open Mobile API (by means of the smartcard system service) in

Adding the Open Mobile API library to an Android device to get APDU-based access to the SIM

由 …衆ロ難τιáo~ 提交于 2019-12-12 05:07:28
问题 I have a device without NFC. This device also does not support the Open Mobile API. I need access to the SIM applet on that device. Now I wonder if I could add that functionality...If I have a copy of the Open Mobile API library, would it work if pushed that Open Mobile API library to my device through ADB? Could I then exchange APDUs with my SIM applet? 回答1: No, that won't work. The Open Mobile API library is only an interface to the Open Mobile API service ("SmartcardService"). Thus, the

How to Access Secure Element without rooting a device which already supports SmartCard API

由 回眸只為那壹抹淺笑 提交于 2019-12-06 05:32:56
问题 The SEEK-for-Android documentation says that listed devices support the SmartCard API. I want to access a SIM-based secure element (SE) through my Android application. Can I achieve this without rooting any of these supported devices and without rebuilding its Android system image? In my case, the device is a Samsung Galaxy S3. 回答1: Yes, you can use SEEK-for-Android without rooting the system. However, this technology is very device-dependent; some vendor specific libraries must be present in

Javacard applet RPDU does not contain any data when accessed from seek-for-android

由 这一生的挚爱 提交于 2019-12-04 14:26:00
问题 I have a complex Javacard applet, which is developed and tested for ordinary Smart Card (e. g. NXP J3E145, T=1). Now I have to use it in UICC in a mobile phone and access it from my Android app. The UICC uses T=0 protocol. When I communicate to the SIM card from an ordinary card reader (Omnikey 5321), the applet works fine. However, when I move it into my mobile phone (Sony Xperia S) and send APDUs via seek-for-android API, some RPDUs do not contain any data part, there is only the status

How to Access Secure Element without rooting a device which already supports SmartCard API

由 ☆樱花仙子☆ 提交于 2019-12-04 10:48:43
The SEEK-for-Android documentation says that listed devices support the SmartCard API. I want to access a SIM-based secure element (SE) through my Android application. Can I achieve this without rooting any of these supported devices and without rebuilding its Android system image? In my case, the device is a Samsung Galaxy S3. vojta Yes, you can use SEEK-for-Android without rooting the system. However, this technology is very device-dependent; some vendor specific libraries must be present in the system. It worked fine for me with Sony Xperia with no necessary changes. After adding some

Javacard applet RPDU does not contain any data when accessed from seek-for-android

由 亡梦爱人 提交于 2019-12-03 09:13:19
I have a complex Javacard applet, which is developed and tested for ordinary Smart Card (e. g. NXP J3E145, T=1). Now I have to use it in UICC in a mobile phone and access it from my Android app. The UICC uses T=0 protocol. When I communicate to the SIM card from an ordinary card reader (Omnikey 5321), the applet works fine. However, when I move it into my mobile phone (Sony Xperia S) and send APDUs via seek-for-android API, some RPDUs do not contain any data part, there is only the status word 0x9000 and the data part is missing! These APDUs are failing: 80 04 00 00 00 --> 90 00 (although

Android Open Mobile API Release Difficulties

由 落花浮王杯 提交于 2019-12-02 08:03:05
I am using the "org.simalliance.openmobileapi.jar" file from SDK. I copied it to my libs folder and added the dependency like this Case #1: working fine (in debug mode) In app Gradle file I have: provided files('libs/org.simalliance.openmobileapi.jar') Case #2: not working (in release mode - without minifyEnabled) In app Gradle file I have: compile files('libs/org.simalliance.openmobileapi.jar') In case #2 I get the following exception: (java.lang.SecurityException: Access Control Enforcer: no APDU access allowed!) What could cause the problem? First of all, you need to use the "provided"

List of OMAPI supported devices

由 回眸只為那壹抹淺笑 提交于 2019-11-29 02:39:00
I'm developing with the Open Mobile API but so far haven't found a list of devices that support the API by default (by default being using the OEM ROM). I realise that since API level 21, Android telephony supports sending APDUs via basic and logical channels dirctly through the TelephonyManager. But I'd like to know about devices running pre-API level 21 too. So, has a list already been compiled of devices with built-in support or is there a way to find out for myself? I'm not aware of any complete list. However, there is a not so comprehensive one in our report Open Mobile API: Accessing the
订阅 open-mobile-api