The best way to stay connected to the Android pulse everywhere. Our new app contains all the top Android news, reviews, app & games and the best deals just for you. Now with Disqus profile integration.

Android Authority newsletter

The best way to stay connected to the Android pulse. Our main newsletter is the Android Weekly which is sent every Sunday and contains all the top Android news, reviews and features from the past week.

100% Privacy, No Spam Policy: We value privacy and your email address will be 100% secure. We hate spam just like you do and will never send you too much email, nor will we ever share your information with anyone.

Buy now!

Name:

Subject:

Message:

Some Nexus 4 users running into issues after installing KitKat

Last week the Android 4.4 KitKat OTA update finally started rolling out to Nexus 4 users, after a fairly long wait. Now that the update has arrived, it seems that some unfortunate Nexus 4 owners are reportedly experiencing issues including problems with the lockscreen, a broken dialer, a non-working home button, quick setting issues and more.

Not all of these issues are necessarily experienced all at once, with some folks reporting just one issue and others being plagued by several problems. Those that have ran into issues seem to have one thing in common — they used the OTA upgrade to go from Jelly Bean JWR66Y over to KRT16S.

It’s important to note that these errors are only affecting some users, and its unclear just how widespread of an issue this is.

So what’s the fix here? While Google has yet to chime in, there are a couple suggested fixes. First, you can always perform a factory reset and hope things go better second time around. Of course this also wipes any apps or files your have stored on your handset.

Luckily there’s also a second solution for those that don’t want to mess around with backups and factory resets: you can use ADB to run the setup wizard again, which is said to fix several of the above-mentioned problems. Within ADB, you’ll need to send the command: ‘adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity‘ .

For those that have yet to upgrade, should you avoid the OTA? Honestly that’s up to you.

If you don’t mind troubleshooting in the (hopefully rare) event that something goes wrong, than go right ahead and grab the update as soon as it becomes available. If you’d rather not have to worry about dealing with any potential bugs or other upgrade issues, you might be better off waiting a bit longer until Google releases some kind of fix.

Once again it’s important to note that these errors are only affecting some users, and its unclear just how widespread of an issue this is. We’ve reached out to Google for comment and will update if and when we hear back.

Have you ran into any of the above issues with your Nexus 4 KitKat update? Any other tips or tricks on how to solve the problem? Let us know in the comments!

Andrew is one of the three Managing Editors of Android Authority, primarily responsible for the overseeing of US team of writers, in addition to several other projects such as VR Source and more. He loves tech, gaming, his family, and good conversations with like-minded folks.