yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Guides, News, & Discussion] iansolo5:
Hello,

Same issue with my pixel 3 XL: have you find a solution? Poximity and light sensors don't work on mine... No hardware detection.

Thx
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
If some sensors work and some don't, then your problem's root cause is not the same as the issue that we faced in this thread. In our case, it is

all sensors works in Pie but all sensors fails in Android10

.

Doing whatever "fixes" in this thread will not help solving your problems.
[Google Pixel 3 XL Guides, News, & Discussion] iansolo5:
No one of my sensors work under 10 since the last update but after I replace the persist.img, just gyroscope and accelerometer works again.

I was test under 9, same issue...

Thx!
[Google Pixel 3 XL Guides, News, & Discussion] ShorelineDroid:
This isn't just related to custom recovery and kernel mods. I can unequivocally say that it also happens on stock. I am currently running a locked Verizon bone stocker Android 10 and all sensors are dead. I find after I toggle the sensor quick tile and restart about 5 times they come back. Updated to recent beta and the sensors work somewhat - proximity always detects so when you answer the phone it goes black and won't come back until the call is disconnected. Seems like they are trying to fix it but just haven't done so yet. At least not for the people that CAN'T rewrite the persist. Anyone out there on the sad and lonely locked Verizon bench know how to fix the sensor issue?
[Google Pixel 3 XL Guides, News, & Discussion] danny.sunju:
Could you please guide me to step by step process to fix this issue on a Pixel 3?

Thanks.
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
Why don't you read the OP? I've mentioned all steps and methods there.
[Google Pixel 3 XL Guides, News, & Discussion] danny.sunju:
Yes, I did read them but was sceptical as some of them responded that they were still facing issues despite following any one or all the steps mentioned. Also, where can I find the persist file?

Thanks.
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
The solution is 100% working, IF (big IF) you have the exact problem like we did. Most of those who said didn't work basically have other problems and not this exact problem that we faced.

The persist file is in /root.
[Google Pixel 3 XL Guides, News, & Discussion] danny.sunju:
Thank you. I will give this a try. Also, could you suggest which method works best?

Also, I have to get the persist file from another device right? Is that file uploaded somewhere? And finally, I am on Android 11, so will it be the same persist file or do I need to get it from someone who is on Android 11.

Thanks a lot. This sensor thing is really irritating, and I hope to have the phone for another year before changing back to Samsung.
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
Skill-wise it depends on your Android knowledge and confidence. Hardware-wise it depends on if your phone is rooted or not. Personally I used the method under EDIT1 because I know what I was doing.

Yes you need a persist file from other users. Correction to what I said earlier, the persist folder is a root/mnt/vendor/persist/

Blueline sensor file is here. Although you could have easily found this yourself via thread search.

I haven't tried with A11, but I assume it should be the same, since the files you will edit "persists" across whatever ROM you are using.

I am however skeptical about whether you have the same problem as we did, because according to Google (the quote, see OP) this supposed to be fixed already, not needing to do all these steps.

The only major symptom is: ALL sensors work in Pie, but NOT in Android10.

I also assume none of us tested in Android11.
[Google Pixel 3 XL Guides, News, & Discussion] danny.sunju:
Thanks. I will give it a try. And yes, after the July Update on Android 11 Beta, the phone sensors stopped functioning. Proximity Sensor, Auto-Brightness, Double Tap to View, Lift to View, Flip to Shhh; all these stopped working. I tried the following -

1. I went back to Android 10 hoping it would fix the issue, but it was still there.

2. Tried safe mode, it was still there.

3. Flashed May Update, and it was still there.

4. And now, on a sensor test app, the Light and Proximity sensors do not reflect. At one point, the accelerometer, gyroscope also didn't function. However, after restarting the phone they started functioning. Apart from this, Active Edge also doesn't work occasionally, but a restart fixed that.

So, these are the symptoms and I hope it is similar to what you guys experienced. Now, I am back on Android 11 but these (Proximity Sensor, Auto-Brightness, Double Tap to View, Lift to View, Flip to Shhh) still don't work.

