Hello all,
It appears my NFC sensor has quit working on my T-Mobile Galaxy S5. To provide some back story in hopes of finding a solution, here's what's going on:
A few days back, everything was running fine. I flashed an unofficial CM12 ROM (Albinoman887's) to my phone, which at the time had broken hotspot and no Netflix support. NFC worked for me at that point, as I used it to 'Tap n Go' when setting up my account to transfer everything to my S5 from my N7.
The next build that was released fixed Netflix for me, but since then I haven't been able to get any functionality out of NFC. According to the ROM developer, NFC works on his device, as it also does for several other T-Mobile S5 owners. I definitely believe that it works for them, but it's super frustrating to me that it won't for me -- even though I rarely use NFC. I'm just irritated at the thought that my sensor may have died and I have no idea why/how. The phone has never been dropped, so it shouldn't be shock damage.
It's also worth noting that I Odin'd back to my stock firmware, just to test NFC, and I couldn't get any NFC functions to work once I started fresh.
I'm not sure what my options are at this point, but I was hoping someone might have some input to help steer me in the right direction.
Quick update: I flashed a CM 11 ROM (Bliss Stalk, to be exact), and my NFC sensors now work like normal. I'm glad to see it's not dead, but I'm completely baffled as to why it doesn't work on CM 12, when the ROM developer is running the same device and it works for him.
Ahh, the perils of Android development. I'm still glad Lollipop is coming along so smoothly, and I apologize to @albinoman887 for being such a pain in his butt!
Related
I cannot turn on my N7's NFC anymore. Whenever I try to turn it on, the option will just remain grayed out. I even tried quicksetting toggles to no avail.
I have tried different kernels, rom, and even flashed the Google stock image but it is still grayed out no matter what I do.
When my N7 was still new, I would always turn it off since I don't have other NFC devices and tags. Eventually I forgot about it and didn't bother with it whenever I flash a new rom.
However, there was a point when I flashed buttered AOKP rom and I noticed that NFC is taking a huge amount of battery in the battery report in settings. This is when I discovered that my NFC is not working anymore.
Interestingly, whenever I am on buttered AOKP, battery report would show that NFC is taking a huge amount of battery. I even notice the draining even when my device is idle. This does not happen to any other ROMs that I have tried. However, I am not implying that buttered AOKP caused this problem on my device, especially since there are no other users who have experienced this issue.
It is really a shame since I recently got a N4 and I can finally make use of NFC android beam. Do you have any other ideas or suggestions for this issue? Do you think that this is hardware related already? It would be great if there is a way to conclusively test that this is a hardware issue since it is really bothering me.
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
Heya,
So i experienced a lot of problems with the stock ROM on my S4 taking up way too much space and being kinda slow and crappy, so after hearing of CM and the speed increases and benefits it can have, i decided i'd give it a go, and for about a year now its been my daily driver.
However it has some issues, which are recently becoming more of a problem to me.
Now the first one might have seemed like a deal breaker to anyone else but honestly i wasnt too frustrated with it.
This issue is that the 3g connection with the device when im out and about straight up doesnt work. It shows red in the pull down menu and just doesnt work.
Next issue is that the camera has been severely downgraded in image quality.
Now recently i've been requiring the phone more than usual when out and about doing my job as tech support.
My issue is that i want these features to work correctly, but i dont want to run the stock ROM, can anyone advise how i can either fix these issue with CM or can you help me choose a different ROM which doesnt have these particular problems?
Run one of the Google Play Edition ROMs. Fewer problems will be had as these ROMs are versions of Android untouched by Samsung except for the inclusion of the libs needed to properly run the phone.
Another alternative is to go back to stock, but with the addition of some time spent in debloating the ROM, and with the addition of a new launcher to replace the stock version.
Excellent, thanks for the advice, i've now installed JFLTE after a bit of research and it's so far a very pleasant experience, ill report back if i have further problems with the mobile data connection but so far it appears to work.
Hello, I have a OnePlus Two running the latest CM 14.1 nightly. My fingerprint sensor will not work. It stopped working a week ago, at which point I was still running Oxygen OS, whatever the latest update for it had been. my sensor became buggy, not responding, then quit altogether. I have to use onscreen buttons. I still had fingerprint options at that point in my system settings, but I couldn't do anything with them because they were grayed out. I ended up switching to CM 14.1 hoping a new ROM would help it to work, but now my fingerprint sensor is still non-functional.
At this point, I do not even have fingerprint settings in my settings. I can not locate the com.fingerprint.... process that is supposed to be running, so at this point i feel like the sensor might work, but the process is gone or does not exist. When I dial *#808# it does not recognize that dial code and gives me no feedback, which reinforces my thought that the fingerprint service just does not exist.
user: johnthepig, at the end of this forum (http://forum.xda-developers.com/oneplus-2/help/home-button-tried-fixes-t3366992/page2) said back in may that after Oxygen 3.0.1, the fingerprint sensor would not work in anything else. that he tried going to CM and it wouldn't work and then he went back to Oxygen and it worked, and back to CM again and it wouldn't work. My experience was that it just stopped working in Oxygen. Is there a way to manually give my phone the proper com.fingerprint service/process to run?
jcgordon10 said:
Hello, I have a OnePlus Two running the latest CM 14.1 nightly. My fingerprint sensor will not work. It stopped working a week ago, at which point I was still running Oxygen OS, whatever the latest update for it had been. my sensor became buggy, not responding, then quit altogether. I have to use onscreen buttons. I still had fingerprint options at that point in my system settings, but I couldn't do anything with them because they were grayed out. I ended up switching to CM 14.1 hoping a new ROM would help it to work, but now my fingerprint sensor is still non-functional.
At this point, I do not even have fingerprint settings in my settings. I can not locate the com.fingerprint.... process that is supposed to be running, so at this point i feel like the sensor might work, but the process is gone or does not exist. When I dial *#808# it does not recognize that dial code and gives me no feedback, which reinforces my thought that the fingerprint service just does not exist.
user: johnthepig, at the end of this forum (http://forum.xda-developers.com/oneplus-2/help/home-button-tried-fixes-t3366992/page2) said back in may that after Oxygen 3.0.1, the fingerprint sensor would not work in anything else. that he tried going to CM and it wouldn't work and then he went back to Oxygen and it worked, and back to CM again and it wouldn't work. My experience was that it just stopped working in Oxygen. Is there a way to manually give my phone the proper com.fingerprint service/process to run?
Click to expand...
Click to collapse
This is BY FAR the best description and observation of the issue. Did you find any information on that service missing from the apps menu?
Roadsalt said:
This is BY FAR the best description and observation of the issue. Did you find any information on that service missing from the apps menu?
Click to expand...
Click to collapse
No, unfortunately I never found a resolution to the issue. I'm still using my OnePlus Two and just operating it with the on screen buttons. At this point I'm just used to it and don't think about it anymore. It was very annoying originally. I'm still not sure if it's just the missing process, or whether it's a hardware issue and because the hardware isn't there, it doesn't obtain the process or what. Idk honestly. I resigned myself to on screen buttons till I upgrade in another year or so.
I'm gonna go back to stock because it seems lineage is not going to get screen cast feature in my nexus 9 flounder. Already tried editing build.prop file... didn't work.
It's sad 'cause it's a really fast and well made rom, but it misses a critical feature for me.
Thanks for the great work!
I was having cast troubles with my Nexus 9 as well, but managed to resolve it. Here's what I did:
1) Dirty flash stock Gapps (I was on tiny).
2) Update my device to the latest LineageOS release.
3) Reset the Chromecast's WIFI setting.
After that full system casting started working again, though I did notice something weird - the system gets frozen for a few seconds after disconnecting, however it does come back and should I want to cast again - it still works.
Hope this helps anyone who comes across this thread.