NEXUS 5 Proximity Sensor News [Massive Downgrade] - Nexus 5 Q&A, Help & Troubleshooting

Dear XDA friends,
I believe it's almost 6 months, since I start having problems with my Nexus 5 Proximity Sensor.
If you search for the WEB, you'll find tons of users like me, who which Google is simply ignoring.. A series of OTA updates, that fried up Proximity and Light Sensors firmware of hundreds of Nexus 5, among other Nexus phones.
Basically, this problem resumes to a constant 0.0mm value returned by the Proximity Sensor, which makes the phone believe that you ear is always close to the phone. I can belive you know how frustrating this is in daily use.
I believe this subject was already reported here, in XDA forum. However, allow me to report my story, that is almost unbelievable.
So, here's exactly what happened:
Bought the phone two and a half years ago with Android 4.4.4.
Android 4.4.4 - Sensors OK.
OTA 5.0 - Sensors OK.
OTA 5.1.1 - Sensors OK.
OTA 6.0 - Sensors OK.
OTA 6.0.1 - Proximity Sensor Faulty
ADB DOWNGRADE to 6.0 - Proximity Sensor Faulty
ADB DOWNGRADE to 5.0 - Proximity Sensor Faulty
ROOTED
CWM Flash to CM 14.1 - Proximity Sensor Faulty
CWM Flash to CM 14.0 - Proximity Sensor Faulty
CWM Flash to CM 13.0 - Proximity Sensor Faulty
CWM Flash to CM 12.1 - Proximity Sensor Faulty
CWM Flash to CM 11.0 - Proximity Sensor Faulty
There are hundreds of Nexus 5 users with the same problem, but I believe no one has tried a downgrade so agressive as I did.
Google has been ignoring this problem timer over time, as I'm starting to believe that they will never solve this.
This is my last call for help, before I move to a MOTO G or something like that...
Shame on you Google, shame on you Nexus team...
Thank you for your time!

Related

[Q] Missing sensors in Nexus 5 after install Android 5.0

Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
What app are you using? This looks like a bug in an app, than in Android itself.
I had this problem even before installed any apps. In android l developer preview I didn't have sensors also, so after installed final version of lollipop the first thing I made was check sensors. On kitkat everything worked perfect.
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
i don't have light and proximity sensors too...
i did full wipe and flash stock OTA
hope they will fix it soon
Since upgrading to Lollipop my proximity and light sensor also stops working after a few minutes. It works again after a restart, but only for a few minutes.
I have flashed 4.4.4 again and the problem is not present there. After upgrading to 5.0 again the problem came back.
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
gamer.11 said:
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
Click to expand...
Click to collapse
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
m4nic4ndroid said:
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
Click to expand...
Click to collapse
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I haven't tried any other Lollipop ROMs, I thought about it and I might actually give it a go to see if the problem persists on other ROMs as well, but I would prefer to have stock Android running on my phone, so I'm really hoping for a fix from Google. I'm on few other threads about the same issue, so I know there's a lot of people with the same problem. I had this on the dev preview as well.
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Light Sensor & Proximity Sensor Error
m4nic4ndroid said:
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Click to expand...
Click to collapse
The Same Problem For Me As Well, My Light Sensor & Proximity Sensor Arent Working. I have downloaded the Final Image from Google Website for 5.0 hammerhead. But still the problem persists.
Nyk
After I got the Play services (with secure locations) update two days ago my light and proximity sensors are gone too. They will work for a while after reboot, but eventually they die.
All other sensors are working fine and only other updates have been to Skype, SwiftKey and TuneIn Radio.
Edit: I'm on stock OTA, no root and never unlocked the bootloader.
Sent from my Nexus 5 using Tapatalk
So uninstalling the play services update resolve the issue? I'm back to KitKat as without light sensor I find uncomfortable to use the phone. Will await the fix before moving to lollipop..
Sent from my Nexus 5 using XDA Free mobile app
"Clean install" using factory images? I did, no issues here.
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Did you reboot after disabling update?
Sent from my Nexus 5 using XDA Free mobile app
rawimage said:
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Uninstalling Play Services and Play Store update made no difference here. Problem still persists.
michalnied said:
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
Click to expand...
Click to collapse
Hi I have the same problems . Sensors are working after restarting my phone random time. Also you can read here
Uninstalling Play services didn't do it for me either. Sensors work for approximately 4-5 hours then they die.
Sent from my Nexus 5 using Tapatalk
Installed Play services update again after a few days and now my phone has been running fine for 50 hours with all sensors working 100%.
Sent from my Nexus 5 using Tapatalk

