[Q] NFC doesn't work on Oreo 8.1 - Essential Phone Questions & Answers

The NFC function lost after upgrating to Stock Oreo 8.1.0, while it works well on 7.1 all the time.
I confirm that I turned on the NFC botton in the settings menue, but the NFC didn't work.
I have unlocked the critical partitions before flashing, also tried OTA, but the NFC doesn't work at ANY TIME.
Anyone can help me? Thanks so much...

It works fine on 8.1 for me but I never unlocked anything. Normally the best thing to do would be to factory reset your phone and choose the start fresh option in the setup menu instead of restoring from a Google backup. Problems after a big update like Nougat to Oreo aren't uncommon and are nearly always fixable by doing a factory reset correctly (fresh start). But since you modded your phone something else might be going on.

symtb said:
The NFC function lost after upgrating to Stock Oreo 8.1.0, while it works well on 7.1 all the time.
I confirm that I turned on the NFC botton in the settings menue, but the NFC didn't work.
I have unlocked the critical partitions before flashing, also tried OTA, but the NFC doesn't work at ANY TIME.
Anyone can help me? Thanks so much...
Click to expand...
Click to collapse
Works fine for me.
I am rooted 8.1, Magisk, ElementalX.

I don't have any issues with it and I'm stock 8.1 unrooted.

I have tried third party Oreo 8.1, the NFC works fine.
Only failed on Stock Oreo 8.1.
I tried another time to do a new flashing with Back_to_Stock package 8.1, when flashing system_a.img and system_b.img, it showed a message " Invalid sparse file format at header magic", and after that, it began to flash the system image normally. But as usual, the NFC didn't work.
-----------
Anything related to the mistake? Thanks.

Deleted

i've got the same issue. nfc doesn't recognize any card or device whilst it is activated in settings and nfc test app says anything is fine.
i'm using android pie but it was the same on oreo. my bootloader is fully unlocked. i always update via back-to-stock and fastboot.

M!tch said:
i've got the same issue. nfc doesn't recognize any card or device whilst it is activated in settings and nfc test app says anything is fine.
i'm using android pie but it was the same on oreo. my bootloader is fully unlocked. i always update via back-to-stock and fastboot.
Click to expand...
Click to collapse
I am running stock 8.1 and NFC didn't seem to work for me either until I touched a tag to the lower portion of the back and it fired. I was used to the sensor in previous phones being in the middle or toward the top. It would not work until it was in the lower 20% of the back side.
Don't know if it will be the same for you, but here's hoping.

yes, it was the same for me. i realized it just a few minutes after my post but didn't find it then. so i couldn't delete it.

I've been fighting to get mine to work, so far nothing. I contacted Essential tech support and they had me clear the cache and showed where the NFC sensor is (bottom part of the phone on the back). I tried using Android Beam to send/receive URL's with my old phone (confirmed that it can send/receive through Android Beam). Nothing is working. Debating whether or not to return the phone and get something else. Any help would be appreciated.
Here's what tech support sent me:
As a verification step, confirm that you're using the correct area of the phone for NFC. Unlike most smartphones, the Essential Phone's NFC chip is located on the bottom of the device.
If you are aware of the NFC position, to isolate the issue further and determine the best way to resolve this, I'd like you to try a few steps.
Ensure that NFC is enabled in settings. (Settings > Connected Devices > Connected Preferences > NFC)
Ensure that Google Pay is the default Tap & pay sevice (Settings > Apps & notifications > Advanced > Default apps > Tap & pay > Payment default > select the desired payment app)
Clear the cache in the NFC Service and reboot the device. (Settings > Apps & Notifications > See all apps > Three dots in the top right > Show System > NFC Service > Storage > Clear Cache)
Attempt to use the NFC service with another app or service like Android Beam (Settings > Connected Devices > Android Beam)

Chiming into this thread - NFC doesn't even show up for me in Connected Devices, on Android 9.

Look under connection preferences in connected devices

kboya said:
Look under connection preferences in connected devices
Click to expand...
Click to collapse
I don't have NFC or android beam in my preferences window.

Ok, what do you have?
Edit: just noticed it's you in two threads

Finally got mine resolved. Received a new phone under warranty yesterday. Confirmed that NFC works.

Related

