yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] Maik93:
ooook guys, Chainfire has published last version of CF-Auto-Root (I'm a new user, I can't post the link)

I think there's no more nothing to say! It worked!!
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] midskool:
Can you guys access the hidden menu by dialing "*#*#4636#*#*" ?

I want to access this to fix my sms service centre number?

Or do you guys know of any app that can edit the sms service centre number?

P.S: I'm rooted.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] :
Add this to the end of your build.prop and reboot. You should be set after that.

#Hidden Menu

sys.hiddenmenu.enable=1
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] midskool:
Which File Browser or app would you recommend to edit that file?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] :
I prefer FX File Explorer with the root add-on.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] midskool:
It shows this error when saving the build.prop.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] :
You need to press the lock icon at the top when you are in the system folder to unlock the files to edit.

View attachment 3015560
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] midskool:
Thanks for the guidance. I did save and restart. But still it won't let me dial *#*#4636#*#*.

I have found a fix around. I have installed an app named "Shortcut Master" to launch the hidden menu of *#*#4636#*#* .
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] :
You probably have to edit the file in /efs/carrier/HiddenMenu from OFF to ON. This is on by default on the VZW S5 but might not be on yours.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] midskool:
Hidden Menu was set to off in efs/carrier by default.

I turned it ON and restart.

Now some of the codes are working like *#0*# or *#06# but still *#*#4636#*#* not working directly from dialing app. :-/
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] wareju:
Did you ever figure out a way to change smsc? I'm currently having this problem on rooted 5.0
[Nexus 5 Q&A, Help & Troubleshooting] dmtcher:
Need help. I have troubles with light sensor and proximity sensor after update to lollipop. After updating in fastboot mode (without any errors) these sensors don't work until I restart my nexus. After restarting sensors are working just a few minutes (5-10) and all repeats...

I tryed to downgrde android to 4.4.2, 4.4.3, 4.4.4 - in all of them sensors are working.

Please tell me what can i do to solve this problem!
[Nexus 5 Q&A, Help & Troubleshooting] gaz_1:
Same problem!!

I too have this same problem after the update!
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
same here

same here !!!

if i restart the phone its work for few mintues
[Nexus 5 Q&A, Help & Troubleshooting] Jnewell05:
Weird because I don't have this issue. However I had to perform a factory data reset through stock recovery because my internal storage was reading 16gb not 32gb. I mention this because maybe that'll help u. Plus I'm completely stock so far.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
Have the same issue. Its so annoying. My brother and i did the updates on 2 phones. Mine has the issue, his is working fine. Any solution
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
I'm having the same issue, I pushed the OTA update via ADB first and has this issue. Then i tried A factory reset and still had it. Then I tried flashing the factory image using fastboot and I'm still having this problem. Everything else seems to be working great.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
Do you guys think its an app related issue?
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
I don't think so, i booted into safe mode and still had this problem, unless the issue is being caused by a native app.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
Yeh tried that too. Same thing. How come my brothers phone is fine tho
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
I don't know man, hopefully someone with a bit more knowledge will be able to help us out, glad I'm not alone though lol.
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
I fixed mine! I just needed to re-install my factory image manually. Follow the directions in this thread and use method 2.

http://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
I thought I do that on my phone too with no success. I used the nexus toolkit tho. Does it make a difference
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
*EDIT*

Never mind, it's still broke, I let the phone sit for about an hour and when I came back the sensor wasn't responding again.. I give up.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
is it working still. i just got home, about to attempt it

---------- Post added at 07:43 PM ---------- Previous post was at 07:06 PM ----------

