Develop Bugs

[Q] NFC not working?

Hi Guys.
My friend was trying to tell me how awesome NFC is, but no matter what we tried we cannot get it to work.
Its fine between his Nexus and S3, but neither will connect with my HOX.
I am running Leedroid, though im not sure that will matter.
I will try with my wifes HOX later, but has anyone else encountered trouble and how did you get it working?

lets get the stupid questions out of the way first...
You turned it on in settings >more >NFC?
you got android beam turned on just underneath that?

Yep, all of these things ticked.
And you are right, stupid questions out of the way first!
I tried with out my phone case and his phone case just to be sure. I tried all combinations of holding together (front to front, back to back, front to back etc) but still nothing.
Any other ideas would be great

I did succesfull with two HOX. And it worked fine to "beam" a contact (back on back) wich is opened. I'm also using NFC tags since weeks.
I think the problem are the two different vendors of the phones. Probably S Beam is not comptabile to Android Beam of HTC

S Beam is just for Galaxy S III. It should still support Android Beam. Yay for more proprietary standards.
Try it with another phone to see if its the HOX or SIII
My NFC worked fine for sharing a web link...

Thanks for the advice.
Tried with the wifes HOX, worked first time.
Guess it is a bit of a hiccup between vendors, might be something that gets patched in the future

ME TOO - But different issue?
I'm seeing similar...
Having now found out that Android Beam cannot be used for transfer of photos and video files, I discovered "Blue NFC"
The principle behind this app is simple...
When tapping your two devices together, the NFC chip, which is not suited for heavy file transfer, INSTEAD does the back-end work at automating a BLUETOOTH pairing between both devices, without any security questions, user action etc. It then uses BLUETOOTH to send the file, and then closes the connection.
But it seems there is some strange issue with the HTC One X...
As trying this method, bumping the devices (A Galaxy S3 and an HTC One X both with Blue NFC installed), causes the Galaxy S3 (as the host device) to allow me to tap to send the file to the One X...
Blue NFC sets up the Bluetooth connection automatically, and the file starts sending.
BUT... when it reaches 99%, on the HTC one X, I receive a "File Transfer/Could not be received" error, EVERY TIME.
Alas, I think this must have something to do with the new BT 4.0 spec on the Galaxy S3, and the HTC One X not supporting this, and I think this for the following reason...
Setting aside any fancy NFC wizardry, when trying a normal, traditional, Bluetooth image transfer the "old fashioned normal" way from a SGS3 to an HOX, the file transfers up to 99%, and fails every time then too.
Yet file sending FROM the HTC One X, back TO the SGS3, works fine.
The SGS3 can receive files fine. The HOX however cannot.
Has anyone else been able to send files either via:
1. ANDROID/S-Beam from SGS3 to HTC One X
2. Blue NFC from SGS3 to HOX
3. Traditional standard BT File Transfer from SGS3 to HOX
-
It's totally doing my head in!

Perhaps you can try File Expert. I don't know how it is establishing the transfer.
Early I read that the concepts planned to use WiFi direct to transfer data

Shadamehr said:
I'm seeing similar...
Alas, I think this must have something to do with the new BT 4.0 spec on the Galaxy S3, and the HTC One X not supporting this, and I think this for the following reason...
Click to expand...
Click to collapse
The HTC One X is Bluetooth 4.0 so id doubt its that.

My NFC is not working at all. Can anybody help. It has just stopped, it worked on stock 1.28, since ive ran slim, arhd, + leedroid, now im on stock 1.29.401.11 and it is not working at all. can anybody please help
thanks
drew071

Another bit of info is that in alogcat, the software is switching NFC on and off with the screen state.
Is there a way the NFC hardware could have been damaged?
drew071

