• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Google Play Services not Working :(

On a lighter note, I have customized my lockscreen and home page with Google's new clock, that much they got right, looks kind of nice I think.
Screenshot_2015-09-22-21-55-22.png
 
cameras, launchers are sometimes notorious for causing issues, try going stock for above if you can and see how stable it runs
 
Lpen21 said:
Hmm, something else must be causing a conflict. Is it trigerring errors just when you refresh play store?
Click to expand...
It throws errors when just about anything happens on the phone. When i go to tap a text field, when an icon pops up, when i switch apps, navigate setting. The more i do the less it crashes but after restarting the phone it crahses like crazy for a while.

Right now all ive done to it was root it, no cameras or launcher, etc. I did the factory reset and I cant find a stock rom or similar to try restoring it entirely.
 
Sythus5 said:
So, after all this deflecting, I'm left with the only remaining option, to contact Google support. From there, I'm expecting to hear that I must contact Kyocera. This big whole circle of deflection is going to get me nowhere, and I'll be left with a malfunctioning phone and three companies that will take no responsibility for it. I see class action lawsuit impending.
Click to expand...

jplee3 said:
This is super-annoying and is a major bug for Kyocera users. I bet you they're having meetings about this now and saying "well, the customer base for this bug is pretty slim so it's a corner case and not high priority blah blah blah" - I only know [and would assume] this because I'm in QA :)
Click to expand...

It's not Kyocera nor Virgin Mobile's fault, at least at this stage. They made sure everything worked at a certain point in time when the phone passed through their hands. Maybe Kyocera's Android implementation/design wasn't ideal and triggered this, whereas other phones don't see it. But the biggest guilty party here (worthy of lawsuit threats) is Google, who have pushed out buggy code to live customers devices with no easy way to roll back or prevent auto-update. Google has so much cash and expanding/hiring like crazy, the quality of their products is suffering. They're moving too fast without the right checks in place to prevent something like this.

Lollipop had its higher share of bugs after release is another example of this. I'm personally not in a hurry to get the latest products from Google if I can help it, but Play Services is one of the few apks that are shoved down EVERY Android device on a too frequent schedule.
 
Okamisolaris said:
I have done a couple so far as well as going through the usual with clearing cache and other steps ive come across. Trying to log in again it isnt just the play services crashing. com.google.process.gapps is also crashing when attempting to log in. Before the factory reset things wouldnt work well with play crashing less frequently but after the reset it seems even less stable now. Ive tried what I can with no success though I did find a lot of crash logs. I cant quite make out heads or tails of them. Ill include one though if someone here can.

Put them on pastebin to keep the page cleaner since these are pretty long.

Not sure what this first one is, decided to include it.

system_app_anr@1442888164201:
http://pastebin.com/2L1UVFyC

And this one is one of many crash logs.

system_app_crash@1442886405334:
http://pastebin.com/AKPKghdM

Edit: A lot of the crash logs seem to mention other things. I can include those if its needed.
Click to expand...

Confirmed this does not work... The simplest way to test this is open Play Music with the latest update and watch it crash...
 
I think I figured out something. If you go in to developer settings then select runtime mode and Change Dalvik to ART I think this might fix the problem... Sadly Every time I change it, it goes back to Dalvik....

*My art won't stick because of exposed installer :/
I guess this does not work either :/
 
Last edited:
I tried this and did not work for changing google app crashes? Are you saying this fixed it for you? Ie all apps worjed?
 
Blackb0x said:
I think I figured out something. If you go in to developer settings then select runtime mode and Change Dalvik to ART I think this might fix the problem... Sadly Every time I change it, it goes back to Dalvik....
Click to expand...
This did not work for me, still crashed, tried 2 times with music. I may try other apps and see, but failed so far
 
Lpen21 said:
This did not work for me, still crashed, tried 2 times with music. I may try other apps and see, but failed so far
Click to expand...
Thanks for checking spending most the morning trying to disable Xposed Framework so i can get ART again... Ugh. Sorry it didn't work. Was worth a try...
 
Okamisolaris said:
It throws errors when just about anything happens on the phone. When i go to tap a text field, when an icon pops up, when i switch apps, navigate setting. The more i do the less it crashes but after restarting the phone it crahses like crazy for a while.

Right now all ive done to it was root it, no cameras or launcher, etc. I did the factory reset and I cant find a stock rom or similar to try restoring it entirely.
Click to expand...
Did you remove any system apps after rooting?
 
Tried it, no change sadly. I know for sure the other things I uninstalled were bloat that VM added in. Looking at the mountain of crash logs that are being made as a result it seems there may be other issues happening but while I can read the crashlog I dont know enough about Android to be able to understand what it all means.
 
Okamisolaris said:
Tried it, no change sadly. I know for sure the other things I uninstalled were bloat that VM added in. Looking at the mountain of crash logs that are being made as a result it seems there may be other issues happening but while I can read the crashlog I dont know enough about Android to be able to understand what it all means.
Click to expand...
Ok, or you have another app that s now not playing nice with play services. You coud try removing one by one to see which one may be at odds, possibly one that requires location services
 
Weather and maps are the only two i could think of that would be using.

I turned off location and now play store gives the same error every time instead of every now and then. I hit refresh, gapps crashes and it says "Authentication is required. You need to sign into your google account" which I am but im going to, against better judgement, try readding it.
 
For what it's worth. I did a reset and reinstalled everything. That didn't work, so I rolled everything back to previous versions of anything google. Then updated google play services. Everything still worked with the older versions of google apps. Updated gmail and the minute I started gmail, it would crash. Rolled that back again and still the older version worked. All the new versions of Gmail, google pay, wallet, play music, play movies, couple of others I forget. Everything else works.
 
Okamisolaris Turning on location services will be apain, you may have to uninstall updates to play services then turn on location and update services again, otherwise you may be locked out
 
Im still combing through the logs since I moved them to my desktop finally. It looks like gapss is crashing from three different apps because it cant get permissions it needs. I moved both play store and play services to the system apps but it still throws up the same errors.

Process: com.google.process.gapps
Flags: 0x40c8be45
Package: com.google.android.syncadapters.contacts v19 (4.4.2-1289630)
Package: com.google.android.gms v7895034 (7.8.95 (2113048-034))
Package: com.google.android.gsf.login v19 (4.4.2-1289630)
Build: kyocera/C6725/C6725:4.4.2/KVT49L/2.033SP.02.a:user/release-keys
Date(LocalTime): Wed Sep 23 21:37:59 EDT 2015
Date(UTCTime): Thu Sep 24 01:37:59 GMT+00:00 2015

java.lang.RuntimeException: Unable to create service com.google.android.gms.auth.GetToken: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2586)
at android.app.ActivityThread.access$1800(ActivityThread.java:139)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1282)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5057)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.LoadedApk.makeApplication(LoadedApk.java:529)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2572)
... 10 more
Caused by: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.ContextImpl.enforce(ContextImpl.java:1712)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1741)
at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:572)
at com.google.android.gsf.f.c(SourceFile:107)
at com.google.android.gsf.f.a(SourceFile:121)
at com.google.android.gsf.f.a(SourceFile:227)
at com.google.android.gms.common.b.m.a(SourceFile:304)
at com.google.android.gms.common.b.f.a(SourceFile:222)
at com.google.android.gms.common.b.e.c(SourceFile:200)
at com.google.android.gms.common.app.GmsApplication.onCreate(SourceFile:92)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
at android.app.LoadedApk.makeApplication(LoadedApk.java:526)
... 11 more
 
