Question Multiple sensors not working.

[Samuel Holland]

I've tried everything I could think of personally. I flashed stock to both slots, wiped a couple of times, and flashed my persist partition backup thinking that would help.
When I try a proximity sensor app it acts like I don't have one. The sensors I believe are null are proximity, tap 2 wake, and auto screen brightness sensor.
I thought I'd ask before calling Google.
I tried connecting to there repair web page but after connecting I always get tinted out.

 

[blackhawk]

Try in safe mode if any 3rd party apps have been loaded, otherwise...
Install DevChek and see what sensors are or aren't working.
If you're running stock and a block of sensor readings aren't showing or are skewed, it sounds like a mobo failure.

 

[Samuel Holland]

Try in safe mode if any 3rd party apps have been loaded, otherwise...
Install DevChek and see what sensors are or aren't working.
If you're running stock and a block of sensor readings aren't showing or are skewed, it sounds like a mobo failure.

Hi thanks for replying.
I've tried safe mode, sorry I forgot to mention.
I've tried a few apps including flar2's dev check.
The ones that you can test sensors, say it either doesn't exist, etc. I replaced persist from backup with fastboot, etc. I'm starting to think maybe it is a hardware fault.

 

[blackhawk]

Hi thanks for replying.
I've tried safe mode, sorry I forgot to mention.
I've tried a few apps including flar2's dev check.
The ones that you can test sensors, say it either doesn't exist, etc. I replaced persist from backup with fastboot, etc. I'm starting to think maybe it is a hardware fault.

One reason I run stock is it makes troubleshooting much easier. If the stock firmware's reloaded right it's a hardware fault of some kind.

 

[Samuel Holland]

One reason I run stock is it makes troubleshooting much easier. If the firmware's loaded right it's a hardware fault of some kind.

Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.

 

[hungragezone]

Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.

Do u use Evo with its kernel or other kernel?

 

[Freak07]

Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.

what might be worth a last effort try, is to reflash stock firmware and wipe data/factory reset the phone from stock recovery, if reflashing firmware with a wipe does not work.

to enter stock recovery: boot to recovery on your phone, when on the no command screen press and hold power button, while holding power button press volume up.

That was the only thing that could clear up corruption in the face unlock firmware back on pixel 4xl, which happened sporadically for a few months until google fixed it properly.

 

[Samuel Holland]

what might be worth a last effort try, is to reflash stock firmware and wipe data/factory reset the phone from stock recovery, if reflashing firmware with a wipe does not work.

to enter stock recovery: boot to recovery on your phone, when on the no command screen press and hold power button, while holding power button press volume up.

That was the only thing that could clear up corruption in the face unlock firmware back on pixel 4xl, which happened sporadically for a few months until google fixed it properly.

Thank you, I'm gonna have to give that a shot, I did flash stock but I didn't wipe in stock recovery. That's a good idea come to think about it. Thanks for replying.

 

[blackhawk]

Thank you, I'm gonna have to give that a shot, I did flash stock but I didn't wipe in stock recovery. That's a good idea come to think about it. Thanks for replying.

Freak07 may be right... there may still be a firmware issue. I find it odd you lost both the double tap wake and proximity.

I simply never had to trouble on that level with Androids. I didn't mention a hard reboot but probably should have I rarely use that option.
More commonly I would clear the system cache but I understand that's not an option on Pixels.

 

[Samuel Holland]

Freak07 may be right... there may still be a firmware issue. I find it odd you lost both the double tap wake and proximity.

I simply never had to trouble on that level with Androids. I didn't mention a hard reboot but probably should have I rarely use that option.
More commonly I would clear the system cache but I understand that's not an option on Pixels.

Yes, I hope so, I'm gonna give it a shot in the next couple days before calling Google. By the way the three sensors not working are barometer, proximity, & light sensor. I'll report back. Thx

 

[jaseman]

Yes, I hope so, I'm gonna give it a shot in the next couple days before calling Google. By the way the three sensors not working are barometer, proximity, & light sensor. I'll report back. Thx