what if it is an application that is causing this?
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
No sorry, it took about an hour but the problem came back. I didn't have any apps downloaded yet and it still happened. I would try though, can't really hurt anything. Maybe it will work for you. I'm just tired of rebuilding my whole phone every time, I'm going to ride it out maybe someone will figure something out.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
Can you guys try disabling google play services. I have it disabled for 30 min now and looks like its kk
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
Is yours still working? I just tried this and besides making the phone generally unusable it did nothing, sensors still didn't work. I think I may flash back to 4.4.4, I'm really tired of all this tinkering just to get things working correctly.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
Nope. Didn't work. Is your phone a replacement phone by any chance? I called google they acknowledged a firmware bug. They will get back to me soon
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
No, mine is a launch device. Did they tell you any specifics?
[Nexus 5 Q&A, Help & Troubleshooting] donwhall70:
Sensors work fine for me.
[Nexus 5 Q&A, Help & Troubleshooting] zzzaaakk:
same here not working after update...
[Nexus 5 Q&A, Help & Troubleshooting] embhorn:
The proximity sensor was not working on my N5 after flashing 5.0.

I basically couldn't use the phone because my face was hitting buttons constantly. But a restart has gotten it working for the past 8 hrs. Hopefully it will keep working.

Update:

Still not working right.
[Nexus 5 Q&A, Help & Troubleshooting] cisco2900:
not working for me.

Mine is not working. I have been rebooting the phone every time the sensors fail. Let see if Google come up with the solution quickly.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
I tried it. No luck. Google is sending me the replacement tomorrow. All my friends with the nexus 5 updated with no issues
[Nexus 5 Q&A, Help & Troubleshooting] pha9992001:
my proximity sensor broke, too

After the 5.0 OTA update, proximity sensor stopped working. Reboot fixes it for a bit, but after some time it stops working again and I have to reboot again.
[Nexus 5 Q&A, Help & Troubleshooting] cisco2900:
I reboted mine in Safe Mode and I used it for 8 Hrs in Safe Mode. I restarted back into normal mode and it last for 18 Hrs and stopped working again. This really sucks big time. No word from Google still. I think I'm going back to 4.4.4.:mad:
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
Glad I'm not alone

I have the same problem, and for a while it felt like I'm the only one. Here is what I tried without success:

Factory Reset, no success.

I flashed factory image with the flash-all script as mentioned on Google's Factory image page, no success.

I flashed the factory image manually via fastboot, no success.

I flashed 4.4.4 factory image, used it for a day to confirm that the sensors are in fact working as they should then upgraded to 5.0 via OTA and now the problem is back again.

I had the problem with the Developer preview as well, but I thought that was because it was a preview and not an official release.
[Nexus 5 Q&A, Help & Troubleshooting] cisco2900:
Good news

Guys good news. I found the fixed for this issue. I turned off Developer Options and the problem is gone. My phone is been working fine for more than a day without restarted. I hope it works for you too.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
I just tried turning developer option off. Didn't work form me. Is it just simply turning it off?
[Nexus 5 Q&A, Help & Troubleshooting] cisco2900:
Restart your phone after turning Developer options off.
[Nexus 5 Q&A, Help & Troubleshooting] procitysam:
I'm having the same issue here. I'm using the N5X 5.5 LRX21V ROM right now, and sensors will just randomly stop working. Soft rebooting doesn't work. In SensorBox, if you soft reboot when they aren't working and go back into SensorBox after rebooting, it will say that the light sensor or proximity sensor is not supported. A hard reboot will fix that, but then the sensors only work for a short period of time.
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
I still have the same problem, even after restarting
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
i think i fixed mine...

i flashed code blue kernel and now its fine.

hope it can help :D
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
What is everyone's hardware variant? Mine is D820(H) and i'm having this issue and my girlfriend's is D820(E) and her's is operating just fine. A few other people's are the same way and I'm noticing this pattern.
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
I have the D821(E) and I have the same problem.

I tried the Code-Blue kernel and the problem persists.
[Nexus 5 Q&A, Help & Troubleshooting] SlickNolte:
Hmm, I chatted with google support last night and let them know about the bug. I suggest we all do that just to get the word out.
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
i used wug's toolkit to flash stock kernel then flash code blue.

my sensors are still working...
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
I also used Wug's toolkit. Did you flash the zip directly from the toolkit or did you boot into custom recovery temporarily via the toolkit and flashed it from there? I flashed the zip directly from the toolkit, then after establishing that it does not work I flashed the stock kernel again. I now tried booting into TWRP temporarily via the toolkit and flashing Code_Blue from there. I don't think the method of flashing the kernel makes a difference, but it's worth a try. I will let you know if it worked this time round.