Okamisolaris said:
Im still combing through the logs since I moved them to my desktop finally. It looks like gapss is crashing from three different apps because it cant get permissions it needs. I moved both play store and play services to the system apps but it still throws up the same errors.

Process: com.google.process.gapps
Flags: 0x40c8be45
Package: com.google.android.syncadapters.contacts v19 (4.4.2-1289630)
Package: com.google.android.gms v7895034 (7.8.95 (2113048-034))
Package: com.google.android.gsf.login v19 (4.4.2-1289630)
Build: kyocera/C6725/C6725:4.4.2/KVT49L/2.033SP.02.a:user/release-keys
Date(LocalTime): Wed Sep 23 21:37:59 EDT 2015
Date(UTCTime): Thu Sep 24 01:37:59 GMT+00:00 2015

java.lang.RuntimeException: Unable to create service com.google.android.gms.auth.GetToken: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2586)
at android.app.ActivityThread.access$1800(ActivityThread.java:139)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1282)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5057)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.RuntimeException: Unable to create application com.google.android.gms.common.app.GmsApplication: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.LoadedApk.makeApplication(LoadedApk.java:529)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2572)
... 10 more
Caused by: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10005 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
at android.app.ContextImpl.enforce(ContextImpl.java:1712)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1741)
at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:572)
at com.google.android.gsf.f.c(SourceFile:107)
at com.google.android.gsf.f.a(SourceFile:121)
at com.google.android.gsf.f.a(SourceFile:227)
at com.google.android.gms.common.b.m.a(SourceFile:304)
at com.google.android.gms.common.b.f.a(SourceFile:222)
at com.google.android.gms.common.b.e.c(SourceFile:200)
at com.google.android.gms.common.app.GmsApplication.onCreate(SourceFile:92)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
at android.app.LoadedApk.makeApplication(LoadedApk.java:526)
... 11 more
Click to expand...
good work! We need people to look deeper into this!
 
I'm relieved to find this thread. I own a Kyocera Hydro Vibe from Virgin Mobile with the same problem as everyone else.

Fruitlessly, VM walked me through updating, clearing, and restoring everything imaginable including a master reset. They even sent me a replacement phone, but the problem persisted. Before understanding the problem I spent over three hours across several days with six advisors from VM before I was finally told "it is a software issue that has been escalated to find a fix." I hope that's true. Actually, I initially thought the replacement phone was problem free, but that's when it was running on the older Android operating system. As soon as I updated to Kit Kat, the problem started just like on my original phone.

Before understanding the problem was not unique to me, I spent over three hours across several days with six advisors from VM before I was finally told "it is a software issue that has been escalated to find a fix." I hope that's true.

I get by for now by uninstalling the updates to the problematic apps and by preventing them from auto-updating.

Like others, I cannot open Google location services without it crashing, and like another user mentioned, I also had Google Play Games update itself despite that feature being turned off.

I appreciate knowing I'm not alone, and I only hope an update is made available soon to fix all this.

I'm not technologically savvy like others on this thread, do many of the ideas talked about here aren't easy for me to understand or implement.
 
You must log in or register to reply here.
Back
Top Bottom