[Q] S4 i9505 CM10.1 - wifi won't turn on, has no MAC

Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
TrallaP said:
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
Click to expand...
Click to collapse
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
sylvisj said:
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
Click to expand...
Click to collapse
Here's the 'ls -a' output for /data:
Code:
[email protected]:/data # ls -a
.container_1
.container_2
.container_3
.layout_version
.mtp_stream
.npswifi_stream
.pcsync_stream
.psm.info
.socket_stream
.ssh
anr
app
app-asec
app-lib
app-private
audio
backup
bcmnfc
bluetooth
cam_socket0
cam_socket1
container
dalvik-cache
data
dontpanic
drm
fota
hostapd
local
log
lost+found
media
misc
nfc
property
qcks
radio
resource-cache
security
shared
ssh
system
time
tombstones
user
wiper
wpstiles
Bump.
I have the same problem......
ninne1 said:
I have the same problem......
Click to expand...
Click to collapse
Bump again.
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
r47z said:
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
Click to expand...
Click to collapse
I dunno about EFS, but I know the IMEI is already correct - *#06* is showing the same IMEI as the label on the back of my phone.
My phone is work well after flashing CM, but no WIFI.
No /data/.cid.info file!
*#06# - show IMEI.
Did we ever get to the bottom of this?
Im having exactly the same problem, so bump. Its been like that for 6 months, my workaround so far was getting a bigger data subscribtion since 4g is working fine
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Hi sylvis,
I realize that this is an old post. However. perhaps this thread will help someone else:
I flashed a Samsung Galaxy S4 (T-mobile SGH-M919) to CyanogenMod (CM11) this weekend. It worked ok for a couple days. The owner then said that they can't get any WI-FI. I found your post here and read with optimism that I might be able to fix this problem. Our problem was exactly "word for word" the same problem as you described in your original post. (Well almost exactly; we couldn't get "USA" to stick as the region code)
Before flashing the phone, I did install Philz ClockworkMod and did do a backup of the OEM ROM before flashing to CM11. That said, I found that I did not have to go down the road of restoring a missing IMEI file (as other threaders here describe). Here's what worked for me:
I dialed *#06# on the phone to see if there was an IMEI number present, and there was. I wrote down that number. So I decide to see if that number matched the printed number on the phone, that we can find under the battery.
Before I do a power off of the phone, I recall that I had turned OFF both Bluetooth and Mobile Networks. WI-FI was still turned ON, but in it's non-functional "greyed out" state like you and I both experienced.
Now I power off the phone, take off the back cover, and take out the battery to have a look at the printed IMEI number. Yes, it does march the number that I saw via *#06#.
I had to get up to do something, then returned a couple minutes later. I popped in the battery and restarted the phone. To my utter surprise, WI-FI was back up! In "Advanced" I now see the MAC address and the region is locked on USA
I turn on Mobile Networks, and WI-FI's still working. Being the fool that I am, I have to test this further. So I power off the phone again and just let it sit there for a couple minutes. I power back on and there is still JOY. Problem resolved and happy customer.
In closing: I don't think that the removal and reinsertion of the battery was the total solution, because the owner had already tried that. However, the owner did not let the phone sit with the battery removed for very long. They just popped it out, waited a couple seconds, then popped it back in. I think the total solution was having WI-FI enabled, Bluetooth and Mobile disabled, then doing a power off, with an extended wait time before reinserting the battery.
Hope that helps.
Regards,
Brcobrem

[Q] Where are the NFC Advanced Settings Galaxy S5 Lollipop?

I have a NFC door lock , I need to change the NFC Processing Method but I do not have advanced settings in the menu. Even though when I click help on the device itself and select tap and pay it says for the help category it says:
To change your default processing method, go to setings > NFC > Advanced Settings.
Which NFC isn't even it's own menu off settings. I have been in developers setting and other went through the other settings and I am not finding it.
Anyone have any idea where it is? The lock developers says I have to change it from sim card to the android operation system in the settings.
This is what they gave me but it doesn't match up on the Verizon edition.
•Samsung S5 - Settings > Connections > NFC > Advanced settings (top right button) > Change NFC Processing Method == SE SIM Card // Android operating system. Change to Android operating system
Thanks
Mine has the advanced settings with SE SIM card & Android operating system options enabled by default... Not sure but try to clear the app data of your settings from Application manager. If it's still not there try maybe flashing another ROM(official or custom).
I tried clearing the app data and still nothing. I have the latest update from Verizon on the phone, so I don't run a custom rom.
Probably verizon had it disabled on their ROMs? I know most carriers are known for disabling specific phone features.

No NFC after update