drew071 said:
My NFC is not working at all. Can anybody help. It has just stopped, it worked on stock 1.28, since ive ran slim, arhd, + leedroid, now im on stock 1.29.401.11 and it is not working at all. can anybody please help
thanks
drew071
Click to expand...
Click to collapse
I figured mine out. The NFC chip is in the stock battery, so my non-OEM extended "2850 mAh" (they're pretty close to stock time-wise, though) effectively removes the NFC hardware from the phone.
So, I'm going to try putting some packing foam around the stock S3 battery in my Note and see if I can rig up or find the software to support it.

My wife got anS3 the other day, and every time we'e tried it with my HOX, I can't beam a picture. I've been able to transfer an app (link to the play store)
When I try to transfer a picture from the S3 to my HOX, I get the message,
text/DirectShareGallery

rushwal said:
My wife got anS3 the other day, and every time we'e tried it with my HOX, I can't beam a picture. I've been able to transfer an app (link to the play store)
When I try to transfer a picture from the S3 to my HOX, I get the message,
text/DirectShareGallery
Click to expand...
Click to collapse
As mentioned before the phones are not compatible. Perhaps it works if you use Roms like AOSP

ive just tried this with a galaxy s3 user and my CM10 HOX. worked well with youtube vids, pictures and contacts. The bumping phones process is a bit weird, to be honest

Glad to hear that this works with CM10, really disappointed that it doesn't work with Sense. Hopefully they fixed it in the Jellybean update?
Sent from my HTC One X using Tapatalk 2

Not working
Just tested with a s3 and a htc one x, both jelly bean and it doesn't work

NFC S Beam

Hello NFC experts.
I received my Nexus 10 yesterday and I love it. I also have a Galaxy S3 running Stock Jellybean and would like to be able to beam photos or music from it to the Nexus 10. Although I can send webpages and YouTube links via NFC, I cannot send pictures.
Whenever I try, the connection is made but the Nexus opens the Play Store instead of receiving the file.
I have tried it with S-Beam off but the S3 insists on it being on.
The Nexus will however send photos to the S3.
I have a similar question in the Nexus 10 forum at the moment but thought that this may be the best place to ask.
Any ideas?
Sent from my GT-I9300 using xda app-developers app

That's because S Beam and AOSP use different methods of transferring the data. AOSP uses Bluetooth, S Beam uses Wi-Fi Direct. Small files work because they use NFC to transfer. (NFC is slow, that's why it's not used for larger files.)
Sent from my Galaxy Nexus using xda premium

I had the same issue as him. I just want to know if it is possible to get an app for the s3 or note 2 that will send it to the nexus using the AOSP standard?

same problem... no ideas!?

Question
what is NFC and what is its role in Mobile Phones? anyone help!

kingayazkhan said:
what is NFC and what is its role in Mobile Phones? anyone help!
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Near_field_communication
It allows for very easy handshakes for transferring files. (Just tap two compatible devices together and the download will start)
Sent from my Galaxy Nexus using xda premium

Android Beam is one of the standard features of Android platform and implemented within Android Application Framework.
On the other hand, S-Beam is Samsung's proprietary and that works only between two Galaxy S3s.
When you try to send pictures from the Galaxy S3 to the Nexus 10, Galaxy S3 sends a handover request message for
establishing a Wi-Fi Direct link to the Nexus 10, as in S-Beam manner. However the Nexus 10 doesn't support S-Beam
and that attempt fails.
When you try to send pictures from the Nexus 10 to the Galaxy S3, Nexus 10 sends a handover request message for
establishing a Bluetooth link to the Galaxy S3, as in Android Beam manner. Because Android Beam is a standard
feature of Jelly Bean, Galaxy S3 accepts the request and return a handover select message to the Nexus 10. Then a
Bluetooth OPP link is established between those two devices and the pictures are transferred.
Hope this could help you.
chugglet said:
Hello NFC experts.
I received my Nexus 10 yesterday and I love it. I also have a Galaxy S3 running Stock Jellybean and would like to be able to beam photos or music from it to the Nexus 10. Although I can send webpages and YouTube links via NFC, I cannot send pictures.
Whenever I try, the connection is made but the Nexus opens the Play Store instead of receiving the file.
I have tried it with S-Beam off but the S3 insists on it being on.
The Nexus will however send photos to the S3.
I have a similar question in the Nexus 10 forum at the moment but thought that this may be the best place to ask.
Any ideas?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse

k.h. said:
Android Beam is one of the standard features of Android platform and implemented within Android Application Framework. On the other hand, S-Beam is Samsung's proprietary and that works only between two Galaxy S3s. .....
Click to expand...
Click to collapse
Yep, good description!
From my point of view, this is a good example why NFC is struggling for years (believe it, or not, the first nfc phone , Nokia 6131 NFC ; was introduced 2007 ...) ...Let me explain my point of view:
- First, some kudos to Samsung for implementing the WiFi transfer via S-Beam ! Not sure, why this is not implemented within the android standard, but i think it´s only a matter of time...
- Second, some BOO to Samsung for messing with the standard and introducing a not compatible function (btw.. There is a connection handover specification defined by the NFC Forum... and Samsung implemented two major flaws):
1.) Why not let the devices handle out the alternate carriers (WiFi/ Bluetooth), e.g. if WiFi is available ,use Wifi (S-Beam), else use Bluetooth (Android-Beam) ...No, S-Beam insists on WiFi ....
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Bottom line: Hello samsung, fixing one of the mistakes above, will do the trick
Edit: Samsung fixed 2.) with new GS3 firmware (4.1.2) ...