I flashed r646 of the kernel, which release did you flash?

UPDATE:

Sensors stopped working again, this time it took about 25 mins instead of 5 for it to stop working but the problem is still there. Flashing stock kernel again now.
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
well after 12 hours its stooped working again...will have to wait for google fix i guess :(
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
I already spoke to google. They sent me a replacement. I will get it later on today. I will keep you posted
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
I'm thinking of flashing a LRX21V based custom rom to see if that might fix it.
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
could be...let us know
[Nexus 5 Q&A, Help & Troubleshooting] cisco2900:
I agree. I did that too.
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
Flashed Vanilla AOSP LRX21V. The problem is still there. I am almost considering running 4.4.4 until the problem is solved, if only I didn't like Lollipop so much.
[Nexus 5 Q&A, Help & Troubleshooting] benjamin831:
Thank god I found this thread, thought it was just me lol. Anyways, yes, same problem after updating Lollipop.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
I have problem with light sensor. It stops working after sometime. Haven't been using the phone as I'm out of the country.

Will try and see if disabling developer option fixes the issue or not.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
Disabling developer option, reboot doesn't fix it.

Flashing a new kernel (basically hard boot) fixes it for some time and then the problem again appears.

It is driving me nuts. Thinking of downgrading back to omni kitkat as it gave better battery life and there are no such problems.
[Nexus 5 Q&A, Help & Troubleshooting] lion7718:
It's not just a Nexus 5 issue, I flashed my Nexus 4 2 days ago & have the same problem.
[Nexus 5 Q&A, Help & Troubleshooting] haroyac:
My issue was resolved with the replacement phone that google sent me
[Nexus 5 Q&A, Help & Troubleshooting] froggy2288:
I have same issue and after talking with Google support today I will be receiving a new device in the mail soon. They asked me if I had done a factory data reset and tested safe mode otherwise they had no other advice at this time.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
It's problem with lollipop. I went back to KitKat and it works fine. Replacing the phone is no option if it's not hardware but software issue
[Nexus 5 Q&A, Help & Troubleshooting] matolch:
Is there an app that can simulate proximity sensor via front cam or smth while we are waiting for fix from Google? Experienced the same shi* on brand new 32G D821 from Hong Kong.
[Nexus 5 Q&A, Help & Troubleshooting] lihuedon:
Internal dirt was blocking proximity sensor

I fought this issue on my Nexus 4. Bare phone, no screen guard and when there was an active call, the screen would go black. Long story short, I took the phone apart, removed the proximity/light sensor unit and carefully blew out the dust and grit with shop air. Voila! Good as new. There is a video out there showing the steps... Time to get a good phone cover! :p
[Nexus 5 Q&A, Help & Troubleshooting] lihuedon:
I too suspected the Lollipop upgrade because it was about then that problem cropped up, but as I said in #53 above it was dust in the machine. Maybe Lollipop software is more sensitive? Just speculation...
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
I very much doubt that's the case... That would mean that after every restart it works fine (like it did in KitKat), then after a few minutes the software suddenly becomes more sensitive. And my phone is also less than 2 months old, so I doubt dust will be the culprit in my case. Glad it worked for you, but I suspect this is a different scenario all together.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
Please add your comments to this bug report It would be better to discuss here and report there too so that android devs/google is aware about this.
[Nexus 5 Q&A, Help & Troubleshooting] lihuedon:
For the record, I bought my N4 in September. So dust infiltration is a definite hardware design problem.
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
That is fair enough, but if it was purely a hardware problem then it would not even work for a few minutes. If it was a sensor sensitivity problem then it would not work for a little while and then stop completely, it would rather constantly be unreliable instead of stopping completely.
[Nexus 5 Q&A, Help & Troubleshooting] matolch:
Any news here anyone? My main concern here is that not so much people facing this issue, could it be possible that Google will not fix it in nearest weeks?
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
Report it and vote for the bug I have posted earlier. More people vote, chances of google looking into it becomes higher.
[Nexus 5 Q&A, Help & Troubleshooting] benjamin831:
Definitly not a hardware issue. It works in Kitkat but stops working right after upgrading to Lollipop. Also, it works after restart every time but then stops working after 30 mins or so.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
Hopefully 5.0.1 merges to the AOSP fixes the issues. Awaiting a ROM with 5.0.1 to confirm.
[Nexus 5 Q&A, Help & Troubleshooting] matolch:
https://code.google.com/p/android/issues/detail?id=80149

That's soooo ridiculous... No reaction from Google guys, and this bug still in priority Small :rolleyes:
[Nexus 5 Q&A, Help & Troubleshooting] embhorn:
I just got my out-of-warranty replacement phone from Google Support. While I agree this is a software issue, it must only be affecting a subset of hardware, otherwise I assume this would be a much bigger problem for N5 users.

I couldn't use my phone ~as a phone~, so that was pretty much a deal breaker worthy of contacting support. I've only had the new phone a few hours, so I'm not yet sure if the "new" one has the proximity sensor issue.
[Nexus 5 Q&A, Help & Troubleshooting] shri_chanakya:
My sister has Nexus 5 bought in India and she doesn't have this problem. While I have two Nexus 5 both bought from USA and they exhibit same behaviour, broken sensors with update.

---------- Post added at 11:56 PM ---------- Previous post was at 11:54 PM ----------

Seems like google has reached out to user for this bug report. Please vote in this bug if you are facing it. Will help getting more traction on the issue.
[Nexus 5 Q&A, Help & Troubleshooting] m4nic4ndroid:
No fix on 5.0.1

I flashed 5.0.1 via the factory image and it did not take long for the problem to reappear.
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
update to 5.0.1 didn't help me too

same here...i miss my sensors :crying:
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
Anyone with this issue and root access, have you tried this by any chance?

http://xdaforums.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915

Also if you have a barometer app, or something similar it may be disabling the sensors such as happened here.

http://xdaforums.com/google-nexus-5/help/nexus-5-sensors-stop-random-output-t2513100
[Nexus 5 Q&A, Help & Troubleshooting] LostHawkGSW:
definitely having same issues;

phone is unresponsive after some time (can see it is still on by blinking led notification) -- need to force restart

phone restarts occasionally on its own as well when it becomes unresponsive.

trying to figure out how to disable the sensors completely

Android 5.0.1
[Nexus 5 Q&A, Help & Troubleshooting] SebLemery:
I have the same issue with my Nexus 4 on SimpleAOSP. Tried Tasker, tried a few things. No success. I will post the solution here when i find it.

Edit: I FOUND A SOLUTION! And it worked.

Open your phone, disconnect the battery (no need to remove it)

Remove the motherboard completely. (Be really careful)

Then, you see on the right where the 3.5mm audio jack is? Just put something in the jack, and pull it off (its sticked in place) You will see [IMG="Proximity Sensor+audio jack"]http://puu.sh/dWhuD/59955afdcd.jpg[/IMG] Just rotate the rubber on the proximity sensor halfway.

So the small hole with the big one, and the big one with the small one. (when you have it in your hands you will understand)

Rebuild your phone, reboot, enjoy :)