Would you still suggest that I go ahead with one of the methods suggested earlier?

Finally, my question with the persist file is if it is the same for all Android version - 9 through 11.

Thanks a lot for your input once again.
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
Have you tried on Pie? because that should 100% work. Try flashing stock pie. If your sensors are working then welcome to the club.
[Google Pixel 3 XL Guides, News, & Discussion] danny.sunju:
Thanks, I will do that and post what I experience.
[Google Pixel 3 XL Guides, News, & Discussion] ptmuldoon:
Just want to add my own experiences with this bug so far. My phone has never had TWRP and is running factory stock on an unlocked phone.

I remember when android 10 first hit, I didn't like it much and did root and go back to pie. But then eventually did let phone take the update and along the way all the sensors broke.

This past months update pushed me to android 11. And then miraculously all of my sensors work.

But that appears short lived. All of my sensors worked last night, and then this morning they were all dead again. So they worked for about 2 weeks. And phone simply sat charging overnight. Few reboots later, they are still all dead.

If copying from a working phone is a permanent fix, I'll try it. Just don't want to reroot and start fresh on the phone again it's it's only a temp fix.

Edit. I just found a power off and then power back on, and not a reboot got the sensors going again. I just hope it lasts.
[Google Pixel 3 XL Guides, News, & Discussion] jbaumert:
So, I've seemed to get the dreaded sensor bug and now a re-flash will not fix it. Can anyone share the sensor file for a Pixel 3a XL 'bonito'? - TIA
[Google Pixel 3 XL Guides, News, & Discussion] pilu01:
Please have someone look at the problem.

https://xdaforums.com/poco-f2-pro/help/fingerprint-sensor-error-poco-f2-pro-t4193287

Is it possible that the solution described here can help me?
[Google Pixel 3 XL Guides, News, & Discussion] neocyon:
I need a copy of this persist.img file, but the link is invalid, please send a copy to my mailbox, thank you very much ：） liusender@gmail.com
[Google Pixel 3 XL Guides, News, & Discussion] Hammad rehman:
Please can anybody sent me persist.img of pixel 3xl i accidentally corrupt persist partition :(
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Sure! Here is an image of the persist partition taken a few minutes ago from my Pixel 3 XL.

MD5: cbae909758feafccaab01b91ba8feaed
SHA256: 98e90daa1c2b7db915f7ab70902ccdb1bb77026c4b1d3dcc6c6ae0424e05167d
[Google Pixel 3 XL Guides, News, & Discussion] Hammad rehman:
Thank you soo much for your appreciated response and saving my pixel 3xl.
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
You're welcome! :)
[Google Pixel 3 XL Guides, News, & Discussion] ptmuldoon:
I plan/hope to try replacing the persist.img with one from here on my Pixel 3XL, and hoping someone can confirm the correct dd command on where to send it to. I've seen mention of 3 different paths, and don't want to screw it up.

Right now I'm on Android 11, but could move back to 10 if think its necessary.

So, in reading through everything I can find, I have seen these 3 mentioned.

Which one is correct for the Pixel 3XL?

dd if=/sdcard/persist.img of=/dev/block/sdf2

dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist

dd if=/sdcard/persist.img of=/dev/block/by-name/persist
[Google Pixel 3 XL Guides, News, & Discussion] chowhoundb:
I just developed this issue on a custom rom running Android 11 on blueline. I have downgraded back to android 9 but the light, proximity, and dt2w are still not working. I tried edit 5 and copied the sensors folder from a working device in this thread, but still no luck.

I assume this means my hardware is the problem. I was trying to hold out until the 6 gets released.
[Google Pixel 3 XL Guides, News, & Discussion] ipdev:
Hi. :)

I am not sure if you found an answer yet but, I see no one replied in this thread.

I do not have a Pixel 3XL so I can not verify the partition(s).​

With that being said, if persist is sdf2 then all three will be the same.

The by-name directory is a directory of symlinks to the partitions.