ascsa said:
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Click to expand...
Click to collapse
That's because pure NFC file transfert is very slow, as mentionned earlier in the thread. You can send/receive small files of few bites but not more. And I agree with you, S-Beam system with direct wifi transfert for all compatible smartphones should be the next feature of android

Okay, so my question is this. I have the Nexus 10 and the Galaxy Nexus, but they will not transfer or connect correctly. Definitely get an acknowledgement sound, but nothing further. What else is required on my part? Also, what are some of the ways people are using NFC tags?
Sent from my Nexus 10 using Tapatalk 2

frankynov said:
That's because pure NFC file transfert is very slow, as mentionned earlier in the thread. You can send/receive small files of few bites but not more. And I agree with you, S-Beam system with direct wifi transfert for all compatible smartphones should be the next feature of android
Click to expand...
Click to collapse
Sorry, not correct!
(standard) Android -Beam uses Bluetooth to transfer pictures ... works without any problems between a nexus 7 and a nexus 10 ...

Speed_419 said:
Okay, so my question is this. I have the Nexus 10 and the Galaxy Nexus, but they will not transfer or connect correctly. Definitely get an acknowledgement sound, but nothing further. What else is required on my part? Also, what are some of the ways people are using NFC tags?
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, my experience is, that most users (including myself ) struggling with the handling of the beam feature, especially if you try it alone....I would love to have a third hand for this ....
Let´s try to beam a picture step by step:
- First enable android beam (-->settings) on both devices ...
- Be aware, that standard nfc will only work when device is not locked and screen is on(--> e.g. homescreen on both devices!)
- open the galerie app on the sending device --> then open the picture ...
- tap the devices together with their "nfc sweet spot" ...--> you should hear the nfc sound AND the picture should shrink and a message "touch to beam" should appear
- Touch the shrinked picture without losing the nfc connection (thats where the third hand would be nice ) and voila the beam should start ....

Earlier tonight a friend had a nexus 7 and I had my nexus 10, we tried to get NFC working for like a half hour, with no success. We both had NFC and Beam on, we were both connected to WiFi, and we eve tried with Bluetooth being turned on (but not paired).
Is there something we were doing wrong?
Is this the incompatibility that Samsung has?
I'm not on CM10, but I am rooted and on the latest update (ends with D).

Is your nexus 7 running the latest version 4.2? I have both devices as well and they are both up to date, nexus 7 is on a custom rom, but nfc works fine between both devices when say loading YouTube video on nexus 7, then holding holding both devices until connection is made then holding down the shrunken video then it opens youtube on nexus 10 and goes to the video. The issue with Samsung is for who knows what reason, when i first got it stock with ics it only had sbeam. As opposed to when I upgraded to JB, they added android beam as well. That way you could connect to non Samsung devices over nfc. Since as someone else said sbeam uses wifi direct to make the connection resulting in a much faster connection. While beam is over bluetooth. I ve heard rumors of the upcoming updates will more than likely contain the wifi direct version of NFC as its much faster and transferring files, etc is too slow as is. I dont know why its not in there already since 4.2 waa supposed to be the Android version that supports miracast, which relies on wifi direct as well. Although Samsung augmented there JB 4.1 with the update for allshare fw update that allows miracast transfer using there dongle.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

