Related
Does anyone know why there are only eight devices (seven phones and the Nexus 7) that support Google wallet? Shouldn't any phone with NFC be able to support the ability to pay anywhere? I really wish there was a way to contact Google about this, I want to know why my HTC One X isn't supported by Google Wallet. It isn't even the AT&T one, so it can't be AT&T requesting it doesn't work. Thoughts?
I'm guessing NFC Secure Element.
Secure Element
j2cool2012 said:
I'm guessing NFC Secure Element.
Click to expand...
Click to collapse
That's probably correct. Having the keys to the secure element gives you control over what goes in there. Google (via First Data) controls the keys to their hardware secure element (attached to the NFC controller, as opposed to a SIM/UICC secure element attached to the baseband controller). This means they don't need carrier approval to push payment applets to their secure element (the carriers only control the keys to the SIM/UICC SE).
I thought that this new update didn't need the secure element because of the cloud wallet stuff.
Sent from my HTC One X
mibikin said:
I thought that this new update didn't need the secure element because of the cloud wallet stuff.
Sent from my HTC One X
Click to expand...
Click to collapse
The secure element is still necessary for card emulation. The SE connects directly to the NFC controller and allows the device to "emulate" a payment card. Also, there is one CC # for all of your credit cards in the "cloud" Google Wallet. That number is transmitted via NFC to the PoS terminal, and then Google magically knows which of your credit cards to charge.
__multiplex said:
The secure element is still necessary for card emulation. The SE connects directly to the NFC controller and allows the device to "emulate" a payment card. Also, there is one CC # for all of your credit cards in the "cloud" Google Wallet. That number is transmitted via NFC to the PoS terminal, and then Google magically knows which of your credit cards to charge.
Click to expand...
Click to collapse
So what about those SD cards that come with NFC?
In theory if they were to be deployed in the market, they could not use Google Wallet, due to the "secure element" missing?
I dont see many uses to NFC but this and data sharing. If you cut half of the "important" uses, the technology is kinda DOA?
mibikin said:
Does anyone know why there are only eight devices (seven phones and the Nexus 7) that support Google wallet? Shouldn't any phone with NFC be able to support the ability to pay anywhere? I really wish there was a way to contact Google about this, I want to know why my HTC One X isn't supported by Google Wallet. It isn't even the AT&T one, so it can't be AT&T requesting it doesn't work. Thoughts?
Click to expand...
Click to collapse
You can Install and use Google Wallet on any phone with my original guide here! http://forum.xda-developers.com/showthread.php?t=1810282 Best of luck.
HeroKhar said:
You can Install and use Google Wallet on any phone with my original guide here! http://forum.xda-developers.com/showthread.php?t=1810282 Best of luck.
Click to expand...
Click to collapse
I thanked you, but I haven't rooted my One X yet, so I couldn't actually try this. Thanks for the response though.
Sent from my HTC One X
Shadow89 said:
So what about those SD cards that come with NFC?
In theory if they were to be deployed in the market, they could not use Google Wallet, due to the "secure element" missing?
I dont see many uses to NFC but this and data sharing. If you cut half of the "important" uses, the technology is kinda DOA?
Click to expand...
Click to collapse
The SD cards are an NFC antenna, secure element, and some standard storage, all wrapped into one. See: (apparently I can't post links, but look around for IN2PAY_MICROSD_V2.1.pdf)
I still think the Google Wallet issue comes down to who has the keys to the Secure Element. Google needs to load one card into the SE to do card emulation. I could be wrong here, but I'm assuming that if they don't have the keys (or permission from whoever has they keys), they can't load their initial card in there and Wallet can't be installed on the device.
mibikin said:
I thanked you, but I haven't rooted my One X yet, so I couldn't actually try this. Thanks for the response though.
Sent from my HTC One X
Click to expand...
Click to collapse
Haha, anytime I glad I could help you! Thanks for the +Thanks also, I greatly appreciate it!
Sent from my Xoom using XDA Premium HD app
HeroKhar said:
You can Install and use Google Wallet on any phone with my original guide here! http://forum.xda-developers.com/showthread.php?t=1810282 Best of luck.
Click to expand...
Click to collapse
Sadly, it doesnt't work on all devices. Since The att One X is missing the secure library files needed to run Google Wallet, it stays stuck on the activating account screen...trust me, I have tried 4 different methods and none have worked...
HTCFAN0923 said:
Sadly, it doesnt't work on all devices. Since The att One X is missing the secure library files needed to run Google Wallet, it stays stuck on the activating account screen...trust me, I have tried 4 different methods and none have worked...
Click to expand...
Click to collapse
Oh Okay, thatnks for the reply! I can add that to my Guide! +Thanked you too
HTCFAN0923 said:
Sadly, it doesnt't work on all devices. Since The att One X is missing the secure library files needed to run Google Wallet, it stays stuck on the activating account screen...trust me, I have tried 4 different methods and none have worked...
Click to expand...
Click to collapse
That isn't my issue. I have the international One X, not the AT&T one.
Sent from my HTC One X
what are the chances of getting a secured element emulator?
waiters said:
what are the chances of getting a secured element emulator?
Click to expand...
Click to collapse
Very little unfortunately :'(
Sent from my Xoom using xda app-developers app
HeroKhar said:
Very little unfortunately :'(
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Someone had a patch to emulate a secure element ( http://forum.xda-developers.com/showthread.php?t=1832499 )- the problem is we cannot emulate the secure element *as programmed by Google*, which Wallet expects.
The problem is:
To use the SE of devices that support GW, you need Google's keys
To use Google's SE cardlets on a device, the SE must be programmed with the correct keys
Entropy512 said:
Someone had a patch to emulate a secure element ( http://forum.xda-developers.com/showthread.php?t=1832499 )- the problem is we cannot emulate the secure element *as programmed by Google*, which Wallet expects.
The problem is:
To use the SE of devices that support GW, you need Google's keys
To use Google's SE cardlets on a device, the SE must be programmed with the correct keys
Click to expand...
Click to collapse
Exactly, Google DOESN'T want Wallet on other devices and variants, but there may be a Dev who can extract the keys from a compatible device...
Sent from my Nexus S using xda app-developers app
Is Google doesn't want it on all android devices and will try to keep it to Google branded phones only, it will fail.
Soon ios will have the passbook, carriers will have isis, and Google will have Wallet but only on 3 devices??
Sent from my SAMSUNG-SGH-I747 using xda premium
I want Google Wallet on my S3... Google should create or addapt Google Wallet forma all devices...
Enviado desde Tapatalk 2
I'm trying to create a method to get wallet working on the htc incredible 4g on verizon. But it gets stuck on the adding account screen. What exactly is the secure element? Is there any way to get it on a phone that's missing it? Is there anything I can do? Thanks
I've been looking into NFC card emulation on Android and have done some pretty thorough Googling.
As far as I understand, some modifications were made way back in Android 2.3 by another XDA member. Later on, a more complete framework for emulation was made by adding PCD tag types to Cyanogen 9.1+, enabling emulation in a semi-supported way for those running Cyanogen. With the latest versions of Android, it seems like Google has semi-official support for card emulation through the com.android.nfc_extras class.
My main questions: are there any useful apps out there that take advantage of this? Does this semiofficial API work with the Nexus 4 / GS4, which use a different NFC chip (non-NXP) from all other Android phones? Does this, perhaps, enable easy card emulation for assorted cards like Blackberry has had for a while?
Your not the only one trying to figure the problem of NFC emulation on Android devices,
From what I've been been able to conclude so far:
1) Stock versions of Android don't support smart card emulation
2) The NFC libraries that the Stock versions of Android do not contain smart card emulation libraries (as you mentioned the ISOPcdA and ISOPcdB classes)
3) Of the NFC chipsets out on the market right now, not all NFC chipsets have a Secure Element
4) There are only three (as far as I know) Android application that utilize the NFC Chipsets for contactless money transactions (Google Wallet, ISIS Mobile Wallet and Simply Tapp)
Some technical background stuff on the Secure Element
1) The Secure Element is not directly accessed from the Android Operating system, but an applications ability to access the secure element is dependent upon the proper keys (public/private keys), where the manufacturer holds the master key for access
2) When the proper key(s) is/are entered the application writes some code into the memory of the Secure Element. To prevent a brute force attack, after several incorrect password attempts, access to the Secure Element is permanently disabled
3) When the Application needs the Secure Element, what could be assumed as a vector is preformed within the Android operating system that requests the code stored on the Secure Element to execute
4) Early adopters of Google Wallet faced the possibility of borking the Secure Element if they did not deattach Wallet before preforming an Android System update (from what I've read AFAIK, Google has since moved to a cloud storage of the needed keys)
From the business perspective:
1) Only one Major US Cell Carrier, Sprint, officially supports Google Wallet
2) The other three carriers, AT&T, T-Mobile and Verizon refuses to allow Google Wallet to be installed on their devices, instead forcing users to use ISIS Mobile Wallet
3) Speculation is that these three carriers may have wanted a monetary kickback for transactions
Looking at the reviews for ISIS Mobile Wallet, majority of them are poor reviews with a handful easily citing the actions of these three as anti-competitive. There where also reports of a poor supporting backbone, inability of specialized SIM cards that contain a secure element (access to the NFC is done via a decitated wire or wire pair link), and non-compatibility even with the official hardware needed. Back in May Verizon was quoted as blocking Google Wallet due to needed access to the Secure Element, yet has no problem with ISIS accessing it (http://techcrunch.com/2013/05/16/google-wallet-rolls-out-to-more-devices-nope-still-no-love-for-verizon-att-or-t-mobile-owners/) From a good faith perspective of these action, I recently submitted a concern of anti-trust to the US Department of Justice.
You mentioned the NFC emulation in CM 9.1 + . To extend upon the post mentioned, other developers continued down that path to improve the code. As a good reference, this blog link does provide some technical info about the emulation (http://nelenkov.blogspot.com/2012/10/emulating-pki-smart-card-with-cm91.html). Doug Yeager, one who holds several patents in NFC technology ended up writing the ISOPcdA and ISOPcdB classes with official incorporation into CM 9.1 + (git link, https://github.com/CyanogenMod/android_frameworks_base/tree/ics/core/java/android/nfc/tech). Yeager and his business partner Ted Fifelski (coming from the Point of Sale sector), both wanting to create a more open NFC environment created Simply Tapp (http://www.simplytapp.com/about.html). Simply Tapp also stores the keys remotely. As of right now, there has been no reported cases of the cell carriers blocking Simply Tapps' data connection.
Because the frameworks of the manufacturers variants of the Android Operating system are closed source, difficulty has been encountered trying to add these classes. To try and remove this barrier, I ended up submitted an enhancement ticket to try and get Google to add this code (http://code.google.com/p/android/issues/detail?id=56509) with what appears to be a positive response.
Hopefully this information helps you out seeing the current situation with NFC emulation,
Joe
Thanks
This information is very useful it's a shame there is not a simple way or at least a better way to emulate any NFC Forum defined tag hopefully google will make aviable in it's Android SDK a way to emulate a NFC tag
luisrojito said:
This information is very useful it's a shame there is not a simple way or at least a better way to emulate any NFC Forum defined tag hopefully google will make aviable in it's Android SDK a way to emulate a NFC tag
Click to expand...
Click to collapse
The only viable way (I'm concluded) to get NFC to move beyond a novelty to a truly respectable standard is to adapt the technology to devices that are not subject to the polices of the cellular carriers ( I have a concept, but I don't want to disclose too much at this point in the brainstorming)
Sending an email to NXP semiconductor about the access to the secure element resulted in a reply directed me to their product page http://www.nxp.com/products/identification_and_security/reader_ics/nfc_contactless_reader_ics/ (link working as of 2013-08-07).
EDIT: In addition to the above the following links may also help us out:
http://www.nxp.com/products/identification_and_security/authentication/
Smart Card ICs (Integrated circuits not ice cream sandwich)
-Landing Page
http://www.nxp.com/products/identification_and_security/smart_card_ics/
-Fast Pay secure Contactless Payment
http://www.nxp.com/products/identification_and_security/smart_card_ics/fastpay_secure_contactless_payment/
-MIFARE Smart Card ICs
--Landing Page
http://www.nxp.com/products/identification_and_security/smart_card_ics/mifare_smart_card_ics/
--SmarteID
http://www.nxp.com/products/identification_and_security/smart_card_ics/smarteid/
--SmartMX contact interface controllers
http://www.nxp.com/products/identification_and_security/smart_card_ics/smartmx_contact_interface_controllers/
--SmartMX dual interface controllers
http://www.nxp.com/products/identification_and_security/smart_card_ics/smartmx_dual_interface_controllers/
--SmartMX2
http://www.nxp.com/products/identification_and_security/smart_card_ics/smartmx2/
From http://developer.android.com/about/versions/kitkat.html#44-hce
New NFC capabilities through Host Card Emulation
Android 4.4 introduces new platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments, loyalty programs, card access, transit passes, and other custom services. With HCE, any app on an Android device can emulate an NFC smart card, letting users tap to initiate transactions with an app of their choice — no provisioned secure element (SE) in the device is needed. Apps can also use a new Reader Mode to act as readers for HCE cards and other NFC-based transactions.
Android HCE emulates ISO/IEC 7816 based smart cards that use the contactless ISO/IEC 14443-4 (ISO-DEP) protocol for transmission. These cards are used by many systems today, including the existing EMVCO NFC payment infrastructure. Android uses Application Identifiers (AIDs) as defined in ISO/IEC 7816-4 as the basis for routing transactions to the correct Android applications.
Apps declare the AIDs they support in their manifest files, along with a category identifier that indicates the type of support available (for example, "payments"). In cases where multiple apps support the same AID in the same category, Android displays a dialog that lets the user choose which app to use.
When the user taps to pay at a point-of-sale terminal, the system extracts the preferred AID and routes the transaction to the correct application. The app reads the transaction data and can use any local or network-based services to verify and then complete the transaction.
Android HCE requires an NFC controller to be present in the device. Support for HCE is already widely available on most NFC controllers, which offer dynamic support for both HCE and SE transactions. Android 4.4 devices that support NFC will include Tap & Pay for easy payments using HCE.
Click to expand...
Click to collapse
Shouldn't this mean devices like the nexus 7 (2013) without a secure element should be able use Google wallet for NFC payments? I heard somewhere that the nexus 5 uses the same chip as the nexus 7 (2013)
Sent from my Nexus 7 using xda premium
Big_Red77 said:
Shouldn't this mean devices like the nexus 7 (2013) without a secure element should be able use Google wallet for NFC payments? I heard somewhere that the nexus 5 uses the same chip as the nexus 7 (2013)
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It does indeed.
What about the AT&T HTC One?
From some general research I did earlier this year with NFC being used for contactless payments, there were three different means of implementation; a) the Secure Element on the NFC chipset itself (Google Wallet), b) The secure element on the SIM card with a SWP link (used by ISIS Mobile wallet) and c) Secure Element Emulation via the cloud (Simply Tapp)
for a) the problem dealt with the fact that for some reason(s) three of the four major United States Cellular Carriers (AT&T, T-Mobile and Verizon) would not provide Google with the required TSM (Trusted service management) credentials to access the protected memory of the secure element. It was suggested that because of the time invested prior to actual availability, the above carriers elected to adopt their own standard to implementing the secure element.
for b) The sim cards used by GSM carriers were developed with the secure element onboard. The problem that was experienced dealt with the limited availability of special sim cards (only two markets had them, Salt Lake City and Austin) as well as the poor support and backbone to the system, leaving most users calling foul on the carriers abuse of power (a personal attempt at contacting the FTC about a possible obligopy resulted in that is not).
the concept of c) was approached by Doug Yeager and Ted Fifelski, both of whom are more than knowledgeable with the POS and NFC markets. Instead of requiring the secure element hardware on the device, emulate it by using the cloud. As previously mentioned the libraries in the Android operating system did not include smart/host card emulation. Doug Yeager then created and had merged into the CyangenmodRom builds 9.1 + the open source IsoPCDA and IsoPCDB libraries.
Looking up on NFC World, Google collaborated with Simply Tapp to officially bring HCE into the 4.4 http://www.nfcworld.com/2013/10/31/326619/google-gets-around-carriers-host-card-emulation-nfc-payments/
Does this mean I can, with the proper app and so on, "emulate" NFC tags (or at least some types of NFC tags/cards)? Does anyone plan on making an app to do just this...'record' and 'emulate' nfc tags/cards of supported types (not just 'credit cards')?
TjPhysicist said:
Does this mean I can, with the proper app and so on, "emulate" NFC tags (or at least some types of NFC tags/cards)? Does anyone plan on making an app to do just this...'record' and 'emulate' nfc tags/cards of supported types (not just 'credit cards')?
Click to expand...
Click to collapse
This is what I was wondering as well... tried endlessly searching apps or even figuring out how to do it on my own.Everything was a dead-end, always returning to that damned secure element. Does anyone know if there's any hope?
TjPhysicist said:
Does this mean I can, with the proper app and so on, "emulate" NFC tags (or at least some types of NFC tags/cards)? Does anyone plan on making an app to do just this...'record' and 'emulate' nfc tags/cards of supported types (not just 'credit cards')?
Click to expand...
Click to collapse
+1 for TJ's question, I'd love to ditch the corporate RFID tag and use my phone. I mean if it's really going to be a wallet replacement, that's one of the things in my wallet.
TjPhysicist said:
Does this mean I can, with the proper app and so on, "emulate" NFC tags (or at least some types of NFC tags/cards)? Does anyone plan on making an app to do just this...'record' and 'emulate' nfc tags/cards of supported types (not just 'credit cards')?
Click to expand...
Click to collapse
Ya I'm wondering that same. My senior project is due in 3 weeks and I build a "door unlocker" based off NFC tags. The NFC shield on an Arduino reads a tag and unlocks a door. I have a Nexus 5 and would love to be able to emulate a tag and use it to open a door.
Android 4.4 NFC HCE demo app
Please have a look at this article: blog.opendatalab.de/hack/2013/11/07/android-host-card-emulation-with-acr122/
An Android sample project that use NFC HCE is available here: github.com/grundid/host-card-emulation-sample
Any updates for this? Really looking forward to using my phone as a replacement for transit cards.
Bump? I would really like an emulation app.
TjPhysicist said:
Does this mean I can, with the proper app and so on, "emulate" NFC tags (or at least some types of NFC tags/cards)? Does anyone plan on making an app to do just this...'record' and 'emulate' nfc tags/cards of supported types (not just 'credit cards')?
Click to expand...
Click to collapse
Host card emulation is not to emulate NFC tags but make payment through NFC possible with Google Wallet even without a secure element chip. The devices technically could be a NFC tags (think about it, android beam can go both directions so the device beams to the other devices which acts KIND of like a tag).
NFC tags are cheap anyway so what's the need to try to emulate them? You can program them from the phone.
tiny4579 said:
Host card emulation is not to emulate NFC tags but make payment through NFC possible with Google Wallet even without a secure element chip. The devices technically could be a NFC tags (think about it, android beam can go both directions so the device beams to the other devices which acts KIND of like a tag).
NFC tags are cheap anyway so what's the need to try to emulate them? You can program them from the phone.
Click to expand...
Click to collapse
I thought hce allows for the phone to emulate a NFC card, for example, a transit card.
Sent from my Nexus 4 using Tapatalk
Sfkn2 said:
I thought hce allows for the phone to emulate a NFC card, for example, a transit card.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
It's for payments strictly. It emulates a payment card and I think the android implementation is strictly for Google wallet. I'm not sure the transit systems would use Google wallet or not. Maybe they do.
tiny4579 said:
It's for payments strictly. It emulates a payment card and I think the android implementation is strictly for Google wallet. I'm not sure the transit systems would use Google wallet or not. Maybe they do.
Click to expand...
Click to collapse
Nope, KitKat "supports emulating cards that are based on the NFC-Forum ISO-DEP specification (based on ISO/IEC 14443-4)...". This is a standard for Identification cards used for payments but also could be used for other use cases. Android 4.4 also supports different HCE service groups "Category_PAYMENT" and "Category_OTHER" , so I wouldn´t say it´s strictly for payments! (Although, I think, your right, that´s the main purpose Google had in mind by implementing this emulation feature ...)
Doesn´t mean that you could "clone" your (or your neighbors) company badge or transit card and use your android device instead, but that´s a completely different story.
-Psycho- said:
This is what I was wondering as well... tried endlessly searching apps or even figuring out how to do it on my own.Everything was a dead-end, always returning to that damned secure element. Does anyone know if there's any hope?
Click to expand...
Click to collapse
No hope, secure elements are secure by design. You can't download them wihout hacking the card. In most cases, this is just as complicated as hacking into someone's bank account.
Sorry but that is the reason why we trust these cards in the first place.
ascsa said:
Doesn´t mean that you could "clone" your (or your neighbors) company badge or transit card and use your android device instead, but that´s a completely different story.
Click to expand...
Click to collapse
Although that would be awesome..
Sent from my Nexus 4 using Tapatalk
Stupid question, but if the secure element isn't necessary anmyore, is Google wallet now secure enough?
I mean, Google kind of used this for a reason I presume before, I know why they got rid of it, but is this risky or not? Because I haven't heard people discussing this side yet.
Also, what other payment services may work with this once they support it (if ever), ISIS? Paypass?
Axe Homeless said:
Stupid question, but if the secure element isn't necessary anmyore, is Google wallet now secure enough?
I mean, Google kind of used this for a reason I presume before, I know why they got rid of it, but is this risky or not? Because I haven't heard people discussing this side yet.
Also, what other payment services may work with this once they support it (if ever), ISIS? Paypass?
Click to expand...
Click to collapse
A few months ago, a Google patent application surfaced that explains some details of how they did it.
1) Previously, PIN entry to GW did not require a network connection - it only unlocked the SE. Now, you cannot unlock Wallet without a network connection. Also, PINs used to be device-specific but are now common to all devices on your Wallet account
2) The patent application references creation of a virtual card that is geographically and time-restricted
So pretty much, I think what happens is that when you unlock Wallet now, it creates a "virtual" card that is restricted to the unlock timeout in time and to some sort of geographic limitations.
I have a done a bit of looking but all I've come up with is mainly 'use trigger' or something like it. But my question is: Is there a way with Trigger to write a tag that anyone can read? Or is there another NFC tag writer app that I should use?
The thing I want to do is make a tag for friends to tap when they call over that will connect them to my wifi network, but if they have to go and download trigger first then no one is going to use my tag.
Sorry if this is a re-posted question, I looked and didn't see it anywhere here and when I put the title in there was no recommended threads that had what I was asking.
I've tried different apps, and it looks like connect to wireless is not one of the default actions that is included in Android. I've only found connect to bluetooth.
Hi, you can use NFC Tools for that.
All records on "write" tab is compatible with other NFC device.
daniel_loft said:
I've tried different apps, and it looks like connect to wireless is not one of the default actions that is included in Android. I've only found connect to bluetooth.
Click to expand...
Click to collapse
I am new to NFC and I am a little confused about what NFC can do. I have the nfc-tool App and I can read many NFC tags that I have.
But for an Android phone with NFC support, without installing any 3rd party App, what can it do? Is NFC enabled by default? Are there native NFC apps that can trigger action, open URL, etc?
Also, since each NFC tag already has a unique identifier, it seems to me writing data to NFC tag isn't all that useful when only 1 phone is using it. As you could have just programmed the command to the phone. The same applies to multiple phones if you can program the phones through some other means. Am I missing something here?
As I was saying, looks like what you want is only possible in Android L.
Have a nice day!
nookin said:
I am new to NFC and I am a little confused about what NFC can do. I have the nfc-tool App and I can read many NFC tags that I have.
But for an Android phone with NFC support, without installing any 3rd party App, what can it do? Is NFC enabled by default? Are there native NFC apps that can trigger action, open URL, etc?
Click to expand...
Click to collapse
Android has native build-in support for some simple standard NFC activities, like reading a messages/contact, open URL/URI, launch application etc. .For more sophisticated activities you will always need an app to parse the tag content and handle the activities.
Also, since each NFC tag already has a unique identifier, it seems to me writing data to NFC tag isn't all that useful when only 1 phone is using it. As you could have just programmed the command to the phone. The same applies to multiple phones if you can program the phones through some other means. Am I missing something here?
Click to expand...
Click to collapse
yep, fully agree. Have a look at NFC ReTag
ascsa said:
Android has native build-in support for some simple standard NFC activities, like reading a messages/contact, open URL/URI, launch application etc.
Click to expand...
Click to collapse
I'm a newbie here. I have a phone running 4.2.2. How do I make it read an NFC tag and take action without installing additional app? Just tap?
So I finally found an official NFC tag in mall. When I place my phone on it, it asks me to choose between stock Browser and Chrome. I guess if I have already chosen a default, it will just open a webpage. Now I wonder if there are security concerns. What if the URL is malicious? What if it downloaded a lot of data when the user is roaming?
I wonder what other functions an NFC tag can trigger without installing additional Apps? If I buy writable NFC tags, like the Samsung TecTiles, can it be programmed just like the mall NFC tag?
Android Pay & E.SUN wallet in my country uses HCE for Tap & Pay, any one got these working on OnePlus 3? Thanks...