I may be completely wrong here but...I don't think the Pixel 7 Pro even has a barometer? As for the proximity sensor and the light sensor...I think they are one-and-the-same. In that case all you have is one faulty sensor which can be calibrated using the screen brightness slider while auto brightness is turned on! YMMV

 

[binary**#]

I may be completely wrong here but...I don't think the Pixel 7 Pro even has a barometer?

It does have a barometer

 

[pgrey2]

As for the proximity sensor and the light sensor...I think they are one-and-the-same.

These are definitely discrete sensors.
The main reason I'm so sure, is that I use my P7P (and older phones, way, way back) in zliploc baggies, quite often, as a road-cyclist.
It 100% knows it's in a bag (and is sometimes a pain to use, but the P7P does better than many older phones), AND it still adjusts the brightness, accordingly...

 

[jaseman]

These are definitely discrete sensors.
The main reason I'm so sure, is that I use my P7P (and older phones, way, way back) in zliploc baggies, quite often, as a road-cyclist.
It 100% knows it's in a bag (and is sometimes a pain to use, but the P7P does better than many older phones), AND it still adjusts the brightness, accordingly...

If the bag is clear then the brightness adjustment will still work. As for the phone being a pain to use is because there is a layer of loose plastic over the screen! This has nothing to do with proximity sensor. I am sticking to my original view that the proximity sensor and the light sensor are the same! It only makes sense! HOWEVER, I admit I could be wrong!

 

[Samuel Holland]

Well update I stock flashed June update and wiped using stock recovery, but unfortunately they are still not working.
I asked through email if I could send in using warranty, hopefully they will allow me to get it fixed. Used to I could call, but they asked me to email, so I'm on my sixth email going on the second week so hopefully Monday they will allow me to send in. I'm gonna also try the support tab under setting. Thanks everyone for the input and suggestions.

 

[pgrey2]

If the bag is clear then the brightness adjustment will still work. As for the phone being a pain to use is because there is a layer of loose plastic over the screen! This has nothing to do with proximity sensor. I am sticking to my original view that the proximity sensor and the light sensor are the same! It only makes sense! HOWEVER, I admit I could be wrong!

The point is, the proximity sensor works with a clear bag, which means it's not using the light sensor.
See this teardown:

Google also lists them as discrete sensors: https://support.google.com/pixelphone/answer/7158570?hl=en&ref_topic=7530176&sjid=15388427490819596714-NA#zippy=,pixel-pro

If you scroll down this last (after looking at the P7P specs for sensors), to the original Pixel/XL, you'll see where they list this sensor as a combined unit, for comparison.

My phone works well inside a ziploc, even WITH a screen protector to-boot. The only thing that's hit-miss, is the fingerprint sensor (works maybe 50% through the extra layers), and the tap-to-wake. This 2nd one is where the proximity sensor comes in, if it were just a light sensor, the bag would have minimal affect, right?

 

[Rstment ^m^]

The point is, the proximity sensor works with a clear bag, which means it's not using the light sensor.

What is it using then? Crystal ball?

 

[pgrey2]

What is it using then? Crystal ball?

Nope, IR emitter and receiver.

Another cool way to test, is to take your phone in a completely dark room, in a call (NOT with speakerphone on, this disables the proximity sensor, for obvious reasons), and see if you can still use the screen (hint, you can). If the standard light sensor were being used, it would prevent the phone screen from waking, in this scenario.

There are also a variety of (well rated) sensor test apps out there, which will also demonstrate the difference between the sensors. The light sensor will vary, a LOT, across a wide variety of values, in a lighted room, whereas the proximity sensor will be off, until your hand/face/whatever-body-part is within about 5cm (ish), at which point it triggers, in a very binary way.
The actual light sensor itself (not the LED emitter) may be repurposed for receiving the expected IR, that part is tough to discern, from the specs tests, or schematics. It may be possible to peruse the device-level code, to get more specificity here, but I'm not quite that motivated, at this point...