For the past 3 days, periodically throughout the day, I get a notice the Google Services Framework is unresposive and must force close. My question is...
1. Is it something important I should be worried about?
2. Is anyone else getting this?
3. Is there a specific app causing this?
3a. If not, I there a known cause?
4. Is there a fix?
Btw, I am using a nonrooted Epic. I did search. And all help is greatly appreciated.
Sent from my non-rooted Epic 4G using the free XDA App
I had this problem after dropping my phone and having the battery pop out while running.
I went into Settings / Applications / Manage Applications / All, then I found Google Services Framework, opened it and clicked "Clear Data", and that seemed to fix it (note, it took 2 days for the Android Market to show anything under "My Apps")
Note, I'm rooted on Bonsai 4.1.3. This "google services framework" FC occurred even after restoring from a prior CWM backup oddly enough which is why I decided to try clearing the data in Applications.
Good luck, hopefully you have a backup in case my idea blows up your house.
I have been getting random vibrate, pause then three more vibrates like something is force closing but nothing shows on screen. I also have had maps force close several times. I am on eg22 rooted.
Sent from my SPH-D700 using XDA Premium App
I have gotten this force close a few times and wiping everything 3x and restoring a nandroid didn't work for me 9 times out of 10. I ended up having to use Odin to get rid of it. Hopefully just wiping the data works for you otherwise Odin may be the only way to get it fixed. So, try wiping cache and Dalvik 3x first. If that doesn't work, try wiping everything 3x and restoring a backup. If that doesn't work, try re-flashing the ROM and finally the last resort is Odin
Sent from my SPH-D700 using XDA Premium App
I am not using any roms, nor is my phone flashed with anything. Its stock EC05. It appears to have rectified itself but I'd still like to know what's happening to prevent it again.
Someone I know had this same exact problem a few days ago. Wiping the data for Google Services Framework fixed it.
This happened to me a few weeks ago. Clearing data is the best fix for some, for me however it just made my launcher loop-crash. If clearing data fails, go into cwm and 'fix permissions'. This got me back on my feet
Sent from my Syndicated Epic using XDA Premium App
Happened to me last night and Odin was my only fix. Tried fixing permissions, clearing data, neither worked for me. Issues still remained after a nandroid restore
Sent from my SPH-D700 using XDA Premium App
MY phone tends to overheat when on calls outside at lunch and 20% of the time this is the result when I reboot. And sometimes the fix permissions works and sometimes it doesnt. If it doesn't I was reodin'ing to fix it.. Sucks for when you are not around a computer when this happens.. My fix to a computer free solution was to keep a copy of the ec05 reRFS.zip on my sd card. I can hop over to clockwork and flash this and it will at least take me back to a stock rooted and working phone until I can get back to a computer or whatever....
I have also experienced this annoying issue and my only fix was odining as wel
So rooting my phone is the only fix if clearing the data fails?
Sent from my non-rooted Epic 4G using the free XDA App
No you don't have to root. Just odin the ec05 tar. You will lose all of your data because it basically reinstalls the os it's like starting over. If you do root you can use titanium backup and that will save all of your apps and data.
My epic does this on every custom rom. So I went back to stock no more problems.
Sent from my SPH-D700 using XDA App
Elite11b said:
No you don't have to root. Just odin the ec05 tar. You will lose all of your data because it basically reinstalls the os it's like starting over. If you do root you can use titanium backup and that will save all of your apps and data.
Click to expand...
Click to collapse
Well... I don't want to loose everything. So far it hasn't stopped functionality. I dunno if this helps but 3rd party apps running are...
Trillian
Lookout
Skype
Go Launcher EX
Go Launcher EX Notification
Google Music
Google+
Blogger
P.S. - as typing this I noticed the crash happens during background syncing
Sent from my non-rooted Epic 4G using the free XDA App
Ok I think I found it. I turn off auto sync and it fine and now it looks like facebook sync is what is crashing. Thanks for all your help..
Sent from my non-rooted Epic 4G using the free XDA App
Hi all,
EDIT2: MAIN PROBLEM FIXED!
I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.
I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.
Lo and behold, I rebooted three times now and NO KNOCK LOOP!
I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.
As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?
EDIT: Not Greenify causing this, but some other combo of rooting and system file changes. Could also be the proximity sensor misbehaving or just a bad copy of the phone.
Just a friendly PSA, but Greenify (the popular hibernation app that is really awesome) will gimp your knock-on feature for good. As in: returning to stock does not fix it. Myself and at least one other user have had this problem. I'm now having to swap out my phone after just getting it how I like it, which is infuriating.
I'd rather wait until somebody gets a fix up, but I'm within 14-days so I'm not risking it.
Note: This is CLEARLY not the fault of Greenify. It's some bizarre file system/sensor error. Greenify is great.
Related thread where the problem was thought to be fixed... but is not for people who installed Greenify.
I'm using the Verizon variant, so I don't know if this applies to GSM models.
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
I've been using greenify since the day after I got the phone and rooted it, so 2 weeks now, and knock on works perfectly every single time.
Sent from my VS980 4G using Tapatalk 4
---------- Post added at 12:14 PM ---------- Previous post was at 12:14 PM ----------
and I'm on the Verizon version. what app are you guys hibernating that's causing this?
Sent from my VS980 4G using Tapatalk 4
burningembers said:
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
Click to expand...
Click to collapse
I'd have to agree with this!!
Sent from my GT-N7100 using xda app-developers app
Knock on seems to work on mine (most of the time anyway) while using Greenify for a couple of weeks now. If it was going to gimp it, I'm thinking it would have by now. I have the T-Mobile variant. Its basically just hibernating apps from the market, not any system apps so I guess I don't see the correlation.
Greenify works for me
I'm stock rooted and I heavily use Greenify with my Verizon G2. No problems with Knock On at all!
Edit: Stock rooted (not the chinese way), no OTA, auto-hibernation feature works perfectly too.
um question... did you guys who have the problem use the Chinese root method? someone brought it up and now I'm curious....
i did but then flashed back to stock to reroot the good way. you guys who aren't having the issue with me, you use Chinese or regular?
Sent from my VS980 4G using Tapatalk 4
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Sent from my VS980 4G using XDA Premium 4 mobile app
lattiboy said:
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Click to expand...
Click to collapse
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
burningembers said:
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
Click to expand...
Click to collapse
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
You should really rename this thread. I have not experienced any knock issues and I've installed this app since I bought the phone. False psa
---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------
lattiboy said:
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
Click to expand...
Click to collapse
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
SysAdmNj said:
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
Click to expand...
Click to collapse
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?
The issue might be caused by misuse of Greenify. Have you greenified any system apps related to the Knock-on feature?
Greenify should never "damage" your device in a non-recoverable way since it never touches any system files. Just simply de-greenify the app and manually relaunch it once to restore everything to normal.
Hope one of you G2 users could find out that key greenified app which caused this terrible issue, thus we could warn others in a more effective way.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
burningembers said:
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
Click to expand...
Click to collapse
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
lattiboy said:
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
Click to expand...
Click to collapse
So flashing back to pre-OTA doesn't clear the problem at all?
burningembers said:
So flashing back to pre-OTA doesn't clear the problem at all?
Click to expand...
Click to collapse
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
lattiboy said:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
Click to expand...
Click to collapse
What's your Baseband and Kernel version in Software Information?
I know for a *fact* that the OTA changed the cpu scheduler. What I'm curious is if their scheduler changes have somehow caused service-level applications like the KnockOn APK to die/hibernate during a lengthy deep sleep. This makes way more sense to me than merely using Greenify causing a permanent breaking of software/kernel interactions.
burningembers said:
What's your Baseband and Kernel version in Software Information?.
Click to expand...
Click to collapse
This is it. No root, fresh stock 15 minutes ago.
Strange problem. My phone freezes on me every 35-40 hours of power on. I need to remove battery and restart the phone for it to work. I could be just be in the app drawer or playing a graphic intensive game the phone would just freeze.
I don't know why this would happen to an otherwise wonderful phone. Snappy fast and great battery otherwise.
I've done the official Sammy firmware upgrade OTA and the phone is stock unrooted
Any clues?
Sent from my SM-N900 using xda app-developers app
shubhm_22 said:
Strange problem. My phone freezes on me every 35-40 hours of power on. I need to remove battery and restart the phone for it to work. I could be just be in the app drawer or playing a graphic intensive game the phone would just freeze.
I don't know why this would happen to an otherwise wonderful phone. Snappy fast and great battery otherwise.
I've done the official Sammy firmware upgrade OTA and the phone is stock unrooted
Any clues?
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
You could try a factory reset
Thanks. Is there a way to backup my apps and app status without rooting and titanium backup. I don't wanna root while its new.
Sent from my SM-N900 using xda app-developers app
shubhm_22 said:
Thanks. Is there a way to backup my apps and app status without rooting and titanium backup. I don't wanna root while its new.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Use Helium, It's an app by Clockwork Mod, It does the same as Titanium backup but doesn't require root
I'm having the same problem it will freeze home button or power button doesn't have to take battery out its a bit annoying!
shubhm_22 said:
Strange problem. My phone freezes on me every 35-40 hours of power on. I need to remove battery and restart the phone for it to work. I could be just be in the app drawer or playing a graphic intensive game the phone would just freeze.
I don't know why this would happen to an otherwise wonderful phone. Snappy fast and great battery otherwise.
I've done the official Sammy firmware upgrade OTA and the phone is stock unrooted
Any clues?
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Try to use without ext sd card if there is any & observe.
Hey guys, I just wanted to share my experience with my SM-N9005 that's a week old today.
When I first unboxed it, it slipped in my sim card and 64GB sdcard and turned the phone on.
During the second or third screen of the wizard, the phone froze and rebooted.
After that, I went through the wizard again with no problems and finally to the homescreen.
I noticed on the status bar that the Play Store is failing to install / recover a whole host of apps and during that, I received that "Prevention Information" nonsense, the phone froze and rebooted after I tapped to see if I can find this app but all it showed me one was app, which was the Play Store services. I assume, maybe the apps failed because the services and Play Store wanted to update.
Well after all of that, there are times when the "Prevention Information" comes up, the phone won't freeze and soft restart (Just show the Samsung logo and come back to the homescreen with one or two vibrations) right away but eventually. There have been instances, where for example, I would be in the BBM for Android app or WhatsApp when this happens and return with no chat history but that happened once or twice, I think there was another instance that I lost information but that might not necesserily be an emmc issue but due to a sudden reboot or freeze without being able to save properly.
I also get a notification toast that I am running low on memory when I have plenty of memory left. (I would start seeing this around and after 10GBs have been used)
Things I have tried:
Factory Reset from the menu option.
Factory Reset from Recovery.
PC ODIN to the very first .tar ROM with corresponding CSC (XME) for my handset.
Removed the sdcard to see if it was that.
Nothing worked but the problems aren't as frequent.
I can't play games for too long because it will soft reboot. The phone does get warm quickly, which is a concern.
I think that's about it, I do love the phone but if this continues and this is a Samsung bug, I might just hold off from sending it back and buy a Nexus 5.
Samsung has been having too many issues with their handsets like faulty emmc chips, sudden bricked phones, multi-touch screen issues, etc.
This will be my last Samsung device either way but I am hoping that there's a fix because if I send it back, that's that.
I'm thinking of returning mine and sticking with the s4 to much hassle I've factory reset my device and left out my 64gb we card and see where it goes from here.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I'm thinking of returning mine and sticking with the s4 to much hassle I've factory reset my device and left out my 64gb we card and see where it goes from here. I'm starting not to enjoy it and it feels like a hassle
just got my S5 last week..and since ive had it i have to do constant battery pulls..
for some reason either it locks up OR the screen simply goes black and the only way to get it back up and running is to do a battery pull.
any idea as to why this would happen and/or a possible fix?
t.i.a :good:
I haven't had any problems with mine except i had the camera fail, then replaced with new phone, but since no problems. But I have most if not all bloat frozen, and anything else that I don't need I have disabled that too.
I'm going to knock on wood as I write this, and say I haven't had any issues with mine.
kilroy1stcav said:
I haven't had any problems with mine except i had the camera fail, then replaced with new phone, but since no problems. But I have most if not all bloat frozen, and anything else that I don't need I have disabled that too.
Click to expand...
Click to collapse
howd u freeze all the bloated apps?
i thought we didnt have the capabilities since we're on vzw
SoCalSpecialist said:
howd u freeze all the bloated apps?
i thought we didnt have the capabilities since we're on vzw
Click to expand...
Click to collapse
You can force stop APS, settings> applications>application manager. Scroll to the right to all. Select on one and stop it.
Also, I think it's all the bkoatware and 4.4 bugs in general. My 4.2/4.3 S4 never had These issues rooted on aosp ROMs, let alone brand new stock
Sent from my SM-G900V using XDA Free mobile app
You can disable them also so that they don't start. And as you can see from these screen shots they are disabled/turned off. These are the ones that I have disabled:
thank you both..i just frooze a ton of apps!
lets see how this plays out.