[Google Pixel 3 Guides, News, & Discussion] nikhilnangia:
EDIT

This issue was fixed. The problem is with the persist partition getting corrupted on some devices. The reasons are not clear, but we have strong reasons to believe this is due to TWRP's implementation of leaving logs and cache files on the /persist partition, which is limited in size. The log files often exceed 20MB in size and cause the sensor config and calibration files to become corrupted on that partition.

Steps to get this fixed:

Obtain a working persist.img from someone (it is device specific. You can find the ones for crosshatch and blueline on this thread, but will have to ask someone else for other devices)

Replace your persist partition with the persist.img you obtained. This needs to be done using an advanced command (dd) and you need to be on Android 9 in TWRP (rooted) to do this. Read the thread (around page 19) for more details.

Flash Android 10 (does not need to be a clean install, but clean install is always recommended).

WARNING: replacing your persist partition with someone else's (even the same device) WILL replace your original, unique factory calibration data with someone else's. This includes audio config files, camera calibration files, sensor calibration files. Backup your original /partition image before doing this and only do this if it is absolutely necessary. You have been warned!

No one on this thread assumes responsibility for anything bad happening to your device. It worked for all of us, but is not guaranteed to work for you. Still no news from Google, who are still investigating.

ORIGINAL THREAD

Starting a new thread here from the old one: https://xdaforums.com/pixel-3-xl/how-to/android-10-final-version-release-t3963794/page7

What is the problem?

Many users of Pixel 3 XL, Pixel 3, Pixel 2 XL and even the OG Pixel are reporting a major bug after upgrading to Android 10. All the sensors seem to be disabled.

This includes Active Edge, Proximity Sensor, Ambient Light Sensor, Auto-brightness, Accelerometer (Auto-rotation, flip to shhh, double tap to wake and lift to wake). All of these are dead on Android 10.

What we know:

Whether we upgrade directly from Android Pie or do a clean install using the factory images does not seem to matter. The issue only affects a certain set of users and only goes away if we revert to Pie. The phone works perfectly then.

Manually erasing all partitions and installing from the image does not work either.

Installing Android 10 individually on partitions A and B does not help either.

Re-locking the bootloader and returning completely to stock does not work either.

The only thing in common for all of us is that we were all rooted and/ or using a custom kernel in the past. However, some others who had been rooted and using custom kernels/ ROMs report they do not face this issue.

Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.

Some users suspect this could be happening due to "something left-over somewhere hidden on the phone." (not verified, but makes sense, in theory)

Coverage

This issue is widely covered now:

https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/

https://www.androidauthority.com/pixel-sensors-android-10-1026027/

https://9to5google.com/2019/09/05/pixel-active-edge-sensors-android-10/

https://mobilesyrup.com/2019/09/05/pixel-users-experience-dead-sensors-post-android-10-update/

... and many more

Next steps:

If you face this issue, please add your comments and what you have tried here and update the bug on Google's issue tracker that we have filed here:

https://issuetracker.google.com/issues/140476661​

There is also a help center article on Google's support forum that you can upvote here: https://support.google.com/pixelphone/thread/13511202?hl=en