(I think it has something to do with sensitivity) I was running Sensor Box and i could see that the sensor was not responding at all. I did the fix, and now it does!

If you have any questions, reply to this post ;) (I MIGHT make a video out of it if i see too many people with similar questions)

Happy hacking.
[Nexus 5 Q&A, Help & Troubleshooting] leomacmac:
a how to video would be great! is this the only fix out there?

Thanks for the tip, a video would be really helpful! I cant beleive thry have such a big QC priblem here... Is this covered under warranty?
[Nexus 5 Q&A, Help & Troubleshooting] slipperpro:
I have this sensor problem on my n5. Proximity not working, so when making call the screen wont' turn off

Tried lollipop stock rom, n5x rom, terminus rom with n5x kernel and code blue kernel, no fix

But i have found solution to it, now is pass 24 hours since i last time reboot, proximity still works well

Simple solution : always turn on automatic brightness, this works for me at least at till now 28 hours after reboot
[Nexus 5 Q&A, Help & Troubleshooting] kiricheikoa:
Had a problem, when Proximity sensor almost always was stuck in "near" state. This means that screen was turning off during the calls. I was able to fix the issue using suggested solution:

This method requires root privileges!

From root explorer or similar program delete these folders and file

/data/system/sensors

/data/misc/sensors

/persist/sensors/sns.reg