[HELP] Light, heart rate, gyroscope sensors not working

Hello everyone,
I bought some days ago a second hand galaxy S6 (G920F), I checked if everything was working and then updated to official Marshmallow, installed TWRP 3.0, and finally moved to a custom ROM (Pure Stock ExtraLite Rom 4.1).
The problem is that I figured out I had a lot of sensors that were not working anymore like light sensor, gyroscope sensor (so also accelerometer etc...), the heart rate sensor seems only partially working, I didn't try the proximity sensor yet. Here is a screen of the sensor page after a *#0*#:
I already tried to clear cache, wipe everything with clean install, flash back official MM rom, tried to make a calibration using GPS status and toolbox (which shows there is a problem with almost every sensor), but absolutely nothing worked.
Right now I am out of clues and I need your help !
Thank you!
So were the sensors working when you got the device?
My S6 Edge had the same issue - all sensors would stop working (and the IR blaster) for a few days/weeks and then eventually they would work for a while again. In the end though, they stopped working completely. I also tried absolutely everything software related first but it turned out to be a fault with the mainboard. I sent it to Samsung who claimed it was caused by liquid damage and refused to repair it (I'm almost certain it wasn't liquid damage because I haven't got it wet) so ended up claiming on my insurance.
Sadly I didn't take the time to check the sensors before upgrading, so I have absolutely no idea about the sensors before I updated the system...
I saw some people talking about this kind of problems being liquid damage related, but I have no idea what happened to the phone before I got it...).
I hope I will be luckier than you were !
my sensors were working fine in 5.0 and then i officially upgrade my s6 to 6.0.1 and eventually all sensors died.
i make a factory reset and everything fine now

GPS broken on Honor 6-L04 since upgrade to MM

Hey everyone,
Since a couple of days (installing MM B803) GPS is no longer working on my phone. When I try various tools it shows that there is a GPS sensor present but it will not find ANY sattelites. Anyone else had this problem? Should I consider this related to MM or just plain bad luck my sensor is broken.

Huawei Watch 2 Sport - all sensors are dear after latest Wear OS update

Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
koladko said:
Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
Click to expand...
Click to collapse
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
rettinn said:
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
Click to expand...
Click to collapse
THanks... My watch is more than 1 year old, AFAIK warranty is over
Anyway - Thanks for advice!
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
dxtremez said:
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
Click to expand...
Click to collapse
Thank you for your advice . I did exactly what you have mentioned and now my smartwatch is working again .

Microphone and ambient light sensor issues, software or hardware?

Hi there!
First off: I used the search, but am not confident I haven't overlooked something.
If so I'm sorry!
I have a google pixel with lineage-for-microg, whose battery I had replaced some months ago.
Afterwards I wanted to reflash stock android to start afresh and then reflash lineage.
I'm back on lineage 17 (derived from Android10) and have the following problem:
During calls the microphone in speaker mode doesn't work at all, meaning, the person on the other side doesn't here a thing.
The same happens for speaker calls in other apps.
What still works, is audio in videos I take with the camera.
Also the ambient light sensor seems to have stopped working as the automatic luminosity doesn't work and I have to set the light by hand.
And then the proximity sensor during calls doesn't work.
I'd like to fix these and therefore I would like to find out, whether it is more probably a software or a hardware problem.
I found on this forum that it may have to do with the persist.img, that may have been corrupted by twrp.
Unfortunately I don't know where to get a hopefully working persist.img to try that out.
Things that are maybe relevant are these:
1. The battery was changed, so maybe the engineer doing that broke something
2. During reinstallation of lineage17 I had some problem with twrp not working. Afterwards using lineage recovery worked for installing lineage, but I'm not sure, twrp might have broken something.
3. The same issue also is there on stock android 10.
Can anyone point me in some direction?
I realized that the easiest check for software/hardware distinction would be to just flash a new persist.img.
Is anybody out there, that has a pixel sailfish device with working android 10 that would drop me a message? I should be able to just transplant your persist.img to my pixel sailfish.
I would greatly appreciate it!
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Bongzerker said:
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Click to expand...
Click to collapse
Nonetheless, thanks for your time!
If I may ask for even more of it:
Not sure, whether Pixel XL and Pixel are similar when it comes to their hardware ( I have a Pixel, not a Pixel XL), but if you have repaired many of them, do you think it is at all possible, that the hardware shop that changed my battery somehow broke these sensors or forgot to reattach a cable to them?
I don't plan to hold them accountable, as I really like them, just would like to have a hint, whether going to the hassle of bringing my phone there and thus not having it for a few days has a reasonable chance of success.

Categories

Resources