Google literally astounded everyone by not naming the latest iteration of Android after a dessert. Starting from Android 1.5 (Cupcake) in 2009, the company had been going on with the custom that it became difficult for everyone to anticipate an edition without a dessert name.

Android 10 stable went official on Pixel devices first, as expected, then on Essential Phone and Redmi K20 Pro (agreed, that was quite a surprise).

Owing to multiple beta versions arrived months before, one would think the stable build is bug free. But, that’s not the case, especially with Pixel (ambient display issues when placed on Pixel Stand, dead sensor bug, pop-up notification glitch etc to name a few more).

Pixel stand bug

To recall, Android 10 does bring many new features. You get a system-wide dark mode, smart reply for messaging apps, better sharing menu, focus mode, quicker access to settings, overhauled permissions, etc.

Google Pixel users got the chance to enjoy all these features first. However, there may be a few who regret having the latest firmware due to the number of bugs it brings with it. Incoming is another issue pertaining to app shortcuts.

We spotted a video on Reddit, portraying the problem. Below the same, 100+ comments proclaims it’s not an isolated bug experienced by very few users.

When does this bug pop up? In order to see that, you have to open an app (on Pixel, of course) and go home using the gesture navigation. And now, long press on an app to immediately select a shortcut.


We anticipate it would launch the app shortcut. It would, for Android Pie users. On the contrary, Android 10 denies to get along with your action. Instead, the screen just flickers and goes back to the home.

Let’s go back to August, shall we? The stable build hadn’t gone public by then. Those who had interest in the beta version were using it. And, many of them received this bug. They even brought it to Google Issue Tracker as well.


Strangely enough, we could locate a couple of replies that said the company came to know about it. But they didn’t fix even on the public release. Why? You tell us! We all expect an OEM to solve a widely spread bug on the beta build by the time they release it for the public.

As of now, there is no confirmation available on when the fix is going to go live. If and when it happens, we will update this story.

Note:- Don’t forget to check our Google section to read more related stories.

PiunikaWeb is a unique initiative that mainly focuses on investigative journalism. This means we do a lot of hard work to come up with news stories that are either ‘exclusive,’ ‘breaking,’ or ‘curated’ in nature. Perhaps that’s the reason our work has been picked by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and more. Do take a tour of our website to get a feel of our work. And if you like what we do, stay connected with us on Twitter (@PiunikaWeb) and other social media channels to receive timely updates on stories we publish.

Rahul Krishnan
282 Posts

Rahul Krishnan, a wordsmith from Kerala, India is always in lookout for his next article idea. He is a fanatic reader. And, the rumour is that his mom has recently hidden his debit card so that he won't buy books anymore. She doesn't know he has a spare one.

Next article View Article

[Updated] Instagram crashing on all Android phones, but there are workarounds

Here's the crux of the article in video form: New updates are being added at the bottom of this story……. Original story from (June 5, 2018) follows: We're...
Jul 10, 2023 6 Min Read