Hi everyone...
I was at the gas station last night, and thought I'd try using NFC/Google Wallet to try paying for something for the first time.
I went in to turn on NFC, and found that the option is completely grayed out. (The button is set to "on", but its grayed out, and cannot be turned off)
Android Beam is disabled/grayed out.
S Beam is enabled, but I can't seem to change it.
Tap and Pay is disabled, and says, "NFC is turned off".
Something is clearly FUBAR'd here.
I've tried rebooting a couple times.
I've tried pulling the battery (yes, its the original OEM battery).
I've tried wiping data for NFC.
I tried re-installing the stock ROM, and it didn't fix anything.
Any other suggestions?
Thanks..
Just a follow up here... I've also tried a complete wipe of the device... still no go.
sloheim said:
Just a follow up here... I've also tried a complete wipe of the device... still no go.
Click to expand...
Click to collapse
Still running ktoonsez kernel ?
DEATHWISH .500 said:
Still running ktoonsez kernel ?
Click to expand...
Click to collapse
Yes.
And when I did a complete wipe and re-install, I was able to verify that its happening with the stock kernel also, so I don't believe it to be a kernel issue.
I was able to try a different battery today... from someone else with an S5, and the same problem exists.
My next step is to try unrooting and going back to complete stock... obviously I'd like to avoid this if at all possible.
Any other suggestions? Anyone?
Well, I did it today.. unrooted, went back to full stock everything... and I still cant change the NFC setting on my S5.
If anyone has any other suggestions, I'm more than open to anything at this point...
sloheim said:
Well, I did it today.. unrooted, went back to full stock everything... and I still cant change the NFC setting on my S5.
If anyone has any other suggestions, I'm more than open to anything at this point...
Click to expand...
Click to collapse
Do you have insurance ? I would think about taking it to a Sprint store and see what they say. You might have a hardware problem
DEATHWISH .500 said:
Do you have insurance ? I would think about taking it to a Sprint store and see what they say. You might have a hardware problem
Click to expand...
Click to collapse
No, but I may get it for this. What a bummer.
Could someone be so kind as to post a copy of their /data/data/com.android.nfc/shared_prefs/SamsungNfcPrefs.xml file for me?
Also, can you tell me if you have an nxpdevicehost.xml file in that same directory?
Thanks!
Here are the latest details. I feel like I'm so close, yet so far.
Background:
When I would reboot my S5, the NFC setting would be set to "On", but disabled and wouldn't let me change it. On top of that, my phone would never go into Deep Sleep. After exhaustive research, it appears that the phone was constantly trying to enable NFC, which prevented it from hitting Deep Sleep.
I've dug thru a lot of the AOSP code, and discovered the following.
- If I change the nfc_on tag from true to false in my NfcServicePrefs.xml, and add a line setting first_boot = false, NFC does not try to turn on when I reboot the next time (This solves my deep sleep problem).
- If I try to manually turn NFC on after that, it gets stuck the same as before I made any changes to the XML file.
- Based on this code, it looks like there is a java call to "mDeviceHost.initialize()". I'm guessing this is where I'm getting borked.
- The initalize function, found here, seems to want a file called NxpDeviceHost.XML. I cannot find this file anyplace on my S5.
My assumption here is that Samsung forked this process and made their own internal changes. I'm looking at AOSP code, but that doesn't help if Samsung changed things on their end.
Can ANYONE help me debug things from here? I'm a developer by trade, but have never worked in JAVA (although I've figured out how to read enough of it to become dangerous). I dont need a lot of hand-holding... just a push in the right direction here.
Thanks!
sloheim said:
Could someone be so kind as to post a copy of their /data/data/com.android.nfc/shared_prefs/SamsungNfcPrefs.xml file for me?
Also, can you tell me if you have an nxpdevicehost.xml file in that same directory?
Thanks!
Click to expand...
Click to collapse
Once I'm off work Friday night I'll get ya a copy of that file if you still need it
DEATHWISH .500 said:
Once I'm off work Friday night I'll get ya a copy of that file if you still need it
Click to expand...
Click to collapse
Still looking for any help I can get. Thanks.
Actually contents of both XML files in the /data/data/com.android.nfc/shared_prefs would be appreciated.
sloheim said:
Still looking for any help I can get. Thanks.
Actually contents of both XML files in the /data/data/com.android.nfc/shared_prefs would be appreciated.
Click to expand...
Click to collapse
Here ya go. Attached is a zip with everything that was in the shared-prefs folder
I have the same issue on an LG-e970. The NFC option is checked and grayed out, I can't change it. It's always been this way since I got the phone. The new problem in the past 48 hours is some OTA update is causing Nfc Service to prevent the phone from sleeping, but I have no idea what it is. I thought maybe Google Wallet so I uninstalled it, but the problem remains. It happened well after the Android 4.4.4 Cm11-M8 update for this phone. I filed a bug at code google dot com bug ID 74037, which this silly forum won't let me post because I'm too new and it doesn't understand the difference between a google code URL and spam.
Weird. So I powered off the phone, let it charge to 100%, booted in safe mode, Settings > Storage > Cache and reset it, rebooted in normal mode, and let the phone sit unused for 1 hour. The problem with Nfc Service is not occurring, the phone is sleeping most of the time now. When I go to Settings > More > NFC is unchecked, not grayed out. Inexplicable, because I've had no way to uncheck it.
So I just checked it, and it immediately grays out so I can't uncheck it again. I'm leaving the phone unused for another hour and see where things are at.
chrismurphy said:
I just checked it, and it immediately grays out so I can't uncheck it again. I'm leaving the phone unused for another hour and see where things are at.
Click to expand...
Click to collapse
Nfc Service is once again the top battery consumer and won't let the system sleep. The bugreport for the state with the problem (in contrast to the report for the state without the problem):
many instances of:
07-24 11:23:16.870 1064 8319 E NFCJNI : emergency_recovery: NFC stack dead-locked
and also
Wake lock 1027 NfcService:mRoutingWakeLock: 1h 6m 26s 537ms (0 times) realtime
Wake lock NfcService:mRoutingWakeLock: 1h 6m 26s 537ms partial (0 times) realtime
Wake Locks: size=1
PARTIAL_WAKE_LOCK 'NfcService:mRoutingWakeLock' (uid=1027, pid=1064, ws=null)
I've booted recovery, formatted /cache and erased Dalvik cache, see where that goes... obviously if I can figure out how to disable the NFC option again, that solves the no sleep problem.
had same issue but with note 3. It was kernel issue so reverted to the previous kernel i was on and its o
Sorry to bring this thread back to life, but I'm having the same issue and would like to know which solution worked out for you. Thanks.
on oneplus one, can anyone turn off their double tap to wake/sleep ?
i can turn it off from settings, and it works for a bit then automatically turns back on
or to expedite the "bug" turn it off from settings then remove "settings " app from recent windows and go back to the setting and youll see checkmark is back to on
OR if you restart your phone after switching them off, theyre both back on
regardless, it automatically comes back on.... anyone else experiencing this ?
yeah the persistence in settings for this is currently broken. its already been fixed for the next update coming soon.
Where did you see this? Is there a changelog for upcoming update somewhere?
Sent from my Oneplus One
its in the jira somewhere. a guy in irc was talking about it and another guy said it was fixed already.
you can search for it: https://jira.cyanogenmod.org/browse/BACON
Funny, because now this is broken again in the latest update
Sure is along with battery performance
am having an issue with the apps lock screen. I either can not find, or the functionality to manipulate the playback controls does not exist without taking it completely out of lock mode.
I think the app is wonderful but I think this is a major oversight. I saw posts about this same issue in 2014 and I guess you decided not to do it. The controls you have are so unique and helpful that if you could make it easier to manipulate for the those who are on the go most of the time listening to music etc. I do not want to get hit by a bus trying to mess around with the volume\shuffle options\dealing with other app windows on my phone. I hope there is something planned as far as a change may go.
One quick issue. The player pauses for a second every time I turn off the screen. I saw this prob in another thread that was not answered.
I think it would really put your player cleatly ahesf of the competition! Plus I would be eternally grateful
I have a Pixel XL by the way...
Hope to hear back soon,
Andrew
andykc12 said:
am having an issue with the apps lock screen. I either can not find, or the functionality to manipulate the playback controls does not exist without taking it completely out of lock mode.
I think the app is wonderful but I think this is a major oversight. I saw posts about this same issue in 2014 and I guess you decided not to do it. The controls you have are so unique and helpful that if you could make it easier to manipulate for the those who are on the go most of the time listening to music etc. I do not want to get hit by a bus trying to mess around with the volume\shuffle options\dealing with other app windows on my phone. I hope there is something planned as far as a change may go.
One quick issue. The player pauses for a second every time I turn off the screen. I saw this prob in another thread that was not answered.
I think it would really put your player cleatly ahesf of the competition! Plus I would be eternally grateful
I have a Pixel XL by the way...
Hope to hear back soon,
Andrew
Click to expand...
Click to collapse
Probably you might have disabled lock screen notification in device's settings.
Regarding pause while switching between background and foreground, it was intentionally introduced to avoid issues. Development team is already working on it. It's already planned to make it optional. Kindly be patient till they implement it.
My phone kept "falling asleep" for what seemed to be at random times when using the phone. I finally determined it was because of the one-handed mode. When I drag from the side, to the middle, which is supposed to activate the mode, it turns off the phone display off as if I pressed the button to do that, or double tapped it (which I have activated) - is anyone else experiencing this??
The other issue I have is that I recall having the open to pull the notification area down, and along with the brightness, it showed the volume too. I know that you are "supposed to" go to where the pen icon is to edit....but when I press on the three dots, the only option is brightness, so it's not even as if I have the option to enable that, even if I wanted to!
Thoughts? Is there a developer option I need to enable?
PS: I beg that you don't ask me for phone specifics if you're not sure that it would resolve the issue. I have no issue sharing that information with anyone. But if you don't know if Oreo, for example, is the cause...I'd rather not try to locate information that may never be used to troubleshooting, which would waste both of our times.
1: it should not turn off. Are you on an aftermarket display?
2: probably software issue. Did you flash update or OTA install?
GordenW said:
1: it should not turn off. Are you on an aftermarket display?
2: probably software issue. Did you flash update or OTA install?
Click to expand...
Click to collapse
Hi, thank you for the reply.
No I am not on an aftermarket display. I purchased this through Verizon.
Along those lines, all updates have been through the automated process built into the phone.
I agree that it appears to be software, or at least software that may have been installed. Is there a way to search by install date on my device? I may have to reverse engineer what application was installed when this happened (maybe about two months ago, probably less) - my only concern is I may uninstall that software but whatever change was made remains. Wondering if there is a "rollback" feature on the phone where I can just put it back to a certain point in time.
daveaphoto said:
Hi, thank you for the reply.
No I am not on an aftermarket display. I purchased this through Verizon.
Along those lines, all updates have been through the automated process built into the phone.
I agree that it appears to be software, or at least software that may have been installed. Is there a way to search by install date on my device? I may have to reverse engineer what application was installed when this happened (maybe about two months ago, probably less) - my only concern is I may uninstall that software but whatever change was made remains. Wondering if there is a "rollback" feature on the phone where I can just put it back to a certain point in time.
Click to expand...
Click to collapse
I would say the easiest is just to use lg UP to flash a slightly earlier version. I can't tell too much and I don't think an app being installed/uninstalled would matter.
I need help and understanding and issue I'm having with my Moto E6.. so all sudden out of nowhere one day my phone began giving me a notification about how a bug report had been captured and then it happened again it said by report too been captured and then over the course of the next 3 or 4 days and still now to this day cuz it began 3-4 days ago and it's been happening ever since I go and check under developer options in the settings and I look at the enable USB debugging toggle switch and I have insured that it is off for sure and so I know it is not enabled yet it out of nowhere then will enables itself somehow seemingly and give me more notifications about how a bug reported been captured again and then I go check the developer options and oh lo and behold it isn't able to get yet I never enabled it no one's using my phone it's been within my pocket the entire time every time that this has happened and I'm not pressing buttons on accident so I truly need someone to help me understand how is this even possible and what do you think it means? please help thank you any information would be greatly appreciated thanks guys you guys are awesome thanks for being welcoming look forward to hearing from you all on this
I would remove the last app you installed prior to this issue appearing. This is usually related to a bad app. If that doesn't work, try running a malware or virus scan to see if what is messing around with things on your phone..