Google Play Services - Run Out Of Solutions

Krixon

Limp Gawd
Joined
Mar 21, 2015
Messages
371
I tried searching for answers to this to no avail. The usual solutions popped up, but none worked.

So just today (June 14th), on my Galaxy Note 5 N920I (Android Marshmallow), a lot of my apps started to crash. Here's a list:

TypeApp
Pocket
Google Opinions
Calendar
Google
Google Play Store
Best Buy

Now, the first thing I did was to wipe the cache and data of Google Play Services, then Services Framework. After that didn't work, I did the same for all the Google Apps.

One that didn't work, I tried to wipe the cache partition, which did not solve the problem.

Then I tried uninstalling Google Play Services Updates and reinstalling via an APK. This also did not work.

I then tried removing my Google Account, which was a huge mistake. I now cannot add my Google Account or even log into the Play Store because, each time, I am hit with the error "Unfortunately, Google Play Services has Stopped".

So now I am locked out of any Google Apps and most of the apps on my phone will no longer work as Google Play Services crashes as soon as they try to load.

I now have no other solutions that I know of. Any insight would be most appreciated.

Thanks.
 
I will spike this phone onto a polished concrete floor before I factory reset again. This will be the third time in three months that I've had to do that.
 
I will spike this phone onto a polished concrete floor before I factory reset again. This will be the third time in three months that I've had to do that.

What are you doing that requires you to reset that often? That isn't normal.
 
I will spike this phone onto a polished concrete floor before I factory reset again. This will be the third time in three months that I've had to do that.

Smash the phone to bit and get an iPhone. You are doing some combination of activities that just keeps fucking it up and Android completely sucks at letting you know what actually started the problem.
 
What are you doing that requires you to reset that often? That isn't normal.

I cannot think of anything that I am doing that would cause these kinds of errors. The phone isn't rooted and the only 'customization' is Nova launcher - other than that, everything is stock.
 
I cannot think of anything that I am doing that would cause these kinds of errors. The phone isn't rooted and the only 'customization' is Nova launcher - other than that, everything is stock.

What caused the original factory resets? Same sort of issues as in the OP?
 
What caused the original factory resets? Same sort of issues as in the OP?

Similar issues, yes. All the issues revolved around Google Play failing to work in some fashion, either by crashing repeatedly or refusing to download Applications over WiFi connections.
 
Honestly, at the rate you're getting errors, I'd say it was a defective phone. I had a Note 5 from launch, for about 2 months. One day I get a few crashes, think it's odd but nothing TOO bad. Next day the phone can't recognize the 64GB of storage and the phone is a dead man walking.
 
did you ever get this figured out?

I know you dont want to hear this but i had the same issue on an older note after upgrading to the lastest OS. But in my case i flashed the phone rooted and now run a custom OS. I had way too many issues after going to marshmellow. i dont have a contract so rooting and custom os were allowed.

the play store and calender crashed alot for me. super annoying.
 
did you ever get this figured out?

I know you dont want to hear this but i had the same issue on an older note after upgrading to the lastest OS. But in my case i flashed the phone rooted and now run a custom OS. I had way too many issues after going to marshmellow. i dont have a contract so rooting and custom os were allowed.

the play store and calender crashed alot for me. super annoying.

After several calls to both Samsung and Google (both blaming the other for the problem), I was left with no other option than to do a full factory reset. Google maintained that the problem had to be hardware-based, while Samsung insisted that Android 6.0 was the culprit.

I suspect my problems started when I upgraded to 6.0. After doing the full reset, I reinstalled 6.0 and haven't had a problem since, but I doubt that I will be doing any OS upgrades on future android devices that I may or may not purchase. It's just not worth the hassle for me.
 
Back
Top