The by-name directory can be in different/multiply sub-directories but, you will always find it somewhere under /dev/block/​

The first /dev/block/sdf2 the actual partition.

Not sure if this is the persist partition on 3 XL.​

The other two would be a symlink to the persist partition.

These call persist using by-name so they should work regardless of the actual partition number.​

Example:

Using my Pixel 3a XL, persist is mmcblk0p48

bonito:/ # ls -la /dev/block/bootdevice
lrwxrwxrwx 1 root root 36 1972-05-08 05:13 /dev/block/bootdevice -> /dev/block/platform/soc/7c4000.sdhci

bonito:/ # find /dev/block/ -name 'by-name'
/dev/block/by-name
/dev/block/platform/soc/7c4000.sdhci/by-name

bonito:/ # find /dev/block/ -name 'persist'
/dev/block/by-name/persist
/dev/block/platform/soc/7c4000.sdhci/by-name/persist

bonito:/ # ls -la /dev/block/by-name/persist
lrwxrwxrwx 1 root root 21 1972-05-08 05:13 /dev/block/by-name/persist -> /dev/block/mmcblk0p48

bonito:/ # ls -la /dev/block/platform/soc/7c4000.sdhci/by-name/persist
lrwxrwxrwx 1 root root 21 1972-05-08 05:13 /dev/block/platform/soc/7c4000.sdhci/by-name/persist -> /dev/block/mmcblk0p48

bonito:/ # ls -la /dev/block/mmcblk0p48
brw------- 1 root root 259, 16 1972-05-08 05:13 /dev/block/mmcblk0p48

The above example is the same steps I use on all devices to find what partition is what.

You can just list the by-name directory ls -la /dev/block/by-name/ and you will get all the named partitions.​

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Google Pixel 3 XL Guides, News, & Discussion] Shivanshu8795:
Bricked the phone in the process.🤦‍♂️
[Google Pixel 3 XL Guides, News, & Discussion] samonic_official:
Hey guy, hope your all doing well.

So, about the sensors, my pixel 3 was having issue with proximity and light sensor. And i saw the first person's post about getting a tar file and replacing the sensor folder.

I did just that and after that every sensor reported no data, every sensor blacked out. I tried replacing the sensor folder with my original one, but it still wass the same.

Is there any way i can repair this ? Please do help me out here.

I use a device info app that reports much of everything of the phone, and it used to show 33 sensor, after the proximity bug, 31 and after my tar replacing, only 17. Please help me out here.
[Google Pixel 3 XL Guides, News, & Discussion] Palibrix:
Same thing happend to me...

My accelerometer and gyroscope stopped working, tried to fix them and now no data from any sensor...
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
Beta5 used to worked on my end, then flash custom ROM then went back to beta5 to update to 6, but sensors are not working when I went back to 5

---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------

So on my end, custom ROM triggered it, just a hunch
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
Thank you for reporting, my man. However, the 3rd step would have overwritten the bootloader with the latest one. What needs to be done to experiment is to edit the flash-all script to remove updating the bootloader; or, each element except the bootloader needs to be flashed manually.

I'll try doing it whenever I get access to my personal phone.
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
I think it doesn't work that way. If you open the image-crosshatch-qp1a.190711.020.zip it will check the bootloader version:

which Qbeta3 bootloader does not meet: bootloader-crosshatch-b1c1-0.2-5400090.img

Unless you edit the android_info.txt and repackage the zip (I assume will signature check?), I think you will get version mismatch during flashing.
[Google Pixel 3 XL Guides, News, & Discussion] UltraPower31:
You could just flash the old bootloader after flashing the new factory image
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
What file do those sensors located at, vbmeta or system.img? Maybe we can use the GSI image, replaced the one on the official and repackage it:confused:
[Google Pixel 3 XL Guides, News, & Discussion] santod040:
Again, just to clarify, I do not have the sensor bug.

My device is stock and updated through the Betas and Official without issue.

With that being said, I can only use an educated guess, as to any possible causes.

I feel like this is a possible /persist partition corruption.