Restart phone
[Nexus 5 Q&A, Help & Troubleshooting] Indypop:
Hi guys.

This problem is really annoying. And we have no feedback from google yet on the issue 80149.

Do you guys get any luck with the solution?
[Nexus 5 Q&A, Help & Troubleshooting] skullo:
tried this, and it really works. Thanks!
[Nexus 5 Q&A, Help & Troubleshooting] Indypop:
Possible solution

After turning off the location (via notification center, dunno if it is important) and waiting for some time (not immediately) the problem is gone and sensors are working well for two days.

Try this please.
[Nexus 5 Q&A, Help & Troubleshooting] gallok:
I'm root and I cannot find those folders
[Nexus 5 Q&A, Help & Troubleshooting] alonM1982:
5.1 helps

Few hours with Android 5.1 and everything is good

Hope it will hold....

UPDATE : no it does not...same problem after few hours :(
[Nexus 5 Q&A, Help & Troubleshooting] cangzhang:
try this.thank you!
[Nexus 5 Q&A, Help & Troubleshooting] ChromeJob:
I held off on updating my Nexus 4 to 5.0 (actually updated, then factory-flashed back down to 4.4.4 after experiencing Bluetooth and other issues), and recently updated to 5.1. Then noticed that auto-rotate wasn't working at all. Today I got a bit ticked off at it, and investigated ... Yelp Monocle mode wasn't working, rotate wasng working, and realized that in recent weeks, the screen was not coming back after holding the phone to my ear during a call. Maps directions has been a bit flakey, and I know realize that the compass is kaput. Auto-brightness is not working ...

Checking in Phone Tester, NONE of the sensors come up as supported! System Panel Pro also reports no sensors. Deleting /data/system/sensors/, data/misc/sensors/ and /persist/sensors/sns.reg and restarting does nothing.

Think I may have to re-flash back to 4.4.4 YET AGAIN. This is, well, if it's not a catastrphic failure of my sensors on the N4, this is pretty MESSED UP. Anyone else encountered a complete failure of sensors??
[Nexus 5 Q&A, Help & Troubleshooting] lion7718:
5.1 is working fine on my Nexus 4...no problems at all.
[Nexus 5 Q&A, Help & Troubleshooting] ChromeJob:
How did you update to 5.1, did you flash your /userdata partition as well as others? Looks like the sensors directories are under /data not /system.
[Nexus 5 Q&A, Help & Troubleshooting] Firescroll:
Fully working

Tried and worked!! A thousand thanks!!! :D :good:
[Nexus 5 Q&A, Help & Troubleshooting] nat510:
Tried and worked. Thanks

6.0.1 Nexus5
[Nexus 5 Q&A, Help & Troubleshooting] waro470:
Nexus 5 user, running Android 6.0.1. Those instructions have made my sensor work again. Thank you so much!!!

Shame on you Google, for leaving us on our own on this one!
[Nexus 5 Q&A, Help & Troubleshooting] rcitra77:
amazing, it works!!!

many thanks for the solution :)
[Nexus 5 Q&A, Help & Troubleshooting] Phoenix Fire:
Hi, i want to give my old nexus 5 to my mother to replace her windows phone that is near death. I changed the battery because the phone had some reboot problems and apparently it works like a charms, but I had the sensor problem during call that leave the screen black. I try deleting the three folder/file written above with no result. There is anything I can try?
[Nexus 5 Q&A, Help & Troubleshooting] srkisrk:
Omg i cant believe it finally something that worked. Thank you so much this sooo made my day. I tried almost everything watched many videos and nothing worked, i got so frustrated and even took off back cover to try to reach sensor and start picking with my screwdriver, and almost ruined my phone, and then i found link for this thread. Deleted all files and folders like you suggested rebooted phone and voila! No more blank screen for me during phone calls.:victory: