Google looking into Android 8.1 bug that causes lock screen swiping issues

0
124

  • People have reported having swipe issues on the lock screen following the Android 8.1 Oreo update
  • The issues seem to affect Pixel and Nexus devices running the software
  • Google confirmed it is looking into the issue and will reach out to affected users

Android 8.1 Oreo might have turned on the Pixel Visual Core and added a few new touches here and there, it looks like the update also introduced a bug that is giving folks some lock screen issues.

Based on reports on Google’s support site and Reddit, people are having trouble swiping up on the lock screen on their Pixel and Nexus devices following the update. According to affected device owners, they have to swipe up multiple times for the phone to register the swipe and take them to the PIN/pattern/password input.

Others reported they are having trouble swiping away notifications from the lock screen. I have experienced this issue on my Pixel 2 XL and would have to repeatedly swipe at a notification on the lock screen for it to go away.

Editor’s Pick

related article

Android 8 review: Oreo is for everyone

Three years ago Google introduced us to its new design language called Material Design. It was flat, graphical and colorful. It was the visual change that ushered in the beginning of a new age for …

The lock screen issues do not stop there, as others also reported having difficulty swiping the notification bar down.

These issues seem relatively new, since reports of lock screen issues started accumulating last November. That being said, community manager Orrin confirmed that Google is looking into the swipe issues and said he would reach out to affected users for bug reports.

As previously mentioned, the swipe issues seem to affect Pixel and Nexus devices running Android 8.1 Oreo. A Reddit user said that restarting the device in recovery mode did away with the issue, though others did not have the same experience.

In the meantime, let us know in the comments if your Pixel or Nexus device has this issue and if you were able to fix it.

via Android Authority

January 9, 2018 at 11:56PM