It's no secret that Google makes some of the best Android smartphones, but they're also frequently prone to odd issues at launch or after updates. Now, Google's new Pixel 7 has the "Pixel curse," as we see new complaints about frustrating little problems.

Earlier this week, we reported on a display power issue where users noticed excessive battery loss while using the phone outdoors. More so than other devices, high Pixel 7 brightness could potentially drain the entire battery in 3-4 hours. Others have reported eSIM issues.

Now, we're unfortunately starting to see more screen complaints. Users all over Reddit have reported Pixel 7 Pro screen scrolling problems, glitches, lag, or inconsistent behaviors. Sometimes scrolling is sticky or lags, or it doesn't respond at all, while other times, it'll scroll way too fast and glitch out.

Related: Pixel 7 Pro Has Serious Energy Consumption Problems

At this point, we're not sure what's going on. One potential issue is the upgraded 120Hz display refresh rate feels different from those upgrading from an older phone. Maybe Google changed the settings to make it more or less responsive to specific touches, swipes, or scrolling. Or we could just be seeing an early release Pixel 7 and Pixel 7 Pro problem that'll get fixed within the first few weeks.

Most complaints are for Google's premium Pixel 7 Pro, but we also see a few for the regular Pixel 7. In testing our review units, we've yet to experience any Pixel 7 Pro scrolling lag, so this may only affect select users.

So, is there a fix? According to several Reddit users, the software update ready and waiting the day you take your new Pixel 7 out of the box will help. Several owners said this quick update fixed the problem. You can also try disabling the "smooth scrolling" feature in settings, reboot your phone, or maybe Google will quickly release a software patch.

Either way, brand new phones with some initial bugs isn't a unique situation, so hopefully, an update or two can fix things in a timely manner. We'll report back once we know more.

via AndroidPolice