I've found some talk on the internet which suggests that builds of Cyanogen mod from earlier this year enabled some sort of card emulation. The builds in question were CM9 builds from between January 20th to March 22nd 2012. This website claims that a commit was made to enable (again, some sort) of card emulation, but it was removed from future builds due to issues with Google Wallet compatibility.
Can anyone confirm this? I would try myself, but I'm currently not in posession of any of the supported devices. What I'm most interested in is if the emulated card has a static UID. This could be huge news if that's the case. Either way, the video demonstration suggests that they're able to dynamically change the data that is emulated by the phone
I searched through Google and found this page, which holds torrents of CM9 builds from within the above stated time range for the Nexus S, Nexus S 4G, GSM Galaxy Nexus, and the Verizon Galaxy Nexus. For those of you who don't know, the build date is the number before 'NIGHTLY'. By the way, this page has torrents for small update zips. You'll be wanting the larger, full OS zips (over 100mb files).
If you want to compile your own build with card emulation, you'll have to revert these changes.
I've not tested this myself, and I will not be responsible for any issues you might have. Good luck!
If anyone is interested, I've downloaded and I'm seeding the update-cm-9-20120319-NIGHTLY-maguro-signed.zip for the GSM Galaxy Nexus. You can find the torrent here.
This might be interesting to conditionally enable this on devices that will never support GW (no SE). I'll look into doing this later this week.
card emulation
Entropy512 said:
This might be interesting to conditionally enable this on devices that will never support GW (no SE). I'll look into doing this later this week.
Click to expand...
Click to collapse
it is actually currently active in CM9 and above the changes you see have to do with how it is activated. now, unless the app the requires emulation is in the foreground, emulation default is the SE (Gwallet). otherwise, when the app is up, the app emulates. like it should be. anyway, enjoy the patch, i worked hard at it.
-doug
[email protected] said:
it is actually currently active in CM9 and above the changes you see have to do with how it is activated. now, unless the app the requires emulation is in the foreground, emulation default is the SE (Gwallet). otherwise, when the app is up, the app emulates. like it should be. anyway, enjoy the patch, i worked hard at it.
-doug
Click to expand...
Click to collapse
Ah. Thanks for the info... I'm going to look into making it default to emulation on devices with no SE (such as I777)... But first I've gotta forward-port the patches to CM10!
so much to do, so little time.
I'm very interested in testing this. I have a Galaxy Nexus, but I'm unable to download any of the nightly builds, because there are no seeds. Tried the torrents from 18th, 19th and 20th March and 0 seeds. Also tried the torrent from the OP, but no joy. If anyone still has one of these builds laying around, please let me know.
andre.brito said:
I'm very interested in testing this. I have a Galaxy Nexus, but I'm unable to download any of the nightly builds, because there are no seeds. Tried the torrents from 18th, 19th and 20th March and 0 seeds. Also tried the torrent from the OP, but no joy. If anyone still has one of these builds laying around, please let me know.
Click to expand...
Click to collapse
Here's a direct download link for the build that I have.
Entropy512 said:
Ah. Thanks for the info... I'm going to look into making it default to emulation on devices with no SE (such as I777)... But first I've gotta forward-port the patches to CM10!
so much to do, so little time.
Click to expand...
Click to collapse
If you could do this I would be SO happy !
Keep us updated please!
Any chance of getting something like this for the Nexus 7? I'd love to just use my N7 as my ORCA card instead of the card itself.
Doug has yesterday ported the card emulation patches to Jelly Bean, as can be seen here. Could anyone do us a massive favour and compile a stock AOSP build for the GSM Galaxy Nexus with the patches in place?
Is compiling Android from source (with mods) difficult? I'd love to be able to do this kind of stuff on my own without relying on others for help.
LoveNFC said:
Doug has yesterday ported the card emulation patches to Jelly Bean, as can be seen here. Could anyone do us a massive favour and compile a stock AOSP build for the GSM Galaxy Nexus with the patches in place?
Is compiling Android from source (with mods) difficult? I'd love to be able to do this kind of stuff on my own without relying on others for help.
Click to expand...
Click to collapse
If someone could compile it for the GS3 that would be awesome too, please!
Thank you for keeping us updated!
Sent from my SPH-L710 using xda app-developers app
So, I managed to download the nightly build for 19th March and installed it successfully. After booting, I accessed the settings menu and noticed that the NFC option was grayed out. I tried CM9.0.2 and CM9.1.0 and the result was the same, which leads me to believe there is some sort of driver incompatibility, but I can't be sure.
Then I tried the latest CM10 nightly build and now I the NFC option is enabled and working correctly, but no card emulation. I'm currently trying to create a CM build with the card emulation port made by Doug Yeager. I'll let you know how it goes.
I can confirm SimplyTapp runs using CM10 with the latest NFC patch by Doug, but I have no idea if it works. It says "Invalid Card" with my FeliCa-based college ID card, is there another way to maybe get it to work without SimplyTapp?
elfhater said:
I can confirm SimplyTapp runs using CM10 with the latest NFC patch by Doug, but I have no idea if it works. It says "Invalid Card" with my FeliCa-based college ID card, is there another way to maybe get it to work without SimplyTapp?
Click to expand...
Click to collapse
Did you compile the CM10 ROM yourself?
When you say SimplyTapp, do you in fact mean NFC Relay? Either way, there's still no current way to actually copy and use your ID card in Android. The only thing we can copy and emulate (as far as I'm aware) are certain NFC-enabled credit and debit cards.
NFC Guy said:
Did you compile the CM10 ROM yourself?
When you say SimplyTapp, do you in fact mean NFC Relay? Either way, there's still no current way to actually copy your ID card. The only thing we can copy and emulate (as far as I'm aware) are certain NFC-enabled credit and debit cards.
Click to expand...
Click to collapse
I used this CM10 ROM, and I meant SimplyTapp.
The ID card was successfully read by other apps, but couldn't be emulated because of card emulation wasn't enabled. As far as I can tell full card emulation still isn't enabled because the ROM changelog specifically lists emulation as "Tapp Support" and nothing else.
I know ID emulation support exists, as shown by a reviewer here
Any apps that allow the gnex to emulate the same Id or copy the Id of another card and emulate the id?
Beamed from my Maguro.
The NFC changes have been merged into CM10; if your phone has nightlies, you should see this tomorrow.
I would appreciate it if other people could check it out and let me know if they can emulate a FeliCa ID, please!
I flashed it already, but no option to emulate a card or anything.
Beamed from my Maguro.
elfhater said:
I used this CM10 ROM, and I meant SimplyTapp.
The ID card was successfully read by other apps, but couldn't be emulated because of card emulation wasn't enabled. As far as I can tell full card emulation still isn't enabled because the ROM changelog specifically lists emulation as "Tapp Support" and nothing else.
I know ID emulation support exists, as shown by a reviewer here
Click to expand...
Click to collapse
I never had any luck with NFC classic, and I find it a bit odd that that's the only application where people have made claims that they're able to read and then emulate a card.
Even if it does genuinely work, does your FeliCa card use default keys? If not, surely you wouldn't be able to emulate it without cracking your card's keys in the first place.
Mach3.2 said:
I flashed it already, but no option to emulate a card or anything.
Beamed from my Maguro.
Click to expand...
Click to collapse
You can test for card emulation by seeing if the Tapp app runs or force closes.
I'm trying to wait for someone to compile a stock 4.1.1 ROM with the NFC patches, but CM10 is starting to tempt me. Could someone here answer a few questions about ROMs, though?
1) How would I preserve all of my current apps and settings in my stock 4.1.1 and then restore them in CM10? Titanium backup?
2) If I want to go back to stock directly from CM10, can I just go straight into CWM and restore my Nandroid backup and everything will be just as I left it before installing CM10? Could this cause any issues?
LoveNFC said:
I never had any luck with NFC classic, and I find it a bit odd that that's the only application where people have made claims that they're able to read and then emulate a card.
Even if it does genuinely work, does your FeliCa card use default keys? If not, surely you wouldn't be able to emulate it without cracking your card's keys in the first place.
Click to expand...
Click to collapse
I'm pretty sure it does.
To the second part of the statement, yes everything will be the same but you have to remember to wipe data, etc. before restoring the backup.
Before I got my N5x, I remember seeing some articles back in September about Bank of America's iOS and Android apps now supporting fingerprint IDs for logging in, and I even saw a popup on the app on my N5 about this. So now that I have my 5x, this option is not present. From what they were saying about using the built-in fingerprint support, if it isn't supported on the 5x, what device is it supported on? There are even instructions on their web site that talk about setting up fingerprints using the standard Android 6.0 settings that we have on the 5x and 6P.
Is anyone using this app? Any luck with it recognizing the fingerprint support? The only thing I can think of is that there was some sort of security concern and they backed off from offering this feature.
same here
don't see any option for imprint authentication. I did submit a feedback on the app regarding this tho.
dpj52190 said:
same here
don't see any option for imprint authentication. I did submit a feedback on the app regarding this tho.
Click to expand...
Click to collapse
Just found this on the Google Play listing for the app:
• Note: Fingerprint sign-in is currently only supported for select Samsung devices. We’ll be adding support for more devices in future releases.
Compared to the 5x, the fingerprint sensor on my Samsung tablet is terrible!
hah! so much for these companies to advertise on a feature and never deliver.
rochrunner said:
Just found this on the Google Play listing for the app:
• Note: Fingerprint sign-in is currently only supported for select Samsung devices. We’ll be adding support for more devices in future releases.
Compared to the 5x, the fingerprint sensor on my Samsung tablet is terrible!
Click to expand...
Click to collapse
I installed Robinhood (the commission-free brokerage app) and it utilizes the fingerprint scanner. It works awesomely.
Yeah the Bank of America app used the fingerprint reader on my s6, but not the 5x. Looks like they should bring support for us, eventually.
Sent from my Nexus 5X using Tapatalk
its the problem with not having standardized API for all scanners.. I mean at the end of the day all app developers need to make sure is you are the owner of your phone. And eventually pretty much all scanner API gives out a true/false. So they need to unite and create universal standard to make developer's life easier.
Hi everyone,
I'm using the zenfone 2 Z00A (dual sim) and I updated from CM13 to lineage and discovered that the dual sim ringtones feature wasn't there anymore :crying:
Does anyone know if this feature is planned in a near future ?
thanks
I am having the same headache.
M using 14.1-20170707-Nightly-x2 for Le Max 2 (a dual-sim model). Found that Lineage OS (at least this version) does not support dual sim ringtones customization. 1 configuration in Sound settings is sharing with both sim's.
Tried 2 dual-ringtones app in play store, none of them works as they claim. Wonder if any may share a solution here? Need this desperately.
Thanks.
Same here on Redmi 3 and LOS 14.1
its really important feature for me to know right away which part of my life is calling.
So one year later with LineagoOS Oreo (and apparently also Nougat) and we still don't have dual sim ringtone support? Looking through the XDA forums, it seems thee are multiple unanswered threads across the board of phones and also across different operating systems, not just Lineage, with the same problem.
Can't someone at least make an Xposed module or a Root app for a dual sim ringtone workaround? Didn't find any of those either on FDroid or the Play store or the Xposed store. There are a couple of non root apps on the pay store which are unreliable at best.
Thanks to anyone for any insight or status or acknowledgement or something
I totally agree.
This is a useful feature, why is it simply left out? I feel tempted to switch back to my stock OS (Which basically is a Vanilla Android + root anyway)
Runng an Aquaris X Pro 128
Does anyone know if there is a magisk module for dual sim ringing?
We are in 2020, and this functionality which existed in the previous versions and worked perfectly is still not implemented ??? How is it possible ?
edit: this app (full version 1.4) works perfectly meanwhile => https://forum.xda-developers.com/android/apps-games/dualsimringer-t3890457
Hi! The thread for the mentioned app has been closed and download links have been removed. I wonder why? Is there an alternative that works on a Pixel 4a?
Hi,
Just got a new LG G7. When I first used the AI cam feature - I was seeing tags of the things it was recognizing.
After upgrading to Android 9 - I don't see it the tags anymore.
Is this was removed as part of the upgrade or I messed something up with the configurations?
Someting on your phone.. Works for me
Any idea what can cause it?
Is there any configuration to disable it or uninstalling some app \ permissions can cause it?
It's built in the camera app so I have no clue