ascsa said:
Yep, good description!
From my point of view, this is a good example why NFC is struggling for years (believe it, or not, the first nfc phone , Nokia 6131 NFC ; was introduced 2007 ...) ...Let me explain my point of view:
- First, some kudos to Samsung for implementing the WiFi transfer via S-Beam ! Not sure, why this is not implemented within the android standard, but i think it´s only a matter of time...
- Second, some BOO to Samsung for messing with the standard and introducing a not compatible function (btw.. There is a connection handover specification defined by the NFC Forum... and Samsung implemented two major flaws):
1.) Why not let the devices handle out the alternate carriers (WiFi/ Bluetooth), e.g. if WiFi is available ,use Wifi (S-Beam), else use Bluetooth (Android-Beam) ...No, S-Beam insists on WiFi ....
2.) Why make S-Beam mandatory for sending pictures? On a galaxy s3, you could enable/ disable both (S-Beam and Android-Beam) , but sending pictures via the galery insists on using S-Beam ...so the standard Android-Beam is not available for sending pictures on a GS3 ...
Bottom line: Hello samsung, fixing one of the mistakes above, will do the trick
Click to expand...
Click to collapse
Received the 4.1.2 Update for my Samsung GS3 yesterday ... and guess what... Samsung fixed it )) ....They fixed number 2 (above), so S-Beam is not longer mandatory for sending pictures from the galery (just disable S-Beam) ....and android beam works as expected ... beaming pictures from the galery between a GS3 and a nexus 10 over bluetooth works now without problems

there is an app on the app store called wifi direct, from the description and the install it appears to be able to handle nfc initiated wifi direct transfers? i only have my nexus phone so i dont really have another thing to test it against just yet, but it might be the missing link with the beam stuff....

How to screencast LIVE to another phone?

OK I want to build a rig to take better panoramics and to take tight quarters panoramics. problem is will be hard to see the screen in either situation sometimes.
SO it hit me. this thing can stream live content to a tv. well how about to another PHONE. basically use a second phone as a view finder of sorts.
for example I want to slave my S3 to my Note II so I can put the S3 in a rig and "see" what is on the screen of the S3 via my Note II. (since I need to see the little blue dots to do the panoramics)
I tried a VNC "type" setup but the lag time is simply too great and its unstable and unreliable.
I need something that is Point to Point wifi (wifi direct?) and low lag (like the screen cast function)
suggestions on how I can do this?

nerys71 said:
OK I want to build a rig to take better panoramics and to take tight quarters panoramics. problem is will be hard to see the screen in either situation sometimes.
SO it hit me. this thing can stream live content to a tv. well how about to another PHONE. basically use a second phone as a view finder of sorts.
for example I want to slave my S3 to my Note II so I can put the S3 in a rig and "see" what is on the screen of the S3 via my Note II. (since I need to see the little blue dots to do the panoramics)
I tried a VNC "type" setup but the lag time is simply too great and its unstable and unreliable.
I need something that is Point to Point wifi (wifi direct?) and low lag (like the screen cast function)
suggestions on how I can do this?
Click to expand...
Click to collapse
Correct me if I'm wrong but on the samsung website it advertises screen to screen interface, exactly as you are talking about. It doesn't appear laggy at all. I believe it's in your settings, wifi, more settings and then something like screen share. Maybe it only works on note 2 to note 2 and s3 to s3. If that is what you're talking about.

of files yes but i need the live screen like connecting to a tv but device to device

nerys71 said:
of files yes but i need the live screen like connecting to a tv but device to device
Click to expand...
Click to collapse
Meaning...? Please expand upon that thought.

islandjat said:
Meaning...? Please expand upon that thought.
Click to expand...
Click to collapse
you can share/play files over multiple screens via the method you posted....not live video duplication of the original screen.
I looked for something along these lines last uear but gave up after finding very little.
Sent from my SPH-L900 using xda app-developers app

00mred00 said:
you can share/play files over multiple screens via the method you posted....not live video duplication of the original screen.
I looked for something along these lines last uear but gave up after finding very little.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Oh. That sucks. I thought it could do live video duplication.