I have seen similar issues arise on other devices over time, as well as other bugs also caused by the same partition corruption.

On the only device I ever owned, which faced a /persist corruption, no amount of flashing any stock files or factory resets fixed it.

(However, a downgrade would reverse the issue)

In the end, I found the only solution to be, erasing the persist partition from fastboot.

(I had even made a Twrp flashable script/zip file for those who are command line challenged, or lacked a pc)

I AM NOT suggesting you jump to trying to erase anything, without knowing the proper file location/path on this device, or without realizing any possible complications or issues it may or may not cause.

I am mainly posting this as a hint/tip for those who are competent and confident enough, as well as willing to take a risk, realizing I take no responsibility for what they end up doing.

GOOD LUCK to all those effected... :good:
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
Thank you [MENTION=1331268]santod040[/MENTION].

My question is not necessarily to you, but to anyone who would know.

1. Would fastboot erase persist work or is this also slot-specific? Eg. fastboot erase persist_a and persist_b?

2. The next step would be fastboot flash persist persist.img, yes?

3. Would this have any other repercussions?

A quick research tells me we might have something here since users on Mi devices faced similar issues and suggested erasing and flashing persist.

Edited: a lot of threads mention the linkage between persist and sensors. I definitely want to try this out. However, the factory image of Android 10 does not have persist.img. Any idea where I can find that?
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
system/product/build.prop
[Google Pixel 3 XL Guides, News, & Discussion] FcukBloat:
same feelings.. back to custom P. really bored and frustrated of flashing formatting reflashing etc. with no results or minimal clue..

---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------

i tried beta 3 in the past with no success.

funny thing is I'm sure in the past i tried beta 3 and had sensors working. but when sensors broke, when i tried again beta 3, they were still broken ;)
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
I'm confused. Why didn't you flash just the bootloader?
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
Will try later
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
So I figured out why you didn't just flash the bootloader. I tried and it won't boot at all.
[Google Pixel 3 XL Guides, News, & Discussion] boe323:
Anyone tried to flash image of a phone with working sensors?
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Unfortunately I am not sure I understand what you are trying to ask.

---------- Post added at 08:00 PM ---------- Previous post was at 07:41 PM ----------

What would be the benefit to editing build.prop? And what would you even edit?
[Google Pixel 3 XL Guides, News, & Discussion] nikhilnangia:
Editing build.prop is

A. Not possible on Android 10

B. Even if it were, the fix will be temporary and not persist.

I am strongly convinced that this bug can be solved by clearing the /persist/ partition. However, it is risky since there is not enough information out there about Pixel phones.

Does anyone know where to get persist.img for Pixel 3s?
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
If you are rooted you can edit build.prop, but even so I'm not sure what benefit doing so would have. Either way, it would be nice to at least have a workaround for some percentage of the group dealing with this.

As for the clearing the persist partition, what do you believe is to be gained by doing it? I did not even know that such a partition existed.
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
I think you guys are on to something here. Some of my partitions were "resized" while flashing factory images. I wish I remembered which ones.
[Google Pixel 3 XL Guides, News, & Discussion] sliding_billy:
I flashed (minus -w) my wife's Pixel 3. Stock/rooted 9 to stock/rooted 10. Sensors before and after are fine.
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
Build prop is a dead end. Nothing in build prop on Q with sensors.
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
:(

Now what about the partition that [MENTION=7750470]nikhilnangia[/MENTION] mentioned? Any developments on that? I would look into it, but I don't know where to start.
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
There is another build prop in system/product
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Okay, but even so, what do we edit?
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
You have to compare mine with one of yours that's not working. You can't edit system on Q. It would have to be done through Magisk systemlessly

---------- Post added at 11:38 PM ---------- Previous post was at 11:31 PM ----------

Can't mount system r/w on Q because of overlayfs

https://android.googlesource.com/pl...0f0cee97ff33e6254d/fs_mgr/README.overlayfs.md
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
To be honest after so many days finally someone with working Android 10 posted the build.prop to confirm these values, despite we asked and so many people only posted "what are you guys talking about, my sensors are working fine". Of course I can't force everyone to help, but your screenshot confirmed that the problem doesn't lie in setting those values to "true". But it doesn't matter now because we can't save the file after editing the build.prop. so thank you :)

