After downgrading from Android O Developer Preview 2 to Android 7.1.2 Nougat, some Nexus 5X and Nexus 6P users are reporting that some sensors on their phone are not working properly. For example, the 360-degree image does not move with the movement of smartphone. Ambient light sensor, proximity sensor, accelerometer and gyroscope are affected. If you are experiencing sensor issue on Nexus 5X/Nexus 6P, here is how to fix.

If sensors on your Nexus 5X or Nexus 6P are broken after downgrading from Android O DP2, then you can simply fix it. The procedure is very simple, so you can easily bring your sensors back to life. All you need to relock the bootloader. If you are experiencing sensor issue after downgrading to Android Nougat from the Android O, then check out the guide below.

Advertisement

LG-nexus-5x

Before begin with the guide, note that this method might not work with every device. In addition, we do not know if this is a perfect and practical remedy for fixing sensor issue on Nexus 5X or Nexus 6P.

Read on to know how to fix sensor issue on Nexus 5X or Nexus 6P after downgrading it to Android Nougat from Android O Developer Preview 2.

How to Fix Sensor Issue on Nexus 5X/Nexus 6P

1. Connect your device to your PC, go to the ‘Platform tools’ folder and open a command window from there.

2. Reboot your device into fastboot mode by issuing the command: adb reboot bootloader

3. Now, issue the below command to relock the bootlosder:

fastboot flashing lock

Note: Locking the bootloader will wipe the data you have on the phone. So back up any important file before proceeding.

Does this method helped you to fix sensor issues on your Nexus 5X or Nexus 6P. Let us know in the comment section below. (Source)

Previous articleDownload 6 Leaked OnePlus 5 Wallpapers
Next articleLineageOS 14.1 (Android 7.1.2) Now Available for Nexus 9 (Installation Guide)
Kannan
Kannan is a computer and Android enthusiast, a blogger by passion and a tech freak. His always ready-to-help attitude, knowledge and hard work is what drives him.

2 COMMENTS

  1. Didn’t work for me, my phone was locked and still get the issue.

    The solution was to unlock, flash it with the latest factory image and lock it again.

    Thanks

Comments are closed.