Pixel bug camĂ©ra : la preuve par l’application gratuite

**đŸ”„LATEST UPDATE (Oct 9): New Investigation – The ZOOM Stutter!đŸ”„**

Prompted by several users, I’ve done a quick follow-up investigation into the jerky zoom and color shift when switching lenses. The full text is below, and **you can watch the new comparison 🔗** [**video here**](https://youtu.be/oFxFZK-bZoA).

**My initial findings:**

1. **The Key Takeaway:** ProShot was the clear winner in overall smoothness, which is obvious in the frame-by-frame comparison. However, the most critical finding is this: **the Pixel hardware IS capable of a smooth zoom transition.** During the close-up test (with my bike), I intentionally tried to replicate a smooth transition and eventually managed to achieve it on **ALL THREE APPS**, including the stock camera. This proves there’s a « sweet spot » or a specific software pattern that works correctly. The issue is that Google’s software is inconsistent and fails to trigger this smooth transition reliably.

2. **A New Hypothesis:** This led me to a new theory. What if the Optical Image Stabilization (OIS) on the telephoto lens is inactive while the main camera is being used, and its abrupt activation when switching causes the physical « jerk » we all see?

**Disclaimer:** This was just a quick field test. A full investigation would require more controlled conditions (like a tripod).

Hello everyone,

Yes, it’s me again. I know this is my third post on the same topic, and I truly hope it will be the penultimate one. The final one, I hope, will be about our collective victory.

This all started again when a fellow Redditor with a new Pixel 10 Pro (a huge shout-out to ‘***Apprehensive-Bug9480***’ for the tip!) suggested I test a free app called **Open Camera**.

Honestly, I was skeptical. After testing « *professional* » apps like **BlackMagic** and **ProShot**, what could a free app possibly show me? **The answer, it turns out, was everything.**

The crucial difference is that Open Camera has its **OWN stabilization API**, and it lets you switch between its own API and Google’s native Pixel API. And this is where we found the smoking gun.

* **Using its own API, Open Camera completely FIXED the stutter on my 5X telephoto lens.** It’s smooth. It’s stable. It’s what you’d expect from a flagship.

* The Redditor who suggested it confirmed the same: his main camera and telephoto stutters were also GONE.

This is the definitive proof we needed. **The hardware is fine. The problem is, and has always been, Google’s broken software API.**

**⭐ A Temporary Workaround For You ⭐**

**While we wait for Google to (hopefully) fix this, I strongly recommend you try Open Camera for yourself, especially for video. It’s free on the Play Store. You can use it as a temporary replacement for the faulty stock camera app when you need to record stable video. For photos, the standard Pixel Camera is still great.**

**The Video Proof (Side-by-Side Comparison)**

I went out again and recorded a comprehensive comparison video to show you exactly what’s going on. You can see the difference with your own eyes.

**🔗**[**Full Video Link**](https://youtu.be/BS7_VMv-Ozg)

Here are the key moments with direct timestamped links:

* [**00:00 – Telephoto (5X) Test: Open Camera API vs. Google’s BROKEN API**](https://youtu.be/BS7_VMv-Ozg) \- Here you can see the night-and-day difference. One is smooth, the other is « teleporting. »

* [**00:25 – Main Camera (2X/1X) Test: Exposing Stabilization & Crop Issues**](https://youtu.be/BS7_VMv-Ozg?t=25) \- We dive into the weird « LOCK » mode and prove that even on the main camera, Google’s API crops the image more for a worse result.

* [**00:46 – Ultrawide (0.5X) Test: An Honest Comparison**](https://youtu.be/BS7_VMv-Ozg?t=46) \- To be fully objective, here’s a scenario where the stock Pixel Camera actually performs better. We’re not here to hate, we’re here for the truth.

* [**00:52 – VideoBoost Analysis: Is It a Fix? (Spoiler: No)**](https://youtu.be/BS7_VMv-Ozg?t=52) \- A deep dive into VideoBoost and why it’s a cool feature, but NOT a fix for the stabilization.

**A Quick Word on VideoBoost**

I was wrong in my previous post about how VideoBoost works. It doesn’t upscale from FHD. It records in your chosen resolution (e.g., 4K 60fps), sending that huge source file to the cloud for processing while leaving a small FHD preview on your phone.

But my conclusion remains the same: it’s a great *enhancer* for colors and detail (especially at night), but it **cannot fix the underlying stutter**. It would be a much better feature inside Google Photos, allowing us to apply it to any video later, without having to remember to manually enable it every single time before shooting.

**Why I’m Doing This (And Our Call to Action)**

I love my Pixel phone. That is precisely why I’m putting so much effort into this. I’m not here to spread hate; I’m here because I want this device to be as good as it can be. If I didn’t care, I wouldn’t have spent weeks on this investigation.

And now, I need your help to get this over the finish line.

**1. AMPLIFY OUR VOICE ON TWITTER (X):** Please, go to the tweet I just posted, **like it, and especially retweet it**. This is how we get the attention of tech journalists and Google’s social media teams. [**Link to the Tweet**](https://x.com/CaPl9l/status/1975987421402820802)

**2. FLOOD THEM WITH DATA (The « Hardcore » Method):** If you have this issue, please file a full bug report with logs 🔗 [**via Pixel support**](https://support.google.com/pixelphone/gethelp?sjid=15327295042132003880-EU). The more tickets and data their engineers get, the higher the priority will be. 🔗 [**Google Instructions**](https://support.google.com/pixelphone/answer/6398243?hl=en&ref_topic=7084203&sjid=15327295042132003880-EU)**.**

>*In your report, you can simply say: « My camera video stutters with EIS enabled. This is a known issue related to the EIS/OIS software conflict, as proven in this investigation: » and link to this Reddit post or my YouTube video.*

I’m now **going to update** my own official bug report with all this new evidence. I truly believe that if we push together, we can make a difference. Let’s get this fixed and show the strength of the Pixel community!

**Thank you!**

**UPDATE (Oct 8):** The comprehensive follow-up report has now been sent to Google Support and officially added to my case. It includes all the new evidence: the Open Camera discovery, the side-by-side video proof, and all the new logs. The ball is in their court now. **Thank you all for the incredible support!**

7 replies

  1. Corentin Voisin · 6 days ago

    Vous voulez savoir quelque chose de plus ? Il est possible que le bĂ©gaiement x5 provienne parfois de votre camĂ©ra principale, car Ă  5 fois, parfois le logiciel Google dĂ©cide d’utiliser encore la camĂ©ra principale large. Cela semble fou mais j’ai parfois repĂ©rĂ© cela.

  2. Harlow Pierce · 5 days ago

    Aucun problĂšme ici. Mais la stabilisation d’image n’est qu’une option pour les vidĂ©os sur gcam. Je ne zoome pas. Si je le faisais, j’obtiendrais seulement 2x et c’est suffisamment Ă©trange que les gens veulent un zoom fou par rapport Ă  un macro Ă  haute rĂ©solution. C’est un peu effrayant.

  3. Nolan Palmer · 4 days ago

    Merci pour ton effort mec, j’espĂšre qu’ils rĂ©pareront aussi le lag de ma camĂ©ra principale 😂 pour l’instant, au cas oĂč je utiliserais Open Camera, qui est surprenamment bon

  4. Finn Simpson · 2 days ago

    FrĂšre, tu fais un magnifique travail ! J’espĂšre que Google t’Ă©coute !

  5. Emily Stevens · 2 days ago

    On dirait que l’application Pixel Camera a Ă©tĂ© mise Ă  jour ce matin, curieux de savoir s’ils ont vraiment fait quelque chose.

    OP, as-tu vu ça ?

  6. Violet Gonzales · 2 days ago

    C’est embarrassant que Google ne puisse plus crĂ©er un bon logiciel pour leurs tĂ©lĂ©phones.

Répondre à Violet Gonzales Annuler la réponse

Votre adresse e-mail ne sera pas publiée. Les champs obligatoires sont indiqués avec *