Google as usual released the latest December security update on the first Monday of the month, which happened to be early this week.

Unfortunately, though, the December patches haven’t hit all Google Pixel phones, with those yet to see the OTA notification already flocking to various platforms to air their grievances.

This update marked the last time owners of the original Pixel and Pixel XL will receive a software update from Google. The same update also happened to bring the much-awaited support for gesture support in third-party launchers.


For some reason, though, the original Pixels missed out on this feature, meaning those who turn to none other than the default Pixel Launcher won’t be able to enjoy the full power of Android 10 gestures on launchers like Nova, Lawnchair, and so on.

Soon after the December security update hit the Pixel range of devices earlier this week, reports started coming in saying that the Pixel Launcher had been rendered unresponsive.

After installing the update, multiple Pixel owners say the launcher repeatedly crashes on the affected devices, leaving some of them contemplating hard-resetting their devices.

So previously I installed a small custom update made by other developer for the slide down homescreen for notification panel. Now after i install the latest December updates, my pixel launcher keep on crashing. Can someone explain how to fix this problem? Thanks.

I sideloaded the December update as I usually do, and on restart the Pixel Launcher kept crashing. I can barely use the phone, as I can only do about a tap before the message reappears.

So previously I installed a small custom update made by other developer for the slide down homescreen for notification panel. Now after i install the latest December updates, my pixel launcher keep on crashing. Can someone explain how to fix this problem? Thanks.

How to fix Pixel Launcher crashing issue after December update

If you are experiencing the Pixel Launcher crashing bug on your Pixel phone after the latest December security update, there are a couple or so workarounds that have been suggested by Redditors.

These fixes have already been put into use and proven to work, but before you proceed, below are some things to take note of.

Notes to consider (Source)

With the above in mind, below are the temporary fixes you could apply to fix the Pixel Launcher crashing bug on Google Pixel phones after the latest December security update.

Via App Infos

The easiest but trickiest way to fix this issue is by uninstalling the latest Pixel Launcher updates, but achieving this feat can be an uphill task since the force stop message keeps coming again and again. If you are up for the task, follow the steps below:

1. Tap on App Info in the dialogue

2. On the right corner, click on the 3 dots icon

3. Uninstall updates

4. If it didn’t work, go to C.

Via Google Play Store

Another way to deal with this is via the Google Play Store app using the steps below:

1. Open the Play Store if you can. Else, go to C.

2. Search for Pixel Launcher

3. Uninstall. This won’t really uninstall the launcher, but revert it to an old version.

Using ADB

With the help of ADB command, you can forcefully roll back to the older Pixel Launcher version that worked well. Below is the guide you need to accomplish this mission:

1. Set up ADB on your computer using this guide (note that if “adb” returns errors, replace by “./adb”)

2. Download this APK, place it in the platform-tools folder and edit the name to “pixellauncher.apk” (actually whatever you want, avoid any special char and keep .apk).

3. Enable USB debugging in Developer Options.

4. Connect your Pixel to your computer. If a prompt talking about allowing USB debugging appears on the Pixel, say Yes.

5. Tap the notification that appeared (the one saying you’re connected to the computer). Settings will open.

6. Select Files transfer/Android Auto as Data Transfer method.

7. On your computer, open ADB, and type the following command (adb install -d -r pixellauncher.apk) without the brackets. Replace “pixellauncher” with the name you chose in step 2 above.

8. If step 7 above returns an error, replace “adb” with “./adb”

9. Hit Enter and wait for Success to appear

10. Unplug and enjoy your phone, it should be back to life

Even with these workarounds, we still expect that Google will address this issue in an official capacity, but when exactly is unknown to us. We will keep an eye on the developments and let you know if and when Google rolls out the fix.

NOTE: We have more Google-related stuff here.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Hillary Keverenge
2078 Posts

Tech has been my playground for over a decade. While the Android journey began early, it truly took flight with the revolutionary Lollipop update. Since then, it's been a parade of Android devices (with a sprinkle of iOS), culminating in a mostly happy marriage with Google's smart home ecosystem. Expect insightful articles and explorations of the ever-evolving world of Android and Google products coupled with occasional rants on the Nest smart home ecosystem.

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