Closed GoogleCodeExporter closed 5 years ago
Not sure what I can do. I'd assume that CM11's manifest does not contain the
Mifare bit anymore. On the other hand I thought the device capability check was
server-side. Not that the Play Store app is supported on CM at all. Hm. (The
Play Store's admin interface does list the Galaxy S3, of course.)
Digging a bit with Google Search it seems a bunch of people reported Mifare
Classic cards not working anymore with 4.2.2. And now I see that this is not
the 4.4.2 I thought about, but 4.2.2. Great. With which version did it work?
4.1?
Original comment by philipp.kern
on 13 Jan 2014 at 11:00
Hi,
Thank you for your quick response!
I'm sorry, ofcourse I meant Android 4.4.2!
I went from 4.3 to 4.4.2 and also updated in the meantime the Google play
services to v4.1 which promise better battery usage... So it could be one of
this why I can't install it from the playstore anymore.
If I install the apk file from here, the APP runs fine like before!
Thanks for taking a look;)
Original comment by hottma...@gmail.com
on 13 Jan 2014 at 11:19
Could you install
https://play.google.com/store/apps/details?id=at.mroland.android.apps.nfctaginfo
&hl=en and check if it shows a Mifare Classic section within the Type A one?
Original comment by philipp.kern
on 13 Jan 2014 at 11:32
Original comment by philipp.kern
on 13 Jan 2014 at 11:32
It's my student card (Studentenwerk Karlsruhe) with Mifare classic 1k Type A
Like said before, the app works fine, but cannot be installed from play
store...
Original comment by hottma...@gmail.com
on 14 Jan 2014 at 1:07
Well, I do not check the HW capabilities with my app and rely on the Play Store
supplying it. I hoped that NFC TagInfo would be smarter.
Original comment by philipp.kern
on 14 Jan 2014 at 2:09
How can I or you find out why the store thinks it's not compatible?
Original comment by hottma...@gmail.com
on 14 Jan 2014 at 5:10
So I assume this is still a problem? If we would be talking about stock Android
I'd know what I'm targeting but with CM it's a bit more fuzzy for me.
Original comment by philipp.kern
on 9 May 2014 at 10:23
I just checked the Play Store backend too and it shows the S3 as supported. Hm.
What device is it? (Settings, About Phone, Build number I guess.)
Something about m3/d2* or so. d2dcm, m3dcm, and SC-03E are listed as
unsupported, as is the S3 Mini.
Original comment by philipp.kern
on 9 May 2014 at 10:26
Original issue reported on code.google.com by
hottma...@gmail.com
on 13 Jan 2014 at 8:04