"com.android.keyguard has stopped"

[FrancisS]

This issue is addressed in other threads here, but I cannot figure out how to use them. I have a Tracfone LG L41C. I hope some of the following is helpful: Android version 4.4.2, Baseband version M8610B-AAAANAZM-1.0.6048, Kernel version 3.4.0+, Build number KOT491.L41CV10a, Software version L41CV10a The message "unfortunately com.android.keyguard has stopped" appears from time to time when I turn on the phone. Initially I am unable to do anything. After a few minutes, I am able to turn the phone off (Power Off). Then, when I turn the phone back on, the message is not there, and the phone works fine. But the message will reappear a day or so later when turning the phone on. Its recurrence is unpredictable. I will REALLY appreciate any help! Thank you. Francis

 

[Phalon4]

This issue is addressed in other threads here, but I cannot figure out how to use them. I have a Tracfone LG L41C. I hope some of the following is helpful: Android version 4.4.2, Baseband version M8610B-AAAANAZM-1.0.6048, Kernel version 3.4.0+, Build number KOT491.L41CV10a, Software version L41CV10a The message "unfortunately com.android.keyguard has stopped" appears from time to time when I turn on the phone. Initially I am unable to do anything. After a few minutes, I am able to turn the phone off (Power Off). Then, when I turn the phone back on, the message is not there, and the phone works fine. But the message will reappear a day or so later when turning the phone on. Its recurrence is unpredictable. I will REALLY appreciate any help! Thank you. Francis

Go into your SETTINGS and locate that keyboard app and try clearing out your cache, also any message apps and see if that fixes it because from time to time it gets full and it will cause an app to display unfortunately xxxx app has stopped. Then power cycle your device.

 

[FrancisS]

Go into your SETTINGS and locate that keyboard app and try clearing out your cache, also any message apps and see if that fixes it because from time to time it gets full and it will cause an app to display unfortunately xxxx app has stopped. Then power cycle your device.

At Apps>>All, I found “com.android.keyguard” and “LG Keyboard”; I clicked “Clear Cache” at each of those. There are three LG Keyboard Themes: Black, Lovely, and Natural. At each, the cache is 0.00 B, so I did nothing there. There is also “Language and Input”, where Default is “LG Keyboard”; there is no “Cache” indicated, so I did nothing there. At “Messaging” I clicked “Clear Cache”. There is also “Phone/Messaging Storage”; here the cache is 0.00 B, so again I did nothing. Then I Powered Off and restarted the phone. Everything worked.

I powered off and on several times (at least five minutes between), and it was fine. Then, after it had been off for a longer while, I powered on again, and again got the "unfortunately com.android.keyguard has stopped".

I noticed that a lot of the other Apps in the list at Apps>>All have some cache showing, and offer the option to “Clear Cache”. Is there any reason I should not clear the cache on each of them? Might it help?

THANK YOU for your help and for being so clear in your instruction! I am extremely grateful.

 

[FrancisS]

Update: I had not originally focused on this carefully. Here is the sequence: When I turn the phone on, if it opens properly, I simply swipe the screen, and the "home page" opens properly. The "unfortunately ..." message arises on certain occasions when the opening screen displays "service disabled" and/or "no service". If I swipe it with either or both of those displayed is, I am pretty sure, when the "unfortunately ..." message appears. However, if I wait a few minutes, the "no service" and/or "service disabled" messages disappear on their own (that is, without my doing anything); if I swipe the screen then, the phone functions properly. I apologize for not having mentioned this earlier, but I hadn't properly observed the sequence until now.

 

[FrancisS]

This morning, I went to Settings>>Storage>>Clear Cached Data, and clicked on "OK". Since then, I have turned the phone off and on several times, and so far, no appearance of the "unfortunately ..." notice. And the phone works.