driving me nuts 100% of the needed tech IS HERE just needs the software to do it. Grrrr
think of it like remote login. where you log in remotely to someone elses computer and their screen shows up on your screen so you can interact with their computer.
I need that without internet direct point to point wifi. (I tried vnc type things and while it "works" its way way too slow to be at all useable)
Grrr

nerys71 said:
driving me nuts 100% of the needed tech IS HERE just needs the software to do it. Grrrr
think of it like remote login. where you log in remotely to someone elses computer and their screen shows up on your screen so you can interact with their computer.
I need that without internet direct point to point wifi. (I tried vnc type things and while it "works" its way way too slow to be at all useable)
Grrr
Click to expand...
Click to collapse
You should email samsung and tell them how to do their job
---------- Post added at 11:24 AM ---------- Previous post was at 11:17 AM ----------
now that I think about it, if they added that kind of functionality into the phone, think of how good it would be for people like a business meetings how they could interact so very easily. That would be a huge marketing tool they could use.

I know that this is a vnc connection, but have you tried teamviewer? I think its called quick connect, but im not sure if there would be lag if the two phones were on the same wifi network

[Q] Android Beam/ S-Beam

Hey guys,
I just joined up today so bare with me as I am new. My wife just got the Nexus 4 and I currently have the Galaxy Note 2. We are both with tmobile. We were trying to "bump" phones last night to share music. Everytime I tried to share a song from my phone to hers it would get all the way to the point where it would have you click the screen and then pull the phone away but then nothing happened on her end or android google play store would pop open with a error message. Can you not use Android Beam and S-beam together? Do you have to use certain settings?
Any help would be appreciated!
Thanks

Did you have sbeam/android beam, nfc and bluetooth turned on on both phones?
Android uses nfc to connect the phones but for larger files it actually uses bluetooth to transfer the files. Try turning on nfc only and transfering a web page that is just a link that transfers and should show theat your nfc is working as it will open the browser on the receiving phone to the same web site.
Also when you beam something you have to have compatible apps on both phones to make it work so sometimes it works better to use 3rd party apps on both phones.
I was trying to get the Nexus 4 I had to work with my wifes Sony Xperia Acro S with only partial luck and have not gotten around to trying my Note 2 with her Sony Xperia Acro S yet but suspect it will only be partially effective.

The nexus 4 doesn't have s beam. ..so there are these issues. ..no solutions yet. ...I had made a thread addressing the same issue with my nexus 4 and s3 and note 2... in the nexus forum. ..no fix. ... yesterday tried doing that sane with a nokia Lumia 920... same problem. ...only Samsung has the full features of nfc working with the amazing s beam
scribbled from my note 2 (N7100)

AT&T Push to Talk on Note 2

For those who may find this useful...
I added the PTT service on my phone not thinking that my device may not yet be compatible with the app from AT&T. I found out the hard way but figured out how to get it going on my device.
1. After adding the service online I got a text a half hour later that it was active on the account.
2. I then rooted my Note 2 on the latest stock 4.3 rom.
3. Downloaded the app: Device Spoofer from the Play Store.
4. Backed up the device's current information in Device Spoofer
5. Changed the device's ID to that of the Galaxy S4 (i.e. sgh-i337)
6. Restart the device.
7.Launch At&t EPTT app and activate.
8. Once activated you can run spoofer again and restore your device's I'D and restart and the app will still work.
Just guessing but I would think this should work on the Note 3 as well. Everyone uses this at work so I thought it was worth looking into.
***EDIT: I used the Helium app to backup the At&t EPTT app and data to my Google Drive account and restored it on my At&t Note 3 and can confirm it works. I did not root my note 3 due to the Knox issues discussed here on XDA, so if anyone has another device that is rooted this is an easy way to get the PTT app working on a non rooted one.***
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

THANKS!!
This is awesome. Was thinking about trying this with a Nexus 5. Currently stuck with a Rugby Pro and it is BRUTAL. Glad to know there's a way around AT&T's BS.

