I've tried to beam anything (photo, video, webpage, etc) from my Nexus 7 to my Galaxy Nexus and it won't work. I went into settings and made sure that NFC was checked and Android Beam on. This was the case for the GN but the 7 didn't allow me to select it. The NFC is checked but it's 'greyed' out and won't let me select it. Same with the Android Beam.
Anyone else having this issue? Or know how to solve it?
Many thanks in advance!
lexdouble said:
I've tried to beam anything (photo, video, webpage, etc) from my Nexus 7 to my Galaxy Nexus and it won't work. I went into settings and made sure that NFC was checked and Android Beam on. This was the case for the GN but the 7 didn't allow me to select it. The NFC is checked but it's 'greyed' out and won't let me select it. Same with the Android Beam.
Anyone else having this issue? Or know how to solve it?
Many thanks in advance!
Click to expand...
Click to collapse
Do you have airplane mode turned on?
I may be wrong but I believe android beam only allows for web and application address data to be shared. Pictures and whatnot are to large for the NFC chip to handle.
Sent from my EVO using xda app-developers app
Yea it passes small amounts of data although I just saw a SGSIII commercial at the movies where a guy does this. I'm not sure if it uses NFC the whole way or merely as a flag to turn on Bluetooth, pair, transfer, and disconnect... or use WiFi beam.
Sent from my Nexus 7 using xda premium
Did you ever find out a solution to your problem? I noticed I now have the same problem. I just used a NFC tag a week ago and am trying to figure out what I have done to the tablet since then. Definitely not in airplane mode.
EDIT: Never mind, a power off fixed it.
Is NFC turned on? settings > more > nfc - tick
Open Google Wallet
The NFC option on mine was not available until I activated (opened) Google Wallet.
Did you try a restart? Mine was greyed out last night along with NFC. Restart fixed it
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
This may not get you working, but it's definitely a little more insight as to what is happening for this type of transfer (larger payloads):
Android Beam
Android Beam is a popular NFC-based technology that lets users instantly share, just by touching two NFC-enabled phones together.
In Android 4.1, Android Beam makes it easier to share images, videos, or other payloads by leveraging Bluetooth for the data transfer. When the user triggers a transfer, Android Beam hands over from NFC to Bluetooth, making it really easy to manage the transfer of a file from one device to another.
Source: http://developer.android.com/about/versions/jelly-bean.html - about 3/4 down the page
I have bigger problem. My NFC and everything is working fine as far as software is concerned and the option is not out grayed out either. The option is checked however I am not able to beam anything to my SGS3. There is no sound or indication when I put them together from back. I know my SGS3 works fine because I have beamed someone before using it.
Sent from my Nexus 7 using xda premium
SOLVED: Restart N7 to enable NFC
Domino_13 said:
Do you have airplane mode turned on?
Click to expand...
Click to collapse
I had the same problem. All you have to do is shut down your Nexus 7 and turn it back on and you're all set.
I bought two xperia NFC tags over ebay, but since I have no experience with NFC, I am not sure if one of them work.
Red one is recognised by Smart connect and already had some action recorded and even has a nice red icon among devices. I can change data on it so it is ok.
But black one is not recognised. Then I tried NFC Taginfo and got very different results, from not readable to normaly wrtitable. After that I checked NFC Task Launcher and tried to write an action (change volume). On both tags I got 'not writable' warning, but it worked fine on red tag, but again nothing on black.
Can someone explain if I am doing something wrong or tag is corrupted? Maybe I should use some other app?
Another thing worrying me - is it possible I got a tag with malicius data? Is it possible to check if any unwanted data was sent from phone?
I guess it is corrupt/broken, you got it frmo eBay And one of them works so maybe something went wrong while shipping
I'm having some problems with NFC. Prior to Friday evening, my NFC was working great with Android Beam, Google Wallet, etc.
Friday afternoon I was playing around with Tasker and the NFC Locale plugin to create some tasks when a specific NFC tag was read. I made just a simple "turn on flashlight" task and was wowing myself with the magic of the tag. I also installed the Xposed module that lets you use NFC with the screen off. After playing with it for awhile I put my phone in airplane mode (I was in a poor service area). A few hours later (still in airplane mode but with NFC turned on) I resumed play with NFC and Tasker to make some more interesting tasks but noticed my phone wasn't responding to my previously used tag or any other (unused) tags. I thought maybe since I didn't cell signal that is why it wasn't working (stupid thought, I know) and decided to wait till I had service to resume the tinkering.
Fast forward to tonight, I still can't get my phone to respond to any NFC tags or any tap to pay terminals (for use with Google Wallet) or Android Beam with my SO's Moto X and I can't think of what else to try before I do a factory reset.
So far I have:
1) frozen/hibernated every NFC using app individually to test each one to see if any of them would work on their own
2) uninstalled every app and Xposed module that uses NFC except Google Wallet
3) rebooted my phone multiple times ensuring NFC is on
4) ran a logcat to make sure NFC is actually turning on/off and from what I can tell it is (I can post the logcat if need be)
Factory resets are such a PIA and I'd like to avoid it at all costs but I am thinking that is the way I need to go unless anyone has any other ideas for me. Googling around it seems like a lot of NFC issues tend to be hardware related...I am definitely hoping that is not the case.
Thanks in advance for any advice or input!
Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?
Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app
I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.
Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone
Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.
I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app
I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.
Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.
Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay
My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.
My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)
Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk
After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.
Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!
Greetings, mages,
My HTC One is presently running CM11 M10. I understand 4.4.4 includes a new "HCE" feature, which I was hoping to use to get Google Wallet's NFC working with my phone.
NFC enabled in settings. Google Wallet's option to enable Tap and Pay is missing - it's not present in Google Wallet's settings screen like it is supposed to.
So today, I wanted to see if NFC worked at all. I downloaded two apps that purport to be NFC readers and scanned several cards which I know to be NFC-capable. The apps are NFC Tools and NFC Reader, the cards are a generic RFID access card, my DOD CAC, and a Chase CSP credit card. To rule out a proximity issue, I removed my phone from my case and tried scanning the cards in multiple positions and orientations near my phone's camera lens, where the NFC reader is supposed to be located, while each app was open in turn. None of this resulted in an NFC "read", even though the app was open and NFC was enabled.
Now that I'm at home, I have tested with my CAC again - the phone is making a sound whenever it's near my CAC, but not any of the other things I believe to be NFC capable, including a passport. Still no go with any of these apps.
Is there a log to check or some way to debug this to see why these tags aren't being scanned? Any way to get Wallet to recognize that my phone has NFC?
I don't know what's happening, but if I were you I would try getting a logcat to see what's going on
While testing that, I tried another card that I didn't have with me yesterday and the phone was able to connect and launch the app. So, that rules out the hardware itself as being the problem with Google Wallet, but I can't figure out why it won't give me the option to enable tap-and-pay.