I also believe that the issue lies within those partitioning and formatting, ie. Factory reset is not real clean reset, because with the sensors breaking, I find my location fixed (blue dot) in gMaps at location where I was a few weeks ago, despite not logged in into my Google account. This is definitely impossible if we're "-w" is fullwipe as we understood so far. Maybe it's just look like stock on the surface, but underneath it isn't a clean, proper wipe after all.

Anything else I could try??
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
I'm confused. As I understand, the image you posted above is from a Pixel 3 XL that is working, and you are saying we need to make changes to our build.prop to match yours. Correct?

As for how to update it using Magisk see this post: https://xdaforums.com/showpost.php?p=69621730&postcount=7

Specifically, see the "New Badass Tool - resetprop" section.
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
The image is from a working 3XL Q build prop. All I'm saying is to compare the working build prop to one that is not working. If there is a difference, you might want to try and edit it
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Oh okay I can do that! So to be clear, since there are apparently multiple build.prop files, the one that I should look at is under system/product/build.prop. Correct?
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
Yes sir
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
I just looked on my phone that is having the problem and there is no difference. ?
[Google Pixel 3 XL Guides, News, & Discussion] Golf c:
Bummer
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
thats a bummer...what im doing right now is copy some files from the pie files on the image, which has more files than the 10 and paste it to android 10, as of right now I am flashing it...well if it bricks, it'll break my heart=) hehehe
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Please please please tell me you're not doing this without a backup.
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
using two laptops, while on the right hand is some whiskey to make it thru the night=)
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Stay strong!
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
I don't care, waiting for the Pixel 4XL:D just me, been flashing everyday and the phone still boots

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

the screen on my phone is all black now, while the powershell is still flashing=)

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

it's booting now.....
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
I will be shocked if this works.
[Google Pixel 3 XL Guides, News, & Discussion] wangdaning:
All Pixel3 buyers should get a bottle of real bourbon and a Pixel4, google owes us that much with their half dev available device. :highfive:
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
hahaha, nothing happen same thing, I'll try to do format first
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
That's what I expected. :(
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
This deserves more F5 on my keyboard than Android 10 on Sept. 3rd.
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
this is what happens when your drinking and debugging=) pictures are sideways

---------- Post added at 08:02 PM ---------- Previous post was at 07:54 PM ----------

second try, if not going back to PIE and just keep BOOTLEGGING=)

---------- Post added at 08:32 PM ---------- Previous post was at 08:02 PM ----------

well it is still there, going back to pie now

---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------

well it is still there, going back to pie now
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
Another one bites the dust.
[Google Pixel 3 XL Guides, News, & Discussion] imna357:
:good:
[Google Pixel 3 XL Guides, News, & Discussion] ultimatepichu:
Can I get help from you guys? I need 2 persons:

1. Working Android 10 with root

2. Not working Android 10 with root

Using explorer, go to : root/persist/sensors/registry/registry or /mnt/vendor/persist/sensors/registry/registry

There's bunch of sensor files there, check if the size of the files

for person 1 I expect them to have some files with some bytes of data

For person 2 I expect them to be all 0 Byte.

If someone can verify this then I think we have clear direction: We need to get working persist folder into our dysfunctional Android 10.

I still can't give up lol. I'm on Pie right now, but I can slowly go to person2. I still need the person1 to verify.
[Google Pixel 3 XL Guides, News, & Discussion] steal25:
I can reflash 10 tommorow and help out. I would be person 2 in your scenario.
[Google Pixel 3 XL Guides, News, & Discussion] ffchampmt:
Working w/root
[Google Pixel 3 XL Guides, News, & Discussion] David B.:
I think you might be on to something! I am rooted, not working and sure enough, 0 bytes. (See attached image.)