Yubico Forum

Re: Problem with Samsung Galaxy S4

2013-11-12T09:01:56+01:00

So the problem actually was the battery in the phone. All works now.

Statistics: Posted by thofmann — Tue Nov 12, 2013 9:01 am

Re: Problem with Samsung Galaxy S4

2013-11-11T23:25:57+01:00

So after testing out different things I changed my battery and now it seems to work. I will do some more testing. I was not using the original battery before.

Statistics: Posted by thofmann — Mon Nov 11, 2013 11:25 pm

Re: Problem with Samsung Galaxy S4

2013-11-11T22:01:47+01:00

After reading your FAQ here is the info from TagInfo by NXP:

** TagInfo scan (version 2.00) 2013-11-11 21:59:28 **

-- INFO ------------------------------

# IC manufacturer:
NXP Semiconductors

# IC type:
Unknown IC

# MIFARE applications:
No MIFARE support present in Android

-- NDEF ------------------------------

# No NFC data set storage:

-- EXTRA ------------------------------

# IC detailed information:
MIFARE Classic emulation

-- TECH ------------------------------

# Technologies supported:
ISO/IEC 14443-4 (Type A) compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible

# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.IsoDep, android.nfc.tech.NfcA]
android.nfc.tech.IsoDep
* Maximum transceive length: 261 bytes
* Default maximum transceive time-out: 1000 ms
* Extended length APDUs not supported
android.nfc.tech.NfcA
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 1000 ms
No MIFARE Classic support present in Android

# Detailed protocol information:
ID:
ATQA: 0x4400
SAK: 0x28
ATS Historical bytes: |YubikeyNEOr3|

Statistics: Posted by thofmann — Mon Nov 11, 2013 10:01 pm

Re: Problem with Samsung Galaxy S4

2013-11-11T21:48:17+01:00

I did some more testing. I installed https://play.google.com/store/apps/deta ... nfctaginfo and swiped the NEO.

I got an error message that the tag could not be read completely.

But it shows the following:

RF Technology:
Type A (ISO/IEC 14443 Type A)

Tag type:
ISO/IEC 14443-4 Smart Card,
Mifare Classic 1K (emulated)

Manufacturer
NXP Semiconductors (Germany)

ATQA
0044

SAK
28

Target technology classed (Android)
android.nfc.tech.IsoDep,
android.nfc.tech.NfcA

And then a message:
Mifare Classic is not supported on your device!

If this problem is due to the fact that the NEO acts as Mifare Classic 1K what can be done about this?

Regards, Thomas

Statistics: Posted by thofmann — Mon Nov 11, 2013 9:48 pm

[SOLVED] - Problem with Samsung Galaxy S4

2013-11-11T21:30:50+01:00

Hi,

I just got my Yubikey NEO today. I want to use it together with lastpass and also the Android YubiOATH app.

It seems that my phone a Samsung Galaxy S4 GT-I9505 with Android 4.2.2 is not able to communicate with the key how it is supposed to.
I installed the OATH applet, started YubiOATH and scanned a code. When I swipe the Neo I get a toast that the communication failed.

Looking at the logcat I see the following messages (not dependent on whether the YubiOATH is running):

NativeNfcTag (Debug) : Connect to a tech with a different handle
NativeNfcTag (Debug): Check NDEF Failed - status = 3
NativeNfcTag (Debug): Check NDEF Failed - status = 3
NativeNfcTag (Debug): Tag lost, restarting polling loop
BrcmNfcJni (Error): nativeNfcTag_doDisconnect: tag already deactivated
NativeNfcTag (Debug): Stopping background presence check

I wrote NDEF info to slot 1 before.

Could this be related to http://www.anandtech.com/show/6919/sams ... -announced ?

How can I provide more information to debug this problem?

For now it seems like I cannot use the NEO with the phone what was why I bought the NEO for.

Thanks, Thomas

Statistics: Posted by thofmann — Mon Nov 11, 2013 9:30 pm