By
Karandeep Singh Oberoi
Published 3 minutes ago
Karandeep Singh Oberoi is a Durham College Journalism and Mass Media graduate who joined the Android Police team in April 2024, after serving as a full-time News Writer at Canadian publication MobileSyrup.
Prior to joining Android Police, Oberoi worked on feature stories, reviews, evergreen articles, and focused on 'how-to' resources.
Additionally, he informed readers about the latest deals and discounts with quick hit pieces and buyer's guides for all occasions.
Oberoi lives in Toronto, Canada. When not working on a new story, he likes to hit the gym, play soccer (although he keeps calling it football for some reason🤔) and try out new restaurants in the Greater Toronto Area.
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
The Pixel experience is mostly a bug-free one, but from time to time, a software glitch does surface that makes everyday usage just a tad bit frustrating.
Right now, Pixel 10 users are battling a video stabilization bug, though that's mostly limited to the 5x telephoto with EIS enabled. That's a niche issue, but Pixel users are also currently battling a more pervasive problem.
Related
Blame the Google Pixel 10’s shaky videos on a Camera API bug
It's not a hardware fault
Posts By Rajesh Pandey Oct 9, 2025Users are reporting that the Pixel Launcher sometimes reopens a recently closed app, even when users consciously tap on a different app's icon on the home screen.
The bug was highlighted by the folks over at PiunikaWeb, citing user reports on Reddit and Google's IssueTracker, with the latter rocking over 200 'plus ones,' suggesting that it might not be all that isolated.
Google knows about the issue
But it has still been radio silent
According to user gemb0_0 on Reddit, they've had problems with said bug for roughly six months now. Several other Reddit users commented, adding credence, indicating that they've encountered the same bug but were never able to reproduce it.
"Good job on getting a recording of it, i was trying to get one," wrote user DiodeInc, while user HackZy01 wrote "Jesus I've had this issue ever since upgrading, you need to wait until it closes fully, google doesn't acknowledge this issue like many other."
HackZy01's tip about waiting until an app completely closes before triggering a new one makes sense. However, the following statement about Google not acknowledging the issue is incorrect.
As mentioned earlier, the bug made its way to IssueTracker, where it was acknowledged and passed on to the development team.
Thanks for reporting this issue. We have passed this to the development team and will update this issue with more information as it becomes available.
This was on November 5th. There have been no verbal updates from Google since. Until an official fix is out, users will have to rely on temporary workarounds, like carefully waiting for an app to fully close before opening a new one.
-
Applications
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 emailThis thread is open for discussion.
Be the first to post your thoughts.
- Terms
- Privacy
- Feedback
1 day ago
This is the Google TV streaming device that costs just $9
6 hours ago
Poco's new tablets look like budget-friendly winners
8 hours ago
Google Gemini gets a game-changing productivity feature that rivals will envy
1 day ago
How to use Safe Mode on the Google Pixel 10
Trending Now
6 reasons I bailed on YouTube Music and landed on Spotify's free tier
Why One UI 8 is the first version that understands attention spans
Follow up questions on Circle to Search now default to AI Mode