ercave1 said:
For those who may find this useful...
I added the PTT service on my phone not thinking that my device may not yet be compatible with the app from AT&T. I found out the hard way but figured out how to get it going on my device.
1. After adding the service online I got a text a half hour later that it was active on the account.
2. I then rooted my Note 2 on the latest stock 4.3 rom.
3. Downloaded the app: Device Spoofer from the Play Store.
4. Backed up the device's current information in Device Spoofer
5. Changed the device's ID to that of the Galaxy S4 (i.e. sgh-i337)
6. Restart the device.
7.Launch At&t EPTT app and activate.
8. Once activated you can run spoofer again and restore your device's I'D and restart and the app will still work.
Just guessing but I would think this should work on the Note 3 as well. Everyone uses this at work so I thought it was worth looking into.
***EDIT: I used the Helium app to backup the At&t EPTT app and data to my Google Drive account and restored it on my At&t Note 3 and can confirm it works. I did not root my note 3 due to the Knox issues discussed here on XDA, so if anyone has another device that is rooted this is an easy way to get the PTT app working on a non rooted one.***
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a rooted S3 and used helium to backup and transfer to my new S5 and it doesn't work. It tries to activate and then fails saying i dont have a supported device. I must be doing something wrong?
EDIT: Rooted my S5 and tried your first method and still no dice. Hmmmm this is interesting. If I cant get this figured out I guess I will have to return the phone. Are you using your old sim or the new one that comes with the phone?

ProStreetCamaro said:
I have a rooted S3 and used helium to backup and transfer to my new S5 and it doesn't work. It tries to activate and then fails saying i dont have a supported device. I must be doing something wrong?
EDIT: Rooted my S5 and tried your first method and still no dice. Hmmmm this is interesting. If I cant get this figured out I guess I will have to return the phone. Are you using your old sim or the new one that comes with the phone?
Click to expand...
Click to collapse
It seems that my original method no longer works since they updated the PTT app. I was able to Spoof My Note 1's (sold my Note 2) device ID to that of an S4 and the app activates that way. I was hoping I could back it up again with Helium and Restore to my Note 3 but it tries to reactivate on the Note 3 and detects the current device ID. So at this point I believe my only option is to root my Note 3, spoof the device ID, and activate. Not something I want to do.
I also found that if I enable airplane mode then enable WIFI and you launch the app, after a minute or two it asks if you want to try to activate over WIFI, and then asks to enter an code provided by an administrator. I wonder if ATT would be willing to provide a code to users that already have the feature on the account and want to try the app on a newer device...It's a shot in the dark but couldn't hurt to ask.
EDIT: By ID, I mean model number.

ercave1 said:
It seems that my original method no longer works since they updated the PTT app. I was able to Spoof My Note 1's (sold my Note 2) device ID to that of an S4 and the app activates that way. I was hoping I could back it up again with Helium and Restore to my Note 3 but it tries to reactivate on the Note 3 and detects the current device ID. So at this point I believe my only option is to root my Note 3, spoof the device ID, and activate. Not something I want to do.
I also found that if I enable airplane mode then enable WIFI and you launch the app, after a minute or two it asks if you want to try to activate over WIFI, and then asks to enter an code provided by an administrator. I wonder if ATT would be willing to provide a code to users that already have the feature on the account and want to try the app on a newer device...It's a shot in the dark but couldn't hurt to ask.
EDIT: By ID, I mean model number.
Click to expand...
Click to collapse
I got it working. The app now looks at the phones model number. I simply changed the model number to that of an S4. It activated right away once i did that. When I go to about device my S5 shows as SAMSUNG-SGH-I337 which is an S4. :good:

Changing the ID appears to screw up NFC until you change it back to the original, at least on my Note 3. Changing back to the original kills the activation. Att seems to have caught on because the app, even the older version now activates on reboot.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

ercave1 said:
Changing the ID appears to screw up NFC until you change it back to the original, at least on my Note 3. Changing back to the original kills the activation. Att seems to have caught on because the app, even the older version now activates on reboot.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm interesting on the NFC. I dont use it so im not sure how the S5 reacts to the change. The eptt app has been working flawless though and the manager at the store called corporate and they told him they would be updating the app in the near future to support the S5.