Google’s in no hurry to fix the Pixel 10’s shaky video bug

Google’s in no hurry to fix the Pixel 10’s shaky video bug By  Rajesh Pandey Published 5 minutes ago Rajesh started following the latest happenings in the world of Android around the release of the Nexus One and Samsung Galaxy S. After flashing custom ROMs and kernels on his beloved Galaxy S, he started writing about Android for a living. He uses the latest Samsung or Pixel flagship as his daily driver. And yes, he carries an iPhone as a secondary device. Rajesh has been writing for Android Police since 2021, covering news, how-tos, and features. Based in India, he has previously written for Neowin, AndroidBeat, Times of India, iPhoneHacks, MySmartPrice, and MakeUseOf. When not working, you will find him mindlessly scrolling through X, playing with new AI models, or going on long road trips. You can reach out to him on Twitter or drop a mail at [email protected]. Sign in to your Android Police account Summary Generate a summary of this story follow Follow followed Followed Like Like Thread Log in Here is a fact-based summary of the story contents: Try something different: Show me the facts Explain it like I’m 5 Give me a lighthearted recap

In October, a Redditor published a detailed bug report behind the Pixel 10's poor video stabilization with the telephoto camera, especially with EIS enabled. As it turned out, the problem stemmed from a fault in Google’s Camera API that led to a conflict between OIS and EIS and had nothing to do with the hardware. Since it’s a software issue, you’d think Google’s engineers would be quick to fix it. Unfortunately, it seems the company is not interested in addressing the issue at all.

Redditor u/No_Particular7571, who went to great lengths to track down the cause of the camera stuttering issue, reached out to Google with detailed reports in hopes of getting the issue fixed for good.

A Google support member supposedly told him a few weeks ago that the engineering team had "addressed the concern in the latest fixes." But, based on the Redditor's testing, that was not the case. After collecting more information from affected Pixel users, he sent another detailed report to Google to help address the bug.

Sadly, instead of acknowledging that the issue still exists or appreciating the Redditor’s extensive effort, Google’s support team offered a rather deflating response: "Thank you for your patience. Unfortunately, our engineers will need more time to look into this specific issue. While we can’t promise a fix to the specific issue you have, we do release bug fixes on a monthly basis. We’re sorry for the inconvenience."

Even if the response came from a Google support representative, it’s still disappointing. For one, it dismisses the hard work the Redditor put in to track down the root cause, gather logs, and detailed bug reports — all in a bid to provide Google engineers with as much information as possible to fix the problem. Yet, it seems like the Pixel team has not made any noticeable progress on this front.

Why is Google dragging its feet on a major pixel bug?

The irony here is also hard to ignore. A Pixel user did all the hard work for Google, going as far as pinpointing the exact cause of the problem. Yet, the company can't promise a fix.

Yes, there might be more technical challenges involved, but when a Pixel user provides such a detailed bug report on an issue that affects all Pixel phones, you'd expect a more detailed response and some urgency.

The cameras on recent Pixel phones have been heavily criticized for their inferior stabilization. So, it's even more puzzling to see Google not jumping on a possible solution to this problem.

• Phones

Follow Followed Like Share Facebook X WhatsApp Threads Bluesky LinkedIn Reddit Flipboard Copy link Email Close Thread Sign in to your Android Police account

We want to hear from you! Share your opinions in the thread below and remember to keep it respectful.

Be the first to post Images Attachment(s) Please respect our community guidelines. No links, inappropriate language, or spam.

Your comment has not been saved

Send confirmation email

This thread is open for discussion.

Be the first to post your thoughts.

• Terms
• Privacy
• Feedback

Recommended 2 days ago

I don't trust Pixel phones anymore — here's why

31 minutes ago

YouTube is finally fixing its 'broken' home feed, the absolute easiest way it can

1 day ago

Google quietly confirms when it's pulling the plug on Assistant

3 days ago

Quirky indie phone is a modular Nokia/iPod hybrid, and proof there's still some fun in mobile tech

Trending Now Samsung Galaxy S26 may debut a Perplexity-powered Bixby The tiny One UI tweak that changed how I use my Samsung phones Anker's Qi2 multi-device charger is my personal favorite, and a Black Friday steal