Help com.google.process.gapps has stopped...

[MotoMoto]

Every time I restart my phone I get this message:
"Unfortunately, the process com.google.process.gapps has stopped [OK]"

I tap ok and the phone works fine.

The phone came new with this problem, so it didn't start because of an app I downloaded.

Any idea what this is?

A

 

[iowabowtech]

Are you using the LG keyboard or other?

 

[MotoMoto]

Are you using the LG keyboard or other?

Im using Google's keyboard which I believe came as an option on the phone.

 

[VoidedSaint]

Im using Google's keyboard which I believe came as an option on the phone.

The LG keyboard is the option that came with the phone, the google keyboard(if you installed it) might be the cause of your problem.

 

[iowabowtech]

Yeah for whatever reason, the Google keyboard causes this. It's seemingly a non-issue other than than just being a pain. Many people (if not all) who use the Google keyboard on both the G2 and G3, and on KitKat have noted the same issue.

To verify for yourself, switch to the LG keyboard temporarily and reboot. The popup won't be there when it boots. Switch back to Google keyboard and it'll return on the next reboot.

 

[zipred]

I've experienced this same issue with my Nexus 5 out of the clear blue. In fact lots of searches across the net reveals this is related in some, not all cases, to the keyboard. There's literally a thousand or more posts in Google Groups, as well as lots of entries in various forms. If changing the keyboard fixes it consider yourself very lucky. I've tried everything I can think of and it's not fixed.

 

[iowabowtech]

I've experienced this same issue with my Nexus 5 out of the clear blue. In fact lots of searches across the net reveals this is related in some, not all cases, to the keyboard. There's literally a thousand or more posts in Google Groups, as well as lots of entries in various forms. If changing the keyboard fixes it consider yourself very lucky. I've tried everything I can think of and it's not fixed.

Guess its possible ours is a separate issue related to LG code. Have you seen cases where G2/G3 users haven't fixed this by switching to the LG keyboard?

 

[mlblack16]

Mine does this only when I use a keyboard other than the stock LG.

 

[zipred]

Guess its possible ours is a separate issue related to LG code. Have you seen cases where G2/G3 users haven't fixed this by switching to the LG keyboard?

The particular error message that appears, does so across a wide variety of makes and models. It's also known to be random. We have a very large contingent of Android enthusiasts at work. Currently there's eight of us that have multiple activated phones of the following kinds: Nexus 5, HTC M8, LG G3. Of the eight individuals with these three phones three of us are currently experiencing this phenomenon, I call it that because it is indeed so random. The only predictable solution in some, not all cases is changing the keyboard as previously mentioned.

 

[grdh20]

I get this fairly often on my V G3, but not always, using the Google Keyboard. I had this on my G2 using Swiftkey till Swiftkey updated something. Nevertheless, you'd think Google would fix this annoyance.....

 

[zipred]

I get this fairly often on my V G3, but not always, using the Google Keyboard. I had this on my G2 using Swiftkey till Swiftkey updated something. Nevertheless, you'd think Google would fix this annoyance.....

As it relates to the Google keyboard, I agree. However where third party apps are concerned I understand why Google is not responsible.

I might add that of the SIX Nexus 5's I've purchased for my family upon it's release, only mine has displayed the condition and only just recently.

Would I prefer not to experience this? Yes, but considering it's the only problem I've had, I'd say that's a great track record.

In fact quite candidly I just took delivery of another new Nexus 5 from Google. Being one of my favorites that's going to be replaced by the Nexus 6, I happily bought this as a spare. That's how much I enjoy it.

 

[KOLIO]

As it relates to the Google keyboard, I agree. However where third party apps are concerned I understand why Google is not responsible.

Would I prefer not to experience this? Yes, but considering it's the only problem I've had, I'd say that's a great track record.

It's a minor nuisance at most,I agree with you there.Especially if you look back a couple years ago & depending on your phone/carrier choices,this pales in comparison.

FWIW,it's happening on my OPPO FIND7 w/CM11 (4.4.4) & SWIFTKEY on-board.
However it was not happening on my 1+1,ROOTED/STOCK CM11S (4.4.4) & SWIFTKEY on-board.

Who knows what's the cause,& if a fix will ever come about,as GOOGLE has their eyes set on ANDROID L.

 

[zipred]

It's a minor nuisance at most,I agree with you there.Especially if you look back a couple years ago & depending on your phone/carrier choices,this pales in comparison.

FWIW,it's happening on my OPPO FIND7 w/CM11 (4.4.4) & SWIFTKEY on-board.
However it was not happening on my 1+1,ROOTED/STOCK CM11S (4.4.4) & SWIFTKEY on-board.

Who knows what's the cause,& if a fix will ever come about,as GOOGLE has their eyes set on ANDROID L.

This is simply too coincidental, no sooner did I author my post, when one of my fellow engineers approached me with this same issue just having occurred on his OPPO Find 7, with SwiftKey!

Good friends, we ordered our Find 7's concurrently and thus far performance has been exemplary. I'm running SWYPE on mine, although I also have SwiftKey installed. I enjoy using SwiftKey once in a while just to keep up my dexterity and familiarity with it in case new features are introduced that surpass those of SWYPE.