Hello Community!
Yesterday I received my Elephone P9000. What a nice phone. The first thing I did was installing the new update (20160419) and rooting it afterwards (TWRP 3.0.2.1 and Updated SuperSU).
Everything works and runs smoothly except for one thing: NFC.
It isn't in my settings anymore (Settings -> More -> no NFC?!). But I remember that there was NFC in the settings when I started the phone the first time.
If I share some content via Android Beam (for exanple a picture --> share --> Android Beam) I can enable NFC (via the prompt) but then I can't disable it normally. I would have to go to the Nfc Service.apk and force stop it.
Has anyone encountered the same problem?
Should I reset my phone?
Kooperativ said:
Hello Community!
Yesterday I received my Elephone P9000. What a nice phone. The first thing I did was installing the new update (20160419) and rooting it afterwards (TWRP 3.0.2.1 and Updated SuperSU).
Everything works and runs smoothly except for one thing: NFC.
It isn't in my settings anymore (Settings -> More -> no NFC?!). But I remember that there was NFC in the settings when I started the phone the first time.
If I share some content via Android Beam (for exanple a picture --> share --> Android Beam) I can enable NFC (via the prompt) but then I can't disable it normally. I would have to go to the Nfc Service.apk and force stop it.
Has anyone encountered the same problem?
Should I reset my phone?
Click to expand...
Click to collapse
Wrong thread, mate! This one's for the P7000.

App changer, home button, quick settings, lock screen and much more doesn't work

I can't open the quick settings menu from the notification center and can't really do much. Only interact with already installed apps. I can't hange the user, I can't enable developer options I can't save the files via USB and neither does adb work.
I never worked with a Motorola, do you have any idea what I could try?
___​
Android 6.0.1 // Build MPDS24.107-52-5
System version 24.201.5.lux_reteu.reteu.en.EU.reteu
(not rooted)
Polyparadox said:
I can't open the quick settings menu from the notification center and can't really do much. Only interact with already installed apps. I can't hange the user, I can't enable developer options I can't save the files via USB and neither does adb work.
I never worked with a Motorola, do you have any idea what I could try?
___​
Android 6.0.1 // Build MPDS24.107-52-5
System version 24.201.5.lux_reteu.reteu.en.EU.reteu
(not rooted)
Click to expand...
Click to collapse
If it happened all of a sudden after OTA update, check out this answer:
https://forum.xda-developers.com/showpost.php?p=70320663&postcount=2

Moto X Play Frozen Software Keys and other errors

Hi All,
I'm currently experiencing the following issues with my Moto X Play :-
- Home & Multitasking buttons not working
- SD Card reader not working
- Apps cannot be installed(even though there is plenty of disk space)
- Quick settings drop down menu is not pulling down
- cannot receive phone calls but Internet(whatsapp) calls work
- cannot switch to front facing camera view
- Developer options are enabled but cannot access developer options menu. error message:"Developer options are not available for this user".
- google accounts only contain sync's for chrome, google play music and inbox - even though other apps are installed.
I've tried the following solutions without any luck:
- hard reset - when trying to access recovery the screen get's stuck on a dead android image and the volume/power buttons are useless.
- factory reset - factory reset protection (FRP) is in place.(tried all the hacks but no luck there)
- flash factory image - when trying to unlock bootloader i get the following error message:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
I obviously cannot 'Allow OEM Unlock' as developer options is not working.
Only bonus is that I can install apks - so any solutions via that route may work.
My Device Details are:
Moto X play (XT1562)
Android 6.0.1
Build Number: MPDS24.107-52-11
Security Patch Level: 1st Jan 2017
Thanks in advanced.
Have you actually succeeded to do factory reset? Did you go through all the initial Setup after that (setting language, wifi details, signing up to google, etc)? It looks weird but maybe for some reason you can't get out of setup mode, so install Activity Launcher, find Setup Wizard on the list of all activities and launch com.google.android.setupwizard.SetupExitActivity.
Thank you very much! That worked like a charm.
I was ready to open her up and perform an operation but can't believe it was something as simple as that. Do you think it got like this during an update?
BTW - Factory reset did not actually work for me.
Kofi o said:
Thank you very much! That worked like a charm.
I was ready to open her up and perform an operation but can't believe it was something as simple as that. Do you think it got like this during an update?
BTW - Factory reset did not actually work for me.
Click to expand...
Click to collapse
I'm glad it worked. It just happens randomly on some devices (not only Moto) for some mysterious reason - maybe it's update related, but I'm not 100% sure.

Categories

Resources